From: Pat LaVarre <p.lavarre@ieee.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi@vger.kernel.org, usb-storage@lists.one-eyed-alien.net,
Alan Stern <stern@rowland.harvard.edu>,
Philippe Troin <phil@fifi.org>
Subject: Re: [usb-storage] Re: iRiver H100 series and usb-storage issues
Date: 08 Jun 2004 10:10:05 -0600 [thread overview]
Message-ID: <1086711004.3647.23.camel@patibmrh9> (raw)
In-Reply-To: <1086709937.2105.8.camel@mulgrave>
James B:
> underflow ... meaning ... supposed to be
> "return an error if you transfer fewer than underflow bytes".
> The error's not specified,
> but something like DID_ERROR with SUGGEST_RETRY should be fine.
Incisive, thank you.
> ... Usually HBAs ignore underflow,
> because it simply works correctly ...
Is there an easy way to test whether an HBA implements underflow
correctly?
For example, to inject an underflow into ioctl SG_IO, trivially I ask
for a one block read CDB to fill a two block buffer.
Pat LaVarre
P.S. A possibly relevant glance into the source is:
http://lxr.linux.no/search?v=2.6.5&string=underflow
search: SCSI
http://lxr.linux.no/source/drivers/scsi/sd.c?v=2.6.5#L374
...
static int sd_init_command(struct scsi_cmnd * SCpnt)
...
SCpnt->underflow = this_count << 9;
...
next prev parent reply other threads:[~2004-06-08 16:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 23:42 Patch for iriver-mp3player Tobias Lieber
2004-06-06 14:48 ` James Bottomley
2004-06-06 22:32 ` Matthew Dharm
2004-06-07 14:36 ` Alan Stern
2004-06-28 19:42 ` Tobias Lieber
2004-06-07 14:47 ` iRiver H100 series and usb-storage issues Alan Stern
2004-06-07 19:43 ` Philippe Troin
2004-06-07 20:22 ` Alan Stern
2004-06-07 21:18 ` Philippe Troin
2004-06-07 22:27 ` [usb-storage] " Pat LaVarre
2004-06-08 14:24 ` Alan Stern
2004-06-08 15:52 ` James Bottomley
2004-06-08 16:10 ` Pat LaVarre [this message]
2004-06-08 16:16 ` James Bottomley
2004-06-08 17:01 ` Mike Anderson
2004-06-08 14:19 ` Alan Stern
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=1086711004.3647.23.camel@patibmrh9 \
--to=p.lavarre@ieee.org \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=phil@fifi.org \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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