> No. Linux guarantees that YOUR interrupt will not occur. This means
> that you have free reign about your own device (the ncr8xx). However
> if you cannot tolerate being interrupted for a few microseconds, (e.g.
> if the device has a microsecond timeout after writing a "low word")
> you can opt for running the whole interrupt routine with interrupts
> off to keep things "consistent".
I didn't realize my question and lame BIOS would spark such a lively
debate. Anyone care to guess which is the best way to procede? Make the
NCR driver use slow interrupts? Make the Tulip driver use fast ones? Try
to somehow force them onto different IRQ's without the BIOS's help?
Note...I'm looking for a solution usable with 2.0.x. A possible solution
requiring 2.1.x has already been suggested, but I'd rather not go there
yet.
------------------------------------------------------------------
Jon Lewis <jlewis@fdt.net> | Unsolicited commercial e-mail will
Network Administrator | be proof-read for $199/message.
Florida Digital Turnpike |
______http://inorganic5.fdt.net/~jlewis/pgp for PGP public key____
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu