Shane,
I had a very similar situation. Speed was also a consideration for me.
parport in 2.2.x doesn't use the hardware epp (or ecp?) handshanks and is
thus considerably slower. Our "driver" talks to the parallel port
hardware directly - the "ioperm and inb/outb" solution. To get
interrupts, we wrote a very simple kernel module - your user program opens
a device file, and does a read. The read blocks until an interrupt occurs.
That's about it.
If that sound useful to you, I could post the kernel module and some
outline of our driver code.
We get very good throughput - using 32 bit writes we can output data at a
1 MB/s using a SIIG parallel pro dual isa card.
I haven't done any testing of the latentcy between interrupt occuring and
the return of the user program - that hasn't been very important here.
Carl
> I am new to kernel programming and especially new to parallel programming
> under Linux. I am wondering if anyone can point me in the direction of
> information regarding using the parport driver under Linux? Basically what
> I need to do is write a driver for a custom parallel device. It is
> interrupt driven so I'm told that I must write a kernel based interrupt
> handler. Since parport seems to provide much of the functions I will use,
> I'd rather use it than write my own module from the ground up. Is there any
> programming documentation out there or a simple driver I could read to give
> me some clues on where to begin?
-- 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 2b29 : Tue Mar 28 2000 - 20:36:54 EST