Re: [linux-usb-devel] [RFC] consolidate /sbin/hotplug call for pciand usb

From: Oliver Neukum <oliver@neukum.name>
To: Alan Stern <stern@rowland.harvard.edu>, Greg KH <greg@kroah.com>
Cc: David Brownell <david-b@pacbell.net>,
	<linux-usb-devel@lists.sourceforge.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] [RFC] consolidate /sbin/hotplug call for pciand usb
Date: Fri, 27 Sep 2002 01:35:17 +0200	[thread overview]
Message-ID: <200209270135.18010.oliver@neukum.name> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0209261522340.910-100000@ida.rowland.org>

> This raises a generally interesting question:  When should a driver
> module be loaded?

It is an interesting question, but it is not a kernel problem :-)

[..]
> I think it's clear that the answer must depend on the particular driver,
> and that no single scheme involving usage counts (or the equivalent) can
> suffice for every situation.
>
> Is there a way to let the kernel provide a variety of mechanisms and let
> the device driver (or even the user) select which one gets used?

That is more or less what is in place. There's a kernel aspect to the problem,
because the kernel needs to implement an unload if nothing is bound to method,
as user space cannot do that without a race.

	Regards
		Oliver