From ce02f903adc4f2c276d08c60c2315467b595b253 Mon Sep 17 00:00:00 2001 From: Henning Geinitz Date: Mon, 28 Jun 2004 17:40:54 +0000 Subject: [PATCH] Added Microtek ScanMaker i320. --- unsupported/microtek-scanmaker-i320.html | 191 +++++++++++++++++++++++ 1 file changed, 191 insertions(+) create mode 100644 unsupported/microtek-scanmaker-i320.html diff --git a/unsupported/microtek-scanmaker-i320.html b/unsupported/microtek-scanmaker-i320.html new file mode 100644 index 00000000..0a0d78b3 --- /dev/null +++ b/unsupported/microtek-scanmaker-i320.html @@ -0,0 +1,191 @@ + + + + + Scanner information + + + + + + + + + +

Scanners not supported by SANE

+

Manufacturer and model

+

+ Microtek ScanMaker i320 +

+

Bus type

+

+ USB +

+

Vendor ID

+

+ 0x05da +

+

Product ID

+

+ 0x30e6 +

+

Chipset

+

+

+

Comments

+

+

+

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

+ 
+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=05da ProdID=30e6 Rev= 1.00 
+S: Manufacturer=Prolific Technology Inc. 
+S: Product=USB 2.0 Scanner Controller 
+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= 64 Ivl=0ms 
+E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms 
+E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=3ms
+
+<device descriptor of 0x05da/0x30e6 at 001:002 (Prolific Technology Inc. USB 2.0 Scanner Controller)> 
+bLength 18 
+bDescriptorType 1 
+bcdUSB 2.00 
+bDeviceClass 0 
+bDeviceSubClass 0 
+bDeviceProtocol 0 
+bMaxPacketSize0 64 
+idVendor 0x05DA 
+idProduct 0x30E6 
+bcdDevice 1.00 
+iManufacturer 1 (Prolific Technology Inc.) 
+iProduct 2 (USB 2.0 Scanner Controller) 
+iSerialNumber 0 () 
+bNumConfigurations 1 
+<configuration 0> 
+bLength 9 
+bDescriptorType 2 
+wTotalLength 39 
+bNumInterfaces 1 
+bConfigurationValue 1 
+iConfiguration 0 () 
+bmAttributes 192 (Self-powered) 
+MaxPower 100 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 64 
+bInterval 0 ms 
+bRefresh 0 
+bSynchAddress 0 
+<endpoint 1> 
+bLength 7 
+bDescriptorType 5 
+bEndpointAddress 0x82 (in 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 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 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 ... 
+check 1, this is not a ICM532B (bDeviceClass = 0, bInterfaceClass = 255) 
+<Couldn't determine the type of the USB chip> 
+found USB scanner (vendor=0x05da [Prolific Technology Inc.], product=0x30e6 [USB 2.0 Scanner Controller]) at libusb:001: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$ +

+ + +