From: Luben Tuikov <tluben@rogers.com>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-scsi@vger.kernel.org, Jens Axboe <axboe@suse.de>
Subject: Re: "do ata" scsi command?
Date: Fri, 16 May 2003 15:02:49 -0400 [thread overview]
Message-ID: <3EC535D9.10504@rogers.com> (raw)
In-Reply-To: <20030516183732.GA102@win.tue.nl>
Andries Brouwer wrote:
> On Fri, May 16, 2003 at 12:35:43PM -0400, Jeff Garzik wrote:
>
>
>>I have chosen the standard, existing scsi-generic nterface as the one by
>>which raw taskfiles will be sent to devices. The taskfile will be
>>wrapped inside a SCSI cdb. To me this solution is the most flexibility
>>for least cost.
>>
>>So, what opcode do I choose for "send taskfile"? Either (a) pick a
>>vendor-specific one, or (b) someone else already chose an opcode.
>>
>>So my post was really these questions: a or b? if b, what opcode?
>
>
> 0xAA ?
>
> (have you seen rfc2143 ?)
This is for a communications device, which according to the
spec is obsolete, but most importantly it's not a block device
opcode.
But the idea isn't new -- AFAIR, the 3ware LLDD/userspace tools
use(d) 0x80 XDWRITE EXTENDED (16) which is _optional_ for block devices.
For what pupose, it's closed, but it will have something to do with
the hdwr array management/id.
--
Luben
next prev parent reply other threads:[~2003-05-16 18:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 23:02 "do ata" scsi command? Jeff Garzik
2003-05-16 6:03 ` Jens Axboe
2003-05-16 15:54 ` Jeff Garzik
2003-05-16 16:05 ` Jens Axboe
2003-05-16 16:30 ` Jeff Garzik
2003-05-16 16:35 ` Jens Axboe
2003-05-16 16:41 ` Jeff Garzik
2003-05-16 16:43 ` Jens Axboe
2003-05-16 16:46 ` Jeff Garzik
2003-05-17 4:17 ` Douglas Gilbert
2003-05-17 7:49 ` Luben Tuikov
2003-05-16 16:35 ` Jeff Garzik
2003-05-16 16:40 ` Jens Axboe
2003-05-16 16:45 ` Jeff Garzik
2003-05-16 18:37 ` Andries Brouwer
2003-05-16 19:02 ` Luben Tuikov [this message]
2003-05-16 18:50 ` Luben Tuikov
2003-05-16 19:31 ` 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=3EC535D9.10504@rogers.com \
--to=tluben@rogers.com \
--cc=aebr@win.tue.nl \
--cc=axboe@suse.de \
--cc=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