mirror
/
sane-project-website
kopia lustrzana https://gitlab.com/sane-project/website
1
0
Forkuj 0
Kod Zgłoszenia Projekty Wydania Wiki Aktywność
sane-project-website/old-archive/2001-02/0240.html

193 wiersze
7.7 KiB
HTML
Czysty Zwykły widok Historia

Import old-archive/ for static website generation purposes
2018-02-17 07:25:17 +00:00
<!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: Fujitsu fi-4750C Backend Project</TITLE>
<META NAME="Author" CONTENT="Davis, Tom (Tom.Davis@minolta-qms.com)">
<META NAME="Subject" CONTENT="RE: Fujitsu fi-4750C Backend Project">
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<H1>RE: Fujitsu fi-4750C Backend Project</H1>
<!-- received="Tue Feb 27 12:02:44 2001" -->
<!-- isoreceived="20010227200244" -->
<!-- sent="Tue, 27 Feb 2001 14:15:01 -0600" -->
<!-- isosent="20010227201501" -->
<!-- name="Davis, Tom" -->
<!-- email="Tom.Davis@minolta-qms.com" -->
<!-- subject="RE: Fujitsu fi-4750C Backend Project" -->
<!-- id="3D0DF647212CD411B0990008C786947C76585E@qms-ex01" -->
<!-- inreplyto="Fujitsu fi-4750C Backend Project" -->
<STRONG>From:</STRONG> Davis, Tom (<A HREF="mailto:Tom.Davis@minolta-qms.com?Subject=RE:%20Fujitsu%20fi-4750C%20Backend%20Project&In-Reply-To=&lt;3D0DF647212CD411B0990008C786947C76585E@qms-ex01&gt;"><EM>Tom.Davis@minolta-qms.com</EM></A>)<BR>
<STRONG>Date:</STRONG> Tue Feb 27 2001 - 12:15:01 PST
<P>
<!-- next="start" -->
<LI><STRONG>Next message:</STRONG> <A HREF="0241.html">Steven Ellis: "Re: Ivina 1200U"</A>
<UL>
<LI><STRONG>Previous message:</STRONG> <A HREF="0239.html">Frederik Ramm: "Duplex (was: Fujitsu M3091 backend)"</A>
<LI><STRONG>Maybe in reply to:</STRONG> <A HREF="0233.html">Davis, Tom: "Fujitsu fi-4750C Backend Project"</A>
<!-- nextthread="start" -->
<LI><STRONG>Next in thread:</STRONG> <A HREF="0243.html">Randolph Bentson: "Re: Fujitsu fi-4750C Backend Project"</A>
<!-- reply="end" -->
<LI><STRONG>Messages sorted by:</STRONG>
<A HREF="date.html#240">[ date ]</A>
<A HREF="index.html#240">[ thread ]</A>
<A HREF="subject.html#240">[ subject ]</A>
<A HREF="author.html#240">[ author ]</A>
</UL>
<HR NOSHADE><P>
<!-- body="start" -->
<P>
Frederik,
<BR>
<P>I am currently studying the SANE API, so I don't know SANE well yet. I
<BR>
understand what the problem is, but need to get a little further before I
<BR>
know how it might be handled. I can't really contribute to the conversation
<BR>
until I get a little further in study.
<BR>
<P>I did something similar in a pSOS environment a few years ago where I wrote
<BR>
a driver that supported multiple Fujitsu scanners. The sets of allowable
<BR>
resolutions, color depths, etc. were simply keyed off the Vendor and Model
<BR>
strings that ultimately come from the SCSI Inquiry command. This info was
<BR>
stored in the SCSI low-level (chip level)driver after the inquiry and could
<BR>
be handed back to the higher layers when asked for. In this case, I would
<BR>
expect the SANE backend for Fujitsu scanners to parse the Vendor:Model
<BR>
strings and then hand back capabilities info from an internally stored
<BR>
scanner specific set that matches. I would try very hard NOT to use
<BR>
#ifdef's. Instead I would try to add small amount of switch() logic with
<BR>
cases for each supported scanner. Should have minimal performance impact.
<BR>
<P>NOTE: Just received Oliver Rauch email with duplex suggestion... seems at
<BR>
first like the proper approach. I'll just follow the thread until I know
<BR>
more...
<BR>
<P>Thanks for your comments,
<BR>
Tom Davis
<BR>
<P><P>-----Original Message-----
<BR>
From: Frederik Ramm [mailto:<A HREF="mailto:frederik@remote.org?Subject=RE:%20Fujitsu%20fi-4750C%20Backend%20Project&In-Reply-To=&lt;3D0DF647212CD411B0990008C786947C76585E@qms-ex01&gt;">frederik@remote.org</A>]
<BR>
Sent: Tuesday, February 27, 2001 12:03 PM
<BR>
To: <A HREF="mailto:sane-devel@mostang.com?Subject=RE:%20Fujitsu%20fi-4750C%20Backend%20Project&In-Reply-To=&lt;3D0DF647212CD411B0990008C786947C76585E@qms-ex01&gt;">sane-devel@mostang.com</A>
<BR>
Subject: Re: Fujitsu fi-4750C Backend Project
<BR>
<P><P>Hi Tom,
<BR>
<P><EM>&gt; In case there is any interest... I have begun writing a backend for the
</EM><BR>
<EM>&gt; Fujitsu fi-4750C scanner. (As this is a low-volume duplex &quot;production&quot;
</EM><BR>
color
<BR>
<EM>&gt; scanner, I doubt there will be much interest.)
</EM><BR>
<P>Seems you're in a similar position to me. What do you think you'll do
<BR>
about the duplex thing? The suggestion to buffer one full page might
<BR>
be viable... although it's a shame, the Windows software that came
<BR>
with the scanner supported duplex out-of-the-box.
<BR>
<P><EM>&gt; Which brings up a general question... Since most of the Fujitsu scanners
</EM><BR>
<EM>&gt; that I have been exposed to in the past have very similar SCSI command
</EM><BR>
sets,
<BR>
<EM>&gt; shouldn't we try to merge the functionality of the &quot;sp15c&quot;, m3096g&quot;,
</EM><BR>
&quot;m3091&quot;
<BR>
<EM>&gt; (re: post by Frederik Ramm), and whatever I produce for the &quot;fi-4750C&quot;.
</EM><BR>
<P>I'd love to. But how do we handle things like different allowable
<BR>
resolutions, different maximum page sizes, and so on. It wouldn't be a
<BR>
problem to produce one source code file that, using &quot;#ifdef&quot;s, can
<BR>
produce three or four different drivers, but what options would we
<BR>
have if we were to try producing one single driver. An extra
<BR>
parameter, &quot;--model&quot;, maybe - but how would we communicate to the SANE
<BR>
front-ends that certain settings e.g. of the &quot;resolution&quot; parameter
<BR>
are only available if the &quot;model&quot; parameter has been set to something
<BR>
specific? I doubt the current mechanism supports that.
<BR>
<P><EM>&gt; With that in mind, I will 'try' to make my enhancements to a
</EM><BR>
<EM>&gt; &quot;m3096g&quot; base keeping the original functionality unaffected.
</EM><BR>
<P>I won't bother since it's all a &quot;draft&quot; anyway. The main work will be
<BR>
figuring out *how* it works, and once I've got that, I'll be willing
<BR>
and able to build m3091 support into any clean, combined driver. I
<BR>
hope .-)
<BR>
<P>Bye
<BR>
Frederik
<BR>
<P><PRE>
--
Frederik Ramm ## eMail <A HREF="mailto:frederik@remote.org?Subject=RE:%20Fujitsu%20fi-4750C%20Backend%20Project&In-Reply-To=&lt;3D0DF647212CD411B0990008C786947C76585E@qms-ex01&gt;">frederik@remote.org</A> ## N57<35>48.10' W005<30>40.32'
<P><P>--
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:%20Fujitsu%20fi-4750C%20Backend%20Project&In-Reply-To=&lt;3D0DF647212CD411B0990008C786947C76585E@qms-ex01&gt;">majordomo@mostang.com</A>
<P><P>--
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:%20Fujitsu%20fi-4750C%20Backend%20Project&In-Reply-To=&lt;3D0DF647212CD411B0990008C786947C76585E@qms-ex01&gt;">majordomo@mostang.com</A>
</PRE>
<P><!-- body="end" -->
<HR NOSHADE>
<UL>
<!-- next="start" -->
<LI><STRONG>Next message:</STRONG> <A HREF="0241.html">Steven Ellis: "Re: Ivina 1200U"</A>
<LI><STRONG>Previous message:</STRONG> <A HREF="0239.html">Frederik Ramm: "Duplex (was: Fujitsu M3091 backend)"</A>
<LI><STRONG>Maybe in reply to:</STRONG> <A HREF="0233.html">Davis, Tom: "Fujitsu fi-4750C Backend Project"</A>
<!-- nextthread="start" -->
<LI><STRONG>Next in thread:</STRONG> <A HREF="0243.html">Randolph Bentson: "Re: Fujitsu fi-4750C Backend Project"</A>
<!-- reply="end" -->
<LI><STRONG>Messages sorted by:</STRONG>
<A HREF="date.html#240">[ date ]</A>
<A HREF="index.html#240">[ thread ]</A>
<A HREF="subject.html#240">[ subject ]</A>
<A HREF="author.html#240">[ 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>Tue Feb 27 2001 - 12:03:59 PST</EM>
</EM>
</SMALL>
</BODY>
</HTML>