mirror
/
sane-project-website
kopia lustrzana https://gitlab.com/sane-project/website
1
0
Forkuj 0
Kod Zgłoszenia Projekty Wydania Wiki Aktywność

Added some scanners.

merge-requests/1/head
Henning Geinitz 2003-12-14 16:47:17 +00:00
rodzic dbd6f87153
commit 3d0fc2a035
2 zmienionych plików z 365 dodań i 0 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

199
unsupported/brother-mfc9160c.html 100644
Wyświetl plik

@ -0,0 +1,199 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Scanner information</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="author" content="Henning Meier-Geinitz">
<meta name="keywords" content="sane, backend, driver, scanner, unsupported">
<link href="mailto:henning@meier-geinitz.de" rev="made">
<link rel="icon" href="/favicon.ico" type="image/x-icon">
<link rel="shortcut icon" href="/favicon.ico" type="image/x-icon">
</head>
<body>
<h1>Scanners not supported by SANE</h1>
<h2>Manufacturer and model</h2>
<p>
Brother MFC 9160C
</p>
<h2>Bus type</h2>
<p>
USB, parport
</p>
<h2>Vendor ID</h2>
<p>
0x04f9
</p>
<h2>Product ID</h2>
<p>
0x011f
</p>
<h2>Chipset</h2>
<p>
</p>
<h2>Comments</h2>
<p>
Printer + scanner + fax. The devices output looks similar to that of the
MFC 5100.
</p>
<h2>Output of /proc/bus/usb/devices or sane-find-scanner -v -v</h2>
<pre>
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
&lt;device descriptor of 0x04f9/0x011f at 001:002&gt;
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
&lt;configuration 0&gt;
bLength 9
bDescriptorType 2
wTotalLength 62
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0 ()
bmAttributes 64 (Self-powered)
MaxPower 0 mA
&lt;interface 0&gt;
&lt;altsetting 0&gt;
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 7
bInterfaceSubClass 1
bInterfaceProtocol 2
iInterface 0 ()
&lt;endpoint 0&gt;
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 (out 0x01)
bmAttributes 2 (bulk)
wMaxPacketSize 64
bInterval 0 ms
bRefresh 0
bSynchAddress 0
&lt;endpoint 1&gt;
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 (in 0x02)
bmAttributes 2 (bulk)
wMaxPacketSize 16
bInterval 0 ms
bRefresh 0
bSynchAddress 0
&lt;interface 1&gt;
&lt;altsetting 0&gt;
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255
bInterfaceSubClass 255
bInterfaceProtocol 255
iInterface 0 ()
&lt;endpoint 0&gt;
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 (out 0x03)
bmAttributes 2 (bulk)
wMaxPacketSize 16
bInterval 0 ms
bRefresh 0
bSynchAddress 0
&lt;endpoint 1&gt;
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 (in 0x04)
bmAttributes 2 (bulk)
wMaxPacketSize 64
bInterval 0 ms
bRefresh 0
bSynchAddress 0
&lt;endpoint 2&gt;
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 (in 0x05)
bmAttributes 3 (interrupt)
wMaxPacketSize 8
bInterval 100 ms
bRefresh 0
bSynchAddress 0
</pre>
<h1>Want to add or correct information?</h1>
<p>
If anything is wrong or missing on this page please <a href="/bugs.html">file a bug report</a>
or use the <a href="http://www.meier-geinitz.de:80/tinc?key=rDoQ7lrj&#38;formname=adddev" target="_top">the
form for adding an unsupported device</a>.
</p>
<p>
If you own an unsupported scanner, please send as much information as
possible. Especially the output of <em>sane-find-scanner -v -v</em>
and/or <em>cat /proc/scsi/scsi</em> (for SCSI scanners) or <em>cat
/proc/bus/usb/devices</em> (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.
</p>
<h1><a href="/manufacturers.html">Information for Manufacturers</a></h1>
<p>
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 <a
href="/manufacturers.html">information for manufacturers</a>.
</p>
<h1>Links</h1>
<ul>
<li>
General information on how to <a href="/contrib.html">contribute to SANE</a>, e.g. by writing
backends
</li>
<li>
<a
href="/cgi-bin/driver.pl">Scanner
search engine</a>
</li>
<li>
<a href="http://www.sane-project.org/">SANE homepage</a>
</li>
</ul>
<hr>
<p>
<a href="/">SANE homepage</a><br>
<a href="/imprint.html">Contact</a>
</p>
<p>
<font size="-1">$Date$ $Author$</font>
</p>
</body>
</html>

166
unsupported/reflecta-proscan-4000.html 100644
Wyświetl plik

@ -0,0 +1,166 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Scanner information</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="author" content="Henning Meier-Geinitz">
<meta name="keywords" content="sane, backend, driver, scanner, unsupported">
<link href="mailto:henning@meier-geinitz.de" rev="made">
<link rel="icon" href="/favicon.ico" type="image/x-icon">
<link rel="shortcut icon" href="/favicon.ico" type="image/x-icon">
</head>
<body>
<h1>Scanners not supported by SANE</h1>
<h2>Manufacturer and model</h2>
<p>
Reflecta ProScan 4000
</p>
<h2>Bus type</h2>
<p>
USB, IEEE-1394
</p>
<h2>Vendor ID</h2>
<p>
0x05e3
</p>
<h2>Product ID</h2>
<p>
0x0143
</p>
<h2>Chipset</h2>
<p>
</p>
<h2>Comments</h2>
<p>
</p>
<h2>Output of /proc/bus/usb/devices or sane-find-scanner -v -v</h2>
<pre>
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
&lt;device descriptor of 0x05e3/0x0143 at 001:004&gt;
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
&lt;configuration 0&gt;
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0 ()
bmAttributes 192 (Self-powered)
MaxPower 10 mA
&lt;interface 0&gt;
&lt;altsetting 0&gt;
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255
bInterfaceSubClass 255
bInterfaceProtocol 255
iInterface 0 ()
&lt;endpoint 0&gt;
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 (in 0x01)
bmAttributes 2 (bulk)
wMaxPacketSize 64
bInterval 0 ms
bRefresh 0
bSynchAddress 0
&lt;endpoint 1&gt;
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 (out 0x02)
bmAttributes 2 (bulk)
wMaxPacketSize 64
bInterval 0 ms
bRefresh 0
bSynchAddress 0
&lt;endpoint 2&gt;
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
</pre>
<h1>Want to add or correct information?</h1>
<p>
If anything is wrong or missing on this page please <a href="/bugs.html">file a bug report</a>
or use the <a href="http://www.meier-geinitz.de:80/tinc?key=rDoQ7lrj&#38;formname=adddev" target="_top">the
form for adding an unsupported device</a>.
</p>
<p>
If you own an unsupported scanner, please send as much information as
possible. Especially the output of <em>sane-find-scanner -v -v</em>
and/or <em>cat /proc/scsi/scsi</em> (for SCSI scanners) or <em>cat
/proc/bus/usb/devices</em> (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.
</p>
<h1><a href="/manufacturers.html">Information for Manufacturers</a></h1>
<p>
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 <a
href="/manufacturers.html">information for manufacturers</a>.
</p>
<h1>Links</h1>
<ul>
<li>
General information on how to <a href="/contrib.html">contribute to SANE</a>, e.g. by writing
backends
</li>
<li>
<a
href="/cgi-bin/driver.pl">Scanner
search engine</a>
</li>
<li>
<a href="http://www.sane-project.org/">SANE homepage</a>
</li>
</ul>
<hr>
<p>
<a href="/">SANE homepage</a><br>
<a href="/imprint.html">Contact</a>
</p>
<p>
<font size="-1">$Date$ $Author$</font>
</p>
</body>
</html>