From: Luben Tuikov <ltuikov@yahoo.com>
To: dougg@torque.net, James Bottomley <James.Bottomley@SteelEye.com>
Cc: Mark Lord <liml@rtr.ca>, Linux IDE <linux-ide@vger.kernel.org>,
Tejun Heo <htejun@gmail.com>, Jeff Garzik <jeff@garzik.org>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] SCSI, libata: add support for ATA_16 commands to libata ATAPI devices
Date: Sun, 7 Jan 2007 21:00:37 -0800 (PST) [thread overview]
Message-ID: <141410.19366.qm@web31811.mail.mud.yahoo.com> (raw)
In-Reply-To: <459C066D.30507@torque.net>
--- Douglas Gilbert <dougg@torque.net> wrote:
>
> I seem to be fighting a losing battle against the mindset
That may be the case.
> It is the _transport_ that should block the command,
> if it so chooses. In this case the transport is a
> virtual one between sr/sg and libata and libata should
> recognize SCSI ATA PASS-THROUGH (12+16) cdbs as
> transport related and not (directly) to be sent to
> the logical unit. And it is at this level we should
> add the wrinkle that if the pdt=5 (cd or dvd) then
> don't translate ATA_12. [I have already been around this
> loop with Luben and his SATL: sorted with the minimum
> of fuss.]
LOL, I don't think your mentioning my name in an email
to bottomley is going to convince him of anything, in
fact it may prompt him to do it the opposite way.
Good luck!
As to the "been around this loop", the fix was a two
liner, without checking the PDT, and ATA_16, ATA_12
and BLANK work as expected.
> ** I have been told that USB disk enclosures being designed
> now will include at a SATL. This will mean smartmontools
Absolutely. Many reasons, one of which is having to deal
with battles like this one, probably the least one, but
still a reason which is sometimes mentioned.
Luben
next prev parent reply other threads:[~2007-01-08 5:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 0:35 [PATCH] SCSI, libata: add support for ATA_16 commands to libata ATAPI devices Mark Lord
2007-01-03 1:40 ` James Bottomley
2007-01-03 5:42 ` Mark Lord
2007-01-03 15:31 ` James Bottomley
2007-01-03 15:45 ` Jeff Garzik
2007-01-03 15:57 ` James Bottomley
2007-01-03 17:58 ` Mark Lord
2007-01-03 19:39 ` Douglas Gilbert
2007-01-03 21:41 ` James Bottomley
2007-01-03 23:57 ` Mark Lord
2007-01-04 15:09 ` Jens Axboe
2007-01-04 15:29 ` Mark Lord
2007-01-04 15:51 ` Jens Axboe
2007-01-08 5:00 ` Luben Tuikov [this message]
[not found] ` <200701311346.26644.liml@rtr.ca>
2007-02-01 0:33 ` [PATCH] RESEND: " Tejun Heo
2007-02-01 0:42 ` Mark Lord
2007-02-01 0:48 ` James Bottomley
2007-02-01 0:53 ` Mark Lord
2007-02-01 0:48 ` Tejun Heo
2007-02-01 1:01 ` Mark Lord
2007-02-01 8:30 ` Jeff Garzik
2007-02-01 8:28 ` Jeff Garzik
2007-02-01 8:43 ` Tejun Heo
2007-02-01 9:54 ` Jeff Garzik
2007-02-01 15:09 ` James Bottomley
2007-02-01 15:15 ` Jeff Garzik
2007-02-01 20:21 ` Douglas Gilbert
2007-02-01 20:30 ` Jeff Garzik
2007-02-02 9:11 ` Christoph Hellwig
2007-02-01 8:26 ` Jeff Garzik
2007-02-01 8:35 ` Tejun Heo
2007-02-01 9:52 ` Jeff Garzik
2007-02-01 0:44 ` 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=141410.19366.qm@web31811.mail.mud.yahoo.com \
--to=ltuikov@yahoo.com \
--cc=James.Bottomley@SteelEye.com \
--cc=dougg@torque.net \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--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 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).