From: Dave Jones <davej@codemonkey.org.uk>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com, alan@redhat.com
Subject: Re: A new Athlon 'bug'.
Date: Tue, 26 Nov 2002 19:41:29 +0000 [thread overview]
Message-ID: <20021126194129.GA24152@suse.de> (raw)
In-Reply-To: <20021125213447.GB12236@elf.ucw.cz>
On Mon, Nov 25, 2002 at 10:34:47PM +0100, Pavel Machek wrote:
> > Very recent Athlons (Model 8 stepping 1 and above) (XPs/MPs and mobiles)
> > have an interesting problem. Certain bits in the CLK_CTL register need
> > to be programmed differently to those in earlier models. The problem arises
> > when people plug these new CPUs into boards running BIOSes that are unaware
> > of this fact.
> What happens when bit is programed wrongly?
The documentation I have says nothing other than "...platforms are more
robust..." with the fix. It's purely a reliability thing, but as it's
fiddling with the CPU clock, it's possible that it may *slightly*
affect performance too.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-11-26 19:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 15:56 A new Athlon 'bug' davej
2002-11-25 21:34 ` Pavel Machek
2002-11-26 19:41 ` Dave Jones [this message]
2002-11-29 15:08 ` Daniel Nofftz
2002-11-29 15:11 ` Dave Jones
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=20021126194129.GA24152@suse.de \
--to=davej@codemonkey.org.uk \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=torvalds@transmeta.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