From: Jonathan Morton <chromi@cyberspace.org>
To: tegeran@home.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Athlon: Try this (was: Re: Athlon bug stomping #2)
Date: Sat, 15 Sep 2001 19:02:37 +0100 [thread overview]
Message-ID: <a05100300b7c94753f227@[192.168.239.101]> (raw)
In-Reply-To: <01091510441001.00174@c779218-a>
In-Reply-To: <E15i2Bp-00017m-00@the-village.bc.nu> <01091510441001.00174@c779218-a>
> > > +static void __init pci_fixup_athlon_bug(struct pci_dev *d)
>> > +{
>> > + u8 v;
>> > + pci_read_config_byte(d, 0x55, &v);
>> > + if(v & 0x80) {
>> > + printk(KERN_NOTICE "Stomping on Athlon bug.\n");
>> > + v &= 0x7f; /* clear bit 55.7 */
>> > + pci_write_config_byte(d, 0x55, v);
>> > + }
>> > +}
>> >
>> > Well, these are cosmetic changes anyway...
>> > What is more important now:
>> > 1) Do we have people who still see Athlon bug with the patch?
>> > 2) Do Alan read these messages? ;-)
>>
>> Im watching the discussion with interest. If it proves to be the magic
>> bullet I will ask VIA for guidance on the issue
>
>Not being a developer or guru on the internal software workings of the
>hardware here, I have to ask, does this clear up some bug, or does it
>disable the optimizations causing the problem? Is this a *fix* or a
>band-aid?
AFAICT, it's a *fix*. The register in question is "for debug use
only, never write anything other than zero in it" but generally shows
non-zero when a faulty BIOS is installed. We're zeroing the bit that
appears to cause the problem. It's highly unlikely to be an extra
optimisation - if it is, it's an unsafe one.
--
--------------------------------------------------------------
from: Jonathan "Chromatix" Morton
mail: chromi@cyberspace.org (not for attachments)
website: http://www.chromatix.uklinux.net/vnc/
geekcode: GCS$/E dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$
V? PS PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
tagline: The key to knowledge is not to rely on people to teach you it.
next prev parent reply other threads:[~2001-09-15 18:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <372BFCD7961@vcnet.vc.cvut.cz>
2001-09-14 18:43 ` Athlon: Try this (was: Re: Athlon bug stomping #2) VDA
2001-09-14 23:16 ` Alan Cox
2001-09-15 17:44 ` Nicholas Knight
2001-09-15 23:23 ` Alan Cox
2001-09-15 18:02 ` Jonathan Morton [this message]
2001-09-16 1:52 ` Petr Vandrovec
2001-09-16 7:21 ` Steffen Persvold
2001-09-16 8:08 ` Jan Niehusmann
2001-09-19 3:47 ` Albert D. Cahalan
2001-09-16 11:02 ` Vojtech Pavlik
2001-09-16 13:53 ` Alan Cox
2001-09-16 13:50 ` Vojtech Pavlik
2001-09-16 14:47 ` Alan Cox
2001-09-16 17:01 ` Vojtech Pavlik
2001-09-16 16:52 ` Roberto Jung Drebes
2001-09-17 0:58 ` Petr Vandrovec
2001-09-17 1:37 ` Ignacio Vazquez-Abrams
2001-09-17 14:59 ` Jonathan Morton
2001-09-18 11:27 ` jury gerold
2001-09-20 23:38 ` bill davidsen
2001-09-14 7:34 Athlon bug stomping #2 Roberto Jung Drebes
2001-09-14 8:27 ` Athlon: Try this (was: Re: Athlon bug stomping #2) Roberto Jung Drebes
2001-09-14 18:19 ` Byron Stanoszek
2001-09-15 18:00 ` Liakakis Kostas
2001-09-15 20:28 ` VDA
2001-09-15 7:15 ` brian
2001-09-19 1:30 ` brian
2001-09-16 21:53 ` Carsten Leonhardt
2001-09-19 3:55 ` Dan Hollis
2001-09-14 9:26 ` Jeff Lightfoot
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='a05100300b7c94753f227@[192.168.239.101]' \
--to=chromi@cyberspace.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tegeran@home.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;
as well as URLs for NNTP newsgroup(s).