summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorJonathan Nieder <jrnieder@gmail.com>2012-02-28 11:51:10 -0700
committerJesse Barnes <jbarnes@virtuousgeek.org>2012-02-28 11:09:09 -0800
commit8411371709610c826bf65684f886bfdfb5780ca1 (patch)
tree7d536d5fb26e39d1c86ce776a0b46cf3a585d483 /README
parent1cc1c96c1658bfaf85d06d764bd7ac00640ae90f (diff)
downloadop-kernel-dev-8411371709610c826bf65684f886bfdfb5780ca1.zip
op-kernel-dev-8411371709610c826bf65684f886bfdfb5780ca1.tar.gz
x86/PCI: use host bridge _CRS info on MSI MS-7253
In the spirit of commit 29cf7a30f8a0 ("x86/PCI: use host bridge _CRS info on ASUS M2V-MX SE"), this DMI quirk turns on "pci_use_crs" by default on a board that needs it. This fixes boot failures and oopses introduced in 3e3da00c01d0 ("x86/pci: AMD one chain system to use pci read out res"). The quirk is quite targetted (to a specific board and BIOS version) for two reasons: (1) to emphasize that this method of tackling the problem one quirk at a time is a little insane (2) to give BIOS vendors an opportunity to use simpler tables and allow us to return to generic behavior (whatever that happens to be) with a later BIOS update In other words, I am not at all happy with having quirks like this. But it is even worse for the kernel not to work out of the box on these machines, so... Reference: https://bugzilla.kernel.org/show_bug.cgi?id=42619 Reported-by: Svante Signell <svante.signell@telia.com> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud