From: Vojtech Pavlik <vojtech@suse.cz>
To: torvalds@transmeta.com
Cc: andre@linux-ide.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] Update of the VIA driver to version 3.20
Date: Tue, 30 Jan 2001 10:49:10 +0100 [thread overview]
Message-ID: <20010130104910.A1672@suse.cz> (raw)
In-Reply-To: <20010130104826.A1650@suse.cz>
In-Reply-To: <20010130104826.A1650@suse.cz>; from vojtech@suse.cz on Tue, Jan 30, 2001 at 10:48:26AM +0100
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]
On Tue, Jan 30, 2001 at 10:48:26AM +0100, Vojtech Pavlik wrote:
> The current VIA driver in 2.4.0 is version 2.1e. I wouldn't push a new
> version, but VIA has released the vt82c686b chip and it's causing a lot
> of trouble.
>
> The 2.1e version can't recognize it from the vt82c686a, the only
> difference being the revision of the ISA bridge. This causes quite a lot
> of trouble, because the 686b chip has some significant changes in its
> UDMA programming, because it can do UDMA100.
>
> The 3.20 driver I'm sending a diff for is well tested and working
> nicely, also enabling the use of UDMA100 on the vt82c686b.
>
> On some vt82c586b's it fixes crashes and reboots, because it disables a
> certain dangerous feature (hold PREQ# till DDACK# unasserted), which
> BIOSes sometimes leave enabled.
>
> It also handles 8-bit (command) timing of the ATA bus better.
>
> I know it's a big change, but please put this patch either in 2.4.1 or
> in 2.4.2 - it'll help a lot of people and I'll be getting much less
> mails about non-working 686b's.
>
> It's against 2.4.1-pre12, but should patch cleanly against pre11 or
> anything later.
And here goes the patch.
--
Vojtech Pavlik
SuSE Labs
[-- Attachment #2: via82cxxx-3.20.diff.gz --]
[-- Type: application/x-gunzip, Size: 11455 bytes --]
prev parent reply other threads:[~2001-01-30 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 9:48 [patch] Update of the VIA driver to version 3.20 Vojtech Pavlik
2001-01-30 9:49 ` Vojtech Pavlik [this message]
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=20010130104910.A1672@suse.cz \
--to=vojtech@suse.cz \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--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