From: Mark Lord <mlord@pobox.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Albert Lee <albertcc@tw.ibm.com>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Doug Maxey <dwm@maxeymade.com>,
IDE Linux <linux-ide@vger.kernel.org>,
"Mudama, Eric" <eric_mudama@Maxtor.com>
Subject: Re: [PATCH libata-dev-2.6 1/3] Add CHS support
Date: Sun, 06 Feb 2005 17:02:06 -0500 [thread overview]
Message-ID: <420693DE.4030407@pobox.com> (raw)
In-Reply-To: <42063123.6070602@pobox.com>
The exact sequence expected by certain pre-ATA4 (or earlier?) drives
was this:
SRST RESET
IDENTIFY
INITIALIZE DRIVE PARAMETERS
anything else..
Some drives were very specific about that exact sequence.
Nowadays, I don't bother with it for anything new I do,
as it is obsolete, and may even get rejected by modern drives.
But for the mainstream Linux ATA support, we should issue it
for drives which IDENTIFY themselves as conforming to pre-ATAx,
where the safest value for "x" is probably "4".
Cheers
--
Mark Lord
Real-Time Remedies Inc.
mlord@pobox.com
Jeff Garzik wrote:
> Mark Lord wrote:
>
>> Jeff Garzik wrote:
>>
>>> 3) In Promise's GPL'd driver for their SATA (w/ PATA) cards, they
>>> unconditionally execute the INITIALIZE DEVICE PARAMETERS command. I
>>> wonder if we should do the same.
>>
>>
>>
>> That command was *necessary* for certain drives at one time,
>> which refused all other commands until they received the IDP one.
>
>
> Except IDENTIFY DEVICE, presumably?
>
> Thanks,
>
> Jeff
>
next prev parent reply other threads:[~2005-02-06 22:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 6:02 [PATCH libata-dev-2.6 1/3] Add CHS support Albert Lee
2005-02-06 6:26 ` Jeff Garzik
2005-02-06 14:41 ` Mark Lord
2005-02-06 15:00 ` Jeff Garzik
2005-02-06 22:02 ` Mark Lord [this message]
2005-02-14 11:09 ` Albert Lee
2005-02-14 11:17 ` Albert Lee
2005-02-14 11:23 ` Albert Lee
2005-02-18 23:40 ` Jeff Garzik
2005-02-22 3:35 ` Albert Lee
2005-02-23 11:25 ` [PATCH libata-dev-2.6] Issue INITIALIZE DEVICE PARAMETERS for CHS only devices Albert Lee
2005-02-23 14:48 ` Mark Lord
2005-02-24 2:36 ` Albert Lee
2005-02-24 2:53 ` Jeff Garzik
2005-02-24 5:29 ` Albert Lee
2005-02-24 5:35 ` Jeff Garzik
2005-02-24 6:41 ` Albert Lee
2005-02-24 6:48 ` Jeff Garzik
2005-02-24 7:01 ` Albert Lee
2005-02-24 7:48 ` Jeff Garzik
2005-02-25 5:01 ` Albert Lee
2005-02-25 5:22 ` Albert Lee
2005-02-25 5:40 ` Jeff Garzik
2005-02-24 3:10 ` Mark Lord
2005-02-24 3:15 ` Jeff Garzik
2005-02-24 3:35 ` Mark Lord
2005-02-23 16:50 ` Bartlomiej Zolnierkiewicz
2005-02-24 3:05 ` Albert Lee
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=420693DE.4030407@pobox.com \
--to=mlord@pobox.com \
--cc=albertcc@tw.ibm.com \
--cc=bzolnier@gmail.com \
--cc=dwm@maxeymade.com \
--cc=eric_mudama@Maxtor.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).