On Mon, 27 Jul 2009, Robert P. J. Day wrote:
>
> recent comment on one of my linux.com columns asks about this from
> drivers/usb/misc/sisusbvga/sisusb.c:
>
> static int sisusb_first_vc = 0;
> static int sisusb_last_vc = 0;
> module_param_named(first, sisusb_first_vc, int, 0);
> module_param_named(last, sisusb_last_vc, int, 0);
> MODULE_PARM_DESC(first, "Number of first console to take over (1 -
> MAX_NR_CONSOLES)");
> MODULE_PARM_DESC(last, "Number of last console to take over (1 -
> MAX_NR_CONSOLES)");
>
> i have to admit, i'm not sure of the value of invoking
> module_param_named() to create alternate names for module parameters
> only to give them permissions of zero so that they don't show up
> under /sys. maybe i don't really understand parameters as well as i
> thought. opinions? what's really happening above?
never mind, i see what's happening -- the command line parms will be
named "first" and "last", but will still not show up under /sys.
carry on.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
"Kernel Newbie Corner" column @ linux.com: http://cli.gs/WG6WYX
========================================================================
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [email protected]
Please read the FAQ at http://kernelnewbies.org/FAQ
