From: Vojtech Pavlik <vojtech@suse.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch] VIA 4.2x driver for 2.2 kernels
Date: Wed, 21 Feb 2001 22:23:58 +0100 [thread overview]
Message-ID: <20010221222358.A1665@suse.cz> (raw)
In-Reply-To: <20010220134028.A5762@suse.cz> <20010220155927.A1543@cm.nu> <20010221080919.A469@suse.cz> <20010220231502.A4618@cm.nu> <20010221082348.A908@suse.cz> <20010221110533.B3374@iname.com>
In-Reply-To: <20010221110533.B3374@iname.com>; from rbrito@iname.com on Wed, Feb 21, 2001 at 11:05:33AM -0300
On Wed, Feb 21, 2001 at 11:05:33AM -0300, Rogerio Brito wrote:
> On Feb 21 2001, Vojtech Pavlik wrote:
> > On Tue, Feb 20, 2001 at 11:15:02PM -0800, Shane Wegner wrote:
> > > Ok, can I still use -u1 -k1 -c1 on the drives or is it even
> > > necessary anymore.
> >
> > If you enable automatic DMA in the kernel config, it isn't necessary
> > at all. The VIA driver sets up everything.
>
> Ok. Please disregard my last message (this one contains
> exactly what I was looking for).
>
> > 4) But VIA is still set to PIO mode
>
> Why does this happen?
>
> And what about the other options to hdparm (-u1 -k1 -c1)? Are
> they potentially dangerous also?
Well, I checked today and my fears were *not* confirmed. Actually the
VIA driver will set up the chipset for UDMA even when UDMA won't be
later used, so it's all OK.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2001-02-21 21:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-20 12:40 [patch] VIA 4.2x driver for 2.2 kernels Vojtech Pavlik
2001-02-20 23:59 ` Shane Wegner
2001-02-21 7:09 ` Vojtech Pavlik
2001-02-21 7:15 ` Shane Wegner
2001-02-21 7:23 ` Vojtech Pavlik
2001-02-21 14:05 ` Rogerio Brito
2001-02-21 21:23 ` Vojtech Pavlik [this message]
2001-02-21 23:45 ` Shane Wegner
2001-02-21 14:00 ` 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=20010221222358.A1665@suse.cz \
--to=vojtech@suse.cz \
--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