Agreed. Awesome news. I don't have a whole lot of time, and no programming experience since like freshman year, but if I can help with something let me know--sniffing or testing or whatever. On Feb 11, 2015 9:42 PM, "Stef" <stef....@free.fr> wrote:
> On 09/02/2015 12:04, Rafe DiDomenico wrote: > >> Hi all, >> >> So I sort of messed up and picked up this scanner. Now I#m debating >> whether to return it or not. If there's hope for support in the (not so >> distant) future, I'll hold off and wait. I'm just touching base to see what >> sort of prospects there are since this model isn't even listed as >> "unsupported" on the website. >> >> Anyway, if anyone needs any info on it this was SANE gave me: >> >> <device descriptor of 0x04a9/0x190f at 002:002 (Canon CanoScan)> >> bLength 18 >> bDescriptorType 1 >> bcdUSB 2.00 >> bDeviceClass 255 >> bDeviceSubClass 255 >> bDeviceProtocol 255 >> bMaxPacketSize0 64 >> idVendor 0x04A9 >> idProduct 0x190F >> bcdDevice 7.04 >> iManufacturer 1 (Canon) >> iProduct 2 (CanoScan) >> iSerialNumber 0 () >> bNumConfigurations 1 >> <configuration 0> >> bLength 9 >> bDescriptorType 2 >> wTotalLength 39 >> bNumInterfaces 1 >> bConfigurationValue 1 >> iConfiguration 0 () >> bmAttributes 160 (Remote Wakeup) >> MaxPower 500 mA >> <interface 0> >> <altsetting 0> >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber 0 >> bAlternateSetting 0 >> bNumEndpoints 3 >> bInterfaceClass 255 >> bInterfaceSubClass 255 >> bInterfaceProtocol 255 >> iInterface 0 () >> <endpoint 0> >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x81 (in 0x01) >> bmAttributes 2 (bulk) >> wMaxPacketSize 512 >> bInterval 0 ms >> bRefresh 0 >> bSynchAddress 0 >> <endpoint 1> >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x02 (out 0x02) >> bmAttributes 2 (bulk) >> wMaxPacketSize 512 >> bInterval 0 ms >> bRefresh 0 >> bSynchAddress 0 >> <endpoint 2> >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x83 (in 0x03) >> bmAttributes 3 (interrupt) >> wMaxPacketSize 1 >> bInterval 8 ms >> bRefresh 0 >> bSynchAddress 0 >> >> <trying to find out which USB chip is used> >> checking for GT-6801 ... >> this is not a GT-6801 (bcdUSB = 0x200) >> checking for GT-6816 ... >> this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255) >> checking for GLxxx ... >> this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255) >> <This USB chip looks like a GL848+ (result from sane-backends 1.0.24)> >> >> found USB scanner (vendor=0x04a9 [Canon], product=0x190f [CanoScan], >> chip=GL848+) at libusb:002:002 >> >> >> Hello, > > I have just received a Canon LiDE 220 donated by Dany Qumsiyeh. Many > thanks to him. Now I'm able to start working on this scanner. > > First tests show that this model operates like previous LiDE 2[01]0 > models, on an undocumented (maybe gl127) ASIC. > > Since I now only have Windows 7 machines, I can't use usnsniff, and > must adapt my decoding scripts to wireshark USB recording. > > I am going to build some sample tests programs based on log sniffing, > without public datasheet this will be surely more complicated and longer > than working with previous genesys ASIC. Once simple operations worked out, > I'll turned it into a backend. > > This is going to take quite some time. > > Regards, > Stef >
-- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
