This is probably a good model for most scanners, since the task division
appears to separate an I/O intensive task (acquiring the scan data) from a
CPU intensive task (whatever processes the sane_read() data... often a
compression task).
Tom Davis
-----Original Message-----
From: Frederik Ramm [mailto:frederik@remote.org]
Sent: Wednesday, February 28, 2001 10:23 AM
To: sane-devel@mostang.com
Subject: Backend: When to use reader process?
Hi,
I've noticed that the driver I am basing my M3091 work on, the
M3096 driver which was in turn derived from the Coolscan driver, uses
a separate process for reading data from the scanner, which is then
fed via a pipe file descriptor to sane_read.
Other drivers (like the Bell+Howell backend I've been looking at for
duplex inspiration) don't use a separate process.
Which would be the preferred way to implement it for a max. 15ppm ADF
scanner?
Bye
Frederik
-- Frederik Ramm ## eMail frederik@remote.org ## N57°48.10' W005°40.32'-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Wed Feb 28 2001 - 08:34:50 PST