Re: [PARPORT] User level custom ECP protocols -- where do I start?


Tim Waugh (twaugh@redhat.com)
Tue, 8 Feb 2000 15:53:58 -0500 (EST)


On Tue, 8 Feb 2000, Greg Nelson wrote:

> 1) Can a "user mode" parallel port driver be written as an
> application, or does it have to be built as a kernel module in

Yes, it can. It won't necessarily be fast enough though. :-( For ECP,
you're in with a chance, since the kernel can do a lot of it for you.

> A) Sample application code which manipulates the new /dev/parport
> device through ioctls or other means to read and write data over
> ECP.

There's some here:
http://www.cyberelk.demon.co.uk/parport/deviceid-0.1.tar.gz. I've got
another small demo app that I'll try to remember to dig out tomorrow.

> B) A list of exposed parport ioctls and what they do.
>
> C) A kernel source code file which implements the ioctls from which
> I can derive this (I don't know my way around the kernel source
> code hierarchy well enough to know where to look for this
> needle-in-a-haystack.)

It's in drivers/char/ppdev.c. I haven't finished writing the
documentation yet.

Tim.
*/

-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --



This archive was generated by hypermail 2.0b3 on Tue 08 Feb 2000 - 15:56:01 EST