sane-project-website/old-archive/1997-02/0125.html

77 wiersze
4.0 KiB
HTML

<!-- received="Wed May 7 18:29:29 1997 MST" -->
<!-- sent="Wed, 7 May 1997 18:16:40 -0700" -->
<!-- name="David Mosberger-Tang" -->
<!-- email="davidm@azstarnet.com" -->
<!-- subject="Re: Mustek/Request-sense problems -&gt; Solution?" -->
<!-- id="199705080116.SAA31292@panda.mosberger" -->
<!-- inreplyto="199705072350.BAA02959@nightshift.uni-paderborn.de" -->
<title>sane-devel: Re: Mustek/Request-sense problems -&gt; Solution?</title>
<h1>Re: Mustek/Request-sense problems -&gt; Solution?</h1>
<b>David Mosberger-Tang</b> (<a href="mailto:davidm@azstarnet.com"><i>davidm@azstarnet.com</i></a>)<br>
<i>Wed, 7 May 1997 18:16:40 -0700</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#125">[ date ]</a><a href="index.html#125">[ thread ]</a><a href="subject.html#125">[ subject ]</a><a href="author.html#125">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0126.html">Thomas Blume: "Re: Mustek/Request-sense problems -&gt; Solution?"</a>
<li> <b>Previous message:</b> <a href="0124.html">Thomas Blume: "Mustek/Request-sense problems -&gt; Solution?"</a>
<li> <b>In reply to:</b> <a href="0124.html">Thomas Blume: "Mustek/Request-sense problems -&gt; Solution?"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0126.html">Thomas Blume: "Re: Mustek/Request-sense problems -&gt; Solution?"</a>
<!-- reply="end" -->
</ul>
<!-- body="start" -->
<i>&gt;&gt;&gt;&gt;&gt; On Thu, 8 May 1997 01:50:01 +0200, Thomas Blume &lt;<a href="mailto:mblum1@nightshift.uni-paderborn.de">mblum1@nightshift.uni-paderborn.de</a>&gt; said:</i><br>
<p>
Thomas&gt; In mustek.c request_sense is called explicitly after some<br>
Thomas&gt; commands as indicated in Mustek's Control-Flow document. As<br>
Thomas&gt; far as I understand the SCSI drafts (SCSI-1, SCSI-2) the<br>
Thomas&gt; sense data are valid only for a limited number of cases,<br>
Thomas&gt; e.g. the command prior to request_sense returns<br>
Thomas&gt; CHECK_CONDITION. These cases are handled already by the<br>
Thomas&gt; low-level drivers in the kernel, so the additional<br>
Thomas&gt; request_sense issued by mustek.c cannot be guaranteed to<br>
Thomas&gt; retrieve valid sense data.<br>
<p>
You're absolutely right.<br>
<p>
Thomas&gt; At least with the above mentioned combo scanning (NOT color<br>
Thomas&gt; scanning) works perfectly after inserting a dummy routine<br>
Thomas&gt; instead of request_sense.<br>
<p>
Are you saying you're having problems with color scanning? I think<br>
Andy has the same scanner type (slightly different firmware, though)<br>
and I thought things work fine for him.<br>
<p>
Thomas&gt; Maybe a function for parsing sense data should be hooked<br>
Thomas&gt; directly to sanei_scsi_cmd, or the valid bit of sense data<br>
Thomas&gt; should be checked.<br>
<p>
I'm downloading the SCSI specs as I'm writing this. I have some ideas<br>
on how to handle this, but want to check the specs first.<br>
<p>
Thomas&gt; Please fix me if I'm wrong, but since it works for me now, I<br>
Thomas&gt; suspect, that the additional request_sense was in fact the<br>
Thomas&gt; source for my problems.<br>
<p>
It works for my controller (ncr810) as well.<br>
<p>
--david<br>
<p>
<pre>
--
Source code, list archive, and docs: <a href="http://www.azstarnet.com/~axplinux/sane/">http://www.azstarnet.com/~axplinux/sane/</a>
To unsubscribe: mail -s unsubscribe <a href="mailto:sane-devel-request@listserv.azstarnet.com">sane-devel-request@listserv.azstarnet.com</a>
</pre>
<!-- body="end" -->
<p>
<ul>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0126.html">Thomas Blume: "Re: Mustek/Request-sense problems -&gt; Solution?"</a>
<li> <b>Previous message:</b> <a href="0124.html">Thomas Blume: "Mustek/Request-sense problems -&gt; Solution?"</a>
<li> <b>In reply to:</b> <a href="0124.html">Thomas Blume: "Mustek/Request-sense problems -&gt; Solution?"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0126.html">Thomas Blume: "Re: Mustek/Request-sense problems -&gt; Solution?"</a>
<!-- reply="end" -->
</ul>