All of lore.kernel.org
 help / color / mirror / Atom feed
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 02:54:48 +0000	[thread overview]
Message-ID: <20051208025448.GB3426@bougret.hpl.hp.com> (raw)
In-Reply-To: <20051207181524.71dc2d41.zaitcev@redhat.com>

On Wed, Dec 07, 2005 at 06:15:24PM -0800, Pete Zaitcev wrote:
> On Wed, 7 Dec 2005 17:23:32 -0800, Greg KH <greg@kroah.com> wrote:
> 
> >  Would something like the libusual code in
> > -mm work better for this instead?
> 
> I have suggested libusual but Pavel rejected it with ... this:
> 
> > From: Pavel Roskin <proski@gnu.org>
> > To: Pete Zaitcev <zaitcev@redhat.com>
> > Subject: Re: Using the "best available" driver
> > Date: Sat, 03 Dec 2005 02:59:21 -0500
> 
> > I think the libusual approach doesn't scale and depends on the good will
> > of the maintainers of the device drivers.
> 
> No comment necessary. :-)
> 
> -- Pete

	Ok, I had a look at libusual. I'm sorry, but it won't work
with some of my scenario (having both a Prism2 and an Orinoco card
active at the same time).

	Moreover, I don't want to offend you, but I personally don't
really like the overall approach. You really want to keep drivers as a
self encapsualted entities, as independant as possible from each
other. This simplify maintainance and avoid breakage, and allow to add
or remove drivers from the kernel tree with minimal disruptions. This
approach also force you to unload drivers to change the bias, and is
very coarse grained (unless you change the libusual API).
	And it's not generic, you have to hack each driver, which is
kernel bloat, whereas this generic issue calls for a generic
solution. Potentially, over time, each libusual may develop it's own
specific extensions for added "features".
	The generic script from Dominik seems to offer a simpler
alternative, which doesn't require extensive changes. An user-space
override table keeps the spirit of "Policy in user space, not in the
kernel" (devfs vs. udev).
	But all my personal opinions don't really matter, as the
libusual simply doesn't support the required scenario.

	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

  reply	other threads:[~2005-12-08  2:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08  2:15 grey- and blacklisting drivers [Was: Re: Using the "best Pete Zaitcev
2005-12-08  2:54 ` Jean Tourrilhes [this message]
2005-12-08 15:31 ` grey- and blacklisting drivers [Was: Re: Using the "best available" driver] Kay Sievers
2005-12-10  4:20 ` Greg KH
2005-12-11  6:43 ` Kay Sievers
2005-12-11 15:48 ` grey- and blacklisting drivers [Was: Re: Using the "best Pavel Roskin
2005-12-11 16:13 ` grey- and blacklisting drivers [Was: Re: Using the "best available" driver] 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
  -- strict thread matches above, loose matches on Subject: below --
2005-12-07 21:37 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

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=20051208025448.GB3426@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.