From: Douglas Gilbert <dougg@torque.net>
To: axboe@suse.de
Cc: linville@tuxdriver.com, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: [patch libata-dev-2.6 1/1] libata: sync SMART ioctls with ATA pass thru spec (T10/04-262r7)
Date: Thu, 03 Feb 2005 09:05:55 +1000 [thread overview]
Message-ID: <42015CD3.60005@torque.net> (raw)
Jens Axboe wrote:
<snip>
> >
> > -/* Temporary values for T10/04-262 until official values are
> allocated */
> > -#define ATA_16 0x85 /* 16-byte pass-thru
> [0x85 == unused]*/
> -#define ATA_12 0xb3 /* 12-byte pass-thru
> [0xb3 == obsolete set limits command] */
> > +/* Values for T10/04-262r7 */
> > +#define ATA_16 0x85 /* 16-byte pass-thru */
> > +#define ATA_12 0xa1 /* 12-byte pass-thru */
>
> Ehh are you sure that is correct? 0xa1 is the BLANK command, I would
> hate to think there would be a collision like that.
That very point came up recently in a MMC meeting:
http://www.t10.org/ftp/t10/document.05/05-056r0.pdf
To confuse things further "ATA_16" is shown as opcode 0x98
in the latest draft of SPC-3 (rev 21c 15 January 2005)
http://www.t10.org/ftp/t10/drafts/spc3/spc3r21c.pdf [annex D.3.1].
Hopefully these matters will be sorted out at the next t10
meeting in March.
Doug Gilbert
next reply other threads:[~2005-02-02 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 23:05 Douglas Gilbert [this message]
2005-02-02 23:36 ` [patch libata-dev-2.6 1/1] libata: sync SMART ioctls with ATA pass thru spec (T10/04-262r7) Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-02-02 18:37 John W. Linville
2005-02-02 18:51 ` Jens Axboe
2005-02-02 18:59 ` John W. Linville
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=42015CD3.60005@torque.net \
--to=dougg@torque.net \
--cc=axboe@suse.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).