From: Jeff Garzik <jgarzik@pobox.com>
To: linux-scsi@vger.kernel.org
Subject: use_10_for_ms revisited?
Date: Sun, 29 Jun 2003 02:30:28 -0400 [thread overview]
Message-ID: <3EFE8784.4000101@pobox.com> (raw)
I was reading the specs just now, and I see that the inquiry page
defines how ATAPI and USB devices indicate they are compliant with MMC-4.
And, MMC-4 does not define read/write/modesen/modesel 6-byte commands at
all.
My conclusion is that we should notice up front when MMC-4 is supported,
and simply adhere to the spec by always sending 10-byte commands for
that device. I do not think that translation of 6-to-10 byte commands
is answer, which is what happens now. Our SCSI layer (sr.c, etc.)
should, IMO, be compliant with MMC-4 and simply send the right commands.
This also implies that use_10_for_ms simply need not exist -- "first try
10 byte commands for this device" is false... for some devices we
should be unconditionally sending 10 byte commands, no ifs, ands, or buts :)
I'll see if I can work up a patch, if noone objects...
Jeff, debugging atapi support in his ata-scsi driver
next reply other threads:[~2003-06-29 6:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-29 6:30 Jeff Garzik [this message]
2003-06-29 6:38 ` use_10_for_ms revisited? 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
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=3EFE8784.4000101@pobox.com \
--to=jgarzik@pobox.com \
--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