becka@rz.uni-duesseldorf.de said:
> If you are using SANE, you probably do so already. Most backends are
> implemented to spawn off a reader process, which communicates with the
> main (control) process via a pipe.
Well, I'm not currently using SANE. I accept that if I am using a frontend
like GIMP then I have no right to expect 300DPI color images to go wizzing
by 2 per second.
However, I want to be able to write SANE front-ends that can drive my
back-end at those sorts of rates. I have put considerable effort into
making sure the kernel mode device driver does *not* copy lots of image
buffers around (app mmaps the image buffer which the card can access
via DMA) and I don't want to see a SANE standard that does gratuitous
copies.
-- Steve Williams "The woods are lovely, dark and deep. steve@icarus.com But I have promises to keep, steve@picturel.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com