Re: irqs and last_ipl[2] already set ...

[Ken T. <ke...@we...>]

On Sun, 29 Sep 2002, Geert Uytterhoeven wrote:

> On Sun, 29 Sep 2002, Ken Tyler wrote:

Hello,

> The main interrupt handler doesn't know for which device the interrupt is
> meant. It just calls all registered device interrupt handlers for that
> interrupt chain with the corresponding dev_id parameter, as passed to
> request_irq().

I eventually figured this out, each drivers interrupt handler gets called
but only with the correct dev_id for that device's handler, from the
irq_desc and ircaction structures.  For each PORTS and EXTERN interrupt,
every handler on that interrupt's list gets 'tried'. 

> How do they handle the side effects on other architectures? Or do they always
> have the 53c710 on its own interrupt line?

I don't know why the 53c7xx driver works for the A4000T and Blizzard
accelerators but not for the A4091.  Probably nothing to do with
interrupts but I have to start (again) somewhere.

Any ideas on the Last ipl[] messages ?

Thanks, Ken.