From: "Trever L. Adams" <tadams-lists@myrealbox.com>
To: "Calin A. Culianu" <calin@ajvar.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Steven Hassani <hassani@its.caltech.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Athlon Optimization Problem
Date: 29 Jan 2002 16:19:16 -0500 [thread overview]
Message-ID: <1012339159.12557.18.camel@aurora> (raw)
In-Reply-To: <Pine.LNX.4.30.0201291604340.10200-100000@rtlab.med.cornell.edu>
In-Reply-To: <Pine.LNX.4.30.0201291604340.10200-100000@rtlab.med.cornell.edu>
On Tue, 2002-01-29 at 16:05, Calin A. Culianu wrote:
> > It may well the case. All I know is that for some people at least leaving
> > 0x95 as the bios set it up works and touching it does not - while for
> > the 0x55 case on older chips it all seems to be positive. VIA's own stuff
> > doesn't touch 0x95 - maybe there is a reason
> >
>
> Really? VIA's own stuff doesn't touch 0x95? Hmm. Well is there ever a
> case where touching 0x95 solved ANYTHING?
>
> What do you think? Should I change the patch to not touch 0x95?
I know it is fairly common for Award BIOS to touch 0x95. For example
Soyo Dragon Plus and Epox 8kha+. Either that or the chipset on these
boards defaults to something that doesn't require the fixup.
Trever Adams
next prev parent reply other threads:[~2002-01-29 21:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-26 9:07 Athlon Optimization Problem Steven Hassani
2002-01-28 10:07 ` Steven Hassani
2002-01-28 19:56 ` Calin A. Culianu
2002-01-28 20:24 ` Alan Cox
2002-01-28 20:28 ` Rene Rebe
2002-01-29 0:46 ` Denis Vlasenko
2002-01-28 20:53 ` Calin A. Culianu
2002-01-28 21:08 ` Alan Cox
2002-01-29 21:05 ` Calin A. Culianu
2002-01-29 21:19 ` Trever L. Adams [this message]
2002-01-29 23:26 ` Alan Cox
2002-01-30 16:04 ` Calin A. Culianu
2002-01-30 22:12 ` Bill Davidsen
2002-01-30 23:10 ` Alan Cox
2002-01-29 8:07 ` Daniel Nofftz
2002-01-29 20:56 ` Calin A. Culianu
2002-01-29 21:22 ` Calin A. Culianu
2002-01-29 23:04 ` Daniel Nofftz
2002-01-29 23:27 ` Calin A. Culianu
2002-01-30 9:05 ` Daniel Nofftz
2002-01-29 22:59 ` Daniel Nofftz
2002-01-29 17:04 ` Paul G. Allen
2002-01-29 17:17 ` Rene Rebe
[not found] <Pine.LNX.4.33.0201301838520.23104-100000@coffee.psychology.mcmaster.ca>
2002-02-04 20:28 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2002-02-05 3:22 Serguei Miridonov
2002-02-05 12:56 ` Denis Vlasenko
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=1012339159.12557.18.camel@aurora \
--to=tadams-lists@myrealbox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=calin@ajvar.org \
--cc=hassani@its.caltech.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox