From: James Bottomley <James.Bottomley@steeleye.com>
To: Matthew Dharm <mdharm-scsi@one-eyed-alien.net>
Cc: 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: 22 Jun 2003 08:58:00 -0500 [thread overview]
Message-ID: <1056290282.1979.4.camel@mulgrave> (raw)
In-Reply-To: <20030621212406.N2811@one-eyed-alien.net>
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.
James
next prev parent reply other threads:[~2003-06-22 13:44 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 [this message]
2003-06-22 19:49 ` Matthew Dharm
2003-06-22 19:56 ` Matthew Dharm
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=1056290282.1979.4.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=greg@kroah.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mdharm-scsi@one-eyed-alien.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