> We still don't know how the interrupt got generated in the parallel port,
> but IMO it would be better to handle the case where there is an interrupt
> pending for the device we are going to irq-probe.
When we disable irqs (nAck- or nFault-triggered), a currently-active
interrupt line causes another interrupt to be generated, to avoid races.
It sounds like that's what's happening, in which case there I don't think
there's really a lot we can do about it.
Tim.
*/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/