Both ${global.linux.bootargs.bootm.appendroot} and
${global.linux.bootargs.machine_id} are magic vars internally populated
by barebox to hold the computed root= or systemd.machine_id options.They are out of place in the help text as they are an implementation detail and not user API. In the case of CONFIG_MMCBLKDEV_ROOTARG, it's even incorrect as the help text is talking about what a user can do to trigger the root= appending and that should be either global.bootm.appendroot=1 or adding linux-appendroot to the blspec file. Signed-off-by: Ahmad Fatoum <[email protected]> --- common/Kconfig | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/common/Kconfig b/common/Kconfig index fd422714d560..28a89265b386 100644 --- a/common/Kconfig +++ b/common/Kconfig @@ -769,7 +769,7 @@ config MMCBLKDEV_ROOTARG kernel doesn't contain commit [1]. The first linux kernel release containing that commit is v5.10-rc1. - The appending only happens if barebox' 'linux.bootargs.bootm.appendroot' + The appending only happens if barebox' 'global.bootm.appendroot' variable is set or the used blspec entry contains 'linux-appendroot'. Note: It is crucial that the kernel device tree and the barebox device @@ -1285,8 +1285,9 @@ config MACHINE_ID updating barebox the machine id might change. global.bootm.provide_machine_id may be used to automatically set - the linux.bootargs.machine_id global variable with a value of - systemd.machine_id=${global.machine_id} + fix up the kernel command line on boot with + + systemd.machine_id=${global.machine_id} Note: if no hashable information is available no machine id will be passed to the kernel. -- 2.47.3
