From: Vojtech Pavlik <vojtech@suse.cz>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: linux-kernel@vger.kernel.org, VDA@port.imtp.ilyichevsk.odessa.ua,
alan@lxorguk.ukuu.org.uk
Subject: Re: Athlon: Try this (was: Re: Athlon bug stomping #2)
Date: Sun, 16 Sep 2001 13:02:01 +0200 [thread overview]
Message-ID: <20010916130201.A1327@suse.cz> (raw)
In-Reply-To: <1292125035.20010914214303@port.imtp.ilyichevsk.odessa.ua> <E15i2Bp-00017m-00@the-village.bc.nu> <20010916035207.C7542@ppc.vc.cvut.cz>
In-Reply-To: <20010916035207.C7542@ppc.vc.cvut.cz>; from vandrove@vc.cvut.cz on Sun, Sep 16, 2001 at 03:52:07AM +0200
On Sun, Sep 16, 2001 at 03:52:07AM +0200, Petr Vandrovec wrote:
> > +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?
>
> Just by any chance - does anybody have KT133 (not KT133A)
> datasheet? I just noticed at home that my KT133 has reg 55 set
> to 0x89 and it happilly lives... So maybe some BIOS vendors
> used KT133 instead of KT133A BIOS image?
Same here ...
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2001-09-16 11: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
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 [this message]
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=20010916130201.A1327@suse.cz \
--to=vojtech@suse.cz \
--cc=VDA@port.imtp.ilyichevsk.odessa.ua \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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).