From: Pat LaVarre <p.lavarre@ieee.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata SATAPI no data
Date: 30 May 2004 09:24:03 -0600 [thread overview]
Message-ID: <1085930643.4318.6.camel@patibmrh9> (raw)
In-Reply-To: <1085607715.4148.128.camel@patibmrh9>
> > Subject: Re: [PATCH] atapi request sense work
> > ...
> > in fact we have NOT yet explained
> > how to insert an ATA op x00 "NOP" ...
> > Instead, my kernel goes down ...
Precisely as expected from our past work,
2.6.7-rc2, even with the not-substantive ata_check_bmdma rewording,
still can't cope with expecting no data for a CDB. A CDB that actually
copies is ok only if I lie to say I expect data:
$ # "INQUIRY" for up to zero bytes
$ sudo plscsi -i 0x12 -x "12 00:00:00 00 00"
$
Honesty receives its expected penalty:
$ sudo plscsi -x "12 00:00:00 00 00"
$
Message from syslogd@patibmrh9 at Sun May 30 09:18:00 2004 ...
patibmrh9 kernel: Disabling IRQ #18
$
Pat LaVarre
prev parent reply other threads:[~2004-05-30 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 21:41 [PATCH] libata SATAPI no data Pat LaVarre
2004-05-30 15:24 ` Pat LaVarre [this message]
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=1085930643.4318.6.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