kopia lustrzana https://gitlab.com/sane-project/website
71 wiersze
3.1 KiB
HTML
71 wiersze
3.1 KiB
HTML
<!-- received="Tue Mar 10 06:52:16 1998 PST" -->
|
|
<!-- sent="Tue, 10 Mar 1998 15:52:30 +0100" -->
|
|
<!-- name="Didier Carlier" -->
|
|
<!-- email="carlierd@acm.org" -->
|
|
<!-- subject="Re: Microtek woes" -->
|
|
<!-- id="199803101452.PAA16771@fritz.sema.be" -->
|
|
<!-- inreplyto="199803100616.BAA18507@yoo-hoo.ai.mit.edu" -->
|
|
<title>sane-devel: Re: Microtek woes</title>
|
|
<h1>Re: Microtek woes</h1>
|
|
<b>Didier Carlier</b> (<a href="mailto:carlierd@acm.org"><i>carlierd@acm.org</i></a>)<br>
|
|
<i>Tue, 10 Mar 1998 15:52:30 +0100</i>
|
|
<p>
|
|
<ul>
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#73">[ date ]</a><a href="index.html#73">[ thread ]</a><a href="subject.html#73">[ subject ]</a><a href="author.html#73">[ author ]</a>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0074.html">Dewey Cheatem & Howe: "Support for UMAX scanners"</a>
|
|
<li> <b>Previous message:</b> <a href="0072.html">Dr. Giovanni A. Orlando: "OfficeJet Pro 1150C Linux drivers .."</a>
|
|
<li> <b>In reply to:</b> <a href="0064.html">Matto Marjanovic: "Microtek woes"</a>
|
|
<!-- nextthread="start" -->
|
|
<li> <b>Next in thread:</b> <a href="0082.html">Stefano Buelow: "Re: Microtek woes"</a>
|
|
<!-- reply="end" -->
|
|
</ul>
|
|
<!-- body="start" -->
|
|
<a href="mailto:maddog@mir.com">maddog@mir.com</a> said:<br>
|
|
<i>> I've been looking into why the Microtek backend has suddenly started </i><br>
|
|
<i>> dying with sane-0.71.... </i><br>
|
|
<p>
|
|
With some scanners (the coolscan is one) the only way to check whether the <br>
|
|
device is busy is to sent it the 'test unit ready' to which the reply is <br>
|
|
'check condition'. You then issue the request sense command and the returned <br>
|
|
sensed data contain codes saying that the scanner is busy. The request sense <br>
|
|
is issued by the kernel itself, not by sane (or the backend).<br>
|
|
<p>
|
|
In this case, the sanei_scsi_cmd did not return SANE_BUSY because although the <br>
|
|
kernel does return sensed data, it does not return an error code.<br>
|
|
<p>
|
|
The patch that was introduced in sane-0.71 fixes this by calling the backend <br>
|
|
'sense handler' whenever sensed data is returned, even when the kernel didn't <br>
|
|
return an error code.<br>
|
|
<p>
|
|
This behaviour shows up on Linux and (I think) on SGI.<br>
|
|
<p>
|
|
<p>
|
|
In short, if a scanner returns a 'check condition' to a 'test unit ready' when <br>
|
|
it is busy, then the backend (sense handler) must be prepared to handle it. <br>
|
|
This was not the case prior to sane-0.71.<br>
|
|
<p>
|
|
Didier<br>
|
|
<br>
|
|
<p>
|
|
<p>
|
|
<p>
|
|
<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="0074.html">Dewey Cheatem & Howe: "Support for UMAX scanners"</a>
|
|
<li> <b>Previous message:</b> <a href="0072.html">Dr. Giovanni A. Orlando: "OfficeJet Pro 1150C Linux drivers .."</a>
|
|
<li> <b>In reply to:</b> <a href="0064.html">Matto Marjanovic: "Microtek woes"</a>
|
|
<!-- nextthread="start" -->
|
|
<li> <b>Next in thread:</b> <a href="0082.html">Stefano Buelow: "Re: Microtek woes"</a>
|
|
<!-- reply="end" -->
|
|
</ul>
|