From: Jan Niehusmann <jan@gondor.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Andre Hedrick <andre@linux-ide.org>,
Alan Chandler <alan@chandlerfamily.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [preview] Latest AMD & VIA IDE drivers with UDMA100 support
Date: Sun, 21 Jan 2001 14:04:33 +0100 [thread overview]
Message-ID: <20010121140433.A1068@gondor.com> (raw)
In-Reply-To: <20010120215641.A1818@suse.cz> <Pine.LNX.4.10.10101201301200.657-100000@master.linux-ide.org> <20010121104606.A398@suse.cz>
In-Reply-To: <20010121104606.A398@suse.cz>; from vojtech@suse.cz on Sun, Jan 21, 2001 at 10:46:06AM +0100
On Sun, Jan 21, 2001 at 10:46:06AM +0100, Vojtech Pavlik wrote:
> Ok, the VIA driver from clean 2.2.18 does nothing. It doesn't even use
> hardcoded timings. It doesn't touch any timing tables. It just blindly
> enables prefetch and writeback in the chips. The thing works because it
> relies on BIOS to set things up correctly, and this is often the case,
> yes.
If BIOS is often correct: Is it possible to read these values and compare
them to the values linux calculates? If both match: OK, continue. If they
are different: Either BIOS or linux is wrong, print a warning and disable
DMA (or go to some other kind of 'safe mode').
Just an idea, I don't know anything about chipsets and IDE timings ;-)
Jan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-21 13:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-20 17:14 [preview] Latest AMD & VIA IDE drivers with UDMA100 support Alan Chandler
[not found] ` <Pine.LNX.4.10.11101200938180.2302-100000@master.linux-ide.org>
2001-01-20 18:45 ` Alan Chandler
2001-01-20 20:56 ` Vojtech Pavlik
2001-01-20 22:57 ` Andre Hedrick
2001-01-20 23:55 ` Alan Chandler
[not found] ` <Pine.LNX.4.10.10101202015510.1776-100000@coffee.psychology.mcmaster.ca>
2001-01-21 10:51 ` Alan Chandler
2001-01-21 11:44 ` Vojtech Pavlik
2001-01-21 9:46 ` Vojtech Pavlik
2001-01-21 13:04 ` Jan Niehusmann [this message]
[not found] ` <Pine.Linu.4.10.10101211237230.2017-100000@mikeg.weiden.de>
2001-01-21 16:32 ` Vojtech Pavlik
2001-01-21 20:49 ` Andre Hedrick
2001-01-22 0:12 ` Dan Hopper
2001-01-22 6:06 ` Mike Galbraith
2001-01-25 21:54 ` David D.W. Downey
2001-01-25 21:56 ` Vojtech Pavlik
2001-01-25 22:00 ` Andre Hedrick
2001-01-26 0:26 ` David D.W. Downey
2001-01-24 18:04 ` Andre Hedrick
2001-01-24 19:25 ` Vojtech Pavlik
2001-01-24 21:58 ` Andre Hedrick
2001-01-25 12:20 ` Vojtech Pavlik
-- strict thread matches above, loose matches on Subject: below --
2001-01-19 15:56 Vojtech Pavlik
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=20010121140433.A1068@gondor.com \
--to=jan@gondor.com \
--cc=alan@chandlerfamily.org.uk \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.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