From f8d2334c63cd5cd0bae2b336b7d9c3d85f5fca25 Mon Sep 17 00:00:00 2001 From: Henning Geinitz Date: Sun, 12 Feb 2006 12:11:25 +0000 Subject: [PATCH] Added Benq 7400UT. --- unsupported/benq-7400ut.html | 186 +++++++++++++++++++++++++++++++++++ 1 file changed, 186 insertions(+) create mode 100644 unsupported/benq-7400ut.html diff --git a/unsupported/benq-7400ut.html b/unsupported/benq-7400ut.html new file mode 100644 index 00000000..5f205cc8 --- /dev/null +++ b/unsupported/benq-7400ut.html @@ -0,0 +1,186 @@ + + + + + Scanner information + + + + + + + + + +

Scanners not supported by SANE

+

Manufacturer and model

+

+ Benq 7400UT +

+

Bus type

+

+ USB +

+

Vendor ID

+

+ 0x04a5 +

+

Product ID

+

+ 0x2202 +

+

Chipset

+

+

+

Comments

+

+

+

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

+ 
+This is sane-find-scanner from sane-backends 1.0.15
+[...]
+<device descriptor of 0x04a5/0x2202 at 004:002 (USB 2.0 Color Scanner)>
+bLength               18
+bDescriptorType       1
+bcdUSB                2.00
+bDeviceClass          255
+bDeviceSubClass       255
+bDeviceProtocol       255
+bMaxPacketSize0       64
+idVendor              0x04A5
+idProduct             0x2202
+bcdDevice             3.02
+iManufacturer         0 ()
+iProduct              1 (USB 2.0 Color Scanner)
+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 ...
+    this is not a GL841 (reading register failed)
+    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=0x04a5, product=0x2202 [USB 2.0 Color Scanner]) at libusb:004:002
+
+ +

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

+ + +