public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ryan Mack <lists@mackman.net>,
	Markus Plail <linux-kernel@gitteundmarkus.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.21 ServerWorks DMA Bugs
Date: Sun, 6 Jul 2003 13:10:15 +0200	[thread overview]
Message-ID: <20030706111015.GA303@louise.pinerecords.com> (raw)
In-Reply-To: <1057482631.705.15.camel@dhcp22.swansea.linux.org.uk>

> [alan@lxorguk.ukuu.org.uk]
> 
> On Sul, 2003-07-06 at 10:06, Tomas Szepe wrote:
> > It doesn't all right. :)
> > 
> > On a G3 Compaq Proliant, all drives come up in PIO by default;
> > DMA needs to be enabled by "/usr/sbin/hdparm -d1 -X69 /dev/hdX".
> 
> This is because your compaq BIOS decided to set it up this way.

Also note that when the '-X' switch is omitted (i.e. one only issues
"/usr/sbin/hdparm -d1 /dev/hdX"), the driver sets up a mode that doesn't
work and then quickly falls back to PIO.

  reply	other threads:[~2003-07-06 10:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-05  6:45 2.4.21 ServerWorks DMA Bugs Ryan Mack
2003-07-05  6:49 ` Andre Hedrick
2003-07-05  7:21 ` Markus Plail
2003-07-05 16:58   ` Ryan Mack
2003-07-05 17:07     ` Jeff Garzik
2003-07-06  7:40     ` Alan Cox
2003-07-06  9:06       ` Tomas Szepe
2003-07-06  9:10         ` Alan Cox
2003-07-06 11:10           ` Tomas Szepe [this message]
2003-07-06 11:38             ` Alan Cox
2003-07-06 16:42               ` Vojtech Pavlik
2003-07-06 17:49                 ` Alan Cox
2003-07-07  0:42                 ` Andre Hedrick
2003-07-07  3:42                   ` Tomas Szepe
2003-07-07  6:42                     ` Alan Cox
2003-07-07  8:49                       ` Tomas Szepe
2003-07-07  8:13                     ` Andre Hedrick
2003-07-07  8:17                     ` Andre Hedrick
2003-07-07  8:45                       ` Tomas Szepe

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=20030706111015.GA303@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@gitteundmarkus.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@mackman.net \
    /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