Re: grey- and blacklisting drivers [Was: Re: Using the "best available" driver]

From: Christian Zoz <zoz@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: grey- and blacklisting drivers [Was: Re: Using the "best available" driver]
Date: Tue, 17 Jan 2006 10:51:09 +0000	[thread overview]
Message-ID: <20060117105109.GD6630@suse.de> (raw)
In-Reply-To: <20051207181524.71dc2d41.zaitcev@redhat.com>

On Mon, Jan 09, Kay Sievers wrote:
> On Sun, Jan 08, 2006 at 10:36:30PM +0100, Dominik Brodowski wrote:
> ...
> > > > > The same is true for sysfs booleans. No need to "describe" "autobind" on
> > > > > and off, right?)
> > 
> > Any progress in this regard? It seems to me that the solving of the few
> > outstanding issues has dropped off some in the pre-holiday season ... now in
> > the New Year, shall we try to solve them and get this feature into a
> > mergeable state? Or have I missed something and is it already on its way
> > into 2.6.16?
> 
> No, nothing happened after the two alternative patches posted to the
> list. We still need to decide on the syfs interface (bool vs. text) and
> the "simple patch to the individual drivers" or go for the "default module
> parameter".

I vote for an boolean interface (autobind) and the "default module
parameter". Boolean because autobind is self-explanatory and
light-weight. And default module parameter bebause i hate fiddling
with different driver behavior.

-- 

ciao, christian

睡眠不足はいい仕事の敵だ。

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel