Re: [Fwd: Re: [PATCH 0/5]PCI: x86 MMCONFIG]
- From: Tony Camuso <tcamuso@xxxxxxxxxx>
- Date: Thu, 20 Dec 2007 20:42:21 -0500
Robert Han*** 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [Fwd: Re: [PATCH 0/5]PCI: x86 MMCONFIG]
- From: Bhavana Nagendra
- Re: [Fwd: Re: [PATCH 0/5]PCI: x86 MMCONFIG]
- References:
- Re: [Fwd: Re: [PATCH 0/5]PCI: x86 MMCONFIG]
- From: Robert Han***
- Re: [Fwd: Re: [PATCH 0/5]PCI: x86 MMCONFIG]
- From: Tony Camuso
- Re: [Fwd: Re: [PATCH 0/5]PCI: x86 MMCONFIG]
- Prev by Date: Linux 2.6.24-rc6
- Next by Date: Re: Trailing periods in kernel messages
- Previous by thread: Re: [Fwd: Re: [PATCH 0/5]PCI: x86 MMCONFIG]
- Next by thread: Re: [Fwd: Re: [PATCH 0/5]PCI: x86 MMCONFIG]
- Index(es):