![]() | |||||||||||||
Messages in this thread |
Brandon Philips wrote: > On 01:47 Sat 09 Sep 2006, Brice Goglin wrote: >> Do we have Brandon lspci so that I can see if any of the MSI quirks is >> involved? > > 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03) > 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) (prog-if 00 [Normal decode]) > 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02) (prog-if 00 [Normal decode]) > 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02) (prog-if 00 [Normal decode]) > 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02) (prog-if 00 [Normal decode]) > 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) (prog-if 01 [Subtractive decode]) > There is no MSI quirk for these chipsets, MSI work fine on Intel. Let me know if your dichotomy leads to one of the following patches: 1) gregkh-pci-msi-cleanup-existing-msi-quirks.patch 2) gregkh-pci-msi-factorize-common-code-in-pci_msi_supported.patch 3) gregkh-pci-msi-export-the-pci_bus_flags_no_msi-flag-in-sysfs.patch 4) gregkh-pci-msi-blacklist-pci-e-chipsets-depending-on-hypertransport-msi-capability.patch 5) fix-gregkh-pci-msi-blacklist-pci-e-chipsets-depending-on-hypertransport-msi-capability.patch (only (1) and (2) should be relevant here) thanks, Brice - 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/ | ||||||||||||
| Last update: 2006-09-09 06:21 [from the cache] ©2003-2008 | |||||||||||||