From: Jeff Garzik <jgarzik@pobox.com>
To: dougg@torque.net
Cc: Tejun Heo <htejun@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: fix ATA passthrough handling for ATAPI devices
Date: Sat, 21 Oct 2006 16:13:31 -0400 [thread overview]
Message-ID: <453A7F6B.1010205@pobox.com> (raw)
In-Reply-To: <453A7C6B.3050108@torque.net>
Douglas Gilbert wrote:
> The 16 byte CDB that Tejun is talking about is the
> ATA PASS THROUGH (16) SCSI command. That is valid to
I'm talking about the changes to the implementation, which appear to
mistakenly allow 16-byte CDBs through to the ATAPI device, even if it
only supports 12-byte CDBs.
I am quite aware of the ATA passthru SCSI command. Heck, the spec had
input from me. I'm talking about something different.
> The only clash between MMC and SATL SCSI opcodes is
> with opcode 0xA1: BLANK in MMC and ATA PASS THROUGH (12)
Ok, so the answer is, yes there is a clash, and thus this change will
remove the ability for working-today setups to use BLANK.
In order to avoid breaking working setups, a method must be found which
tells the SATL to not filter out the ATA passthru commands.
> This is all about being able to send ATA commands to
> ATAPI devices that are valid for PACKET devices, examples:
> IDENTIFY PACKET DEVICE
> SET FEATURES
> IDENTIFY DEVICE (should abort command + set signature)
> DEVICE RESET
> and I assume there are others.
I am quite aware of the purpose of ATA passthru :)
Jeff
next prev parent reply other threads:[~2006-10-21 20:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 5:09 [PATCH] libata: fix ATA passthrough handling for ATAPI devices Tejun Heo
2006-10-21 19:16 ` Jeff Garzik
2006-10-21 20:00 ` Douglas Gilbert
2006-10-21 20:13 ` Jeff Garzik [this message]
2006-10-21 21:18 ` Douglas Gilbert
2006-10-21 21:40 ` Jeff Garzik
2006-10-21 23:11 ` Douglas Gilbert
2006-10-23 2:55 ` Tejun Heo
2006-10-23 13:58 ` Douglas Gilbert
2006-11-01 2:03 ` 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=453A7F6B.1010205@pobox.com \
--to=jgarzik@pobox.com \
--cc=dougg@torque.net \
--cc=htejun@gmail.com \
--cc=linux-ide@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).