public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Dharm <mdharm-scsi@one-eyed-alien.net>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Tobias Lieber <little.tobias@gmx.de>,
	Alan Stern <stern@rowland.harvard.edu>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Patch for iriver-mp3player
Date: Sun, 6 Jun 2004 15:32:50 -0700	[thread overview]
Message-ID: <20040606223250.GA15574@one-eyed-alien.net> (raw)
In-Reply-To: <1086533333.10787.45.camel@mulgrave>

[-- Attachment #1: Type: text/plain, Size: 1642 bytes --]

On Sun, Jun 06, 2004 at 09:48:51AM -0500, James Bottomley wrote:
> On Sat, 2004-05-29 at 18:42, Tobias Lieber wrote:
> > i Javier Marcet wrote in January 2004 a patch for linux-2.6.3, to make a i-River-mp3-Player mounting. It was on lkml: http://lkml.org/lkml/2004/1/6/170
> > i was suprised, that it was not in the kernel, and no other soulution, too. So i read his patch for getting mouted the player, and rewrote it for linux-2.6.7-rc1-bk7. I attached it. It would be nice, if it would be possible mounting the mp3-player without patching the Kernel, so i would greet it, if this or an other solution woulg com into the Kernel.
> 
> Well, but the question is who gets to fix this?
> 
> Since this is a USB device returning broken inquiry data which sd then
> acts on, I'd rather see USB fix it.
> 
> I cc'd the USB people.  Since you already do some scrubbing on the
> inquiry data from this thing (to fix up the ANSI SCSI type), can't you
> just add it as an unusual dev that needs the RMB bit resetting (and, if
> that's so far wrong, probably other vital pieces of inquiry data as
> well)?

We're actually trying to figure out the 'right way' to do this now.  Our
expectation is that there is some algorithmic way to determine if this bit
is "right" or not, as Windows seems to get it right without
white/blacklisting.

Matt

-- 
Matthew Dharm                              Home: mdharm-usb@one-eyed-alien.net 
Maintainer, Linux USB Mass Storage Driver

We've made a business out of making money from annoying and stupid people.
I think you fall under that category.
					-- Chief
User Friendly, 7/11/1998

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-06-06 22:33 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 [this message]
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
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=20040606223250.GA15574@one-eyed-alien.net \
    --to=mdharm-scsi@one-eyed-alien.net \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=little.tobias@gmx.de \
    --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