archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <>
To: xi <>
Cc: Linux Kernel Mailing List <>
Subject: Re: AMD760MPX: bogus chispset ? (was PROBLEM: sound is stutter,	sizzle with lasts kernel releases)
Date: 11 Jul 2003 22:37:39 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Gwe, 2003-07-11 at 22:04, xi wrote:
> And one interesting thing:
> in the AMD762 datasheet (24462.pdf) page 231 (Recommanded BIOS 
> settings), I can see this: "Numerical Values shown with h or b are 
> preferred settings." ; and AMD recommand this:
> -> set bits 2 and 1 of register 0x4C to "0b"
> -> set bits 23 and 3 respectively to "0b" and "1b"
> I can confirm that these settings works much more better, even if they 
> don't exactly follow PCI specs. And I don't think this is specific to my 
>   cards since I have tested others.
> Furthermore, my AMD762 is revision B1 (just before the last one: C0), 
> and my AMD768 revision is B2, the last one.
> Would you accept I make a patch which doesn't make any change in these 
> registers at least up to AMD762 revision B1 (ie keeping recommanded 
> values from AMD) ?

Lets try the AMD recommended settings. My old doc doesnt seem to have
those. I'll by happy to trial the patch in -ac and see if it plays up
the usual suspects for PCI spec violations (tg3 and i2o)

  reply	other threads:[~2003-07-11 21:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2003-07-11 17:08 ` AMD760MPX: bogus chispset ? (was PROBLEM: sound is stutter, sizzle with lasts kernel releases) Alan Cox
2003-07-11 21:04   ` xi
2003-07-11 21:37     ` Alan Cox [this message]
2003-07-12  5:08       ` [PATCH] " xi
2003-07-13  8:13         ` Alan Cox
2003-07-11 16:54 xi

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).