From c339f14185060b2dbe257534d68b94243c601ba5 Mon Sep 17 00:00:00 2001 From: Henning Geinitz Date: Tue, 3 Oct 2006 19:42:45 +0000 Subject: [PATCH] Added. --- unsupported/edt-900c.html | 198 +++++++++++++++++++++ unsupported/plustek-opticpro-st64plus.html | 196 ++++++++++++++++++++ 2 files changed, 394 insertions(+) create mode 100644 unsupported/edt-900c.html create mode 100644 unsupported/plustek-opticpro-st64plus.html diff --git a/unsupported/edt-900c.html b/unsupported/edt-900c.html new file mode 100644 index 00000000..f11fdf7b --- /dev/null +++ b/unsupported/edt-900c.html @@ -0,0 +1,198 @@ + + + + + Scanner information + + + + + + + + + +

Scanners not supported by SANE

+

Manufacturer and model

+

+ EDT (Electronic Document Technology) BizCardReader 900C +

+

Bus type

+

+ USB +

+

Vendor ID

+

+ 0x0A53 +

+

Product ID

+

+ 0x5001 +

+

Chipset

+

+ sq113c +

+

Comments

+

+ (from jnewlin AT medmate.com:) Very small, card scanner. Will scan up to 4 inch card. USB 2.0 scanner. + 24 bit color, 256 grayscale or black and white. Scanner is a 2 inches + deep and 1.5 inches tall. The driver for Microsoft Windows uses + usbscan.sys and a TWAIN DLL. Manufacturer does not have any Linux drivers + available. +

+

Output of /proc/bus/usb/devices or sane-find-scanner -v -v or lsusb -vv

+ 
+<device descriptor of 0x0a53/0x5001 at 001:060 (PANDP Co., Ltd.          USB2.0 Scanner            )>
+bLength               18
+bDescriptorType       1
+bcdUSB                2.00
+bDeviceClass          0
+bDeviceSubClass       0
+bDeviceProtocol       0
+bMaxPacketSize0       64
+idVendor              0x0A53
+idProduct             0x5001
+bcdDevice             1.00
+iManufacturer         1 (PANDP Co., Ltd.         )
+iProduct              2 (USB2.0 Scanner            )
+iSerialNumber         0 ()
+bNumConfigurations    1
+ <configuration 0>
+ bLength              9
+ bDescriptorType      2
+ wTotalLength         39
+ bNumInterfaces       1
+ bConfigurationValue  1
+ iConfiguration       0 ()
+ bmAttributes         128 ()
+ 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  0x01 (out 0x01)
+    bmAttributes      2 (bulk)
+    wMaxPacketSize    512
+    bInterval         0 ms
+    bRefresh          0
+    bSynchAddress     0
+    <endpoint 1>
+    bLength           7
+    bDescriptorType   5
+    bEndpointAddress  0x82 (in 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         3 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)
+    checking for PV8630/LM9830 ...
+    this is not a PV8630/LM9830 (bcdUSB = 0x200)
+    checking for M011 ...
+    this is not a M011 (bDeviceClass = 0)
+    checking for RTS8822L-01H ...
+    this is not a RTS8822L-01H (bEndpointAddress = 0x1, bmAttributes = 0x2, wMaxPacketSize = 0x200, bInterval = 0x0)
+    checking for rts8858c ...
+    this is not a rts8858c (bcdUSB = 0x200)
+    checking for SQ113 ...
+    Sensor not home? (0x28)
+<Couldn't determine the type of the USB chip (result from sane-backends 1.0.18)>
+
+ +

Want to add or correct information?

+

+ 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. +

+ +

Information for Manufacturers

+

+ 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. +

+ +

Links

+ + +
+ +

+ SANE homepage
+ Contact +

+

+ $Date$ $Author$ +

+ + + diff --git a/unsupported/plustek-opticpro-st64plus.html b/unsupported/plustek-opticpro-st64plus.html new file mode 100644 index 00000000..b64809c4 --- /dev/null +++ b/unsupported/plustek-opticpro-st64plus.html @@ -0,0 +1,196 @@ + + + + + Scanner information + + + + + + + + + +

Scanners not supported by SANE

+

Manufacturer and model

+

+ Plustek OpticPro ST64+ +

+

Bus type

+

+ USB +

+

Vendor ID

+

+ 0x07b3 +

+

Product ID

+

+ 0x0c03 +

+

Chipset

+

+ GL843 +

+

Comments

+

+ Chipset is visible without opening the scanner. +

+

Output of /proc/bus/usb/devices or sane-find-scanner -v -v or lsusb -vv

+ 
+<device descriptor of 0x07b3/0x0c03 at 005:003>
+bLength               18
+bDescriptorType       1
+bcdUSB                2.00
+bDeviceClass          255
+bDeviceSubClass       255
+bDeviceProtocol       255
+bMaxPacketSize0       64
+idVendor              0x07B3
+idProduct             0x0C03
+bcdDevice             4.00
+iManufacturer         10 ((null))
+iProduct              11 ((null))
+iSerialNumber         0 ()
+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 ...
+  Couldn't set configuration: could not set config 1: Operation not permitted
+<This USB chip looks like a GL841?>
+
+found USB scanner (vendor=0x07b3, product=0x0c03, chip=GL841?) at libusb:005:003
+
+
+T:  Bus=05 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#=  3 Spd=480 MxCh= 0
+D:  Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs=  1
+P:  Vendor=07b3 ProdID=0c03 Rev= 4.00
+S:  Manufacturer=PLUSTEK INC
+S:  Product=USB2.0 SCANNER
+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
+
+ +

Want to add or correct information?

+

+ 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. +

+ +

Information for Manufacturers

+

+ 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. +

+ +

Links

+ + +
+ +

+ SANE homepage
+ Contact +

+

+ $Date$ $Author$ +

+ + +