kopia lustrzana https://gitlab.com/sane-project/website
84 wiersze
3.8 KiB
HTML
84 wiersze
3.8 KiB
HTML
<!-- received="Fri Apr 10 08:57:55 1998 PDT" -->
|
|
<!-- sent="Fri, 10 Apr 1998 11:57:16 -0400 (EDT)" -->
|
|
<!-- name="Matto Marjanovic" -->
|
|
<!-- email="maddog@mir.com" -->
|
|
<!-- subject="Re: /proc/scsi/scsi" -->
|
|
<!-- id="m0yNgB2-000JAnC@yoo-hoo.ai.mit.edu" -->
|
|
<!-- inreplyto="/proc/scsi/scsi" -->
|
|
<title>sane-devel: Re: /proc/scsi/scsi</title>
|
|
<h1>Re: /proc/scsi/scsi</h1>
|
|
<b>Matto Marjanovic</b> (<a href="mailto:maddog@mir.com"><i>maddog@mir.com</i></a>)<br>
|
|
<i>Fri, 10 Apr 1998 11:57:16 -0400 (EDT)</i>
|
|
<p>
|
|
<ul>
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#101">[ date ]</a><a href="index.html#101">[ thread ]</a><a href="subject.html#101">[ subject ]</a><a href="author.html#101">[ author ]</a>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0102.html">Michael K. Johnson: "Re: /proc/scsi/scsi"</a>
|
|
<li> <b>Previous message:</b> <a href="0100.html">Damyan Pepper: "Artec and Scanner Documentation"</a>
|
|
<li> <b>Maybe in reply to:</b> <a href="0076.html">Oliver.Rauch@Wolfsburg.DE: "/proc/scsi/scsi"</a>
|
|
<!-- nextthread="start" -->
|
|
<li> <b>Next in thread:</b> <a href="0126.html">Oliver.Rauch@Wolfsburg.DE: "Re: /proc/scsi/scsi"</a>
|
|
<li> <b>Next in thread:</b> <a href="0102.html">Michael K. Johnson: "Re: /proc/scsi/scsi"</a>
|
|
<li> <b>Reply:</b> <a href="0126.html">Oliver.Rauch@Wolfsburg.DE: "Re: /proc/scsi/scsi"</a>
|
|
<!-- reply="end" -->
|
|
</ul>
|
|
<!-- body="start" -->
|
|
Mmmm... another problem with just looking at /proc/scsi/scsi is that<br>
|
|
not all scanners provide useful vendor/model strings. <br>
|
|
I don't know about others, but the Microtek scanners provide widely<br>
|
|
varying strings which often do not mention "MICROTEK", nor even the<br>
|
|
model of the scanner. The ID code in the backend looks at a number<br>
|
|
of different clues from the device inquiry to prove to itself that<br>
|
|
a device is indeed a Microtek scanner.<br>
|
|
<p>
|
|
Perhaps a another suggestion would be to just scan /proc/scsi/scsi for<br>
|
|
device *types* --- I don't know of any scanners that don't properly claim<br>
|
|
to be Device Type 0x06 (scanner). In 99% of the cases, there will be only<br>
|
|
one such device on the bus, and that will be the user's scanner. The list<br>
|
|
of such devices could be passed to any and all backends that want a hint.<br>
|
|
<p>
|
|
Then, perhaps the *.conf files could be made so that a device of "/dev/sgN"<br>
|
|
means look at that device explicitly, but "PROC_SCSI_HINTS" means call the<br>
|
|
/proc/scsi/scsi code and get a list of devices to check from there.<br>
|
|
<p>
|
|
Perhaps also, we could borrow the syntax used in Samba smb.conf files (as<br>
|
|
well as Win<gag> config files), and merge all the .conf files into one,<br>
|
|
with a [defaults] section, as well as sections for individual backends,<br>
|
|
as needed:<br>
|
|
<p>
|
|
[defaults]<br>
|
|
device = PROC_SCSI_HINTS<br>
|
|
<p>
|
|
[dll]<br>
|
|
umax<br>
|
|
pnm<br>
|
|
<p>
|
|
[microtek]<br>
|
|
disable-mode-sense-1<br>
|
|
<p>
|
|
<p>
|
|
and so on....<br>
|
|
<p>
|
|
<p>
|
|
-matt m.<br>
|
|
<p>
|
|
<p>
|
|
<pre>
|
|
--
|
|
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
|
|
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
|
|
</pre>
|
|
<!-- body="end" -->
|
|
<p>
|
|
<ul>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0102.html">Michael K. Johnson: "Re: /proc/scsi/scsi"</a>
|
|
<li> <b>Previous message:</b> <a href="0100.html">Damyan Pepper: "Artec and Scanner Documentation"</a>
|
|
<li> <b>Maybe in reply to:</b> <a href="0076.html">Oliver.Rauch@Wolfsburg.DE: "/proc/scsi/scsi"</a>
|
|
<!-- nextthread="start" -->
|
|
<li> <b>Next in thread:</b> <a href="0126.html">Oliver.Rauch@Wolfsburg.DE: "Re: /proc/scsi/scsi"</a>
|
|
<li> <b>Next in thread:</b> <a href="0102.html">Michael K. Johnson: "Re: /proc/scsi/scsi"</a>
|
|
<li> <b>Reply:</b> <a href="0126.html">Oliver.Rauch@Wolfsburg.DE: "Re: /proc/scsi/scsi"</a>
|
|
<!-- reply="end" -->
|
|
</ul>
|