public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rogerio Brito <rbrito@iname.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch] VIA 4.2x driver for 2.2 kernels (fwd)
Date: Thu, 22 Feb 2001 12:20:55 -0300	[thread overview]
Message-ID: <20010222122055.A1278@iname.com> (raw)

	This message was apparently intended to be sent to the list.


	[]s, Roger...

----- Forwarded message from Pozsar Balazs <pozsy@sch.bme.hu> -----

From: Pozsar Balazs <pozsy@sch.bme.hu>
To: Rogerio Brito <rbrito@iname.com>
Subject: Re: [patch] VIA 4.2x driver for 2.2 kernels
Date: Thu, 22 Feb 2001 01:04:27 +0100 (MET)
Message-ID: <Pine.GSO.4.30.0102220103290.8797-100000@balu>


The kernel doesn't seem to set 32bit io transfers by default. Is it
dangerous or unrecommended to set it with hdparm?


On Wed, 21 Feb 2001, 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?
>
>
> 	[]s, Roger...
>
>



----- End forwarded message -----

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
  Rogerio Brito - rbrito@iname.com - http://www.ime.usp.br/~rbrito/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

             reply	other threads:[~2001-02-22 15:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-22 15:20 Rogerio Brito [this message]
2001-02-23 10:50 ` [patch] VIA 4.2x driver for 2.2 kernels (fwd) 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=20010222122055.A1278@iname.com \
    --to=rbrito@iname.com \
    --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