public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Piter PUNK <piterpk@terra.com.br>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2.6.13] x86: check host bridge when applying vendor quirks
Date: Fri, 09 Sep 2005 02:19:35 -0300	[thread overview]
Message-ID: <43211B67.30607@terra.com.br> (raw)
In-Reply-To: <200509090447.10118.ak@suse.de>

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.

Hmmm... no.

root@Weasley:/etc# lspci
00:00.0 Host bridge: ATI Technologies Inc: Unknown device 5950
<...many things...>
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

The Athlon64 machines has an external host bridge. You can look the
ATI Host Bridge in the first line of lspci.

Piter PUNK

  reply	other threads:[~2005-09-09  5:19 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
2005-09-09  5:19   ` Piter PUNK [this message]
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=43211B67.30607@terra.com.br \
    --to=piterpk@terra.com.br \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.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