From: Alan Stern <stern@rowland.harvard.edu>
To: Greg KH <greg@kroah.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>, <linux-kernel@vger.kernel.org>,
<linux-usb-devel@lists.sourceforge.net>,
<linux-usb-storage@lists.one-eyed-alien.net>
Subject: Re: [linux-usb-devel] RFC drivers/usb/storage/libusual
Date: Wed, 28 Sep 2005 15:40:46 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44L0.0509281537070.5193-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <20050928085159.GA11862@kroah.com>
On Wed, 28 Sep 2005, Greg KH wrote:
> If so, a few comments.
> - This only covers the "which module to load" question. Once the
> module is loaded, it still always grabs the storage devices, even if
> another module is loaded later on. Isn't that still the same issue
> we have today? Can't we fix this too?
How about exposing modules' id tables through sysfs and allowing a way
for entries to be marked valid or invalid? Then a userspace utility
program could easily set things up so that normal USB storage devices are
accepted by usb-storage and not ub, or the other way around.
The part that Pete tackled, arranging the preferences when the modules
_aren't_ loaded, is actually the harder part.
Alan Stern
next prev parent reply other threads:[~2005-09-28 19:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 3:55 RFC drivers/usb/storage/libusual Pete Zaitcev
2005-09-28 8:52 ` [linux-usb-devel] " Greg KH
2005-09-28 19:40 ` Alan Stern [this message]
2005-09-29 0:01 ` Pete Zaitcev
2005-10-10 21:15 ` Rusty Russell
2005-10-07 7:24 ` Pete Zaitcev
2005-10-07 14:41 ` [usb-storage] " Alan Stern
2005-10-08 7:35 ` Pete Zaitcev
2005-10-08 15:17 ` Alan Stern
2005-10-08 21:01 ` usb: drivers/usb/storage/libusual Pete Zaitcev
2005-10-09 2:14 ` [usb-storage] " Matthew Dharm
2005-10-09 8:09 ` Pete Zaitcev
2005-09-28 16:56 ` [linux-usb-devel] RFC drivers/usb/storage/libusual Alan Stern
2005-09-29 2:21 ` Pete Zaitcev
2005-09-30 7:09 ` [linux-usb-devel] " Phil Dibowitz
2005-10-01 0:26 ` Pete Zaitcev
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.0509281537070.5193-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linux-usb-storage@lists.one-eyed-alien.net \
--cc=zaitcev@redhat.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;
as well as URLs for NNTP newsgroup(s).