From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Roskin Date: Sun, 11 Dec 2005 15:48:56 +0000 Subject: Re: grey- and blacklisting drivers [Was: Re: Using the "best Message-Id: <20051211104856.yltc04wwgc08ckg0@webmail.spamcop.net> List-Id: References: <20051207181524.71dc2d41.zaitcev@redhat.com> In-Reply-To: <20051207181524.71dc2d41.zaitcev@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Quoting Kay Sievers : > 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 ------------------------------------------------------- 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://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ 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