+ Canon Imagerunner iR1018/1022/1023 +
++ USB +
++ 0x04a9 +
++ 0x269d +
++
++
++<device descriptor of 0x04a9/0x269d at 002:002 (Canon,Inc. iR1018/1022/1023)> +bLength 18 +bDescriptorType 1 +bcdUSB 2.00 +bDeviceClass 0 +bDeviceSubClass 0 +bDeviceProtocol 0 +bMaxPacketSize0 64 +idVendor 0x04A9 +idProduct 0x269D +bcdDevice 0.00 +iManufacturer 1 (Canon,Inc.) +iProduct 2 (iR1018/1022/1023) +iSerialNumber 3 (156BFFGn0016) +bNumConfigurations 1 + <configuration 0> + bLength 9 + bDescriptorType 2 + wTotalLength 62 + bNumInterfaces 2 + bConfigurationValue 2 + iConfiguration 0 () + bmAttributes 192 (Self-powered) + MaxPower 2 mA + <interface 0> + <altsetting 0> + bLength 9 + bDescriptorType 4 + bInterfaceNumber 0 + bAlternateSetting 0 + bNumEndpoints 3 + bInterfaceClass 255 + bInterfaceSubClass 0 + bInterfaceProtocol 255 + iInterface 0 () + <endpoint 0> + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x03 (out 0x03) + bmAttributes 2 (bulk) + wMaxPacketSize 64 + bInterval 0 ms + bRefresh 0 + bSynchAddress 0 + <endpoint 1> + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x84 (in 0x04) + bmAttributes 2 (bulk) + wMaxPacketSize 64 + bInterval 0 ms + bRefresh 0 + bSynchAddress 0 + <endpoint 2> + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x85 (in 0x05) + bmAttributes 3 (interrupt) + wMaxPacketSize 64 + bInterval 200 ms + bRefresh 0 + bSynchAddress 0 + <interface 1> + <altsetting 0> + bLength 9 + bDescriptorType 4 + bInterfaceNumber 1 + bAlternateSetting 0 + bNumEndpoints 2 + bInterfaceClass 7 + bInterfaceSubClass 1 + bInterfaceProtocol 2 + iInterface 0 () + <endpoint 0> + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x06 (out 0x06) + bmAttributes 2 (bulk) + wMaxPacketSize 64 + bInterval 0 ms + bRefresh 0 + bSynchAddress 0 + <endpoint 1> + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x89 (in 0x09) + bmAttributes 2 (bulk) + wMaxPacketSize 64 + bInterval 0 ms + bRefresh 0 + bSynchAddress 0 + +<trying to find out which USB chip is used> + checking for GT-6801 ... + this is not a GT-6801 (bDeviceClass = 0) + checking for GT-6816 ... + this is not a GT-6816 (bcdUSB = 0x200) + checking for GT-8911 ... + this is not a GT-8911 (check 2, bcdUSB = 0x200) + checking for MA-1017 ... + this is not a MA-1017 (bDeviceClass = 0, bInterfaceClass = 255) + checking for MA-1015 ... + this is not a MA-1015 (bDeviceClass = 0) + checking for MA-1509 ... + this is not a MA-1509 (bDeviceClass = 0) + checking for LM983[1,2,3] ... + this is not a LM983x (bcdUSB = 0x200) + checking for GL646 ... + this is not a GL646 (bDeviceClass = 0, bInterfaceClass = 255) + checking for GL646_HP ... + this is not a GL646_HP (bDeviceClass = 0, bInterfaceClass = 255) + checking for GL660+GL646 ... + this is not a GL660+GL646 (bDeviceClass = 0, bInterfaceClass = 255) + checking for GL841 ... + this is not a GL841 (bDeviceClass = 0, bInterfaceClass = 255) + checking for ICM532B ... + this is not a ICM532B (check 1, bDeviceClass = 0, bInterfaceClass = 255) +<Couldn't determine the type of the USB chip> + +found USB scanner (vendor=0x04a9 [Canon,Inc.], product=0x269d [iR1018/1022/1023]) at libusb:002:002 ++ +
+ If anything is wrong or missing on this page please file a bug report + or use the the + form for adding an unsupported device. +
++ If you own an unsupported scanner, please send as much information as + possible. Especially the output of sane-find-scanner -v -v + and/or cat /proc/scsi/scsi (for SCSI scanners) or cat + /proc/bus/usb/devices (for USB scanners) can help. If you dare to + open the scanner, have a look at the text that's printed on the + chips. That may help to identify the chipset. If you know that the + scanner is similar to another one (e.g. supported by the same Windows + driver), please also mention this fact. +
+ ++ Are you a manufacturer or vendor of scanners and one of your scanners is + not supported by SANE yet? In this case please have a look at our information for manufacturers. +
+ +
+ SANE homepage
+ Contact
+
+ $Date$ $Author$ +
+ + +