Messages in this thread | | | Date | Sat, 17 Jun 2006 12:15:34 -0400 | From | Brice Goglin <> | Subject | Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities |
| |
Alistair John Strachan wrote: > On Saturday 17 June 2006 04:01, Brice Goglin wrote: > > I tried your patch on 2.6.17-rc6 (fixed up a view rejects) in an attempt to > get MSI working with my forcedeth NIC, which advertises the capability. The > kernel now gives me the following: >
Well, the aim of my patch is to stop enabling MSI by default, and try to find out when we can and when we cannot use MSI. 2.6.17 will only disable MSI on a few chipsets. My patch will disable on all chipsets but Intel and those having Hypertransport MSI capabilities (Serverworks HT2000 and nVidia CK804). Thus, you cannot expect MSI to be enabled with my patch if it was not before :/
> PCI: Found MSI HT mapping on 0000:00:0b.0 > PCI: Found MSI HT mapping on 0000:00:00.0 > PCI: MSI quirk detected. PCI_BUS_FLAGS_MSI set for 0000:00:0b.0 subordinate > bus. > PCI: Found MSI HT mapping on 0000:00:0c.0 > PCI: Found MSI HT mapping on 0000:00:00.0 > PCI: MSI quirk detected. PCI_BUS_FLAGS_MSI set for 0000:00:0c.0 subordinate > bus. > PCI: Found MSI HT mapping on 0000:00:0d.0 > PCI: Found MSI HT mapping on 0000:00:00.0 > PCI: MSI quirk detected. PCI_BUS_FLAGS_MSI set for 0000:00:0d.0 subordinate > bus. > PCI: Found MSI HT mapping on 0000:00:0e.0 > PCI: Found MSI HT mapping on 0000:00:00.0 > PCI: MSI quirk detected. PCI_BUS_FLAGS_MSI set for 0000:00:0e.0 subordinate > bus. >
If your board is behind one of these bridges, MSI could work (looks like you have 4 nVidia CK804 with MSI enabled in the Hypertransport mapping).
> pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:0b.0:pcie00] > Allocate Port Service[0000:00:0b.0:pcie03] >
It might be the reason why MSI does not work. But I am not familiar with this code, so I can't help, sorry.
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/
| |