mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mathieu Fluhr <mfluhr@nero.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Inquiry data and emulated SG devices
Date: Mon, 15 Oct 2007 18:02:11 +0200	[thread overview]
Message-ID: <1192464131.3234.25.camel@de-c-l-110.nero-de.internal> (raw)

Hello all,


First of all, let me introduce myself a little bit. I am the responsable
for the development of the Nero Linux burning application. So I have
access to all the source code of the application.


Now let's go with the story: It seems that there is a slight problem in
the libata (and also the new pata_xxx) interfaces with the data returned
by the INQUIRY cmd since every S-ATA or IDE device is assumed to be a
SCSI dev.

Normally, the IDE devices (physical type) can be differentied with the
format field of the inquiry data, i.e. the last bytes (ANSI version) are
set to 0 -> This is done and works great with USB external devices for
example.


The thing is that with S-ATA/IDE devices when using the libata/pata
driver, the version field is (always?) set to 5, as any _real_ SCSI
device, and thus the physical device type cannot be checked anymore.

I cannot go so deep in details, but our burn engine is differentiating
IDE and read-good-old-SCSI devices and handles them sometimes in a
different way, so this differenciation is really important for us.

   -> How can I detect the real physical device type now?



Best Regards,
Mathieu


-- 
*********************************************************
Mathieu Fluhr
Linux Development Team Leader

E-mail: mfluhr@nero.com


NERO - BECAUSE TECHNOLOGY COUNTS
www.nero.com

*********************************************************
Nero AG
Im Stoeckmaedle 13-15
76307 Karlsbad
Germany

Vorstand/CEO: Richard Lesser
Aufsichtsratvorsitzender/chairman of the supervisory board: Jim Corbett

Amtsgericht Mannheim HRB 362519
*********************************************************
This e-mail may contain confidential and/or
privileged information. If you are not the intended
recipient (or have received this e-mail in error)
please notify the sender immediately and destroy
this e-mail. Any unauthorised copying, disclosure
or distribution of the material in this e-mail is
strictly forbidden.
********************************************************* 


             reply	other threads:[~2007-10-15 16:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-15 16:02 Mathieu Fluhr [this message]
     [not found] <fa.PgEHbZ0E5ogcX8bZwvrUeZB+eJs@ifi.uio.no>
2007-10-18  1:22 ` 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
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=1192464131.3234.25.camel@de-c-l-110.nero-de.internal \
    --to=mfluhr@nero.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®