From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Paul Burton <paul.burton@mips.com>
Cc: "linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
Paul Burton <pburton@wavecomp.com>
Subject: Re: [PATCH 1/4] MIPS: cmdline: Remove CONFIG_MIPS_CMDLINE_BUILTIN_EXTEND
Date: Wed, 9 Oct 2019 15:13:09 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.21.1910091501580.25653@eddie.linux-mips.org> (raw)
In-Reply-To: <alpine.LFD.2.21.1910091440050.25653@eddie.linux-mips.org>
On Wed, 9 Oct 2019, Maciej W. Rozycki wrote:
> > CONFIG_MIPS_CMDLINE_BUILTIN_EXTEND is not selected by any of our
> > defconfigs, so remove it to simplify the messy command line logic in
> > arch_mem_init() a little.
>
> That sounds like a poor argument for a functional regression to me. I
> have the option enabled in several configs I have been using just to be
> able to temporarily override any built-in parameters with ones typed from
> the console monitor's prompt. Is it my mistake that I haven't put it in a
> defconfig?
Elaborating, there's IMO little sense to set MIPS_CMDLINE_BUILTIN_EXTEND
in a defconfig, because there's usually no default command line to set
there in the first place, as this will be installation-specific. Ergo I
highly doubt the absence of the setting across the board is due to nobody
(except for myself) using it.
Therefore:
Nacked-by: Maciej W. Rozycki <macro@linux-mips.org>
NB DECstation systems use a DS1287 or a similar RTC/NVRAM chip to hold
configuration and space is limited there. Up to 37 of kernel command line
characters can be permanently stored, fewer on some systems, and used for
automatic boot. Conversely when typed at the console monitor prompt there
is no (known to me) limitation as to the length of the kernel command line
requested.
Therefore a kernel configured for those systems will normally have
several parameters embedded within itself while letting the non-volatile
storage or user input extend and/or selectively override them, e.g. for a
different root device or whatever. However, as I noted above, there's no
reasonable universal default command line to use with a defconfig, just
as you could not come up with one for say an x86 PC.
I hope this clarifies the matter.
Maciej
next prev parent reply other threads:[~2019-10-09 14:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 22:20 [PATCH 1/4] MIPS: cmdline: Remove CONFIG_MIPS_CMDLINE_BUILTIN_EXTEND Paul Burton
2019-10-07 22:20 ` [PATCH 3/4] MIPS: cmdline: Remove redundant Kconfig defaults Paul Burton
2019-10-09 12:20 ` Philippe Mathieu-Daudé
2019-10-09 22:53 ` Paul Burton
2019-10-07 22:20 ` [PATCH 2/4] MIPS: cmdline: Remove CONFIG_MIPS_CMDLINE_DTB_EXTEND Paul Burton
2019-10-09 12:35 ` Philippe Mathieu-Daudé
2019-10-07 22:20 ` [PATCH 4/4] MIPS: cmdline: Clean up boot_command_line initialization Paul Burton
2019-10-09 12:34 ` [PATCH 1/4] MIPS: cmdline: Remove CONFIG_MIPS_CMDLINE_BUILTIN_EXTEND Philippe Mathieu-Daudé
2019-10-09 13:46 ` Maciej W. Rozycki
2019-10-09 14:13 ` Maciej W. Rozycki [this message]
2019-10-09 19:39 ` Paul Burton
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.2.21.1910091501580.25653@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=pburton@wavecomp.com \
/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).