kopia lustrzana https://gitlab.com/sane-project/website
103 wiersze
4.9 KiB
HTML
103 wiersze
4.9 KiB
HTML
<!-- received="Thu May 8 13:53:18 1997 MST" -->
|
|
<!-- sent="Thu, 8 May 1997 13:33:23 -0700" -->
|
|
<!-- name="David Mosberger-Tang" -->
|
|
<!-- email="davidm@azstarnet.com" -->
|
|
<!-- subject="Re: Mustek/Request-sense problems -> Solution?" -->
|
|
<!-- id="199705082033.NAA05734@panda.mosberger" -->
|
|
<!-- inreplyto="292247369436113352@toto.iv" -->
|
|
<title>sane-devel: Re: Mustek/Request-sense problems -> Solution?</title>
|
|
<h1>Re: Mustek/Request-sense problems -> Solution?</h1>
|
|
<b>David Mosberger-Tang</b> (<a href="mailto:davidm@azstarnet.com"><i>davidm@azstarnet.com</i></a>)<br>
|
|
<i>Thu, 8 May 1997 13:33:23 -0700</i>
|
|
<p>
|
|
<ul>
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#127">[ date ]</a><a href="index.html#127">[ thread ]</a><a href="subject.html#127">[ subject ]</a><a href="author.html#127">[ author ]</a>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0128.html">David Mosberger-Tang: "Re: sane-0.56 and hp"</a>
|
|
<li> <b>Previous message:</b> <a href="0126.html">Thomas Blume: "Re: Mustek/Request-sense problems -> Solution?"</a>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
</ul>
|
|
<!-- body="start" -->
|
|
<i>>>>>> On Thu, 8 May 1997 16:37:36 +0200, Thomas Blume <<a href="mailto:mblum1@tc9.uni-paderborn.de">mblum1@tc9.uni-paderborn.de</a>> said:</i><br>
|
|
<p>
|
|
Thomas> The results I obtain show the same effects as were mentioned<br>
|
|
Thomas> here with 3-pass scanning. But as lineart mode for faxing is<br>
|
|
Thomas> currently my main application, I didn't try to track it down<br>
|
|
Thomas> further.<br>
|
|
<p>
|
|
Hmmh, the only problem with 3-pass scanning at this point is a<br>
|
|
performance problem. The actual scanning works fine AFAIK. If you<br>
|
|
get horizontal stripes in the scanned images, then maybe we need to<br>
|
|
turn on the MUSTEK_FLAG_LD_MFS for your firmware revision as well.<br>
|
|
There is the following if-statement in mustek.c:attach():<br>
|
|
<p>
|
|
/* Revision 1.00 of the MFS-12000SP firmware is buggy and needs<br>
|
|
this workaround. Maybe others need it too, but this one is<br>
|
|
for sure. We know for certain that revision 1.02 or newer<br>
|
|
has this bug fixed. */<br>
|
|
if (fw_revision < 0x102)<br>
|
|
dev->flags |= MUSTEK_FLAG_LD_MFS;<br>
|
|
<p>
|
|
If you get horizontal strips, could you change the "< 0x102" into "<=<br>
|
|
0x102" and let me know whether that fixes the problem (I'd recommend<br>
|
|
to do a "make clean" in the SANE root directory and then "make" and<br>
|
|
"make install" after making this change---just to be on the safe<br>
|
|
side).<br>
|
|
<p>
|
|
Thomas> I assume that all device independent sense keys are covered<br>
|
|
Thomas> by the kernel correctly, so only device specific keys have<br>
|
|
Thomas> to be checked. In case of sg_header all the information is<br>
|
|
Thomas> provided in req->hdr.sense_buffer and could be checked in<br>
|
|
Thomas> sanei_scsi_cmd. For<br>
|
|
Thomas> ioctl I think that the sense buffer could also be obtained<br>
|
|
Thomas> after the call, but I'm not sure. Perhaps one could call a<br>
|
|
Thomas> backend specific function pointer for parsing if sense key<br>
|
|
Thomas> != NO_SENSE && valid.<br>
|
|
<p>
|
|
What I did is change the SANEI_SCSI interface so you can optionally<br>
|
|
register a sense-handler callback that can be used to translate the<br>
|
|
sense-buffer info into a reasonable SANE status-code. This enables<br>
|
|
the Mustek backend to translate a pretty meaning less "MEDIA ERROR"<br>
|
|
into "scanner cover open." So, I think this is a flexible solution<br>
|
|
that doesn't burden backends that don't need/want to deal with sense<br>
|
|
info (such as the HP backend).<br>
|
|
<p>
|
|
Thomas> BTW: there exists another version of the bundled DTC3181.<br>
|
|
<p>
|
|
Somehow, this doesn't surprise me at all...<br>
|
|
<p>
|
|
Thomas> It<br>
|
|
Thomas> has only 1 jumper for wait, the PNR/PNP jumper is missing.<br>
|
|
<p>
|
|
Can somebody explain to me what Plug-and-Run is as opposed to<br>
|
|
Plug-and-Play? I'm not really all that wired into the pc-world.<br>
|
|
<p>
|
|
Thomas> I<br>
|
|
Thomas> could not manage to get it to work with Linux, but this<br>
|
|
Thomas> rubbish part is not worth any more efforts. With NT4.0<br>
|
|
Thomas> finally Mustek provides a working driver for it, but this<br>
|
|
Thomas> card effectively turns NT into a single tasking OS.<br>
|
|
<p>
|
|
;-))<br>
|
|
<p>
|
|
Yeah, I definitively think $50 for an ncr810 controller is money well<br>
|
|
spent.<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="0128.html">David Mosberger-Tang: "Re: sane-0.56 and hp"</a>
|
|
<li> <b>Previous message:</b> <a href="0126.html">Thomas Blume: "Re: Mustek/Request-sense problems -> Solution?"</a>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
</ul>
|