public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Dharm <mdharm-scsi@one-eyed-alien.net>
To: Andries.Brouwer@cwi.nl
Cc: James.Bottomley@steeleye.com, afafc@rnl.ist.utl.pt,
	alan@lxorguk.ukuu.org.uk, greg@kroah.com,
	linux-scsi@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net, mike@hingston.demon.co.uk,
	stelian@popies.net, torvalds@transmeta.com
Subject: Re: [example PATCH - not for applying] exclude certain commands
Date: Thu, 24 Apr 2003 11:22:00 -0700	[thread overview]
Message-ID: <20030424112200.A10511@one-eyed-alien.net> (raw)
In-Reply-To: <UTC200304240908.h3O98Cw29064.aeb@smtp.cwi.nl>; from Andries.Brouwer@cwi.nl on Thu, Apr 24, 2003 at 11:08:12AM +0200

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

On Thu, Apr 24, 2003 at 11:08:12AM +0200, Andries.Brouwer@cwi.nl wrote:
>     From: Matthew Dharm <mdharm-scsi@one-eyed-alien.net>
> 
>     > Comments?
> 
>     My only comment is that your sample of failed cases primarily seems to
>     address those devices that support some variant of MODE_SENSE -- there are
>     lots of devices that don't support it at all, which is why I wanted to
>     filter it with the (apparently) now-dead command filter concept.
> 
> Well, before we create a new infrastructure it is a good idea
> to make sure that it is needed. James mentioned three cases
> in Bugzilla and it looks like these are fixed by a small correction
> to the MODE_SENSE to MODE_SENSE_10 translation.
> 
> You mention lots of devices that don't support MODE_SENSE at all.
> Do you have Bugzilla or l-k / l-s / l-u refs?

Unfortunately, my data comes from (a) working with this junk for several
years, and (b) non-public conversations with hardware vendors.  While there
linux-usb-devel/users references, you'll have to google for logs to find
them.

Yeah, I know that's a lousy answer.  But try to realize that I've been
dealing with a long, slow, and painful discovery process of what the
'popular OS' uses.

> (Smart Media and similar cards come with a write protect bit.
> I would suppose reporting it is supported by most non-broken hardware.
> We get it from the header of the MODE_SENSE return value.
> So there is some reason to expect that MODE_SENSE[_10] is supported,
> at least in the minimum form where no page but only the header
> is returned. Closer investigation of other error cases might reveal
> more usb-storage flaws.)

This is actually interesting... smart media readers seem to be some of the
worst offenders in terms of not supporting this command (or at least a
variant of it that I've been able to discover).

Hardware vendors tell me that those which build devices based on older
designs (i.e. real SCSI or ATAPI) do support some version of a modesense
because it carried over from their older designs.  Those which are doing
new designs from the ground up do not support it, as apparently neither
Windows nor MacOS check for write-protect this way.  Or so I'm told by the
people who design these things.

Matt

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

Ye gods! I have feet??!
					-- Dust Puppy
User Friendly, 12/4/1997

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

  reply	other threads:[~2003-04-24 18:10 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24  9:08 [example PATCH - not for applying] exclude certain commands Andries.Brouwer
2003-04-24 18:22 ` Matthew Dharm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-27  2:29 Andries.Brouwer
2003-04-27  4:32 ` James Bottomley
2003-04-26 21:44 Andries.Brouwer
2003-04-26 22:13 ` Matthew Dharm
2003-04-26 22:43   ` James Bottomley
2003-04-27  1:34     ` Matthew Dharm
2003-04-27  2:15       ` James Bottomley
2003-04-27  9:35         ` Matthew Dharm
2003-04-27 15:41           ` James Bottomley
2003-04-27 18:52             ` Kai Makisara
2003-04-27 19:52             ` Matthew Dharm
2003-04-28 19:05               ` Luben Tuikov
2003-04-28 19:12                 ` Luben Tuikov
2003-04-28 20:19                 ` Matthew Dharm
2003-04-28 21:33                   ` Luben Tuikov
2003-04-26 22:29 ` James Bottomley
2003-04-27  0:24   ` Patrick Mansfield
2003-04-27  1:39   ` Matthew Dharm
2003-04-25  0:43 Andries.Brouwer
2003-04-25  2:12 ` Matthew Dharm
2003-04-25 14:32 ` Alan Stern
2003-04-25 15:12   ` Oliver Neukum
2003-04-26  0:58     ` Alan Stern
2003-04-26  8:24       ` Oliver Neukum
2003-04-26 15:22         ` Alan Stern
2003-04-24 18:59 Andries.Brouwer
2003-04-24 19:14 ` Matthew Dharm
2003-04-24 20:20   ` James Bottomley
2003-04-24 20:59     ` Matthew Dharm
2003-04-24 21:43       ` Patrick Mansfield
2003-04-24 15:21 Andries.Brouwer
2003-04-24 15:56 ` Pete
2003-04-24 21:33 ` Stelian Pop
2003-04-24  9:46 Andries.Brouwer
2003-04-24  9:56 ` Stelian Pop
2003-04-24 14:05 ` Alan Stern
2003-04-24 14:26   ` James Bottomley
2003-04-24 14:46     ` Alan Stern
2003-04-24 15:26       ` James Bottomley
2003-04-23 22:39 Andries.Brouwer
2003-04-24  0:10 ` Matthew Dharm
2003-04-24  8:05 ` André Cruz
2003-04-24  9:15 ` Stelian Pop
2003-04-24  9:22   ` Stelian Pop
2003-04-24 11:45 ` Mike Bursell
2003-04-24 12:44 ` James Bottomley

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=20030424112200.A10511@one-eyed-alien.net \
    --to=mdharm-scsi@one-eyed-alien.net \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=James.Bottomley@steeleye.com \
    --cc=afafc@rnl.ist.utl.pt \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=mike@hingston.demon.co.uk \
    --cc=stelian@popies.net \
    --cc=torvalds@transmeta.com \
    /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