* module parameters and 2.6 macros
@ 2004-08-15 17:41 Jon Smirl
2004-08-15 17:47 ` Christoph Hellwig
0 siblings, 1 reply; 2+ messages in thread
From: Jon Smirl @ 2004-08-15 17:41 UTC (permalink / raw)
To: lkml
Is there some way to avoid two sets of parsing code with the 2.6 module
parameter macros?
With the new module parameter macros I can do this:
modprobe radeon debug=1 cards_limit=10
compiled in I need:
kernel /vmlinuz-2.6.8.1 radeon=debug:1,cards_limit:10
For the compiled in case the driver has a parser which decodes the
string. I'd like to remove this parser.
Is this what MODULE_SUPPORTED_DEVICE() is for but the code isn't
written yet?
=====
Jon Smirl
jonsmirl@yahoo.com
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: module parameters and 2.6 macros
2004-08-15 17:41 module parameters and 2.6 macros Jon Smirl
@ 2004-08-15 17:47 ` Christoph Hellwig
0 siblings, 0 replies; 2+ messages in thread
From: Christoph Hellwig @ 2004-08-15 17:47 UTC (permalink / raw)
To: Jon Smirl; +Cc: lkml
On Sun, Aug 15, 2004 at 10:41:08AM -0700, Jon Smirl wrote:
> Is there some way to avoid two sets of parsing code with the 2.6 module
> parameter macros?
Yes, if you use module_param{,_named} and a paramter 'foo' you can use
foo=1 at modprobe time and modulename.foo=1 at the kernel command line
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-08-15 17:47 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-08-15 17:41 module parameters and 2.6 macros Jon Smirl
2004-08-15 17:47 ` Christoph Hellwig
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox