From 289daa1e9cd90e85a40adbfdf4d54f2151f9430c Mon Sep 17 00:00:00 2001
From: Henning Geinitz
+ Hewlett Packard ScanJet 5590
+
+ USB
+
+ 0x03f0
+
+ 0x1705
+
+
+
+ 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
+ $Date$ $Author$
+
+ Lexmark X5250
+
+ USB
+
+ 0x043D
+
+ 0x0093
+
+
+
+ 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
+ $Date$ $Author$
+
+ Microtek ScanMaker 6100
+
+ USB
+
+ 0x05da
+
+ 0x30E5
+
+
+
+ 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
+ $Date$ $Author$
+
+ Minolta Dimage Scan Multi Pro
+
+ IEEE-1394
+
+
+
+
+ 35mm to 6x9cm film scanner.
+
+ 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
+ $Date$ $Author$
+ Want to add or correct information?
diff --git a/unsupported/hp-scanjet-5590.html b/unsupported/hp-scanjet-5590.html
new file mode 100644
index 00000000..44e3334b
--- /dev/null
+++ b/unsupported/hp-scanjet-5590.html
@@ -0,0 +1,198 @@
+
+
+
+
+ Scanners not supported by SANE
+ Manufacturer and model
+ Bus type
+ Vendor ID
+ Product ID
+ Chipset
+ Comments
+ Output of /proc/bus/usb/devices or sane-find-scanner -v -v or lsusb -vv
+
+T: Bus=03 Lev=01 Prnt=01 Port=05 Cnt=01 Dev#= 10 Spd=480 MxCh= 0
+D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
+P: Vendor=03f0 ProdID=1705 Rev= 3.05
+S: Manufacturer=Hewlett-Packard
+S: Product=hp scanjet scanner
+S: SerialNumber=CN44HT604C
+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
+
+<device descriptor of 0x03f0/0x1705 at 003:010 (Hewlett-Packard hp scanjet scann
+er)>
+bLength 18
+bDescriptorType 1
+bcdUSB 2.00
+bDeviceClass 255
+bDeviceSubClass 255
+bDeviceProtocol 255
+bMaxPacketSize0 64
+idVendor 0x03F0
+idProduct 0x1705
+bcdDevice 3.05
+iManufacturer 1 (Hewlett-Packard)
+iProduct 2 (hp scanjet scanner)
+iSerialNumber 12 (CN44HT604C)
+bNumConfigurations 1
+ <configuration 0>
+ bLength 9
+ bDescriptorType 2
+ wTotalLength 39
+ bNumInterfaces 1
+ bConfigurationValue 1
+ iConfiguration 0 ()
+ bmAttributes 192 (Self-powered)
+ MaxPower 10 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 GT-8911 ...
+ this is not a GT-8911 (check 1, bDeviceClass = 255, bInterfaceClass = 255)
+ checking for MA-1017 ...
+ this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255)
+ checking for MA-1015 ...
+ this is not a MA-1015 (bcdUSB = 0x200)
+ checking for MA-1509 ...
+ this is not a MA-1509 (bcdUSB = 0x200)
+ checking for LM983[1,2,3] ...
+ 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)
+ checking for GL841 ...
+ this is not a GL841 (reg 0x38 != 0x15)
+ checking for ICM532B ...
+ this is not a ICM532B (check 2, bcdUSB = 0x200)
+<Couldn't determine the type of the USB chip>
+
+found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x1705 [hp scanjet scanner]) at libusb:003:010
+
+
+
+ Want to add or correct information?
+ Information for Manufacturers
+ Links
+
+
+
+
+
+
+ Contact
+ Scanners not supported by SANE
+ Manufacturer and model
+ Bus type
+ Vendor ID
+ Product ID
+ Chipset
+ Comments
+ Output of /proc/bus/usb/devices or sane-find-scanner -v -v or lsusb -vv
+
+T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
+D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
+P: Vendor=043d ProdID=0093 Rev= 0.01
+S: Manufacturer=Lexmark
+S: Product=Lexmark 5200 Series
+S: SerialNumber=21D0185113002MM
+C:* #Ifs= 3 Cfg#= 1 Atr=c0 MxPwr= 16mA
+I: If#= 0 Alt= 0 #EPs= 4 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
+E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
+E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
+E: Ad=87(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
+E: Ad=07(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
+I: If#= 1 Alt= 0 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp
+E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
+E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
+I: If#= 2 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid
+E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=100ms
+
+
+ Want to add or correct information?
+ Information for Manufacturers
+ Links
+
+
+
+
+
+
+ Contact
+ Scanners not supported by SANE
+ Manufacturer and model
+ Bus type
+ Vendor ID
+ Product ID
+ Chipset
+ Comments
+ Output of /proc/bus/usb/devices or sane-find-scanner -v -v or lsusb -vv
+
+T: Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=480 MxCh= 0
+D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
+P: Vendor=05da ProdID=30e5 Rev= 1.00
+S: Manufacturer=Prolific Technology Inc.
+S: Product=USB Scanner
+C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=100mA
+I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
+E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
+E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
+E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=500us
+
+
+
+ Want to add or correct information?
+ Information for Manufacturers
+ Links
+
+
+
+
+
+
+ Contact
+ Scanners not supported by SANE
+ Manufacturer and model
+ Bus type
+ Vendor ID
+ Product ID
+ Chipset
+ Comments
+ Output of /proc/bus/usb/devices or sane-find-scanner -v -v or lsusb -vv
+
+
+
+ Want to add or correct information?
+ Information for Manufacturers
+ Links
+
+
+
+
+
+
+ Contact
+
- 0x040b + 0x040b / 0x0600
- GT6816. + GT6816 (0x040b) / GL646 (0x0600).
- It was previously mentioned that this scanner uses a GL646, but this seems - to be wrong. So it may be supported by the gt68xx backend in future. + It was previously mentioned that this scanner (product id 0x040b) uses a GL646, but this seems + to be wrong. So it may be supported by the gt68xx backend in + future. However, there are newer reports that the product id is is 0x0600 + and that this model uses a gl646. Strange. Please send more reports!
+Product id 0x040b: <device descriptor of 0x07b3/0x040b at 002:003 (600DPI USB Scanner)> bLength 18 bDescriptorType 1 @@ -101,7 +104,102 @@ bNumConfigurations checking for GT-6816 ... <This USB chip looks like a GT-6816> -found USB scanner (vendor=0x07b3, product=0x040b [600DPI USB Scanner], chip=GT-6816) at libusb:002:003 +found USB scanner (vendor=0x07b3, product=0x040b [600DPI USB Scanner], +chip=GT-6816) at libusb:002:003 + +Product id 0x0600: +T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 +D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 +P: Vendor=07b3 ProdID=0600 Rev= 0.00 +S: Manufacturer=PLUSTEK INC +S: Product=USB SCANNER +C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 48mA +I: If#= 0 Alt= 0 #EPs= 3 Cls=10(unk. ) Sub=01 Prot=00 Driver=(none) +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 0x07b3/0x0600 at 003:003 (PLUSTEK INC USB SCANNER)> +bLength 18 +bDescriptorType 1 +bcdUSB 1.10 +bDeviceClass 0 +bDeviceSubClass 0 +bDeviceProtocol 0 +bMaxPacketSize0 8 +idVendor 0x07B3 +idProduct 0x0600 +bcdDevice 0.00 +iManufacturer 10 (PLUSTEK INC) +iProduct 11 (USB SCANNER) +iSerialNumber 0 () +bNumConfigurations 1 +<configuration 0> +bLength 9 +bDescriptorType 2 +wTotalLength 39 +bNumInterfaces 1 +bConfigurationValue 1 +iConfiguration 0 () +bmAttributes 224 (Self-poweredRemote Wakeup) +MaxPower 48 mA +<interface 0> +<altsetting 0> +bLength 9 +bDescriptorType 4 +bInterfaceNumber 0 +bAlternateSetting 0 +bNumEndpoints 3 +bInterfaceClass 16 +bInterfaceSubClass 1 +bInterfaceProtocol 0 +iInterface 0 () +<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 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 (bDeviceClass = 0) +checking for GT-6816 ... +this is not a GT-6816 (bDeviceClass = 0, bInterfaceClass = 16) +checking for MA-1017 ... +this is not a MA-1017 (bDeviceClass = 0, bInterfaceClass = 16) +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 (bDeviceClass = 0, bInterfaceClass = 16) +checking for GL646 ... +<This USB chip looks like a GL646> + +found USB scanner (vendor=0x07b3 [PLUSTEK INC], product=0x0600 [USB SCANNER], chip=GL646) at libusb:003:003 +
+ Primax Colorade USB 9600 +
++ USB +
++ 0x0461 +
++ 0x0340 +
+++------------ IC1 ----------------------------- +EICI 0910oo (oo this is small number zero 00) +F98380285 +----------------------------------------------- +------------------------- IC11 ---------------- +WM 8143-12C +86AD4ET4C +---------------------------------------------- +--------------------------- IC8 --------------- +ScanLogic SL11 982628PLCC-1.1 A003 Taiwan +----------------------------------------------- +---------------------------------------------- +On electric bord describes: +EPCB0J400A-1 + +and decribes +ASYM104250-A +Y42MV83400 +---------------------------------------------- +
+ It seems the EICI 091000 is the scanner chip interface par. port. The + scanlogic SL11 (now Cypress) is the par. port to usb converter bridge. For + info EICI 091000 see also here. + +
++
+++ +
+ 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/tevion-md90009.html b/unsupported/tevion-md90009.html index b82d4d8f..fc89bd9b 100644 --- a/unsupported/tevion-md90009.html +++ b/unsupported/tevion-md90009.html @@ -31,11 +31,15 @@- Perhaps PL-2555 or PL-2551? + Perhaps PL-2555 or + PL-2551?
- Available since 2005-03-09 in German Aldi supermarkets. + Same vendor/product ids as Microtek + Scanmaker 6000. Available since 2005-03-09 in German Aldi supermarkets.
diff --git a/unsupported/trust-combiscan-19200.html b/unsupported/trust-combiscan-19200.html index 9b1b2901..407a62ad 100644 --- a/unsupported/trust-combiscan-19200.html +++ b/unsupported/trust-combiscan-19200.html @@ -18,7 +18,8 @@ Trust CombiScan 19200diff --git a/unsupported/visioneer-onetouch4800.html b/unsupported/visioneer-onetouch4800.html index 5c421bbe..b70356d3 100644 --- a/unsupported/visioneer-onetouch4800.html +++ b/unsupported/visioneer-onetouch4800.html @@ -61,6 +61,98 @@ E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms +<device descriptor of 0x04a7/0x0224 at 002:002> +bLength 18 +bDescriptorType 1 +bcdUSB 1.10 +bDeviceClass 0 +bDeviceSubClass 0 +bDeviceProtocol 0 +bMaxPacketSize0 8 +idVendor 0x04A7 +idProduct 0x0224 +bcdDevice 1.00 +iManufacturer 1 ((null)) +iProduct 2 ((null)) +iSerialNumber 8 ((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 0 + bInterfaceSubClass 0 + bInterfaceProtocol 0 + iInterface 7 ((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 (bDeviceClass = 0, bInterfaceClass = 0) + checking for GT-8911 ... + this is not a GT-8911 (check 1, bDeviceClass = 0, bInterfaceClass = 0) + checking for MA-1017 ... + this is not a MA-1017 (bcdUSB = 0x110) + 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 (bDeviceClass = 0, bInterfaceClass = 0) + checking for GL646 ... + this is not a GL646 (bDeviceClass = 0, bInterfaceClass = 0) + checking for GL646_HP ... + this is not a GL646_HP (bDeviceClass = 0, bInterfaceClass = 0) + checking for GL660+GL646 ... + this is not a GL660+GL646 (bDeviceClass = 0, bInterfaceClass = 0) + checking for GL841 ... + this is not a GL841 (bDeviceClass = 0, bInterfaceClass = 0) + checking for ICM532B ... + this is not a ICM532B (check 1, bDeviceClass = 0, bInterfaceClass = 0) +<Couldn't determine the type of the USB chip> + +found USB scanner (vendor=0x04a7, product=0x0224) at libusb:002:002 + Vantas 3000: T: Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 10 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 diff --git a/unsupported/visioneer-onetouch6600.html b/unsupported/visioneer-onetouch6600.html new file mode 100644 index 00000000..3187e3ee --- /dev/null +++ b/unsupported/visioneer-onetouch6600.html @@ -0,0 +1,96 @@ + + + + +
Boeder Sm@rtScan Office
Avigramm Minidoc
- Compeye Simplex 1236C + Compeye Simplex 1236C
+ Memorex MaxxScan 6122Bus type
@@ -26,7 +27,7 @@
Vendor ID
- 0x5cb + 0x05cb
Product ID
@@ -45,10 +46,14 @@
Comments
- All four scanners have the same ids. The vendor is PowerVision - Technologies. At lest the Avigram was sold as a scanner for + All scanners have the same ids. The vendor is PowerVision + Technologies. At least the Avigram was sold as a scanner for notebooks/mobile use.
++ Memorex explained that it's originally a Visioneer scanner (?). +
+A user reports about using his Boeder scanner's parallel port:
2 years ago i used the parallel bus of my scanner, and it worked. What i did was @@ -102,6 +107,16 @@ C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=(none) E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms +E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=1ms + +Memorex MaxxScan 6122 +T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 +D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 +P: Vendor=05cb ProdID=1483 Rev= 1.00 +C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=100mA +I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=(none) +E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms +E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=1ms
+ Visioneer Onetouch 6600 +
++ USB +
++ 0x04a7 +
++ 0x022a +
+
+ GL646?
+ Number printed on chip: 610800009609
+
+
++ ++ +
+ 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/xerox-2400-onetouch.html b/unsupported/xerox-2400-onetouch.html index 67afc745..aeaceb13 100644 --- a/unsupported/xerox-2400-onetouch.html +++ b/unsupported/xerox-2400-onetouch.html @@ -31,13 +31,15 @@+ GL646_HP
+ As the chip is GL646_HP it may be supported by the genesys backend later.
-<device descriptor of 0x0461/0x038b at 001:003 (Primax USB Scanner)> +<device descriptor of 0x0461/0x038b at 003:002 (Primax USB Scanner)> bLength 18 bDescriptorType 1 bcdUSB 1.10 @@ -99,6 +101,29 @@ bNumConfigurations 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 (bNumEndpoints = 3) + checking for GT-6816 ... + this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255) + checking for GT-8911 ... + this is not a GT-8911 (check 1, bDeviceClass = 255, bInterfaceClass = 255) + checking for MA-1017 ... + this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255) + checking for MA-1015 ... + this is not a MA-1015 (bcdUSB = 0x110) + checking for MA-1509 ... + this is not a MA-1509 (bEndpointAddress = 0x2, bmAttributes = 0x2, wMaxPacketSize = 0x40) + checking for LM983[1,2,3] ... + this is not a LM983x (bDeviceSubClass = 0xff) + checking for GL646 ... + this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255) + checking for GL646_HP ... +<This USB chip looks like a GL646_HP> + +found USB scanner (vendor=0x0461 [Primax], product=0x038b [USB Scanner], chip=GL646_HP) at libusb:003:002 +