From: Javier Marcet <javier@marcet.info>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Matthew Wheeler <matt@yurisko.net>,
Mike Anderson <andmike@us.ibm.com>,
USB Storage list <usb-storage@lists.one-eyed-alien.net>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: PATCH: BLIST flag for non-lockable devices
Date: Mon, 28 Jun 2004 01:10:07 +0200 [thread overview]
Message-ID: <20040627231007.GA12853@marcet.info> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0406251209580.1147-100000@ida.rowland.org>
* Alan Stern <stern@rowland.harvard.edu> [040625 18:14]:
>> Since SCSI already has the device list it would seem like we would
>> possibly add a new flag like was done for mode sense. As this is not a
>> transport issue I would assume we would not want to add flags in
>> usb/storage, but handle it in the mid-layer as a SCSI protocol
>> non-compliance.
>Here is a patch that implements this suggestion. It's rather similar to
>the one that Javier Marcet wrote back in January, in
>http://marc.theaimsgroup.com/?l=linux-usb-users&m=107345268526718&w=2
>Matthew, does this patch work for your digital camera?
For me, as you probably guessed, this is fine. It works very well with
my iRiver.
Yet I wonder why the INQUIRY_36 flag? Isn't it the default? Or you just
try to skip the try & failure over longer inquiries since you already
know these devices' length?
No complaints no my side anyway. Push it upstream when you see it fit :)
--
The entire CHINESE WOMEN'S VOLLEYBALL TEAM all share ONE personality --
and have since BIRTH!!
Javier Marcet <javier@marcet.info>
next prev parent reply other threads:[~2004-06-27 23:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 21:05 Windows and non-lockable devices (fwd) Alan Stern
2004-06-23 19:14 ` Mike Anderson
2004-06-25 16:14 ` PATCH: (as333) BLIST flag for non-lockable devices Alan Stern
2004-06-27 0:52 ` Matthew Wheeler
2004-06-27 23:10 ` Javier Marcet [this message]
2004-06-28 15:54 ` PATCH: " Alan Stern
2004-06-28 20:24 ` 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=20040627231007.GA12853@marcet.info \
--to=javier@marcet.info \
--cc=James.Bottomley@SteelEye.com \
--cc=andmike@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=matt@yurisko.net \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.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