u-boot.git/include, branch u-boot-2023.07.y Unnamed repository; edit this file 'description' to name the repository. imx: hab: Simplify the mechanism 2023-06-24T17:47:02+00:00 Marek Vasut marex@denx.de 2023-05-28T21:00:30+00:00 6039e0edc8540bd2abee780549b260bdaf089168 The current mechanism is unnecessarily complex. Simplify the whole mechanism such that the entire fitImage is signed, IVT is placed at the end, followed by CSF, and this entire bundle is also authenticated. This makes the signing scripting far simpler. Signed-off-by: Marek Vasut <marex@denx.de> 
The current mechanism is unnecessarily complex. Simplify the whole mechanism
such that the entire fitImage is signed, IVT is placed at the end, followed
by CSF, and this entire bundle is also authenticated. This makes the signing
scripting far simpler.

Signed-off-by: Marek Vasut <marex@denx.de>
ubifs: allow loading to above 4GiB 2023-06-06T08:37:25+00:00 Ben Dooks ben.dooks@sifive.com 2023-06-06T08:23:28+00:00 b46cec41664f35c689385c70c76d274a059c7251 The ubifsload command is truncating any address above 4GiB as it casts this address to an u32, instead of using an unsigned long which most of the other load commands do. Change this to an unsigned long to allow loading into high memory for boards which use these areas. Fixes the following error: => ubifsload 0x2100000000 /boot/Image.lzma Loading file '/boot/Image.lzma' to addr 0x00000000... Unhandled exception: Store/AMO access fault Signed-off-by: Ben Dooks <ben.dooks@sifive.com> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk> 
The ubifsload command is truncating any address above 4GiB as it casts
this address to an u32, instead of using an unsigned long which most of
the other load commands do. Change this to an unsigned long to allow
loading into high memory for boards which use these areas.

Fixes the following error:

=> ubifsload 0x2100000000 /boot/Image.lzma
Loading file '/boot/Image.lzma' to addr 0x00000000...
Unhandled exception: Store/AMO access fault

Signed-off-by: Ben Dooks <ben.dooks@sifive.com>
Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
arm: dts: imx93: sync device tree with Linux 2023-05-21T14:54:41+00:00 Peng Fan peng.fan@nxp.com 2023-04-28T04:08:37+00:00 596b9c4e1bbd119bfee0a3a2779ce79438d00d43 Sync device tree with next-20230426 Signed-off-by: Peng Fan <peng.fan@nxp.com> 
Sync device tree with next-20230426

Signed-off-by: Peng Fan <peng.fan@nxp.com>
imx9: imx93_evk: drop unused macro 2023-05-21T14:54:40+00:00 Peng Fan peng.fan@nxp.com 2023-04-28T04:08:23+00:00 298b237f6771714ad18738d8421caa75f1c1adb2 Drop unused macro Signed-off-by: Peng Fan <peng.fan@nxp.com> 
Drop unused macro

Signed-off-by: Peng Fan <peng.fan@nxp.com>
imx: firmware: sci: add inline functions when IMX8 not enabled 2023-05-21T14:54:40+00:00 Peng Fan peng.fan@nxp.com 2023-04-28T04:08:10+00:00 f991e98b3bb76058c6163930e43b0032f7829046 Since we might reuse some drivers for other platforms, while the drivers have sci firmware api, so to avoid build failure add inline functions Signed-off-by: Peng Fan <peng.fan@nxp.com> 
Since we might reuse some drivers for other platforms, while the drivers
have sci firmware api, so to avoid build failure add inline functions

Signed-off-by: Peng Fan <peng.fan@nxp.com>
imx: move imx8 sci header file to include/firmware/imx 2023-05-21T14:54:32+00:00 Peng Fan peng.fan@nxp.com 2023-04-28T04:08:09+00:00 99ac6c769f92b29a6317ee6beb239269bc59a82d Move imx8 sci header file to include/firmware/imx, then we could use build macro to reuse some i.MX8 drivers for i.MX9, such as drivers/cpu/imx8_cpu.c. Signed-off-by: Peng Fan <peng.fan@nxp.com> Signed-off-by: Stefano Babic <sbabic@denx.de> 
Move imx8 sci header file to include/firmware/imx, then we could
use build macro to reuse some i.MX8 drivers for i.MX9, such as
drivers/cpu/imx8_cpu.c.

Signed-off-by: Peng Fan <peng.fan@nxp.com>
Signed-off-by: Stefano Babic <sbabic@denx.de>
Merge tag 'efi-2023-07-rc3' of https://source.denx.de/u-boot/custodians/u-boot-efi 2023-05-16T15:23:30+00:00 Tom Rini trini@konsulko.com 2023-05-16T15:23:30+00:00 6e1852ca2c418e2536ead4b51c4d84a59926b3f1 Pull request efi-2023-07-rc3 Documentation: * update the description of signature algorithms UEFI: * fix unaligned access to GUID in HII database protocol * fix launching EFI binaries loaded via semihosting * fix filling of file path in loaded image protocol for non-block devices 
Pull request efi-2023-07-rc3

Documentation:

* update the description of signature algorithms

UEFI:

* fix unaligned access to GUID in HII database protocol
* fix launching EFI binaries loaded via semihosting
* fix filling of file path in loaded image protocol for non-block devices
environment: ti: rproc: fix remoteproc environment variables 2023-05-15T21:14:46+00:00 Manorit Chawdhry m-chawdhry@ti.com 2023-05-15T06:52:42+00:00 6d677ea8ecd11c26e45dae1ed855ec275177b149 During refactor this seemed to have been missed. Fixes: 65dbb128fb45 ("include: environment: ti: Use .env for environment variables") Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> 
During refactor this seemed to have been missed.

Fixes: 65dbb128fb45 ("include: environment: ti: Use .env for environment variables")

Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.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>
Merge https://source.denx.de/u-boot/custodians/u-boot-cfi-flash 2023-05-15T12:33:16+00:00 Tom Rini trini@konsulko.com 2023-05-15T12:33:16+00:00 c9b2a789281c76d3710036455d0524a1ac997f66 - cfi: respect reg address length (Nuno) 
- cfi: respect reg address length (Nuno)