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: Mon, 17 May 2004 13:57:45 -0400 [thread overview]
Message-ID: <40A8FD19.8050906@pobox.com> (raw)
In-Reply-To: <1084805767.3083.10.camel@patibmrh9>
Pat LaVarre wrote:
>>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.
Last night's -bk4 should include everything except the obvious patch to
include/linux/libata.h to define ATAPI_ENABLE_DMADIR.
> 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.
Good guess, very close: the code is written to see any timeout as if it
were a failure. Calling ata_eng_timeout() function is unfortunately a
bit misnamed.
>>* 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;
Yes, something like this is needed.
We need to indicated MMC-3...
Jeff
next prev parent reply other threads:[~2004-05-17 17:58 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 [this message]
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=40A8FD19.8050906@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox