sane-project-website/old-archive/1999-12/0080.html

80 wiersze
4.0 KiB
HTML

<!-- received="Wed Dec 8 15:59:49 1999 PST" -->
<!-- sent="Wed, 8 Dec 1999 16:00:26 -0800 (PST)" -->
<!-- name="Mathew sienko x7439" -->
<!-- email="msienko@galaxy.nsc.com" -->
<!-- subject="Re: Volunteer for back end development - excellent info in this msg" -->
<!-- id="199912090000.QAA14367@sodium.nsc.com" -->
<!-- inreplyto="Pine.LNX.4.10.9912081627490.2875-100000@draconix.natinst.com" -->
<title>sane-devel: Re: Volunteer for back end development - excellent info in this msg</title>
<h1>Re: Volunteer for back end development - excellent info in this msg</h1>
<b>Mathew sienko x7439</b> (<a href="mailto:msienko@galaxy.nsc.com"><i>msienko@galaxy.nsc.com</i></a>)<br>
<i>Wed, 8 Dec 1999 16:00:26 -0800 (PST)</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#80">[ date ]</a><a href="index.html#80">[ thread ]</a><a href="subject.html#80">[ subject ]</a><a href="author.html#80">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0081.html">David Paschal: "Re: Volunteer for back end development - excellent info in this msg"</a>
<li> <b>Previous message:</b> <a href="0079.html">David E. Nelson: "Volunteer for back end development - excellent info in this msg"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>
<!-- body="start" -->
Hi David,<br>
<p>
I'm glad to see that you are still interested. If you do plan on experamenting,<br>
then perhaps I should what I've been thinking about. I haven't actually<br>
started working on this yet because we've been quite buisy lately, but<br>
I hope to start soon. <br>
<p>
The merlin chips are all controlled through a register file and everything<br>
is done by reading or writing these registers. The datasheet describes<br>
these registers. The backend should then have two parts: functions to <br>
read and write these registers, and then the SANE API implementation that<br>
actually uses these functions to controll the scanner. This way, the <br>
interface can change and all the SANE API's can still be used. (Future<br>
versions of merlin may use a different interface, but this is still too<br>
far away to tell.) My first goal is to be able to read and write one <br>
register at a time. If I get any work done on this, I'll post it to <br>
the sane mailing list.<br>
<p>
I also have a question that I am hoping you will be able to answer. In<br>
SANE, the back-ends can be built as shared libraries so that an application<br>
can easily change back-ends. Would it be easy (or possible) to separate<br>
the two functionalities I mentioned above into two separate library files?<br>
Also, can an application load and unload these back-end libraries while<br>
it is running? I think this would be cool because then an application <br>
could launch that is not tied to a specific scanner and the user could<br>
choose which driver to use and, for the merlin driver, choose the I/O <br>
interface if necessary.<br>
<p>
Matt<br>
<i>&gt; </i><br>
<i>&gt; </i><br>
<i>&gt; Hi Mathew,</i><br>
<i>&gt; </i><br>
<i>&gt; I really dropped the ball on this one. I had hoped to 'experiment' with</i><br>
<i>&gt; my 4200 using the pdf docs from NatSemi...just havn't had time to sit down</i><br>
<i>&gt; with it. I've forward this to the sane-devel list since that should be</i><br>
<i>&gt; the best source for developers. I did ask Peter if he could recommend</i><br>
<i>&gt; anyone and noone came to his mind.</i><br>
<i>&gt; </i><br>
<i>&gt; Regards,</i><br>
<i>&gt; /\/elson</i><br>
<i>&gt; </i><br>
<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="0081.html">David Paschal: "Re: Volunteer for back end development - excellent info in this msg"</a>
<li> <b>Previous message:</b> <a href="0079.html">David E. Nelson: "Volunteer for back end development - excellent info in this msg"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>