From: Jeff Garzik <jgarzik@pobox.com>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: linux-scsi@vger.kernel.org
Subject: Re: use_10_for_ms revisited?
Date: Sun, 29 Jun 2003 14:32:43 -0400 [thread overview]
Message-ID: <3EFF30CB.2050301@pobox.com> (raw)
In-Reply-To: <20030629182546.GB15024@win.tue.nl>
Andries Brouwer wrote:
> On Sun, Jun 29, 2003 at 01:58:04PM -0400, Jeff Garzik wrote:
>
>
>>I would still prefer to detect "MMC", at least in ATAPI's case, and then
>>use that flag to trickle down knowledge to use_10_for_ms and similar
>>features. ATAPI is even easier than I was previously thinking: at
>>host-alloc time, we already know the devices will be MMC, and never ever
>>want 6-byte commands.
>
>
> And what do they want? 12-byte commands?
> What standard are you reading? SFF-8020? ATA-4?
MMC-<1234> from t10.org, which if considered over time (i.e. changes
from 1 -> 2 -> 3 -> 4 are interesting) gives a fairly reasonable picture
of the subset of scsi that atapi belongs to. That picture seems to gibe
with the atapi testing on ancient devices I've done so far. MMC sorta
takes over where SFF left off, IMO. You definitely want the sff docs
too for the full picture (as you no doubt know already).
Jeff
prev parent reply other threads:[~2003-06-29 18:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-29 6:30 use_10_for_ms revisited? Jeff Garzik
2003-06-29 6:38 ` Matthew Dharm
2003-06-29 6:47 ` Jeff Garzik
2003-06-29 6:54 ` Matthew Dharm
2003-06-29 7:27 ` Jeff Garzik
2003-06-29 10:31 ` Alan Cox
2003-06-29 10:22 ` Andries Brouwer
2003-06-29 16:33 ` Jeff Garzik
2003-06-29 17:36 ` Andries Brouwer
2003-06-29 17:58 ` Jeff Garzik
2003-06-29 18:02 ` Matthew Dharm
2003-06-29 18:17 ` Jeff Garzik
2003-06-29 18:35 ` Matthew Dharm
2003-06-29 18:36 ` James Bottomley
2003-06-29 19:07 ` Jeff Garzik
2003-06-30 0:23 ` Matthew Dharm
2003-06-30 3:24 ` Jeff Garzik
2003-06-29 18:25 ` Andries Brouwer
2003-06-29 18:32 ` Jeff Garzik [this message]
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=3EFF30CB.2050301@pobox.com \
--to=jgarzik@pobox.com \
--cc=aebr@win.tue.nl \
--cc=linux-scsi@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