From: thomas schorpp <t.schorpp@gmx.de>
To: Linux SCSI list <linux-scsi@vger.kernel.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: [DOC PATCH] T10/04-262r8
Date: Thu, 10 Nov 2005 07:19:27 +0100 [thread overview]
Message-ID: <4372E66F.5070802@gmx.de> (raw)
In-Reply-To: <1131553363.3271.1.camel@mulgrave>
James Bottomley wrote:
>>> #define ATA_16 0x85 /* 16-byte pass-thru */
>>> #define ATA_12 0xa1 /* 12-byte pass-thru */
>>
is this all, or do we have a preliminary SATL in kernel yet? cant find.
how about full definitions of the pasthru cdb's in kernel structs and approbiate ioctls?
for hdparm ata-security theres ide taskfile used, can scsi command sequences combined with ide taskfiles
which use own ioctls?
are taskfiles needed for this in any case?
for smartctl theres sg_cmnd_io() with (user definable?) struct io_hdr.
so i would try passthru test first with smartctl by adding passthru opcode ATA_12 to smartctl struct scsi_cmd_io io_hdr.
later combining scsi ioparm structs and passthru opcode with usable contents of ide taskfile parm structs in user space.
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?
thx
tom
next prev parent reply other threads:[~2005-11-10 6:20 UTC|newest]
Thread overview: 15+ 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
2005-11-09 15:35 ` [DOC PATCH] T10/04-262r8 thomas schorpp
2005-11-09 15:56 ` Jeff Garzik
2005-11-09 16:22 ` James Bottomley
2005-11-10 6:19 ` thomas schorpp [this message]
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 ` [DOC PATCH] T10/04-262r8 James Bottomley
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=4372E66F.5070802@gmx.de \
--to=t.schorpp@gmx.de \
--cc=linux-ide@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.