From: Jeff Garzik <jgarzik@pobox.com>
To: Mark Lord <lkml@rtr.ca>
Cc: William Knop <wknop@andrew.cmu.edu>, Jon Lewis <jlewis@lewis.org>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: libata badness
Date: Mon, 04 Oct 2004 12:30:42 -0400 [thread overview]
Message-ID: <41617AB2.4030702@pobox.com> (raw)
In-Reply-To: <4161750A.6060200@rtr.ca>
Mark Lord wrote:
> I have used Maxtor "SATA" drives that require
> the O/S to do a "SET FEATURES :: UDMA_MODE" command
> on them before they will operate reliably.
> This despite the SATA spec stating clearly that
> such a command should/will have no effect.
>
> I suppose libata does this already, but just in case not..
> Something simple to check up on.
libata always issues SET FEATURES - XFER MODE.
Jeff
next prev parent reply other threads:[~2004-10-04 16:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 12:12 libata badness William Knop
2004-10-04 13:59 ` Jon Lewis
2004-10-04 15:50 ` William Knop
2004-10-04 16:06 ` Mark Lord
2004-10-04 16:24 ` William Knop
2004-10-04 16:30 ` Jeff Garzik [this message]
2004-10-04 16:09 ` Jon Lewis
2004-10-04 16:34 ` William Knop
2004-10-04 16:30 ` Jeff Garzik
2004-10-04 16:55 ` William Knop
2004-10-04 17:42 ` William Knop
2004-10-04 17:50 ` Jim Paris
2004-10-04 18:03 ` William Knop
2004-10-04 18:01 ` Jeff Garzik
2004-10-04 22:47 ` Neil Brown
2004-10-05 3:11 ` William Knop
2004-10-05 4:49 ` Brad Campbell
2004-10-05 5:27 ` Norman Schmidt
-- strict thread matches above, loose matches on Subject: below --
2008-07-31 18:53 Kumar Gala
2008-07-31 19:02 ` Ben Dooks
2008-07-31 19:02 ` Ben Dooks
2008-07-31 20:24 ` Kumar Gala
2008-07-31 20:24 ` Kumar Gala
2008-07-31 20:37 ` Scott Wood
2008-07-31 20:37 ` Scott Wood
2008-07-31 21:04 ` Anton Vorontsov
2008-07-31 21:04 ` Anton Vorontsov
2008-07-31 21:58 ` Kumar Gala
2008-07-31 21:58 ` Kumar Gala
2008-08-01 10:43 ` Ben Dooks
2008-08-01 10:43 ` Ben Dooks
2008-08-01 12:46 ` Kumar Gala
2008-08-01 12:46 ` Kumar Gala
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=41617AB2.4030702@pobox.com \
--to=jgarzik@pobox.com \
--cc=jlewis@lewis.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=wknop@andrew.cmu.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.