All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Pat LaVarre <p.lavarre@ieee.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata atapi work #2.1
Date: Sun, 16 May 2004 19:20:55 -0400	[thread overview]
Message-ID: <40A7F757.9020200@pobox.com> (raw)
In-Reply-To: <1084721991.3085.6.camel@patibmrh9>

Pat LaVarre wrote:
> I now see SATA stream up past 1.5 GB/min via ioctl SG_IO read & write of
> the disc blocks, after I apply together all four of the patches you
> first posted as:

Sounds like something is working...


>>Subject: [PATCH] libata update 20040515-1
>>Subject: [PATCH] libata atapi work #2.1
>>Subject: [PATCH] libata DMADIR support
>>Subject: [PATCH] Re: SATA ATAPI work in progress
> 
> 
> Heads up, I was myself slow to appreciate:
> 
> Yes still in -bk3 after patch.2.1 we need to apply that fourth patch
> i.e. what I had termed patch.7 i.e. ata_host_intr += ATA_PROT_ATAPI_DMA.

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.


>>Once I add the code to issue a REQUEST SENSE, ...
> 
> 
> Also, of course, to avoid dying for the lack of auto sense, I have to
> duck all errors.

Yes.

Two main things on the SCSI end of ATAPI to do:
* issue REQUEST SENSE, to simulate an auto-sensing scsi device
* 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.

	Jeff




  reply	other threads:[~2004-05-16 23:21 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 [this message]
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
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=40A7F757.9020200@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=p.lavarre@ieee.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 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.