From: Matthew Dharm <mdharm-scsi@one-eyed-alien.net>
To: James Bottomley <James.Bottomley@SteelEye.com>,
torvalds@transmeta.com,
Linux SCSI list <linux-scsi@vger.kernel.org>,
Greg KH <greg@kroah.com>,
USB Developers <linux-usb-devel@lists.sourceforge.net>
Subject: Re: PATCH; make sr.c respect use_10_for_ms
Date: Sun, 22 Jun 2003 12:56:50 -0700 [thread overview]
Message-ID: <20030622125650.D21716@one-eyed-alien.net> (raw)
In-Reply-To: <20030622124917.A21716@one-eyed-alien.net>; from mdharm-scsi@one-eyed-alien.net on Sun, Jun 22, 2003 at 12:49:17PM -0700
[-- Attachment #1: Type: text/plain, Size: 2125 bytes --]
On Sun, Jun 22, 2003 at 12:49:17PM -0700, Matthew Dharm wrote:
> On Sun, Jun 22, 2003 at 08:58:00AM -0500, James Bottomley wrote:
> > On Sat, 2003-06-21 at 23:24, Matthew Dharm wrote:
> > > On Sat, Jun 21, 2003 at 09:54:46PM -0500, James Bottomley wrote:
> > > > }
> > > > - n = buffer[3] + 4;
> > > > + n = rc;
> > > > cd->cdi.speed = ((buffer[n + 8] << 8) + buffer[n + 9]) / 176;
> > >
> > > This bit isn't right. n is supposed to point to the start of the page
> > > data, not the page header. The header is a different size if the command
> > > is 6-byte or 10-byte.
> >
> > Yes it is.
> >
> > That's why I eliminated the dbd bit. Your patch was calculating the
> > offsets past the dbd headers. However, if you tell the mode sense not
> > to send any dbd headers (which are pointless, because the routine isn't
> > interested in them), then you don't have to skip past them. and the mode
> > data begins just past the mode header.
>
> But (as I read it -- remember I'm not an expert), the old sr.c code didn't
> set the DBD bit, just like the new code. So whatever formula applied to
> the old code should apply to the new code, yes?
Okay, according to my copy of the SCSI-2 spec:
A disable block descriptors (DBD) bit of zero indicates that the target
may return zero or more block descriptors in the returned MODE SENSE data
(see 8.3.3), at the target's discretion. A DBD bit of one specifies that
the target shall not return any block descriptors in the returned MODE
SENSE data.
The code James sent sets DBD to 0 -- I like that, as many usb-storage
devices choke when DBD is set to 1. I believe in avoiding the DBD bit as
much as possible, and James seems to have eliminated it.
However, DBD==0 means that a block descriptor is likely to be returned --
so we need to add in the size of the block descriptor header.
Matt
--
Matthew Dharm Home: mdharm-usb@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver
Hi. I have my back hairs caught in my computer fan.
-- Customer
User Friendly, 8/20/1998
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2003-06-22 19:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-21 23:59 PATCH; make sr.c respect use_10_for_ms Matthew Dharm
2003-06-22 0:07 ` Linus Torvalds
2003-06-22 0:12 ` Matthew Dharm
2003-06-22 0:21 ` Linus Torvalds
2003-06-22 0:30 ` Matthew Dharm
2003-06-22 0:38 ` Linus Torvalds
2003-06-22 0:46 ` Matthew Dharm
2003-06-22 0:25 ` James Bottomley
2003-06-22 0:46 ` Matthew Dharm
2003-06-22 2:54 ` James Bottomley
2003-06-22 4:24 ` Matthew Dharm
2003-06-22 5:05 ` Douglas Gilbert
2003-06-22 13:58 ` James Bottomley
2003-06-22 19:49 ` Matthew Dharm
2003-06-22 19:56 ` Matthew Dharm [this message]
2003-06-22 20:37 ` James Bottomley
2003-06-22 21:06 ` Matthew Dharm
2003-06-23 14:33 ` James Bottomley
2003-06-23 17:30 ` Matthew Dharm
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=20030622125650.D21716@one-eyed-alien.net \
--to=mdharm-scsi@one-eyed-alien.net \
--cc=James.Bottomley@SteelEye.com \
--cc=greg@kroah.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=torvalds@transmeta.com \
/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