On Fri, 27 May 2011 14:59:39 +0800 Shaohua Li <shaohua.li@xxxxxxxxx> wrote: > direct access is needed in mmconf mode too. There are two reasons: > 1. we need it to access first 256 bytes. We have bug before that > using mmconf to access pci config space hangs system (when > resizing BARs) > 2. when doing mmconfg bar checking, we need access ACPI _CRS, > which might access PCI config space. > > Signed-off-by: Shaohua Li <shaohua.li@xxxxxxxxx> > > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig > index 880fcb6..90e50d9 100644 > --- a/arch/x86/Kconfig > +++ b/arch/x86/Kconfig > @@ -1907,7 +1907,7 @@ config PCI_BIOS > # x86-64 doesn't support PCI BIOS access from long mode so always go direct. > config PCI_DIRECT > def_bool y > - depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC)) > + depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC || PCI_GOMMCONFIG)) > > config PCI_MMCONFIG > def_bool y Applied to linux-next, thanks. -- Jesse Barnes, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
