Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata atapi work #2.1
Date: 17 May 2004 19:48:34 -0600	[thread overview]
Message-ID: <1084844914.3211.182.camel@patibmrh9> (raw)
In-Reply-To: <1084805767.3083.10.camel@patibmrh9>

> > on the SCSI end of ATAPI ...
> > * issue REQUEST SENSE, to simulate an
> > auto-sensing scsi device
> ...
> I will have to discover how to auto sense only after a plain failure,
> not inappropriately after a timeout.
> ...
> I will try to create a desired inference of ATAPI op x03 "REQUEST SENSE"
> to immediately follow the failing command, after the pattern of the
> existing inference of ATA op xA1 "IDENTIFY".

Sorry, no good.

That won't work well til after someone finishes the "(TODO: investigate
using standard PIO-IN paths)" of ata_dev_identify of
drivers/scsi/libata-core.c to replace the "we hand-code it here" found
there now.

Also ATA folk might resist adding a for-them-unused { u8 sense[0x100]; }
member to the (struct ata_port), by way of analogy with the { u16
id[ATA_ID_WORDS]; } now found there in include/linux/libata.h.

Pat LaVarre



  parent reply	other threads:[~2004-05-18  1:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-16 15:39 [PATCH] libata atapi work #2.1 Pat LaVarre
2004-05-16 23:20 ` Jeff Garzik
2004-05-17 14:56   ` Pat LaVarre
2004-05-17 17:57     ` Jeff Garzik
2004-05-17 19:24       ` Pat LaVarre
2004-05-18  1:48     ` Pat LaVarre [this message]
2004-05-18 21:10       ` Pat LaVarre
  -- strict thread matches above, loose matches on Subject: below --
2004-05-15 22:12 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=1084844914.3211.182.camel@patibmrh9 \
    --to=p.lavarre@ieee.org \
    --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