From: Gary Thomas <gary@mlbassoc.com>
To: Stefan Jeglinski <jeglin@4pi.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: how to pass kernel command parameters?
Date: Tue, 20 Jan 2004 13:35:29 -0700 [thread overview]
Message-ID: <1074630928.26813.599.camel@hermes> (raw)
In-Reply-To: <p06010202bc333bc03e48@[192.168.9.5]>
On Tue, 2004-01-20 at 13:27, Stefan Jeglinski wrote:
> I have a Brightstar box with an MPC823, booting under 2.4.21 at the
> moment. But at the "Linux/PPC load:" line I have to enter a rather
> long string of parameters (IP numbers etc), I guess due to the boot
> ROM code that's part of this little Brightstar device.
>
> What is the proper way to automate the passing of these parameters?
> I'm gathering that all ppc kernel boots have this line to stop at,
> but the passing of parameters to it is automated.
>
> Should I be constructing a custom ram disk that contains the info? If
> so, what's a good resource about making ram disks and how to do this?
> If not, how is one supposed to do it? I don't suppose one should be
> hard-coding misc-simple.c or misc-embedded.c... ?
The default kernel command line can be easily configured using the
standard configuration tools (e.g. make xconfig) This string gets
built into the kernel image and can later be overridden on the console.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-20 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 20:27 how to pass kernel command parameters? Stefan Jeglinski
2004-01-20 20:35 ` Gary Thomas [this message]
2004-01-20 20:38 ` Wolfgang Denk
2004-01-20 23:02 ` Tom Rini
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=1074630928.26813.599.camel@hermes \
--to=gary@mlbassoc.com \
--cc=jeglin@4pi.com \
--cc=linuxppc-dev@lists.linuxppc.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).