From: Vojtech Pavlik <vojtech@suse.cz>
To: John Heil <kerndev@sc-software.com>
Cc: George Garvey <tmwg-linuxknl@inxservices.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.2ac12 (vt82c686 info)
Date: Thu, 8 Mar 2001 09:17:06 +0100 [thread overview]
Message-ID: <20010308091706.B799@suse.cz> (raw)
In-Reply-To: <20010307201437.A5030@suse.cz> <Pine.LNX.3.95.1010307131509.31180A-100000@scsoftware.sc-software.com>
In-Reply-To: <Pine.LNX.3.95.1010307131509.31180A-100000@scsoftware.sc-software.com>; from kerndev@sc-software.com on Wed, Mar 07, 2001 at 01:23:49PM +0000
On Wed, Mar 07, 2001 at 01:23:49PM +0000, John Heil wrote:
> > Also, the vt82c686 will work just fine with Linux, but will be limited
> > to UDMA33, because UDMA66 on this chip does reliably fail.
>
> Based on following the lkml threads on Via chipsets, it seems that
> the 686a at or above rev 22, will run UDMA66 just fine.
> Below that, lies the flakiness...
> My Tyan based 686a rev 22 has been trouble free save a bad cable.
686 rev 00-0f => 686, UDMA33 (UDMA66 broken, chip very rare)
686 rev 10-2f => 686a, UDMA66
686 rev 40 => 686b, UDMA100
> I just acquired a new 1.1G athlon on an asus a7v133. It has a 686b.
> What should I expect w the 686b? and is the Via 686b data sheet
> available somewhere?
Make sure you use the latest 2.4.2-acxx drivers. Most other versions of
my drivers have little bugs in the 686b support. Harmless but somewhat
annoying.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2001-03-08 8:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-06 13:05 Linux 2.4.2ac12 (vt82c686 info) George Garvey
2001-03-07 19:14 ` Vojtech Pavlik
2001-03-07 13:23 ` John Heil
2001-03-08 8:17 ` Vojtech Pavlik [this message]
2001-03-08 17:30 ` Wayne Whitney
2001-03-08 18:51 ` Vojtech Pavlik
2001-03-09 7:25 ` Daniela Engert
2001-03-09 7:53 ` Vojtech Pavlik
2001-03-12 19:33 ` Andre Hedrick
2001-03-08 18:35 ` Harold Oga
2001-03-08 20:54 ` Vojtech Pavlik
2001-03-09 13:10 ` Harold Oga
2001-03-09 15:25 ` Harold Oga
2001-03-08 5:47 ` Rogerio Brito
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=20010308091706.B799@suse.cz \
--to=vojtech@suse.cz \
--cc=kerndev@sc-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tmwg-linuxknl@inxservices.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 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.