From: Pat LaVarre <p.lavarre@ieee.org>
To: stern@rowland.harvard.edu
Cc: ronald@kuetemeier.com, patmans@us.ibm.com,
linux-scsi@vger.kernel.org, usb-storage@one-eyed-alien.net
Subject: Re: [PATCH] SCSI: limit mode sense usage
Date: 29 Oct 2003 08:43:27 -0700 [thread overview]
Message-ID: <1067442207.13824.3.camel@patehci2> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0310290947010.874-100000@ida.rowland.org>
> > There now in -test9 I think I see: ...
> > We guess writable if need be, but we prefer to settle for: ...
> > sdkp->write_prot = ((data.device_specific & 0x80) != 0); ...
> > after the first command that works in the sequence: ...
> > sd_do_mode_sense(..., 0x3F, ..., 4, ...);
> > sd_do_mode_sense(..., 0, buffer, 4, ...);
> > sd_do_mode_sense(..., 0x3F, buffer, 255, ...);
> >
> > I mean to suggest, ... more closely ... Talk Like Windows ...
> > e.g.: ...
> > sd_do_mode_sense(..., 0x08, ..., 4, ...);
>
> There's an excellent reason for _not_ doing this, at least as far as
> usb-storage is concerned. Namely, many USB Mass Storage devices die when
> they receive MODE-SENSE(10) for page x08 but handle page x3F perfectly
> well. Ronald's device is a rather unusual exception.
Do these devices die for all lengths of op x5A MODE_SENSE_10 of page
x08, or only for the rude, header-only, 4 or 8 byte length that we get
by default if we patch drivers/scsi/ minimally?
That is, do these devices die only when assaulted by:
sd_do_mode_sense(..., 0x08, ..., 4, ...);
in place of the more Windows-like:
sd_do_mode_sense(..., 0x08, ..., 0x1C, ...); // if x5A MODE_SENSE_10
sd_do_mode_sense(..., 0x08, ..., 0x18, ...); // if x1A MODE_SENSE
?
Pat LaVarre
next prev parent reply other threads:[~2003-10-29 15:43 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1067293080.1075.8.camel@ronald.kuetemeier.com>
[not found] ` <20031027145531.A2130@beaverton.ibm.com>
2003-10-28 3:51 ` [PATCH] SCSI: limit mode sense usage Ronald Kuetemeier
2003-10-28 15:03 ` [usb-storage] " Alan Stern
2003-10-28 15:16 ` Patrick Mansfield
2003-10-28 15:40 ` Alan Stern
2003-10-28 15:55 ` Ronald Kuetemeier
2003-10-28 16:15 ` Ronald Kuetemeier
2003-10-28 19:17 ` Alan Stern
2003-10-28 19:55 ` Ronald Kuetemeier
2003-10-28 20:29 ` Alan Stern
2003-10-28 21:33 ` Ronald Kuetemeier
2003-10-28 22:49 ` Alan Stern
2003-10-28 23:37 ` Pat LaVarre
2003-10-29 1:51 ` Patrick Mansfield
2003-10-29 2:16 ` Ronald Kuetemeier
2003-10-29 7:27 ` Patrick Mansfield
2003-10-29 7:21 ` Patrick Mansfield
2003-10-29 15:16 ` Alan Stern
2003-10-29 16:04 ` Ronald Kuetemeier
2003-10-29 15:09 ` Alan Stern
2003-10-29 15:53 ` Ronald Kuetemeier
2003-10-29 16:30 ` Patrick Mansfield
2003-10-28 15:42 ` Ronald Kuetemeier
2003-10-29 16:46 ` [PATCH/RFT] check non-scsi part of status in scsi_status_is_good Patrick Mansfield
2003-10-29 17:53 ` Ronald Kuetemeier
2003-10-29 23:16 ` Patrick Mansfield
2003-10-30 15:11 ` Alan Stern
2003-10-30 16:35 ` Pat LaVarre
2003-10-30 17:18 ` Patrick Mansfield
2003-10-30 17:38 ` Pat LaVarre
2003-10-30 18:05 ` [PATCH/RFT] mode sense madness always use page 8 Patrick Mansfield
2003-10-30 18:14 ` Ronald Kuetemeier
2003-10-30 18:25 ` Patrick Mansfield
2003-10-30 18:15 ` Pat LaVarre
2003-10-30 18:56 ` Alan Stern
2003-10-30 19:06 ` Pat LaVarre
2003-10-30 20:00 ` Alan Stern
2003-10-31 20:47 ` Pat LaVarre
2003-10-30 19:26 ` Patrick Mansfield
2003-10-31 20:38 ` Pat LaVarre
2003-11-03 21:40 ` Pat LaVarre
2003-10-30 19:25 ` Ronald Kuetemeier
2003-10-30 19:39 ` Pat LaVarre
2003-10-30 21:48 ` Patrick Mansfield
2003-10-30 21:58 ` Ronald Kuetemeier
2003-10-30 23:59 ` Pat LaVarre
2003-10-31 18:16 ` Patrick Mansfield
2003-10-31 23:11 ` Pat LaVarre
2003-11-06 23:11 ` Douglas Gilbert
2003-11-07 16:13 ` Pat LaVarre
2003-10-28 15:38 ` [PATCH] SCSI: limit mode sense usage Pat LaVarre
2003-10-28 20:56 ` Pat LaVarre
2003-10-28 22:28 ` Alan Stern
2003-10-28 22:54 ` Pat LaVarre
2003-10-29 14:49 ` Alan Stern
2003-10-29 15:43 ` Pat LaVarre [this message]
2003-10-28 20:59 Pat LaVarre
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=1067442207.13824.3.camel@patehci2 \
--to=p.lavarre@ieee.org \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.com \
--cc=ronald@kuetemeier.com \
--cc=stern@rowland.harvard.edu \
--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