From: Andi Kleen <ak@muc.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, mark.langsdorf@amd.com,
root@chaos.analogic.com
Subject: Re: Celistica with AMD chip-set
Date: Mon, 30 Aug 2004 17:28:07 +0200 [thread overview]
Message-ID: <m34qmktzlk.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <2yVb1-2ft-57@gated-at.bofh.it> (Alan Cox's message of "Mon, 30 Aug 2004 16:20:15 +0200")
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> On Llu, 2004-08-30 at 15:02, Richard B. Johnson wrote:
>> Hello all,
>>
>> The Celistica server with the AMD chip-set has very poor
>> PCI performance with Linux (and probably W$ too).
>>
>> The problem was traced to incorrect bridge configuration
>> in the HyperTransport(tm) chips that connect up pairs
>> of slots.
> while((pdev = pci_find_device(0x1022, 0x7450, pdev)) != NULL)
> pci_write_config_dword(pdev, 0x4c, 0x2ec1);
> Can you get Celestica to mail me their PCI subvendor
> id/devid's for the problem configuration or DMI strings
> and then we can do a PCI quirk properly for this.
Celistica is just the contract manufacturer for the AMD
reference design, they're really AMD designs. 0122/7450
is the AMD 8131 PCI-X bridge.
I doubt it is a good idea to blindly change the configuration of the
bridge like this in the kernel. It is probably better to wait for an
BIOS update or if you really need an urgent fix to do it from user
space. Any fix should probably read/change bit/write the register, not
blindly overwrite.
-Andi
next parent reply other threads:[~2004-08-30 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2yV1c-29L-7@gated-at.bofh.it>
[not found] ` <2yVb1-2ft-57@gated-at.bofh.it>
2004-08-30 15:28 ` Andi Kleen [this message]
2004-08-30 17:20 ` Celistica with AMD chip-set Richard B. Johnson
2004-08-30 17:45 ` Andi Kleen
2004-08-30 14:02 Richard B. Johnson
2004-08-30 13:15 ` Alan Cox
2004-08-30 15:04 ` Arthur Perry
2004-08-30 15:34 ` Arthur Perry
2004-08-30 17:26 ` Richard B. Johnson
2004-08-30 17:17 ` Richard B. Johnson
2004-08-30 18:13 ` Arthur Perry
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=m34qmktzlk.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.com \
--cc=root@chaos.analogic.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