public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: use_10_for_ms revisited?
Date: Sun, 29 Jun 2003 19:36:32 +0200	[thread overview]
Message-ID: <20030629173632.GA15024@win.tue.nl> (raw)
In-Reply-To: <3EFF14BD.3030406@pobox.com>

On Sun, Jun 29, 2003 at 12:33:01PM -0400, Jeff Garzik wrote:
> Andries Brouwer wrote:
> >The firmware of existing devices is not magically updated when
> >a new draft standard is released. So reading yesterdays version
> >gives very little information on the real world.
> 
> I'm not implying otherwise...  I just think a hueristic can be found 
> that works with these devices.
> 
> 
> >[And no, none of my USB devices announces MMC-4 compliance.]
> 
> Would you mind posting the first 8 bytes of any of these USB storage 
> devices' INQUIRY pages?
> 

Two that I have right here yield 0 80 2 2 20 0 0 0 and
0 80 0 2 1F 0 0 0, respectively. (All in hex.)

The 20 in the first is a bug - the INQUIRY gives only 36 bytes.

You do not make me happy with wonderful SCSI patches right now.
I like to go slowly.

[I did introduce this use_10_for_ms; it allows a very large
cleanup in the usb-storage code. Submitted the SCSI part of
the patch and waited for it to be applied. That took a while
and when it went in I was a bit short on Linux time. So Matt
got impatient and started doing the rest himself. He patched
sr.c - something I would not have done, I considered the SCSI
part settled - perhaps things broke a bit but James went in and
fixed some things again. So maybe we are now again ready for
the intended large cleanup. I would like to see that done,
and afterwards see this area stable for a few kernel versions.]

Andries


  reply	other threads:[~2003-06-29 17:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-29  6:30 use_10_for_ms revisited? Jeff Garzik
2003-06-29  6:38 ` Matthew Dharm
2003-06-29  6:47   ` Jeff Garzik
2003-06-29  6:54     ` Matthew Dharm
2003-06-29  7:27       ` Jeff Garzik
2003-06-29 10:31         ` Alan Cox
2003-06-29 10:22 ` Andries Brouwer
2003-06-29 16:33   ` Jeff Garzik
2003-06-29 17:36     ` Andries Brouwer [this message]
2003-06-29 17:58       ` Jeff Garzik
2003-06-29 18:02         ` Matthew Dharm
2003-06-29 18:17           ` Jeff Garzik
2003-06-29 18:35             ` Matthew Dharm
2003-06-29 18:36             ` James Bottomley
2003-06-29 19:07               ` Jeff Garzik
2003-06-30  0:23                 ` Matthew Dharm
2003-06-30  3:24                   ` Jeff Garzik
2003-06-29 18:25         ` Andries Brouwer
2003-06-29 18:32           ` 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=20030629173632.GA15024@win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=jgarzik@pobox.com \
    --cc=linux-scsi@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