Andrea Arcangeli (firstname.lastname@example.org)
Mon, 31 Aug 1998 18:08:34 +0200 (CEST)
On Mon, 31 Aug 1998, Alan Cox wrote:
>> Excuse me Alan, I can' t understand again :-( and I don' t understand the
>> differences between library and mid level driver very well :-((.
>Midlevel driver Library
> kernel kernel
> | |
> V V
> parport driver
> | |
> V V
> driver support code
Cool and clear ;-) Thanks.
>> parport_pc_irq() parport_ax_irq() but I can' t see real advantages. It
>> would be less clean I think.
>Yep now I've followed the code its a bit more sane than I first thought
>Surely its up to the hardware specific driver to check the irq and called
>parport_irq(port) if it decides there is an IRQ pending (indeed it may be
>just an inline to do port->cad->....)
So is this the semantic all you like?
the irq is generated from the parallel port can' t detect the IRQ
call parport_generic_irq() and then exit istant exit
I am reimplemented everything following this scheme now.
-- To unsubscribe, send mail to: email@example.com --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2.0b3 on Wed 30 Dec 1998 - 10:18:11 EST