From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Amol Lad <amol.lad@gmail.com>,
linux-embedded <linux-embedded@vger.kernel.org>
Subject: Re: kernel command line from u-boot
Date: Thu, 7 Aug 2008 10:29:57 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0808071023030.19078@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0808071618120.9798@vixen.sonytel.be>
On Thu, 7 Aug 2008, Geert Uytterhoeven wrote:
> On Thu, 7 Aug 2008, Amol Lad wrote:
> > > Probably nobody noticed as this part of the code takes care of the
> > > `obsolete-style' parameters. `module_param' is the new way.
> >
> > Ohh, btw how module_param is different from obsolete style paramaters
> > ? Do we need to pass arguments to kernel from bootloader using a
> > different method for getting them processed using module_param ?
>
> 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
um ... all of the above handles those command-line parms that are
defined in *module* source files, but that doesn't solve the problem
of defining those parms that are always built into the kernel and are
currently defined by one of __setup_param() or __early_param().
from include/linux/init.h:
=====
struct obs_kernel_param {
const char *str;
int (*setup_func)(char *);
int early;
};
/*
* Only for really core code. See moduleparam.h for the normal way.
*
* Force the alignment so the compiler doesn't space elements of the
* obs_kernel_param "array" too far apart in .init.setup.
*/
=====
is the module-based approach really supposed to eventually replace
the above? how?
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
Have classroom, will lecture.
http://crashcourse.ca Waterloo, Ontario, CANADA
========================================================================
next prev parent reply other threads:[~2008-08-07 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 4:41 kernel command line from u-boot Amol Lad
2008-08-07 8:54 ` Geert Uytterhoeven
2008-08-07 11:27 ` Amol Lad
2008-08-07 14:18 ` Geert Uytterhoeven
2008-08-07 14:29 ` Robert P. J. Day [this message]
2008-08-08 15:53 ` Robert P. J. Day
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=alpine.LFD.1.10.0808071023030.19078@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=amol.lad@gmail.com \
--cc=linux-embedded@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).