sane-project-website/old-archive/1998-04/0098.html

82 wiersze
3.8 KiB
HTML

<!-- received="Fri Apr 10 04:36:06 1998 PDT" -->
<!-- sent="Fri, 10 Apr 1998 11:27:13 +0200 (MET DST)" -->
<!-- name="Oliver.Rauch@Wolfsburg.DE" -->
<!-- email="Oliver.Rauch@Wolfsburg.DE" -->
<!-- subject="Re: /proc/scsi/scsi" -->
<!-- id="199804100927.LAA00659@Babylon5.wolfsburg.de" -->
<!-- inreplyto="Pine.LNX.3.94.980409211622.793A-100000@pinguin.seebaer.ruhr.de" -->
<title>sane-devel: Re: /proc/scsi/scsi</title>
<h1>Re: /proc/scsi/scsi</h1>
<a href="mailto:Oliver.Rauch@Wolfsburg.DE"><i>Oliver.Rauch@Wolfsburg.DE</i></a><br>
<i>Fri, 10 Apr 1998 11:27:13 +0200 (MET DST)</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#98">[ date ]</a><a href="index.html#98">[ thread ]</a><a href="subject.html#98">[ subject ]</a><a href="author.html#98">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0099.html">Hugo van der Kooij: "Re: sane-0.72 and mustek 600 II N"</a>
<li> <b>Previous message:</b> <a href="0097.html">mrada: "Re: Plustek OP4800 and Sane ?"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0189.html">Sean Reifschneider: "Re: /proc/scsi/scsi"</a>
<li> <b>Reply:</b> <a href="0189.html">Sean Reifschneider: "Re: /proc/scsi/scsi"</a>
<!-- reply="end" -->
</ul>
<!-- body="start" -->
Hi Bernd,<br>
<p>
<i>&gt; &gt; I am writing a little routine that reads /proc/scsi/scsi</i><br>
<i>&gt; &gt; and tries to find out on which device the scanner is connected.</i><br>
<i>&gt; </i><br>
<i>&gt; Why you don't use the scsi inquiry command on /dev/sg* ? Is there any</i><br>
<i>&gt; problem that I do not see?</i><br>
<i>&gt; </i><br>
<i>&gt; I have written (stolen ;-) a very short program under linux that uses the</i><br>
<i>&gt; scsi generic devices /dev/sg* and lists the scsi inquiry result like the</i><br>
<i>&gt; following example:</i><br>
<i>&gt; </i><br>
<i>&gt; &gt; scsiinfo /dev/sg0</i><br>
<i>&gt; QUANTUM LP240S GM240S01X6.4 040392 142231934661</i><br>
<i>&gt; device is loaded</i><br>
<i>&gt; </i><br>
<i>&gt; &gt; scsiinfo /dev/sg1</i><br>
<i>&gt; QUANTUM LPS540S 590008/05/93185331053867</i><br>
<i>&gt; device is loaded</i><br>
<i>&gt; </i><br>
<i>&gt; Could this solve the problem?</i><br>
<p>
I know that possibilty, we already have a tool "find scanner"<br>
that does exactly the same, but it is not very nice to ask<br>
all scsi-devices for their vendor, model and type when you start<br>
a scan-program.<br>
Some systems use the scsi-ids as device-numbers, but on<br>
other systems linke linux you only have /dev/sg0-9 or sth. like that<br>
because there are not enough major and minor device numbers to<br>
give all possible devices their own major and minor numbers.<br>
In /proc/scsi/scsi there is a list which scsi-hardware is connected<br>
to /dev/sg* (or /dev/uk* ...).<br>
<p>
So if that works, we can enter e.g. a "UMAX" "UMAX 12-S"<br>
in the config-files for the backends instead of /dev/sg2<br>
and if you turn on your cd-burner that shifts your scanner<br>
from /dev/sg2 to /dev/sg3, the backend will find it automatically<br>
without scanning the scsi-bus for it!<br>
<p>
Bye<br>
Oliver<br>
<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="0099.html">Hugo van der Kooij: "Re: sane-0.72 and mustek 600 II N"</a>
<li> <b>Previous message:</b> <a href="0097.html">mrada: "Re: Plustek OP4800 and Sane ?"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0189.html">Sean Reifschneider: "Re: /proc/scsi/scsi"</a>
<li> <b>Reply:</b> <a href="0189.html">Sean Reifschneider: "Re: /proc/scsi/scsi"</a>
<!-- reply="end" -->
</ul>