From: James Bottomley <James.Bottomley@SteelEye.com>
To: t.schorpp@gmx.de
Cc: Linux SCSI list <linux-scsi@vger.kernel.org>, linux-ide@vger.kernel.org
Subject: Re: [DOC PATCH] T10/04-262r8
Date: Thu, 10 Nov 2005 10:58:39 -0500 [thread overview]
Message-ID: <1131638319.3336.9.camel@mulgrave> (raw)
In-Reply-To: <4372E66F.5070802@gmx.de>
On Thu, 2005-11-10 at 07:19 +0100, thomas schorpp wrote:
> how about full definitions of the pasthru cdb's in kernel structs and approbiate ioctls?
Why would we want to do that? The whole point about pass through is
that it is designed to use the existing SCSI infrastructure
transparently (hence use SG_IO to send an ATA command to a bridge that
understands it---but the key point here is that the device so addressed
must understand the opcodes).
> the passthru cdb is also not clear enough to me:
> according to sat-r06 spec byte 0-2 is scsi, 3-9 are ata, 11 is scsi, yes?
Actually, no; byte 0 is the opcode, so you could call that SCSI and byte
11 (or 15) is the control as defined by SAM; the rest all contain SAT
specific fields.
James
prev parent reply other threads:[~2005-11-10 15:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 19:50 [usb-storage] [Merging ATA passthru] on integrating SMART/ATA-Security in usb-storage driver Timothy Thelin
2005-11-09 9:04 ` thomas schorpp
2005-11-09 9:45 ` thomas schorpp
2005-11-09 10:05 ` thomas schorpp
2005-11-09 13:21 ` Mark Lord
2005-11-09 14:05 ` thomas schorpp
[not found] ` <4372172A.50003@gmx.de>
[not found] ` <43721C3C.1010103@pobox.com>
[not found] ` <1131553363.3271.1.camel@mulgrave>
2005-11-10 6:19 ` [DOC PATCH] T10/04-262r8 thomas schorpp
2005-11-10 7:44 ` Jeff Garzik
2005-11-10 14:27 ` Mark Lord
2005-11-10 15:05 ` (SAT) libata + hdparm/smartctl thomas schorpp
2005-11-20 7:10 ` Douglas Gilbert
2005-11-10 15:58 ` James Bottomley [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=1131638319.3336.9.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=t.schorpp@gmx.de \
/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).