Messages in this thread | | | Subject | Re: ncr53c8xx + tulip IRQ sharing | Date | Tue, 17 Feb 1998 13:55:52 +0100 (MET) | From | (Rogier Wolff) |
| |
Doug Ledford wrote: > > 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.
> I'm not sure about Rogier's comments in regards to 2.1.z, but in > regards to 2.0.x, your interrupt handler will never get called more > than once regardless of the flags in use. The difference is that > with the SA_INTERRUPT flag, your handler is called with global > interrupts disabled (cli() state) and upon return the sti() state is > restored and the irq is ended without any further activity. This > means that there is no bottom half [....]
The ncr driver in 2.0.33 would work without the SA_INTERRUPT flag, when you change the two "#if 0" into "#if 1" in the ..._intr routine.
My guess is that it is probably also safe without that change too, but I haven't tested that.
Roger.
-- If it's there and you can see it, it's REAL |___R.E.Wolff@BitWizard.nl | If it's there and you can't see it, it's TRANSPARENT | Tel: +31-15-2137555 | If it's not there and you can see it, it's VIRTUAL |__FAX:_+31-15-2138217 | If it's not there and you can't see it, it's GONE! -- Roy Wilks, 1983 |_____|
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |