u-boot.git/Makefile, branch v2023.07.02 Unnamed repository; edit this file 'description' to name the repository. Prepare v2023.07.02 2023-07-11T15:20:44+00:00 Tom Rini trini@konsulko.com 2023-07-11T15:20:44+00:00 83cdab8b2c6ea0fc0860f8444d083353b47f1d5c Take the v2023.07 tag, which reported to be v2023.07-rc6 still, and change this to be v2023.07.02 (as I made a v2023.07.01 incorrectly). Signed-off-by: Tom Rini <trini@konsulko.com> 
Take the v2023.07 tag, which reported to be v2023.07-rc6 still, and
change this to be v2023.07.02 (as I made a v2023.07.01 incorrectly).

Signed-off-by: Tom Rini <trini@konsulko.com>
Prepare v2023.07-rc6 2023-07-03T17:48:58+00:00 Tom Rini trini@konsulko.com 2023-07-03T17:48:58+00:00 e1bebc16e1d9aa0ddd56c53c0b781f7186dce557 Signed-off-by: Tom Rini <trini@konsulko.com> 
Signed-off-by: Tom Rini <trini@konsulko.com>
Prepare v2023.07-rc5 2023-06-26T15:44:06+00:00 Tom Rini trini@konsulko.com 2023-06-26T15:44:06+00:00 4f1077bc35f683985ff77e442ada7e8a8a52e3b7 Signed-off-by: Tom Rini <trini@konsulko.com> 
Signed-off-by: Tom Rini <trini@konsulko.com>
Makefile: clean lib/efi_loader/helloworld_efi.S 2023-06-16T04:45:19+00:00 Heinrich Schuchardt heinrich.schuchardt@canonical.com 2023-06-02T20:18:23+00:00 12858ab216a2f3faf7e37fb5c292b64afff673cf lib/efi_loader/helloworld_efi.S is a generated file and shall be removed by 'make clean'. Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com> 
lib/efi_loader/helloworld_efi.S is a generated file and shall be removed by
'make clean'.

Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Prepare v2023.07-rc4 2023-06-12T17:45:09+00:00 Tom Rini trini@konsulko.com 2023-06-12T17:45:09+00:00 19b77d3d23966a0d6dbb3c86187765f11100fb6f Signed-off-by: Tom Rini <trini@konsulko.com> 
Signed-off-by: Tom Rini <trini@konsulko.com>
Prepare v2023.07-rc3 2023-05-29T14:59:09+00:00 Tom Rini trini@konsulko.com 2023-05-29T14:59:09+00:00 020520bbc1ff4a542e014f0873c13b4543aea0ea Signed-off-by: Tom Rini <trini@konsulko.com> 
Signed-off-by: Tom Rini <trini@konsulko.com>
envtools lack extra settings since commit 86b9c3e4e4 ("env: Allow U-Boot scripts to be placed in 2023-05-15T21:14:46+00:00 Christophe Leroy christophe.leroy@csgroup.eu 2023-05-11T06:16:49+00:00 40b77f2a3ac13a7547c1b7c9c51a4090869de8f4 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> 
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>
Prepare v2023.07-rc2 2023-05-08T18:16:32+00:00 Tom Rini trini@konsulko.com 2023-05-08T18:16:32+00:00 f1d33a44ca04fdca241c1d89fd79e2e56c930c7e Signed-off-by: Tom Rini <trini@konsulko.com> 
Signed-off-by: Tom Rini <trini@konsulko.com>
Prepare v2023.07-rc1 2023-05-01T16:02:02+00:00 Tom Rini trini@konsulko.com 2023-05-01T16:02:02+00:00 6735ab59e6fd71ced1c58d8dfb3dd6baf3690d16 Signed-off-by: Tom Rini <trini@konsulko.com> 
Signed-off-by: Tom Rini <trini@konsulko.com>
clang: Don't look for libgcc 2023-04-25T19:31:27+00:00 Tom Rini trini@konsulko.com 2023-04-05T23:48:53+00:00 4ad6850d2b4ad0de6eedffc781d8152ec736e234 In the case of using clang to build, and having not already enabled the private libgcc, do not look for it, as it will not be found nor required. Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
In the case of using clang to build, and having not already enabled the
private libgcc, do not look for it, as it will not be found nor
required.

Signed-off-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Simon Glass <sjg@chromium.org>