+ Canon 8400F +
++ USB +
++ 0x04a9 +
++ 0x221e +
++
++ With transparency adapter. +
++T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 +D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 +P: Vendor=04a9 ProdID=221e Rev= 4.00 +S: Manufacturer=Canon +S: Product=CanoScan +C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 10mA +I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) +E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms +E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms +E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=16ms ++ +
+ 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$ +
+ + + diff --git a/unsupported/hp-scanjet-3770.html b/unsupported/hp-scanjet-3770.html new file mode 100644 index 00000000..618162fa --- /dev/null +++ b/unsupported/hp-scanjet-3770.html @@ -0,0 +1,189 @@ + + + + ++ Hewlett-Packard Scanjet 3770 +
++ USB +
++ 0x03f0 +
++ 0x2505 +
++
++
++T: Bus=05 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 +D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 +P: Vendor=03f0 ProdID=2505 Rev= 1.00 +S: Manufacturer=hewlett packard +S: Product=hp scanjet +S: SerialNumber=CN48BAS7SZRX +C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 2mA +I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none) +E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms +E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms +E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=256ms + +<device descriptor of 0x03f0/0x2505 at 001:002 (hewlett packard hp scanjet)> +bLength 18 +bDescriptorType 1 +bcdUSB 2.00 +bDeviceClass 0 +bDeviceSubClass 0 +bDeviceProtocol 0 +bMaxPacketSize0 64 +idVendor 0x03F0 +idProduct 0x2505 +bcdDevice 1.00 +iManufacturer 1 (hewlett packard) +iProduct 2 (hp scanjet) +iSerialNumber 3 (CN46RAS36DRX) +bNumConfigurations 1 + <configuration 0> + bLength 9 + bDescriptorType 2 + wTotalLength 39 + bNumInterfaces 1 + bConfigurationValue 1 + iConfiguration 0 () + bmAttributes 224 (Self-poweredRemote Wakeup) + MaxPower 2 mA + <interface 0> + <altsetting 0> + bLength 9 + bDescriptorType 4 + bInterfaceNumber 0 + bAlternateSetting 0 + bNumEndpoints 3 + bInterfaceClass 255 + bInterfaceSubClass 0 + bInterfaceProtocol 255 + iInterface 5 (Bulk-In, Bulk-Out, Interrupt Interface) + <endpoint 0> + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x81 (in 0x01) + bmAttributes 2 (bulk) + wMaxPacketSize 64 + bInterval 0 ms + bRefresh 0 + bSynchAddress 0 + <endpoint 1> + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x02 (out 0x02) + bmAttributes 2 (bulk) + wMaxPacketSize 64 + bInterval 0 ms + bRefresh 0 + bSynchAddress 0 + <endpoint 2> + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x83 (in 0x03) + bmAttributes 3 (interrupt) + wMaxPacketSize 1 + bInterval 250 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 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 GL660+GL646 ... + this is not a GL660+GL646 (bDeviceClass = 0, bInterfaceClass = 255) +<Couldn't determine the type of the USB chip> + +found USB scanner (vendor=0x03f0 [hewlett packard], product=0x2505 [hp scanjet]) at libusb:001: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$ +
+ + + diff --git a/unsupported/hp-scanjet-4070.html b/unsupported/hp-scanjet-4070.html new file mode 100644 index 00000000..a1fb9bb4 --- /dev/null +++ b/unsupported/hp-scanjet-4070.html @@ -0,0 +1,106 @@ + + + + ++ Hewlett Packard Scanjet 4070 Photosmart +
++ USB +
++ 0x03f0 +
++ 0x2405 +
++ RTS8822L Realtek +
++ Similar to HP Scanjet 3970c. +
++T: Bus=03 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 4 Spd=480 MxCh= 0 +D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 +P: Vendor=03f0 ProdID=2405 Rev= 1.00 +S: Manufacturer=hewlett packard +S: Product=hp scanjet +S: SerialNumber=CN462AL31QRW +C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 2mA +I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none) +E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms +E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms +E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=256ms ++ +
+ 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$ +
+ + + diff --git a/unsupported/hp-scanjet-4570c.html b/unsupported/hp-scanjet-4570c.html index 6f0b4700..63157346 100644 --- a/unsupported/hp-scanjet-4570c.html +++ b/unsupported/hp-scanjet-4570c.html @@ -32,7 +32,9 @@- Similar to a GL841. Not yet confirmed, however. + Similar to a GL841. Not yet confirmed, however. sane-find-scanner seems to + be able to communicate with the chipset in GL841 mode but it doesn't get + the same value it writes to the register back when reading.
These are the chips on the board:
@@ -126,7 +128,8 @@ E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=8ms
-<device descriptor of 0x03f0/0x1305 at 001:002 (Hewlett-Packard hp scanjet scanner)>
+<device descriptor of 0x03f0/0x1305 at 001:002 (Hewlett-Packard hp
+scanjet scanner)>
bLength 18
bDescriptorType 1
bcdUSB 2.00
@@ -166,7 +169,7 @@ bNumConfigurations 1
bDescriptorType 5
bEndpointAddress 0x81 (in 0x01)
bmAttributes 2 (bulk)
- wMaxPacketSize 64
+ wMaxPacketSize 512
bInterval 0 ms
bRefresh 0
bSynchAddress 0
@@ -175,7 +178,7 @@ bNumConfigurations 1
bDescriptorType 5
bEndpointAddress 0x02 (out 0x02)
bmAttributes 2 (bulk)
- wMaxPacketSize 64
+ wMaxPacketSize 512
bInterval 0 ms
bRefresh 0
bSynchAddress 0
@@ -188,7 +191,6 @@ bNumConfigurations 1
bInterval 8 ms
bRefresh 0
bSynchAddress 0
-found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x1305 [hp scanjet scanner]) at libusb:001:002
<trying to find out which USB chip is used>
checking for GT-6801 ...
@@ -205,10 +207,18 @@ found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x1305 [hp scanjet s
this is not a LM983x (bcdUSB = 0x200)
checking for GL646 ...
this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255)
+ checking for GL646_HP ...
+ this is not a GL646_HP (bcdUSB = 0x200)
checking for GL660+GL646 ...
- this is not a GL660+GL646 (bDeviceClass = 255, bInterfaceClass = 255)
+ this is not a GL660+GL646 (bDeviceClass = 255, bInterfaceClass =
+255)
+ checking for GL841 ...
+ this is not a GL841 (reg 0x38 != 0x15)
+ checking for ICM532B ...
+ check 2, this is not a ICM532B (bcdUSB = 0x200)
<Couldn't determine the type of the USB chip>
+found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x1305 [hp scanjet scanner]) at libusb:001:002
diff --git a/unsupported/lexmark-3150.html b/unsupported/lexmark-3150.html
new file mode 100644
index 00000000..fe973b9f
--- /dev/null
+++ b/unsupported/lexmark-3150.html
@@ -0,0 +1,183 @@
+
+
+
+
+ + Lexmark Photo 3150 +
++ USB +
++ 0x043d +
++ 0x007d +
++
++
++ +<device descriptor of 0x043d/0x007d at 002:007> +bLength 18 +bDescriptorType 1 +bcdUSB 1.10 +bDeviceClass 0 +bDeviceSubClass 0 +bDeviceProtocol 0 +bMaxPacketSize0 8 +idVendor 0x043D +idProduct 0x007D +bcdDevice 1.00 +iManufacturer 3 ((null)) +iProduct 4 ((null)) +iSerialNumber 7 ((null)) +bNumConfigurations 1 + <configuration 0> + bLength 9 + bDescriptorType 2 + wTotalLength 39 + bNumInterfaces 1 + bConfigurationValue 1 + iConfiguration 6 ((null)) + bmAttributes 224 (Self-poweredRemote Wakeup) + MaxPower 0 mA + <interface 0> + <altsetting 0> + bLength 9 + bDescriptorType 4 + bInterfaceNumber 0 + bAlternateSetting 0 + bNumEndpoints 3 + bInterfaceClass 255 + bInterfaceSubClass 0 + bInterfaceProtocol 255 + iInterface 9 ((null)) + <endpoint 0> + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x81 (in 0x01) + bmAttributes 2 (bulk) + wMaxPacketSize 64 + bInterval 0 ms + bRefresh 0 + bSynchAddress 0 + <endpoint 1> + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x02 (out 0x02) + bmAttributes 2 (bulk) + wMaxPacketSize 8 + bInterval 0 ms + bRefresh 0 + bSynchAddress 0 + <endpoint 2> + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x83 (in 0x03) + bmAttributes 3 (interrupt) + wMaxPacketSize 1 + bInterval 250 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 (bNumEndpoints = 3) + 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 (bEndpointAddress = 0x81, bmAttributes = 0x2, wMaxPacketSize = 0x40, bInterval = 0x0) + 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 ... + check 1, this is not a ICM532B (bDeviceClass = 0, bInterfaceClass = 255) +<Couldn't determine the type of the USB chip> + +found USB scanner (vendor=0x043d, product=0x007d) at libusb:002:007 ++ +
+ 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$ +
+ + + diff --git a/unsupported/olympus-es10s.html b/unsupported/olympus-es10s.html new file mode 100644 index 00000000..d35e5b0c --- /dev/null +++ b/unsupported/olympus-es10s.html @@ -0,0 +1,104 @@ + + + + ++ Olympus es10s +
++ SCSI +
++ "OLYMPUS" +
++ "ES-10_SCSI" +
++There are 3 mitsubishi M64290FP A to D chips +A mistubish SCSI controller chip M64154AFP +A ISSI IS62c256 SRAM +a couple of M62353 chips without the function labeled +a couple of scsi glue chips and the main chip, the HD6437034F20 ++
+ This is a 1700DPI (actual) negative/slide scanner. +
++ Inquiry for device: + 000: 06 00 00 00 1f 00 00 00 4f 4c 59 4d 50 55 53 20 ........OLYMPUS + 016: 45 53 2d 31 30 5f 53 43 53 49 20 20 20 20 20 20 ES-10_SCSI + 032: 31 2e 30 30 1.00 +found SCSI scanner "OLYMPUS ES-10_SCSI 1.00" at /dev/sg3 ++ +
+ 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$ +
+ + +