From: Jean Tourrilhes <jt@hpl.hp.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: grey- and blacklisting drivers [Was: Re: Using the "best available" driver]
Date: Wed, 07 Dec 2005 23:07:56 +0000 [thread overview]
Message-ID: <20051207230756.GA2811@bougret.hpl.hp.com> (raw)
In-Reply-To: <20051207213721.GC21844@isilmar.linta.de>
On Wed, Dec 07, 2005 at 05:52:11PM -0500, Bill Nottingham wrote:
> Dominik Brodowski (linux@dominikbrodowski.net) said:
> > Hi,
> >
> > For various reasons, it might be necessary to switch to a better driver for
> > a device -- Jean can tell of many examples, if needed. Currently, that's
> > possible using modprobe's blacklisting capability (in
> > module-init-tools-3.2.1, at least) -- but that's for monolithic kernels
> > only.
>
> Why is the blacklisting for monolithic kernels only?
>
> Bill
Actually, I think Dominik inverted the two and that
blacklisting apply only to modular kernel and would fail with
monolithic kernel (because the drivers are already pre-loaded).
Anyway, that's not the point, and it does not really
matter. The point is that blacklisting is clearly not able to deal
with the reality and complexity of Pcmcia drivers (even for fully
modular kernels). If you want more details, feel free to check the
archive of the Pcmcia mailing list.
Therefore, Dominik is proposing a per card overide using the
unbind/bind feature.
Have fun...
Jean
-------------------------------------------------------
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_id\x16865&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
next prev parent reply other threads:[~2005-12-07 23:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 21:37 grey- and blacklisting drivers [Was: Re: Using the "best available" driver] Dominik Brodowski
2005-12-07 22:52 ` Bill Nottingham
2005-12-07 23:07 ` Jean Tourrilhes [this message]
2005-12-08 1:23 ` Greg KH
2005-12-08 1:56 ` Jean Tourrilhes
-- strict thread matches above, loose matches on Subject: below --
2005-12-08 2:15 grey- and blacklisting drivers [Was: Re: Using the "best Pete Zaitcev
2005-12-08 2:54 ` grey- and blacklisting drivers [Was: Re: Using the "best available" driver] Jean Tourrilhes
2005-12-08 15:31 ` Kay Sievers
2005-12-10 4:20 ` Greg KH
2005-12-11 6:43 ` Kay Sievers
2005-12-11 16:13 ` Kay Sievers
2005-12-11 17:20 ` Dmitry Torokhov
2005-12-11 19:59 ` Dominik Brodowski
2005-12-11 20:00 ` Dominik Brodowski
2005-12-11 20:55 ` Kay Sievers
2005-12-11 21:11 ` Kay Sievers
2005-12-13 4:55 ` Kay Sievers
2005-12-13 19:39 ` Dominik Brodowski
2005-12-13 20:46 ` Kay Sievers
2005-12-13 20:56 ` Dmitry Torokhov
2005-12-13 21:27 ` Kay Sievers
2005-12-13 22:00 ` Dmitry Torokhov
2005-12-13 22:54 ` Dominik Brodowski
2006-01-08 21:36 ` Dominik Brodowski
2006-01-09 0:44 ` Kay Sievers
2006-01-17 10:51 ` Christian Zoz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051207230756.GA2811@bougret.hpl.hp.com \
--to=jt@hpl.hp.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).