kopia lustrzana https://gitlab.com/sane-project/website
118 wiersze
5.3 KiB
HTML
118 wiersze
5.3 KiB
HTML
<!-- received="Sun Feb 28 09:01:31 1999 PST" -->
|
|
<!-- sent="Sun, 28 Feb 1999 12:12:40 +0100 (MET)" -->
|
|
<!-- name="becka@rz.uni-duesseldorf.de" -->
|
|
<!-- email="becka@rz.uni-duesseldorf.de" -->
|
|
<!-- subject="Re: Info Peripherals' ImageReaderISA" -->
|
|
<!-- id="m10H49I-000CFmC@hades.beck-sw.de" -->
|
|
<!-- inreplyto="3.0.5.32.19990227110453.007b5350@mindspring.com" -->
|
|
<title>sane-devel: Re: Info Peripherals' ImageReaderISA</title>
|
|
<h1>Re: Info Peripherals' ImageReaderISA</h1>
|
|
<a href="mailto:becka@rz.uni-duesseldorf.de"><i>becka@rz.uni-duesseldorf.de</i></a><br>
|
|
<i>Sun, 28 Feb 1999 12:12:40 +0100 (MET)</i>
|
|
<p>
|
|
<ul>
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#223">[ date ]</a><a href="index.html#223">[ thread ]</a><a href="subject.html#223">[ subject ]</a><a href="author.html#223">[ author ]</a>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0224.html">David Mosberger-Tang: "Re: Porting SANE backends"</a>
|
|
<li> <b>Previous message:</b> <a href="0222.html">Milon Firikis: "Re: Porting SANE backends"</a>
|
|
<li> <b>In reply to:</b> <a href="0201.html">Dennis Putnam: "Info Peripherals' ImageReaderISA"</a>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
</ul>
|
|
<!-- body="start" -->
|
|
HI !<br>
|
|
<p>
|
|
<i>> As I understand the supported devices list, the subject scanner is not</i><br>
|
|
<i>> supported by 'sane'. However, I have a couple of generic questions</i><br>
|
|
<i>> that I can't seem to get from the documentation which apparenly</i><br>
|
|
<i>> assumes a lot of knowledge on the part of the reader. </i><br>
|
|
<p>
|
|
Then we should improve the docs ... Suggestions welcome.<br>
|
|
<p>
|
|
<i>> 1) It appears that 'sane' expects the Linux kernel to recognize the</i><br>
|
|
<i>> device, correct? </i><br>
|
|
<p>
|
|
No. SANE supports mostly SCSI scanners, which due to the SCSI standard<br>
|
|
have a method to query the devicetype.<br>
|
|
<p>
|
|
Thus the Linux kernel "recognizes" the device as some generic SCSI device<br>
|
|
with some vendor name given to it:<br>
|
|
<p>
|
|
Host: scsi1 Channel: 00 Id: 06 Lun: 00<br>
|
|
Vendor: MUSTEK Model: MFS-12000SP Rev: 1.00<br>
|
|
Type: Scanner ANSI SCSI revision: 01<br>
|
|
<p>
|
|
The Linux kernel has no idea of how to actually talk to the scanner.<br>
|
|
That knowledge is in the SANE drivers.<br>
|
|
<p>
|
|
<i>> If so then where and how are the device drivers added? </i><br>
|
|
<p>
|
|
Directly in the SANE source. <br>
|
|
<p>
|
|
<i>> Are the supported device drivers 'modprobe'd in (i.e. 'modprobe</i><br>
|
|
<i>> sane-xxxx') or is there some kernel option I missed that brings in</i><br>
|
|
<i>> drivers? </i><br>
|
|
<p>
|
|
No. For the SCSI devices, you need support for the SCSI adapter and<br>
|
|
for "generic SCSI support" in the kernel. The scanner driver itself<br>
|
|
runs userspace from within SANE.<br>
|
|
This may be a little different for other types of scanners, but usually<br>
|
|
you do not need a per-scanner-type module for the kernel. Scanners with<br>
|
|
proprietary adapter cards, like many handscanners, would be different<br>
|
|
in that respect.<br>
|
|
<p>
|
|
<i>> Am I confusing the backend drivers with device drivers and if</i><br>
|
|
<i>> so where does one get the device drivers if not included in the 'sane'</i><br>
|
|
<i>> distribution?</i><br>
|
|
<p>
|
|
They are in there. You need the SCSI-generic support, and that's it.<br>
|
|
The backend _is_ the driver.<br>
|
|
<p>
|
|
<i>> 2) Where is the documentation for defining /dev/scanner? </i><br>
|
|
<p>
|
|
There is none, because :<br>
|
|
<p>
|
|
<i>> I assume there probably is a symbolic link to the real /dev but how </i><br>
|
|
<i>> is it created and how is it identified? </i><br>
|
|
<p>
|
|
ln -sf /dev/sg?? /dev/scanner<br>
|
|
<p>
|
|
The appropriate dev/sg is identified by looking at /proc/scsi/scsi.<br>
|
|
Count the entries, _all_ of them, starting at '0' or 'a' depending<br>
|
|
on how your distribution names them (RedHat has both), and finding <br>
|
|
the entry that comes from the scanner, like above.<br>
|
|
<p>
|
|
<i>> 3) Since the ImageReader is TWAIN compliant is there not a generic</i><br>
|
|
<i>> TWAIN backend that should work with TWAIN compliant scanners? Or is</i><br>
|
|
<i>> TWAIN an insufficiently defined standard to actually allow a generic</i><br>
|
|
<i>> software solution?</i><br>
|
|
<p>
|
|
TWAIN isn't sane. Not at all. TWAIN defines how Win or Mac programs call<br>
|
|
a scanner driver. The main API call is something like "bring up some nice<br>
|
|
dialog, ask for user input, do the scan and give me the result".<br>
|
|
<p>
|
|
So TWAIN says _nothing_ about the HW-Protocol.<br>
|
|
<p>
|
|
CU, ANdy<br>
|
|
<p>
|
|
<pre>
|
|
--
|
|
= Andreas Beck | Email : <<a href="mailto:andreas.beck@ggi-project.org">andreas.beck@ggi-project.org</a>> =
|
|
======== GGI - The Right Thing To Do : <a href="http://www.ggi-project.org/">http://www.ggi-project.org/</a> ========
|
|
<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="0224.html">David Mosberger-Tang: "Re: Porting SANE backends"</a>
|
|
<li> <b>Previous message:</b> <a href="0222.html">Milon Firikis: "Re: Porting SANE backends"</a>
|
|
<li> <b>In reply to:</b> <a href="0201.html">Dennis Putnam: "Info Peripherals' ImageReaderISA"</a>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
</ul>
|