Messages in this thread | | | From | Andrew de Quincey <> | Subject | Re: [ACPI] Re: Fixing USB interrupt problems with ACPI enabled | Date | Thu, 4 Sep 2003 03:15:09 +0100 |
| |
On Wednesday 03 September 2003 23:37, Chris Wright wrote: > * Nakajima, Jun (jun.nakajima@intel.com) wrote: > > Doing this for Len, who is on vacation. We would like to thank the > > people who provided debugging info such as acpidmp, dmidecode, and > > demsg. This is one of our findings, and we believe this would fix some > > interrupt problems (with USB, for example) with ACPI enabled, especially > > when the dmesg reads like: > > > > ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 0 > > ACPI: PCI Interrupt Link [ALKB] enabled at IRQ 0 > > ACPI: PCI Interrupt Link [ALKC] enabled at IRQ 0 > > ACPI: PCI Interrupt Link [ALKD] enabled at IRQ 0 > > > > Basically we assumed that _CRS returned the one we set with _SRS, when > > setting up a PCI interrupt link device, but that's not the case with > > some AML codes. Some of them always return 0. > > Attached is a patch against 2.4.23-pre1. It should be easy to apply this > > to 2.6.
Wow! This is exactly the idea I've just come up with for VIA boards!
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |