fffdd26a90
can look at the ACPI tables. If the startup fails, we panic and tell the user to try rebooting with ACPI disabled. Previously in this case we would try to use $PIR interrupt routing which only works for the atpic while using the apic to handle interrupts which would result in misrouted interrupts and a hang at boot time with no error message. - Read the SCI out of the FADT instead of hardcoding 9 when checking to see if an interrupt override entry is for the SCI. - Try to work around some BIOS brain damage for the SCI's programming by forcing the SCI to be level triggered and active low if it is routed to a non-ISA interrupt (greater than 15) or if it is identity mapped with edge trigger and active high polarity. This should fix some of the hangs with device apic and ACPI that some people see. Reviewed by: njl |
||
---|---|---|
.. | ||
acpi_machdep.c | ||
acpi_toshiba.c | ||
acpi_wakecode.S | ||
acpi_wakeup.c | ||
genwakecode.sh | ||
madt.c | ||
Makefile | ||
OsdEnvironment.c |