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

[Geert U. <ge...@li...>]

On Sun, 29 Sep 2002, Ken Tyler wrote:
> Secondly, does each device drivers's interrupt handler need to check the
> dev_id parameter that's passed to determine if the interrupt is from/for
> that device ?

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().

> (Reading the two interrupt status registers of the 53c710 has side effects
> with or without pending interrupts)

I'm afraid you do have to use the interrupt status registers of the 53c710. How
else to find out that it was the 53c710 or some other device that posted the
interrupt?

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

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds