Eric W. Biederman wrote:
"Adam Kropelin" <[email protected]> writes:
Can I get the corresponding lspci -xxx output. I suspect the BIOS
did not program the hypertransport MSI mapping capabilities
correctly. All it has to do is set the enable but still,
occasionally BIOS writers miss the most amazing things.
Here you go. This is from 2.6.20-rc7.
Thanks. Conclusion. I could not find bit 16 (the enable bit) set in
any of your hypertransport msi mapping capabilities.
So MSI interrupts won't work until someone enables your chipset
to transform them into hypertransport interrupts.
Naive question... Can the pci layer (or e1000) detect that MSI is not
enabled in the hardware and avoid using it in that case? With the number
of MSI problems showing up it seems risky to assume it's usable on any
given platform without some sort of sanity check.
--Adam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
