diff options
author | Christophe Leroy <christophe.leroy@csgroup.eu> | 2023-05-11 09:16:49 +0300 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2023-05-16 00:14:46 +0300 |
commit | 40b77f2a3ac13a7547c1b7c9c51a4090869de8f4 (patch) | |
tree | 91d38b825fa1aa68c4edddd2847d704905efbb11 /common/dlmalloc.c | |
parent | c9901bd2adad104adb132bdcc92fe2e86b4bcaa0 (diff) | |
download | u-boot-40b77f2a3ac13a7547c1b7c9c51a4090869de8f4.tar.xz |
envtools lack extra settings since commit 86b9c3e4e4 ("env: Allow U-Boot scripts to be placed in
After converting my targets from CFG_EXTRA_ENV_SETTINGS to
CONFIG_EXTRA_ENV_TEXT as suggested by Tom, I discovered that
fw_setenv doesn't set the entire defaut environment anymore.
I tried to fix it with the below patch, but it fails qemu-x86 CI test,
see https://source.denx.de/u-boot/custodians/u-boot-mpc8xx/-/pipelines/16326
That's the only CI test that fails AFAICS.
Could you help with a solution ? This needs to be fixed.
Thanks
Christophe
---- >8 ----
From: Christophe Leroy <christophe.leroy@csgroup.eu>
Subject: [RFC PATCH] envtools: Fix default environment
After converting some targets from CFG_EXTRA_ENV_SETTINGS to
CONFIG_EXTRA_ENV_TEXT, default environment embedded in
fw_env tool missed all extra settings.
Commit 86b9c3e4e4 ("env: Allow U-Boot scripts to be placed in
a .env file") restricted the inclusion of the content of that
file to builds without USE_HOSTCC.
But as mentionned in commit 79fc0c5f49 ("tools/env: cross-compile
fw_printenv without setting HOSTCC"), HOSTCC and USE_HOSTCC are
kept for code re-use.
Remove the restricting so that settings included in a .env
file are also added to fw_env tool.
Fixes: 86b9c3e4e4 ("env: Allow U-Boot scripts to be placed in a .env file")
Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
Diffstat (limited to 'common/dlmalloc.c')
0 files changed, 0 insertions, 0 deletions