From: Chuck Ebbert <76306.1226@compuserve.com>
To: Andi Kleen <ak@suse.de>
Cc: Len Brown <len.brown@intel.com>,
Linus Torvalds <torvalds@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2.6.13] x86: check host bridge when applying vendor quirks
Date: Fri, 9 Sep 2005 00:44:47 -0400 [thread overview]
Message-ID: <200509090046_MC3-1-A99D-882E@compuserve.com> (raw)
In-Reply-To: <200509090447.10118.ak@suse.de>
On Fri, 9 Sep 2005 at 04:47:09 +0200, Andi Kleen wrote:
> 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.
It's at least right on my system:
00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 01)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
__
Chuck
next reply other threads:[~2005-09-09 4:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 4:44 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-09 2:33 Chuck Ebbert
2005-09-09 2:47 ` Andi Kleen
2005-09-09 5:19 ` Piter PUNK
2005-09-09 6:07 ` Andi Kleen
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=200509090046_MC3-1-A99D-882E@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=ak@suse.de \
--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
all inboxes | Powered by JetHome®