From: Mathieu Fluhr <mfluhr@nero.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Jeff Garzik <jeff@garzik.org>, Robert Hancock <hancockr@shaw.ca>,
LKML <linux-kernel@vger.kernel.org>,
ide <linux-ide@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Inquiry data and emulated SG devices
Date: Thu, 18 Oct 2007 14:44:48 +0200 [thread overview]
Message-ID: <1192711488.3254.11.camel@de-c-l-110.nero-de.internal> (raw)
In-Reply-To: <1192709602.13229.27.camel@localhost.localdomain>
On Thu, 2007-10-18 at 08:13 -0400, James Bottomley wrote:
> On Thu, 2007-10-18 at 13:57 +0200, Mathieu Fluhr wrote:
> > On Thu, 2007-10-18 at 06:06 -0400, Jeff Garzik wrote:
> >
> > > The SCSI midlayer makes a lot of "if scsi version <= 2" choices. In the
> > > case of ATAPI, we do not want to force ATAPI down the path of ancient
> > > SCSI devices, as this disables some MMC features that modern ATAPI
> > > devices support.
> >
> > If I fully understand your point, if this faking code wasn't present,
> > and if the inquiry data was left as it is, all modern ATAPI devices
> > would be considered as really old SCSI devices. Am I right?
>
> Not really. Firstly, a lot of ATAPI devices report the correct
> compliance level and secondly, the consequence of reporting no
> compliance (level 0) is that the mid layer will be very careful to use
> the most minimal command set it can (the usual consequence of sending a
> USB device a command it doesn't understand is to have it crash).
>
Ok, then, what about what the standard is saying regarding the ANSI
version field? Quoting to the latest MtFuji draft (Section 17.7.1):
"The ANSI Version field shall contain a non-zero value to comply with
this version of the Specification for a SCSI logical unit or zero for
an ATAPI logical unit."
and this is exactly how we see that the logical unit is a real SCSI one
or an ATAPI one.
> However, this will have no effect for at least CDs: The sr driver is
> only interested in the MMC compliance level not the SCSI compliance
> level.
We are not using the sr driver to perform our SCSI commands, as it is
filtering which CDB is allowed and which isn't. As we have some
vendor-specific SCSI commands (like the one for changing booktype), we
are using the sg driver to be able to use them.
> > As far as I saw in libata-scsi.c there a SCSI-to-ATAPI and ATAPI-to-SCSI
> > translator that automatically transform the command sent... Am I also
> > right on this point?
>
> The former only, I believe.
Absolutly... but if the inquiry data buffer gets modified by the
midlayer, after that I am not able anymore to setup correctly the
commands for the _real_ interface. (once again, the blank command
example).
Mathieu
next prev parent reply other threads:[~2007-10-18 12:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.PgEHbZ0E5ogcX8bZwvrUeZB+eJs@ifi.uio.no>
2007-10-18 1:22 ` Inquiry data and emulated SG devices Robert Hancock
2007-10-18 1:31 ` Jeff Garzik
2007-10-18 9:59 ` Mathieu Fluhr
2007-10-18 10:06 ` Jeff Garzik
2007-10-18 11:57 ` Mathieu Fluhr
2007-10-18 12:13 ` James Bottomley
2007-10-18 12:44 ` Mathieu Fluhr [this message]
2007-10-18 10:57 ` 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=1192711488.3254.11.camel@de-c-l-110.nero-de.internal \
--to=mfluhr@nero.com \
--cc=James.Bottomley@SteelEye.com \
--cc=hancockr@shaw.ca \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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