On Feb 9, 2008 1:30 PM, ron minnich <[EMAIL PROTECTED]> wrote: > I thought ACPI was a superset of _MP_. I have a friend who claims not: > > "0xffffffffffff0390 A P I C > Local APIC Address 0xfee00000, flags 0x00000001 > type 0, length 8 > ACPI Processor ID 1 > APIC ID 0 > Flags 0x00000001 > type 0, length 8 > ACPI Processor ID 2 > APIC ID 1 > Flags 0x00000001 > type 0, length 8 > ACPI Processor ID 3 > APIC ID 2 > Flags 0x00000001 > type 0, length 8 > ACPI Processor ID 4 > APIC ID 3 > Flags 0x00000001 > type 1, length 12 > I/O APIC ID 4 > I/O APIC Address 0xfec00000 > Global System Interrupt Base 0x00000000 > type 1, length 12 > I/O APIC ID 5 > I/O APIC Address 0xfe6fe000 > Global System Interrupt Base 0x00000018 > type 1, length 12 > I/O APIC ID 6 > I/O APIC Address 0xfe6ff000 > Global System Interrupt Base 0x0000001c > type 2, length 10 > IRQ 0 > Global System Interrupt 0x00000002 > Flags 0x0000 > type 2, length 10 > IRQ 0 > Global System Interrupt 0x00000002 > Flags 0x0000 > > > there's not enough info there to actually do anything." > > > Is he missing something? Is this old information? I'd like to know.
you are right. for irq routing: ACPI: need madt + dsdt NON ACPI: need mptable current linux kernel seem could use lapic from ACPI MADT, and other irq routing for device from MPTABLE...never tried... don't think it will work other than AMD 8111/8131 platform YH -- coreboot mailing list [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
