From: Andi Kleen <ak@suse.de>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>,
Len Brown <len.brown@intel.com>
Subject: Re: [patch 2.6.13] x86: check host bridge when applying vendor quirks
Date: Fri, 9 Sep 2005 04:47:09 +0200 [thread overview]
Message-ID: <200509090447.10118.ak@suse.de> (raw)
In-Reply-To: <200509082236_MC3-1-A99D-81DD@compuserve.com>
On Friday 09 September 2005 04:33, Chuck Ebbert wrote:
> I was looking at the i386 ACPI early quirk code and x86_64 equivalent
> and it seems to me it should be checking the host bridge vendor, not
> the one for various PCI bridges. Nvidia might release some kind of
> PCI card with an embedded bridge that would break this code, for
> example. I made this patch but I can't test it:
It's wrong. On AMD K8 systems the host bridge is always from
AMD because the Northbridge is part of the CPU.
-Andi
next prev parent reply other threads:[~2005-09-09 2:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 2:33 [patch 2.6.13] x86: check host bridge when applying vendor quirks Chuck Ebbert
2005-09-09 2:47 ` Andi Kleen [this message]
2005-09-09 5:19 ` Piter PUNK
2005-09-09 6:07 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2005-09-09 4:44 Chuck Ebbert
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=200509090447.10118.ak@suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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