Messages in this thread | | | Date | Mon, 31 Aug 1998 15:33:11 -0500 (CDT) | From | "Andre M. Hedrick" <> | Subject | Re: APIC IO changes in 2.1.118. |
| |
Why can't we do something as simple as auto black_lists? Am I being over simplistic? If so, flag for 82371AB PIIX4 and set it global for anything with this device.
Cheers, Andre
struct ioapic_list_entry __initdata ioapic_irq9_blacklist [] = {
{ "INTEL " , "DK440LX " }, { 0 , 0 } };
static int __init ioapic_irq9_blacklisted(void) { return in_ioapic_list(ioapic_irq9_blacklist); }
[snip]
{ printk("ENABLING IO-APIC IRQs\n"); if (ioapic_irq9_blacklisted()) { io_apic_irqs = ~((1<<2)|(1<<9)|(1<<13)); } else { io_apic_irqs = ~((1<<2)|(1<<13)); } } else { [snip] > Perhaps this snippet from the Intel MB site may help - > > IRQ9 cannot be re-assigned > > IRQ9 is not available to assign to > ISA add-in cards because it is > dedicated to the power > management function of the PIIX4 > controller on the motherboard. > This is true for other motherboards > which use the 82371AB PIIX4 > component. >
Why can't we do something as simple as auto black_lists?
- 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.altern.org/andrebalsa/doc/lkml-faq.html
| |