diff --git a/unsupported/brother-mfc9160c.html b/unsupported/brother-mfc9160c.html new file mode 100644 index 00000000..0817bc8a --- /dev/null +++ b/unsupported/brother-mfc9160c.html @@ -0,0 +1,199 @@ + + + +
++ Brother MFC 9160C +
++ USB, parport +
++ 0x04f9 +
++ 0x011f +
++
++ Printer + scanner + fax. The devices output looks similar to that of the + MFC 5100. +
++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= 8 #Cfgs= 1 +P: Vendor=04f9 ProdID=011f Rev= 1.00 +S: SerialNumber=BROJ3J659731 +C:* #Ifs= 2 Cfg#= 1 Atr=40 MxPwr= 0mA +I: If#= 0 Alt= 0 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp +E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms +E: Ad=82(I) Atr=02(Bulk) MxPS= 16 Ivl=0ms +I: If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) +E: Ad=03(O) Atr=02(Bulk) MxPS= 16 Ivl=0ms +E: Ad=84(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms +E: Ad=85(I) Atr=03(Int.) MxPS= 8 Ivl=100ms + +<device descriptor of 0x04f9/0x011f at 001:002> +bLength 18 +bDescriptorType 1 +bcdUSB 1.00 +bDeviceClass 0 +bDeviceSubClass 0 +bDeviceProtocol 0 +bMaxPacketSize0 8 +idVendor 0x04F9 +idProduct 0x011F +bcdDevice 1.00 +iManufacturer 0 () +iProduct 0 () +iSerialNumber 3 (BROJ3J659731) +bNumConfigurations 1 + <configuration 0> + bLength 9 + bDescriptorType 2 + wTotalLength 62 + bNumInterfaces 2 + bConfigurationValue 1 + iConfiguration 0 () + bmAttributes 64 (Self-powered) + MaxPower 0 mA + <interface 0> + <altsetting 0> + bLength 9 + bDescriptorType 4 + bInterfaceNumber 0 + bAlternateSetting 0 + bNumEndpoints 2 + bInterfaceClass 7 + bInterfaceSubClass 1 + bInterfaceProtocol 2 + 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 16 + bInterval 0 ms + bRefresh 0 + bSynchAddress 0 + <interface 1> + <altsetting 0> + bLength 9 + bDescriptorType 4 + bInterfaceNumber 1 + bAlternateSetting 0 + bNumEndpoints 3 + bInterfaceClass 255 + bInterfaceSubClass 255 + bInterfaceProtocol 255 + iInterface 0 () + <endpoint 0> + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x03 (out 0x03) + bmAttributes 2 (bulk) + wMaxPacketSize 16 + bInterval 0 ms + bRefresh 0 + bSynchAddress 0 + <endpoint 1> + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x84 (in 0x04) + bmAttributes 2 (bulk) + wMaxPacketSize 64 + bInterval 0 ms + bRefresh 0 + bSynchAddress 0 + <endpoint 2> + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x85 (in 0x05) + bmAttributes 3 (interrupt) + wMaxPacketSize 8 + bInterval 100 ms + bRefresh 0 + bSynchAddress 0 ++ +
+ 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/reflecta-proscan-4000.html b/unsupported/reflecta-proscan-4000.html new file mode 100644 index 00000000..fe8329a0 --- /dev/null +++ b/unsupported/reflecta-proscan-4000.html @@ -0,0 +1,166 @@ + + + + ++ Reflecta ProScan 4000 +
++ USB, IEEE-1394 +
++ 0x05e3 +
++ 0x0143 +
++
++
++T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0 +D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 +P: Vendor=05e3 ProdID=0143 Rev= 3.02 +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= 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 + +sane-find-scanner -v -v +<device descriptor of 0x05e3/0x0143 at 001:004> +bLength 18 +bDescriptorType 1 +bcdUSB 2.00 +bDeviceClass 255 +bDeviceSubClass 255 +bDeviceProtocol 255 +bMaxPacketSize0 64 +idVendor 0x05E3 +idProduct 0x0143 +bcdDevice 3.02 +iManufacturer 0 () +iProduct 0 () +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 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 +found USB scanner (vendor=0x05e3, product=0x0143) at libusb:001:004 ++ +
+ 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$ +
+ + +