aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/console
diff options
context:
space:
mode:
authorJonathan Nieder <jrnieder@gmail.com>2012-02-28 11:51:10 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-04-13 08:14:07 -0700
commit06bcd9526cab45751fe74466064d41211b3b45d6 (patch)
treeded6ce3712ff8446818cca1ba8c021a6f87f5890 /Documentation/console
parentd13149924c357cbdb4ce577f17ace9bee927d4ed (diff)
downloadkernel_samsung_espresso10-06bcd9526cab45751fe74466064d41211b3b45d6.zip
kernel_samsung_espresso10-06bcd9526cab45751fe74466064d41211b3b45d6.tar.gz
kernel_samsung_espresso10-06bcd9526cab45751fe74466064d41211b3b45d6.tar.bz2
x86/PCI: use host bridge _CRS info on MSI MS-7253
commit 8411371709610c826bf65684f886bfdfb5780ca1 upstream. 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> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/console')
0 files changed, 0 insertions, 0 deletions