public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Luben Tuikov <tluben@rogers.com>
Cc: linux-scsi@vger.kernel.org, axboe@suse.de
Subject: Re: "do ata" scsi command?
Date: Fri, 16 May 2003 15:31:16 -0400	[thread overview]
Message-ID: <3EC53C84.7020306@pobox.com> (raw)
In-Reply-To: <3EC53307.5070908@rogers.com>

Luben Tuikov wrote:
> It seems like you want what the 3ware LLDD is doing.  The format
> and specs are closed, but the implementation is open: ioctl
> and a char device ioctl.
> 
> What you lose is the block/scsi synchronizaion, but if you want
> to support _closed_ vendor extensions, that's what you get.

This is for programming the drive via userspace.  Same purpose as 
HDIO_DRIVE_TASKFILE.  I would rather move non-essential stuff to 
userspace where possible.  Sending taskfiles directly allows one to 
validate the driver without other parts of the kernel getting in the 
way.  That allows me to narrow down problems to my driver, or 
not-my-driver.  :)

But since it's _far_ more contentious than I thought it would be, I'll 
just put it off until later.


> Unless what you want to support has a command mapping already
> in SCSI?  Did you check SBC-2, SMC-2, SCC-2, SES-2?  Wouldn't
> you find any CDB's there which would fit in?  My guess is not.

I would like to create a target that is fully verifyable as SCSI-2, and 
eventually SCSI-3.  So I _do_ want to support such mappings.  But that 
is parallel to the capability of talking directly to the ATA device.

	Jeff




      reply	other threads:[~2003-05-16 19:18 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
2003-05-16 18:50 ` Luben Tuikov
2003-05-16 19:31   ` 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=3EC53C84.7020306@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=axboe@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tluben@rogers.com \
    /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