Re: module parameters versus kernel command line

[Randy Dunlap <randy.dunlap@oracle.com>]

On Thu, 3 Apr 2008 09:00:53 -0400 Tom Horsley wrote:

> Just curious: Is there any reason even dynamically loaded
> modules shouldn't be able to find module parameters on
> the kernel command line? I haven't actually investigated
> the code involved (since I have no idea where it is :-),
> but it sure seems like it would be convenient to have
> a single place to put module parameters where they
> would always be found regardless of the module's static
> or dynamic build mode (especially when multi-booting
> different kernels built different ways).
> --

Does this answer your question?  from Documentation/kernel-parameters.txt:

Module parameters for loadable modules are specified only as the
parameter name with optional '=' and value as appropriate, such as:

	modprobe usbcore blinkenlights=1

Module parameters for modules that are built into the kernel image
are specified on the kernel command line with the module name plus
'.' plus parameter name, with '=' and value if appropriate, such as:

	usbcore.blinkenlights=1

---
~Randy