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

[Pavel Roskin]

Quoting Kay Sievers <kay.sievers at vrfy.org>:

> This quick hack works for me, but does it at the driver level, which is
> nicer to use than a global bus control.
>
> If the driver is already loaded, it can be controlled in sysfs or it can
> be passed to modprobe and the driver gets initialized with that setting.
> That way, modules/drivers can be set-up in modprobe.conf, to wait for
> manual bind requests.

Please, let's make "manual bind" independent of modules.  In fact, it's less
needed in case of modules, because you can control the order, in which they are
loaded.  When manual bind is really needed is the case of the monolithic kernel.

Every driver has a name, so we should be able to refer to it before it's loaded.
 There should be a way to tell the kernel not to autobind e.g. orinoco_cs,
whether it's a module or an in-kernel driver.  In the later case, we want some
kind of kernel command line support.

--
Regards,
Pavel Roskin