fork of 9front i guess
af8657b8da
when we hit a conflict where the pci INTL register gives us a different irq than we get from southbridge irq router, dont just change the router setting to the bios assigned irq (that was previously known as the BIOS workarround), but assume the southbridge setting to be valid and change the pci INTL register on the device to it. only when the router link doesnt seem to be configured or disabled, then program the router to the irq that bios asisgned in the INTL register. the reason is that changing the router setting changes the irq routing for *all* devices on the same link and changing it breaks previously checked and valid interrupt routings. (so happend with virtualbox where the last device on the bus is some powermanagement device that has wrong INTL setting and changing the routing breaks the ethernet interrupts) this change shouldnt affect modern machines which use ioapic and mp tables or acpi for pci interrupt routing. |
||
|---|---|---|
| 386 | ||
| 68000 | ||
| 68020 | ||
| acme | ||
| adm/timezone | ||
| alpha | ||
| amd64 | ||
| arm | ||
| lib | ||
| mips | ||
| power | ||
| power64 | ||
| rc | ||
| sparc | ||
| sparc64 | ||
| sys | ||
| .hgignore | ||