All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: grey- and blacklisting drivers [Was: Re: Using the "best available" driver]
Date: Tue, 13 Dec 2005 20:46:16 +0000	[thread overview]
Message-ID: <20051213204616.GA7832@vrfy.org> (raw)
In-Reply-To: <20051207181524.71dc2d41.zaitcev@redhat.com>

On Tue, Dec 13, 2005 at 08:39:57PM +0100, Dominik Brodowski wrote:
> Hi,
> 
> On Tue, Dec 13, 2005 at 05:55:04AM +0100, Kay Sievers wrote:
> > New version, which does not do the dirty "default parameters" trick. It
> > depends on a regular module parameter, if "bind_mode" control at module
> > load or boot prompt is needed. It uses "auto" and "manual" as the values
> > and the sysfs file in the driver directory is called "bind_mode".
> 
> 
> The only thing which worries me is that we add quite some bytes to the
> kernel here... What do you think about this?
> 
> #define module_param_bind_mode(driver)					\
> 	module_param_named(dont_bind, &driver->bind_mode, uint, 0);	\
> 	MODULE_PARM_DESC(bind_mode, "Do not bind this driver to "	\
> 				"devices automatically.");
> 
> Then we'd need to add
> 
> module_param_named(&ov511_driver.driver);
> 
> to ov511.c and get the same functionality.

Yes, that we need to decide. I just wanted to see the alternative approach
and posted it. We need to find out if we want:
  "default module parameters"
    - which would work for all modules, without changes
    - like the first patch, but in a more generic way that
      also implements built-in early parameter parsing
or:
    "only modular drivers init support by default"
    - will work fine with the current infrastructure, but modules
      need to have the parameter added if they want boot parameter
      support

If "default module parameters" are something that is considered useful
for other possible use cases too, we may just go for it.

And another thing is the prameters textual value like "auto" and
"manual". If we never add a third option to it, we may stick with the sysfs
boolean, which is smaller and simpler to implement. Not sure what's the
best here.

Thanks,
Kay



-------------------------------------------------------
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

  parent reply	other threads:[~2005-12-13 20:46 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 ` 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 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 [this message]
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=20051213204616.GA7832@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --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.