Andrea Arcangeli (arcangeli@mbox.queen.it)
Mon, 31 Aug 1998 10:47:42 +0200 (CEST)
On Sun, 30 Aug 1998, Philip Blundell wrote:
>>No. _In_Linux_ 2.1.119 is the arch specific irq code that has to know
>>everything about the irq and to ack the irq when it will happen and _then_
>>to recall the irq handler. The device driver has not to know how to ack an
>>irq to the irq controller.
>
>Imagine a system where you have to acknowledge the irq explicitly by writing
>to the parallel port controller (or whatever the device is that's generating
>the interrupt). The irq.c code can't do this because it doesn't know the
>details of every device -- it doesn't even know _which_ device is generating
>the interrupt.
Ok, you convinced me for some other reasons too (now I have understood
better everything so reject my latest proposed patch). The new one will
allow the lowlevel parport driver to wrap the pardevice irq handler.
Andrea[s] Arcangeli
-- 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 Wed 30 Dec 1998 - 10:18:10 EST