kopia lustrzana https://gitlab.com/sane-project/website
130 wiersze
4.8 KiB
HTML
130 wiersze
4.8 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
|
|||
|
"http://www.w3.org/TR/REC-html40/loose.dtd">
|
|||
|
<HTML>
|
|||
|
<HEAD>
|
|||
|
<TITLE>sane-devel: Re: Acer620UT</TITLE>
|
|||
|
<META NAME="Author" CONTENT="Oliver Schwartz (Oliver.Schwartz@gmx.de)">
|
|||
|
<META NAME="Subject" CONTENT="Re: Acer620UT">
|
|||
|
</HEAD>
|
|||
|
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
|
|||
|
<H1>Re: Acer620UT</H1>
|
|||
|
<!-- received="Sun Jul 30 05:08:29 2000" -->
|
|||
|
<!-- isoreceived="20000730120829" -->
|
|||
|
<!-- sent="Sun, 30 Jul 2000 13:50:55 +0200" -->
|
|||
|
<!-- isosent="20000730115055" -->
|
|||
|
<!-- name="Oliver Schwartz" -->
|
|||
|
<!-- email="Oliver.Schwartz@gmx.de" -->
|
|||
|
<!-- subject="Re: Acer620UT" -->
|
|||
|
<!-- id="00073014175401.00493@oliverspc" -->
|
|||
|
<!-- inreplyto="3982BA12.94967F50@coppice.org" -->
|
|||
|
<STRONG>From:</STRONG> Oliver Schwartz (<A HREF="mailto:Oliver.Schwartz@gmx.de?Subject=Re:%20Acer620UT&In-Reply-To=<00073014175401.00493@oliverspc>"><EM>Oliver.Schwartz@gmx.de</EM></A>)<BR>
|
|||
|
<STRONG>Date:</STRONG> Sun Jul 30 2000 - 04:50:55 PDT
|
|||
|
<P>
|
|||
|
<!-- next="start" -->
|
|||
|
<LI><STRONG>Next message:</STRONG> <A HREF="0250.html">Daniel Gr<47>fe: "Gimp-Plugin: GIMP support missing"</A>
|
|||
|
<UL>
|
|||
|
<LI><STRONG>Previous message:</STRONG> <A HREF="0248.html">Oliver Schwartz: "Re: Acer620UT"</A>
|
|||
|
<LI><STRONG>In reply to:</STRONG> <A HREF="0242.html">Steve Underwood: "Re: Acer620UT"</A>
|
|||
|
<!-- nextthread="start" -->
|
|||
|
<LI><STRONG>Next in thread:</STRONG> <A HREF="0247.html">Paul Nixon: "Re: Acer620UT"</A>
|
|||
|
<!-- reply="end" -->
|
|||
|
<LI><STRONG>Messages sorted by:</STRONG>
|
|||
|
<A HREF="date.html#249">[ date ]</A>
|
|||
|
<A HREF="index.html#249">[ thread ]</A>
|
|||
|
<A HREF="subject.html#249">[ subject ]</A>
|
|||
|
<A HREF="author.html#249">[ author ]</A>
|
|||
|
</UL>
|
|||
|
<HR NOSHADE><P>
|
|||
|
<!-- body="start" -->
|
|||
|
<P>
|
|||
|
Hi,
|
|||
|
<BR>
|
|||
|
|
|||
|
<BR>
|
|||
|
<EM>> I wasn't sure what to do about the USB code when I updated the snapscan driver for
|
|||
|
</EM><BR>
|
|||
|
<EM>> colour correction. Iwanted to merge everyone's latest goodies, but I had no way to
|
|||
|
</EM><BR>
|
|||
|
<EM>> test them. I merged the parts of the USB which go into the other files, and the
|
|||
|
</EM><BR>
|
|||
|
<EM>> transparency patch, since they were pretty minor, and made sense in relation to
|
|||
|
</EM><BR>
|
|||
|
<EM>> the rest of the driver. If you find the whole thing runs acceptably with a 620UT
|
|||
|
</EM><BR>
|
|||
|
<EM>> its probably time to stuff the remaining elements of the USB update - the actual
|
|||
|
</EM><BR>
|
|||
|
<EM>> USB interface itself - into CVS.
|
|||
|
</EM><BR>
|
|||
|
<P>The code works for me. It isn't bullet proof and still has a lot of problems
|
|||
|
<BR>
|
|||
|
related to it. The main problem I recognize is that it requires a lot of
|
|||
|
<BR>
|
|||
|
manual interaction:
|
|||
|
<BR>
|
|||
|
(1) modify code (or supply an option during compilation)
|
|||
|
<BR>
|
|||
|
(2) fiddle with kernel modules
|
|||
|
<BR>
|
|||
|
(3) upload firmware.
|
|||
|
<BR>
|
|||
|
<P>(1) prevents the code from being usable in binary distributions,
|
|||
|
<BR>
|
|||
|
(2) may change with kernel 2.4 and more wide-spread USB,
|
|||
|
<BR>
|
|||
|
(3) would require some smart algorithm that recognises the scanner and uploads
|
|||
|
<BR>
|
|||
|
the apropriate firmware file.
|
|||
|
<BR>
|
|||
|
<P>The USB code itself is pretty simple, as far as I can see. It more or less
|
|||
|
<BR>
|
|||
|
sends the raw SCSI commands to the USB interface. As far as I know this is also
|
|||
|
<BR>
|
|||
|
done in other backends (hp?), so maybe it would make sense to have a common
|
|||
|
<BR>
|
|||
|
sane USB layer. This would probably solve (1).
|
|||
|
<BR>
|
|||
|
<P>As far as firmware is concerned I don't know if other backends need firmware
|
|||
|
<BR>
|
|||
|
uploads as well. If so a common solution would probably make sense.
|
|||
|
<BR>
|
|||
|
<P>However, as a first step I think it would make sense to put all USB related
|
|||
|
<BR>
|
|||
|
files (snapscan-usb.*, acerfirm, agfafirm) into CVS so that people who want to
|
|||
|
<BR>
|
|||
|
try USB don't have to get them from 3 different sources.
|
|||
|
<BR>
|
|||
|
<P>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?Subject=Re:%20Acer620UT&In-Reply-To=<00073014175401.00493@oliverspc>">majordomo@mostang.com</A>
|
|||
|
</PRE>
|
|||
|
<P><!-- body="end" -->
|
|||
|
<HR NOSHADE>
|
|||
|
<UL>
|
|||
|
<!-- next="start" -->
|
|||
|
<LI><STRONG>Next message:</STRONG> <A HREF="0250.html">Daniel Gr<47>fe: "Gimp-Plugin: GIMP support missing"</A>
|
|||
|
<LI><STRONG>Previous message:</STRONG> <A HREF="0248.html">Oliver Schwartz: "Re: Acer620UT"</A>
|
|||
|
<LI><STRONG>In reply to:</STRONG> <A HREF="0242.html">Steve Underwood: "Re: Acer620UT"</A>
|
|||
|
<!-- nextthread="start" -->
|
|||
|
<LI><STRONG>Next in thread:</STRONG> <A HREF="0247.html">Paul Nixon: "Re: Acer620UT"</A>
|
|||
|
<!-- reply="end" -->
|
|||
|
<LI><STRONG>Messages sorted by:</STRONG>
|
|||
|
<A HREF="date.html#249">[ date ]</A>
|
|||
|
<A HREF="index.html#249">[ thread ]</A>
|
|||
|
<A HREF="subject.html#249">[ subject ]</A>
|
|||
|
<A HREF="author.html#249">[ author ]</A>
|
|||
|
</UL>
|
|||
|
<!-- trailer="footer" -->
|
|||
|
<HR NOSHADE>
|
|||
|
<P>
|
|||
|
<SMALL>
|
|||
|
<EM>
|
|||
|
This archive was generated by <A HREF="http://www.hypermail.org/">hypermail 2b29</A>
|
|||
|
: <EM>Sun Jul 30 2000 - 05:08:45 PDT</EM>
|
|||
|
</EM>
|
|||
|
</SMALL>
|
|||
|
</BODY>
|
|||
|
</HTML>
|