From: Phil Dibowitz <phil@ipom.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Meelis Roos <mroos@linux.ee>, Andrew Morton <akpm@osdl.org>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: [linux-usb-devel] Fw: garbled usb storage scsi vendor & model in 2.6.19-rc1
Date: Tue, 24 Oct 2006 14:43:22 -0700 [thread overview]
Message-ID: <453E88FA.3070304@ipom.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0610241557500.6203-100000@iolanthe.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
Alan Stern wrote:
> There's a comment about this in the source code, asking what should be
> done if the INQUIRY response is too short (as it is here). Maybe the best
> approach would be always to assume the first 36 bytes are valid, even when
> the device says they aren't. It ought to solve your problem, and it's
> no worse than what we're doing now.
>
> The patch is below. This replaces the patch I sent earlier.
Perhaps a better approach might be to set the product and vendor to some
specific string if the device says it isn't providing one? In the new model,
can't we still have the chance of showing garbage if the device really isn't
setting anything useful? So what if we show "Unknown" and "Unknown" or
something similar in the event that the device sets the 'invalid' bit?
Just a thought...
--
Phil Dibowitz phil@ipom.com
Freeware and Technical Pages Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"Be who you are and say what you feel, because those who mind don't matter
and those who matter don't mind."
- Dr. Seuss
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2006-10-24 21:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061018223058.65f1cf5e.akpm@osdl.org>
2006-10-19 15:42 ` [linux-usb-devel] Fw: garbled usb storage scsi vendor & model in 2.6.19-rc1 Alan Stern
2006-10-23 4:57 ` Meelis Roos
2006-10-23 14:05 ` [linux-usb-devel] " Alan Stern
2006-10-24 19:35 ` Meelis Roos
2006-10-24 20:30 ` [linux-usb-devel] " Alan Stern
2006-10-24 20:47 ` Meelis Roos
2006-10-24 21:43 ` Phil Dibowitz [this message]
2006-10-24 23:18 ` Matthew Dharm
2006-10-25 15:11 ` [linux-usb-devel] " Alan Stern
2006-10-25 15:08 ` Alan Stern
2006-10-24 22:39 ` Stefan Richter
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=453E88FA.3070304@ipom.com \
--to=phil@ipom.com \
--cc=akpm@osdl.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mroos@linux.ee \
--cc=stern@rowland.harvard.edu \
/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