[PATCH] doc: Explain module parameter passing better
in [Kernel]
|
From: Adam Jackson on 27 Apr 2010 11:50 We covered "passing with modprobe" and "builtins on kcmdline" but not "modules on kcmdline". Signed-off-by: Adam Jackson <ajax(a)redhat.com> --- Documentation/kernel-parameters.txt | 9 ++++----- 1 files changed, 4 insertions(+), 5 deletions(-) diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index 5814331..9209ab4 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation/kernel-parameters.txt @@ -6,14 +6,13 @@ The following is a consolidated list of the kernel parameters as implemented (defined as ignoring all punctuation and sorting digits before letters in a case insensitive manner), and with descriptions where known. -Module parameters for loadable modules are specified only as the -parameter name with optional '=' and value as appropriate, such as: +Module parameters are passed to modprobe as the parameter name, with optional +'=' and value if 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: +Module parameters are passed on the kernel command line with the module +name plus '.' plus parameter name, with '=' and value if appropriate, such as: usbcore.blinkenlights=1 -- 1.7.0.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|
Pages: 1 Prev: 2.6.43 - Intel KMS - rendering broken Next: [ANNOUNCE] 2.6.33.3-rt16 |