+ This scanner may be supported by the Genesys + backend, when it's finished. +
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 4 Spd=12 MxCh= 0
diff --git a/unsupported/canon-lide-80.html b/unsupported/canon-lide-80.html
index 587b471d..df2555bd 100644
--- a/unsupported/canon-lide-80.html
+++ b/unsupported/canon-lide-80.html
@@ -31,9 +31,14 @@
Chipset
- Probably Genesys Logic GL841.
+ Genesys Logic GL841.
Comments
+
+ This scanner may be supported by the Genesys
+ backend, when it's finished.
+
Output of /proc/bus/usb/devices or sane-find-scanner -v -v
T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
diff --git a/unsupported/hp-scanjet-2300c.html b/unsupported/hp-scanjet-2300c.html
index 515bcf5b..31cb81a5 100644
--- a/unsupported/hp-scanjet-2300c.html
+++ b/unsupported/hp-scanjet-2300c.html
@@ -31,11 +31,17 @@
Chipset
+ GL646_HP
On the chip these are the no's: fzc1n20gj and m11b41a
Comments
- Someone Genesys
+ backend, when it's finished.
+
+
+ Someone elsewants to
write a backend.
diff --git a/unsupported/hp-scanjet-2400c.html b/unsupported/hp-scanjet-2400c.html
index 83dee5bf..bfee902f 100644
--- a/unsupported/hp-scanjet-2400c.html
+++ b/unsupported/hp-scanjet-2400c.html
@@ -31,11 +31,17 @@
Chipset
+ Maybe GL646_HP
Comments
+
+ If this is the GL646 chip, maybe the Genesys
+ backend can be used, when it's finished?
+
diff --git a/unsupported/hp-scanjet-3670c.html b/unsupported/hp-scanjet-3670c.html
index cf83783e..735f52e9 100644
--- a/unsupported/hp-scanjet-3670c.html
+++ b/unsupported/hp-scanjet-3670c.html
@@ -30,6 +30,9 @@
0x1405
Chipset
+
+ Probably GL646_HP
+
Written on the chipset:
@@ -46,6 +49,11 @@ M1B416256A
DZC1HF2GJ
Comments
+
+ If this is the GL646 chip, maybe the Genesys
+ backend can be used, when it's finished?
+
Same scanner as 3690?
diff --git a/unsupported/hp-scanjet-3690.html b/unsupported/hp-scanjet-3690.html
index 63d2c75a..33f19735 100644
--- a/unsupported/hp-scanjet-3690.html
+++ b/unsupported/hp-scanjet-3690.html
@@ -23,12 +23,16 @@
Vendor ID
-
+ 0x03f0
Product ID
+ 0x1405
Chipset
+
+ Probably GL646_HP
+
26-00204-00A
0314FGKC9-10
@@ -36,6 +40,11 @@
EliteMT 100Mhz
Comments
+
+ If this is the GL646 chip, maybe the Genesys
+ backend can be used, when it's finished?
+
Same scanner as 3670c?
diff --git a/unsupported/hp-scanjet-8290.html b/unsupported/hp-scanjet-8290.html
index 7a55960f..7d015cd4 100644
--- a/unsupported/hp-scanjet-8290.html
+++ b/unsupported/hp-scanjet-8290.html
@@ -32,6 +32,7 @@
Comments
+ Includes ADF and TA. Similar to 8200C?
Output of /proc/bus/usb/devices or sane-find-scanner -v -v
diff --git a/unsupported/lexmark-x1150.html b/unsupported/lexmark-x1150.html
new file mode 100644
index 00000000..b768aa87
--- /dev/null
+++ b/unsupported/lexmark-x1150.html
@@ -0,0 +1,204 @@
+
+
+
+
+ Scanner information
+
+
+
+
+
+
+
+
+
+ Scanners not supported by SANE
+ Manufacturer and model
+
+ Lexmark X1150
+
+ Bus type
+
+ USB
+
+ Vendor ID
+
+ Vendor=043d
+
+ Product ID
+
+ ProdID=007c
+
+ Chipset
+
+ Realtek RTS8852B
+
+
+Board Number BJ4150M02001 Ver A-7
+2 large processors :
+Realtek RTS8852B-03 37012Q1 327F - PC-Based MFP Controller Chip ( close relative to .)
+Lexmark 18K0205 330B31V ARM - Printer controller?
+
+3 smaller ICs:
+SN105082 37AC4LT 14D0205 Silicon Controlled Rectifier
+BD6775 329 H91 NPN Darlington Transistor
+24C01W6 B326L Serial EEPROM
+
+ Comments
+
+ All in one job. Printer works fine with the z600 driver. Info on the
+ scanner chip (well the closes relative I can find) can be found here.
+
+ Output of /proc/bus/usb/devices or sane-find-scanner -v -v
+
+T: Bus=02 Lev=02 Prnt=06 Port=00 Cnt=01 Dev#= 7 Spd=12 MxCh= 0
+D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
+P: Vendor=043d ProdID=007c Rev= 1.00
+S: Manufacturer=Lexmark
+S: Product=X1100 Series
+S: SerialNumber=5003470
+C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
+I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none)
+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 0x043d/0x007c at 002:004>
+bLength 18
+bDescriptorType 1
+bcdUSB 1.10
+bDeviceClass 0
+bDeviceSubClass 0
+bDeviceProtocol 0
+bMaxPacketSize0 8
+idVendor 0x043D
+idProduct 0x007C
+bcdDevice 1.00
+iManufacturer 1 ((null))
+iProduct 2 ((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 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=0x043d, product=0x007c) at libusb:002:004
+
+
+ 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/medion-MD5345.html b/unsupported/medion-MD5345.html index ac993691..137144e0 100644 --- a/unsupported/medion-MD5345.html +++ b/unsupported/medion-MD5345.html @@ -19,7 +19,8 @@ Tevion MD 6228