From: Alan Stern <stern@rowland.harvard.edu>
To: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
Cc: Javier Marcet <javier@marcet.info>,
<linux-kernel@vger.kernel.org>, <usb-storage@one-eyed-alien.net>,
<linux-usb-users@lists.sourceforge.net>
Subject: Re: [usb-storage] Re: usb-storage && iRIVER flash player problem
Date: Tue, 6 Jan 2004 10:37:10 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44L0.0401061035420.770-100000@ida.rowland.org> (raw)
In-Reply-To: <20040106065655.GA10031@one-eyed-alien.net>
On Mon, 5 Jan 2004, Matthew Dharm wrote:
> On Mon, Jan 05, 2004 at 09:03:33PM +0100, Javier Marcet wrote:
> > * Matthew Dharm <mdharm-kernel@one-eyed-alien.net> [040105 20:02]:
> >
> > >It looks like your device is choking over the ALLOW_MEDIUM_REMOVAL command
> > >-- I've never seen a device broken in this particular way before.
> >
> > >If you edit drivers/scsi/sd.c to remove the sending of that command (it's
> > >normally used to lock the media-eject button on devices that support it),
> > >we should be able to test this theory. If this is the case, then we may
> > >need to modify the SCSI layer to only send that command if the RMB bit is
> > >set.
> Hrm... what's the easiest way for Javier to figure out if his device sets
> the RMB or not?
>
> I feel another SCSI enhancement coming on....
It's not so simple, unfortunately. In 2.6, sd.c already does check that
sdev->removable is set before issuing PREVENT ALLOW MEDIUM REMOVAL.
Alan Stern
next prev parent reply other threads:[~2004-01-06 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 12:59 usb-storage && iRIVER flash player problem Javier Marcet
2004-01-05 19:02 ` Matthew Dharm
2004-01-05 20:03 ` Javier Marcet
2004-01-06 6:56 ` [usb-storage] " Matthew Dharm
2004-01-06 15:37 ` Alan Stern [this message]
2004-01-06 20:32 ` Javier Marcet
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=Pine.LNX.4.44L0.0401061035420.770-100000@ida.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=javier@marcet.info \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-users@lists.sourceforge.net \
--cc=mdharm-kernel@one-eyed-alien.net \
--cc=usb-storage@one-eyed-alien.net \
/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;
as well as URLs for NNTP newsgroup(s).