All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: Doug Maxey <dwm@maxeymade.com>
Cc: Patrick Mansfield <patmans@us.ibm.com>,
	Jeff Garzik <jgarzik@pobox.com>,
	Albert CC Lee <albertcc@tw.ibm.com>,
	SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: [RFC] mode pages for ATA/ATAPI devices via libata
Date: Fri, 13 May 2005 15:19:39 +1000	[thread overview]
Message-ID: <428438EB.6050400@torque.net> (raw)
In-Reply-To: <200505111842.j4BIgHY8019500@falcon30.maxeymade.com>

Doug Maxey wrote:
> ahem, the neural pathways are not just worn, they have become ruts. =) 
> 
> s/mode/vpd/.
> 
> On Wed, 11 May 2005 13:01:25 CDT, Doug Maxey wrote:
> 
>>Howdy,
>>
>>When a ATA/ATAPI device is attached via libata, what should the handling 
>>be for mode pages that do not exist in the device?
>>
>>Assuming the page being asked for is 0x83, should libata fake up the
>>page from the IDENTIFY (PACKET) DEVICE data?  Or should it just respond
>>there is no page 0x83 as it does now in INQUIRY?  Likewise for 0x80?

Doug,
For ATAPI, the packet interface is almost always
carrying a SCSI command set (exceptions anybody??),
typically MMC (for CD/DVD drives). Recent SPC-3 drafts
(to which MMC-4,5 should comply) have made the device
identification VPD page (0x83) mandatory. I haven't
seen any compliance yet (or for that matter a drive that
implements feature 0x108: LU serial number).

For ATA, work is being done on a SCSI-ATA Translation
draft standard see:
http://www.t10.org/ftp/t10/drafts/sat/sat-r03.pdf
section 8.1.3.3 .

Doug Gilbert

  reply	other threads:[~2005-05-13  5:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-11 18:01 [RFC] mode pages for ATA/ATAPI devices via libata Doug Maxey
2005-05-11 18:42 ` Doug Maxey
2005-05-13  5:19   ` Douglas Gilbert [this message]
2005-05-13  6:03     ` Doug Maxey
2005-05-13  8:10       ` Douglas Gilbert
2005-05-13 17:06 ` 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=428438EB.6050400@torque.net \
    --to=dougg@torque.net \
    --cc=albertcc@tw.ibm.com \
    --cc=dwm@maxeymade.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=patmans@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.