From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
linux-pci@vger.kernel.org,
Svante Signell <svante.signell@telia.com>
Subject: Re: [PATCH] x86/PCI: use host bridge _CRS info on MSI MS-7253
Date: Tue, 28 Feb 2012 11:09:42 -0800 [thread overview]
Message-ID: <20120228110942.3eb0cbdc@jbarnes-desktop> (raw)
In-Reply-To: <20120228185110.16227.58753.stgit@bhelgaas.mtv.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
On Tue, 28 Feb 2012 11:51:10 -0700
Bjorn Helgaas <bhelgaas@google.com> wrote:
> From: Jonathan Nieder <jrnieder@gmail.com>
>
> 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...
Applied to my for-linus branch, thanks.
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-28 19:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 18:51 [PATCH] x86/PCI: use host bridge _CRS info on MSI MS-7253 Bjorn Helgaas
2012-02-28 18:55 ` Bjorn Helgaas
2012-02-28 19:09 ` Jesse Barnes [this message]
2012-02-28 21:31 ` [PATCH] x86/PCI: do not tie MSI MS-7253 use_crs quirk to BIOS version Jonathan Nieder
2012-02-28 21:35 ` Bjorn Helgaas
2012-03-01 18:57 ` Jesse Barnes
2012-03-02 4:25 ` Jonathan Nieder
2012-04-09 23:47 ` [3.0.y, 3.2.y, 3.3.y] " Jonathan Nieder
2012-04-09 23:50 ` Jonathan Nieder
2012-04-10 23:00 ` Greg Kroah-Hartman
2012-04-11 1:41 ` Jonathan Nieder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120228110942.3eb0cbdc@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=bhelgaas@google.com \
--cc=jrnieder@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=svante.signell@telia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).