All of lore.kernel.org
 help / color / mirror / Atom feed
From: xi <xizard@enib.fr>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: AMD760MPX: bogus chispset ? (was PROBLEM: sound is stutter,	sizzle with lasts kernel releases)
Date: Fri, 11 Jul 2003 21:04:39 +0000	[thread overview]
Message-ID: <3F0F2667.7090103@enib.fr> (raw)
In-Reply-To: <1057943291.20629.30.camel@dhcp22.swansea.linux.org.uk>

Alan Cox wrote:
> On Gwe, 2003-07-11 at 18:02, xi wrote:
> 
>>Now I have done some investigations, and I think I have found the 
>>problem: It has appeared between kernel-2.4.18-pre9 and kernel-2.4.18-rc1
>>If I am not wrong, between these two versions, Alan Cox did a change in 
>>drivers/pci/quirks.c and this is this change which cause the problem.
> 
> 
> As I read the documentation the other change is also required in this
> situation to avoid a chipset lockup. It might be worth you rechecking
> the AMD errata docs for 762/768 again to be sure I didnt screw up and
> there are not newer rules for other revisions. 
> 

Ok, I have rechecked the errata docs. I have not found any 
recommandation change for PCI compliance configuration registers.

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) ?
Or could you propose an other solution ?


Regards,
					Xavier

-- 
E-mail:
ctrl.alt.sup@free.fr xizard@chez.com
Please no longer use xizard@enib.fr, this e-mail will be removed soon.

Homepage:
http://xizard.free.fr
http://www.chez.com/xizard/


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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3F0EED9B.4080502@enib.fr>
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 [this message]
2003-07-11 21:37     ` Alan Cox
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:
  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=3F0F2667.7090103@enib.fr \
    --to=xizard@enib.fr \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.