Tony Camuso wrote:
Robert Hancock wrote:
First off, I would like to see confirmation from the horses's mouths
here (namely AMD, ServerWorks/Broadcom, and whoever else) that there
is no other way to get around this problem than disabling MMCONFIG
for accesses behind those chips.
And here are the excerpts from that page of the spec which are salient
to the present discussion:
----------------------------------------------------------------------
The base configuration space of the AMD-8132 and PCI(-X) devices
attached to it are accessible using only
the mechanism defined in PCI 2.3. Registers of PCI-X Mode 2 devices
attached to the AMD-8132 in the
extended configuration space are not accessible. The AMD-8132 has no
registers in the extended
configuration space.
Fix Planned
No
Prarit, Tony et al, this is as official as it gets. It's pretty
clearly stated.
Bhavana
--
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]
