Messages in this thread | | | Date | Sun, 15 Feb 1998 18:40:24 -0500 (EST) | From | Jon Lewis <> | Subject | Re: ncr53c8xx + tulip IRQ sharing |
| |
On Sun, 15 Feb 1998, Gerard Roudier wrote:
> It seems that all scsi interrupts are requested using (SHIRQ | > SA_INTERRUPT) flags (assumed to be fast), and that all network > interrupts are requested using (SHIRQ) (assumed to be less fast). > So, an IRQ cannot be shared by scsi and network.
Just about. I found that the de4x5.c driver will try with SHIRQ, and if that fails, then try with SHIRQ|SA_INTERRUPT. Unfortunately, later in the comments, it says this is an ugly hack, you shouldn't really use it, and it might cause problems on a busy system. Well...the systems I want PCI net cards in are our news server and a future squid server. Both qualify as pretty busy.
Barring a BIOS upgrade, which AIR says isn't happening, is there any way to force PCI devices to use different IRQs?
------------------------------------------------------------------ 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
| |