lkml.org 
[lkml]   [2004]   [Dec]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: RFC: [2.6 patch] let BLK_DEV_UB depend on EMBEDDED
On Sun, 19 Dec 2004 21:09:52 -0800, "Randy.Dunlap" <rddunlap@osdl.org> wrote:

> Pete Zaitcev wrote:
> > On Mon, 20 Dec 2004 02:35:42 +0100, Adrian Bunk <bunk@stusta.de> wrote:
> >
> >>What about a dependency of BLK_DEV_UB on USB_STORAGE=n ?
> >
> > I have them both as 'm' in my configuration, works like a charm.
>
> ub can work like that, but it makes it darned difficult to
> use usb-storage like that. ub wants to bind to the devices,
> not usb-storage, and if ub is unloaded, usb-storage doesn't
> bind to them. at least that's been my experience with it.

There is no asymmetry in lists of devices in either of them, however
currently there aren't any devices which usb-storage cannot handle
and ub can. Thus it makes sense to conditionalize part of usb-storage
list on ub. Otherwise, it would be a separate configuration item,
I suppose. We'll when we get there.

I don't quite understand why it matters for you if a certain module
is loaded or not loaded. The hotplug acts upon the contents of
modules.usbmap which does not change when you modprobe or rmmod things.
So, the match lists are made non-conflicting between
ub and usb-storage. It looks as if Adrian has the same broken mental
model of the way things work. Once again, what is loaded does not
matter (not in ideal world, but in reality we still have conflicts such
as e100 and eepro100).

-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:08    [W:2.036 / U:1.044 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site