From: ebiederm@xmission.com (Eric W. Biederman)
To: Tom Rini <trini@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86 Boot enhancements, boot protocol 2.04 7/9
Date: 03 Apr 2002 20:23:58 -0700 [thread overview]
Message-ID: <m13cycrvsh.fsf@frodo.biederman.org> (raw)
In-Reply-To: <m1ofh0spik.fsf@frodo.biederman.org> <20020403191538.GA7211@opus.bloom.county>
Tom Rini <trini@kernel.crashing.org> writes:
> On Wed, Apr 03, 2002 at 09:41:55AM -0700, Eric W. Biederman wrote:
>
> > In imitation of the arm and ppc ports a CONFIG_CMDLINE option is also
> > implemented.
>
> Just wondering, why didn't you do it with a
> CONFIG_CMDLINE_BOOL/CONFIG_CMDLINE set of options? The way you did it,
> I _think_ you can't actually get a help msg from 'config' or
> 'oldconfig', you'll just set the commandline to '?'.
I just tested it and oldconfig at least works. The overhead is exactly
one byte.
> Also, on current PPC, if we have a compiled-in commandline we put it in
> arch/ppc/kernel/setup.c and allow it to be overridden. This even makes
> it semi-useful outside of the self-containted {b,}zImage situation.
I currently allow a compiled in command line to be appended to. lilo also
does this when you specify a command line, and to my knowledge all boot options
prefer the last value specified so that should be good enough. As the decision
happens in C code it isn't to hard to change either way.
Eric
next prev parent reply other threads:[~2002-04-04 3:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 16:41 [PATCH] x86 Boot enhancements, boot protocol 2.04 7/9 Eric W. Biederman
2002-04-03 19:15 ` Tom Rini
2002-04-04 3:23 ` Eric W. Biederman [this message]
2002-04-04 14:10 ` Tom Rini
2002-04-04 15:38 ` Eric W. Biederman
2002-04-03 19:34 ` H. Peter Anvin
2002-04-04 17:15 ` Eric W. Biederman
2002-04-04 18:30 ` H. Peter Anvin
2002-04-04 19:04 ` Eric W. Biederman
2002-04-04 19:19 ` H. Peter Anvin
2002-04-04 19:32 ` Eric W. Biederman
2002-04-05 21:30 ` Eric W. Biederman
2002-04-05 22:04 ` H. Peter Anvin
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=m13cycrvsh.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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