From: Patrick Mansfield <patmans@us.ibm.com>
To: James Bottomley <James.Bottomley@steeleye.com>,
usb-storage@one-eyed-alien.net,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Time to conclude the Sony USB mass storage thread
Date: Fri, 14 Nov 2003 12:00:48 -0800 [thread overview]
Message-ID: <20031114120048.A4527@beaverton.ibm.com> (raw)
In-Reply-To: <20031114105212.C19467@one-eyed-alien.net>; from mdharm-scsi@one-eyed-alien.net on Fri, Nov 14, 2003 at 10:52:12AM -0800
On Fri, Nov 14, 2003 at 10:52:12AM -0800, Matthew Dharm wrote:
> It's not immediately clear how we can override it if it's
> scsi_devinfo/dev_flags. Can you elaborate?
The same way you can set it is the same way it can be cleared.
If we want to allow all standard scsi core usage, as if there were not
special flag settings at all, and including using MODE SENSE 6, use
("model" is synonymous with SCSI product):
echo "vendor:model:0" > /proc/scsi/device_info
If we want MODE SENSE 10, default cache write through (if the device can't
do MODE SENSE page 8), use BLIST_USE_10_BYTE_MS | BLIST_MS_SKIP_PAGE_08
(0x8000 | 0x2000):
echo "vendor:model:0xa000" > /proc/scsi/device_info
The above can also be done at boot time or scsi_mod load time, on boot
use:
scsi_mod.dev_flags=vendor:model:0xa000
For scsi_mod as a module just drop the "scsi_mod." prefix.
The above does not allow us to send a variant of the MODE SENSE, like the
Sony really wants - MODE SENSE with a 10 byte (or larger) buffer - but
that would require a patch like the other one I sent, or command filtering
code, plus other code to enable/disable its use.
We still need a sysfs attribute to eventually replace the proc one - this
should be done by using module_param_call instead of module_param_string
(we need a special callout to parse the string, I did not understand
module_param_call when I added module_param usage), plus code to always
(not just for modules) add sysfs parameters for all module_param entries.
The device specific flags override any other settings - the shost->flags
or the scsi_default_dev_flags. We don't have any deletion method other
than reboot, but the last setting added overrides earlier settings, and so
you can even overide static entries in scsi_devinfo.c.
-- Patrick Mansfield
next prev parent reply other threads:[~2003-11-14 20:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 15:52 Time to conclude the Sony USB mass storage thread James Bottomley
2003-11-14 17:26 ` Patrick Mansfield
2003-11-14 17:35 ` Matthew Dharm
2003-11-14 17:58 ` Patrick Mansfield
2003-11-14 18:52 ` Matthew Dharm
2003-11-14 20:00 ` Patrick Mansfield [this message]
2003-11-14 20:30 ` [usb-storage] " Matthew Dharm
2003-11-14 20:56 ` Patrick Mansfield
2003-11-15 2:13 ` Patrick Mansfield
2003-11-15 20:20 ` Matthew Dharm
2003-11-16 0:02 ` Patrick Mansfield
2003-11-17 5:33 ` Matthew Dharm
2003-11-17 16:57 ` Patrick Mansfield
2003-11-14 17:52 ` 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=20031114120048.A4527@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--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