On Wed, Dec 19, 2007 at 05:17:46PM -0500, [EMAIL PROTECTED] wrote: > OVERVIEW > ======= > > The patches should be applied in sequence to obviate any > possible build problems. > > The patch-set was built against 2.6.24-rc5 > > Description > =========== > > There exist devices that do not respond correctly to PCI > MMCONFIG accesses in x86 platforms.
What devices are these? Do you have reports of them somewhere? > This patch-set detects the problem by comparing an MMCONFIG > read to a Legacy PCI config read of the vendor/device dword > of every device discovered during the PCI probing sequence. > > A miscompare means that a device does not correctly respond > to MMCONFIG accesses. When the patch code detects this condition, > the bus that serves this device, and all subordinate buses, will > be programmed to use Legacy PCI Config accesses. > > This patch-set DOES NOT detect devices that generate machine > checks against MMCONFIG accesses. For such systems, > "pci=nommconf" is required in the boot command. That sounds like this patchset can cause bad side affects on hardware that currently works just fine. That is not a good thing to be adding to the kernel, right? thanks, greg k-h -- 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/
