mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Alexander Shiyan <eagle.alexander923@gmail.com>,
	Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 0/3] bootm: append automatic parameters after all other linux.bootargs
Date: Tue,  5 May 2026 11:50:57 +0200	[thread overview]
Message-ID: <20260505095137.1123867-1-a.fatoum@pengutronix.de> (raw)

bootm can be configured to determine suitable values for a number of
kernel command line options that will automatically be fixed up.

Currently, these options are concatenated into the kernel command line
interleaved with all other options in the lexicographical order of the
linux.bootargs. parameter name.

For the root= option, this means that any root= in a blspec file for
example will override barebox' own root=, because:

  global.linux.bootargs.bootm.root < global.linux.bootargs.dyn.bootentries

The other way makes more sense however, especially as there is always a
device parameter or Kconfig option to control whether the fixup should
happen at all.

With the new order, it's now possible to set global.bootm.appendroot=1
and have barebox append a new root= and have it take precedence over a
bootloader spec provided root=. To reflect that this has occurred, the
kernel command-line will continue to list two root='s, which greatly
simplifies debugging if issues happen (e.g. because there was a
rootfstype that is no longer accurate).

Ahmad Fatoum (3):
  common: fix help text reference to internal imagicvars
  Documentation: user: booting-linux: split off mtdparts fixup section
  bootm: append automatic parameters after all other linux.bootargs

 .../migration-guides/migration-master.rst     |  9 +++
 Documentation/user/booting-linux.rst          | 69 +++++++++++++------
 common/Kconfig                                |  7 +-
 common/bootm.c                                | 26 +++++--
 4 files changed, 79 insertions(+), 32 deletions(-)

-- 
2.47.3




             reply	other threads:[~2026-05-05  9:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05  9:50 Ahmad Fatoum [this message]
2026-05-05  9:50 ` [PATCH 1/3] common: fix help text reference to internal imagicvars Ahmad Fatoum
2026-05-05  9:50 ` [PATCH 2/3] Documentation: user: booting-linux: split off mtdparts fixup section Ahmad Fatoum
2026-05-05  9:51 ` [PATCH 3/3] bootm: append automatic parameters after all other linux.bootargs Ahmad Fatoum
2026-05-05 12:45   ` Alexander Shiyan
2026-05-07 11:17   ` (subset) " Sascha Hauer

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=20260505095137.1123867-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=eagle.alexander923@gmail.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