Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Pat LaVarre <p.lavarre@ieee.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata atapi work #2.1
Date: 17 May 2004 08:56:07 -0600	[thread overview]
Message-ID: <1084805767.3083.10.camel@patibmrh9> (raw)
In-Reply-To: <40A7F757.9020200@pobox.com>

Jeff G:

> something is working...
 
Yes!

In my one sample, even misaligning a dd-shattered stream costs me only
0.5 GB/min at the outside of the disc, so command/ status overhead is
running reasonably low.

> Please let me know what patches (if any
> besides #define) are needed for setup, after
> you include patch #2.2 and #2.3 in the pile.

I will revert to -bk3 vanilla, then apply 2.* from linux-ide, then
report back.

> Two main things on the SCSI end of ATAPI to
> do:
> * issue REQUEST SENSE, to simulate an
> auto-sensing scsi device

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".

I will have to discover how to auto sense only after a plain failure,
not inappropriately after a timeout.  Last I checked, the code was
written to see any failure as if it were a timeout.

> * in INQUIRY output, simulate compliance with
> MMC-3.  Linux SCSI stack is not aware that all
> ATAPI devices report zeroes in the SCSI version
> field (as do some USB storage devices).  So,
> we fake it.

I will try to munge the otherwise transparent pass thru of op x12
"INQUIRY" after the pattern of:

http://lxr.linux.no/source/drivers/usb/storage/protocol.c?v=2.6.5#L62

62 static void fix_inquiry_data(Scsi_Cmnd *srb)
...
82         /* Change the SCSI revision number */
83         databuf[2] = (databuf[2] & ~7) | 2;

I suppose there is no saving the transparency of ioctl CDROM_SEND_PACKET
and ioctl SG_IO.  Because of this linux-scsi legacy, we have to lose the
bits that we read from the device.

Pat LaVarre



  reply	other threads:[~2004-05-17 14:56 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 [this message]
2004-05-17 17:57     ` Jeff Garzik
2004-05-17 19:24       ` Pat LaVarre
2004-05-18  1:48     ` Pat LaVarre
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=1084805767.3083.10.camel@patibmrh9 \
    --to=p.lavarre@ieee.org \
    --cc=jgarzik@pobox.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