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: Thu, 08 Dec 2005 01:56:51 +0000 [thread overview]
Message-ID: <20051208015651.GA3131@bougret.hpl.hp.com> (raw)
In-Reply-To: <20051207213721.GC21844@isilmar.linta.de>
On Wed, Dec 07, 2005 at 05:23:32PM -0800, Greg KH wrote:
>
Hi Greg,
Welcome on board.
> So what is the main problem you are trying to fix here?
To get you up to speed, you may want to read these :
http://lists.infradead.org/pipermail/linux-pcmcia/2005-December/002957.html
http://lists.infradead.org/pipermail/linux-pcmcia/2005-December/002997.html
The problem to resolve : two Pcmcia drivers with partial
hardware overlap. This happen quite often in the Pcmcia/Wireless
world.
Basically, we want to offer fine grained control over driver
binding in a user friendly way and push that in distros. The basic
infrastructure is there (sysfs bind/unbind), what's missing is the
user friendly wrapping around (automatic on hotplug event, nice config
file, ...).
> Drivers binding to devices that they should not bind to?
No, that's not what we are trying to solve.
> Why are they binding to these devices in the first place?
Because those drivers do support the device.
> Would something like the libusual code in -mm work better for this instead?
I personally don't know what it does.
> thanks,
>
> greg k-h
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-08 1:56 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
2005-12-08 1:23 ` Greg KH
2005-12-08 1:56 ` Jean Tourrilhes [this message]
-- 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=20051208015651.GA3131@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).