u-boot.git/common/Kconfig, branch next

avb: add board-specific root key provider

2026-08-12T07:44:24Z

The strongest anchor for the root of trust is a key hash burned into hardware (OTP/eFuse), which is inherently SoC-specific and cannot live in common code. Give boards a hook to supply it from wherever their hardware keeps it. The default is deliberately fail-closed: a board that has not wired up a provider refuses verification rather than silently trusting whatever key it is handed. A misconfiguration should stop the boot, not quietly weaken it. Signed-off-by: Igor Opaniuk Reviewed-by: Mattijs Korpershoek Link: https://patch.msgid.link/20260727-avb-root-key-pluggable-v1-3-7e27b2b92cc0@gmail.com Signed-off-by: Mattijs Korpershoek

avb: add OP-TEE root key digest provider

2026-08-12T07:44:24Z

When a device already runs OP-TEE, its root-of-trust key should live in the same secure, RPMB-backed storage that already holds the AVB rollback indexes and lock state, so it is provisioned per device and protected by the secure world -- not shipped inside the bootloader image. Let AVB fetch the trusted digest from the OP-TEE AVB TA. It reuses the existing persistent-value interface, so no change to the TA is required, and a missing value fails closed. Signed-off-by: Igor Opaniuk Reviewed-by: Mattijs Korpershoek Link: https://patch.msgid.link/20260727-avb-root-key-pluggable-v1-2-7e27b2b92cc0@gmail.com Signed-off-by: Mattijs Korpershoek

avb: make the AVB root key source pluggable

2026-08-12T07:44:24Z

AVB's whole chain of trust reduces to a single public key, and that key is currently hard-coded in U-Boot as the AVB reference/test key, whose private half is public. That is fine for bring-up but unusable for a locked product, which must anchor its root of trust in something an attacker cannot swap out -- a hash fused into the SoC, a secure element -- rather than a blob compiled into the bootloader. Make the source of the trusted key digest selectable so a board can decide where its root of trust lives, without touching the verification logic and with any lookup failure treated as untrusted. The built-in key remains the default, so existing users are unaffected; the sources a production device actually needs are added in the following patches. Signed-off-by: Igor Opaniuk Reviewed-by: Mattijs Korpershoek Link: https://patch.msgid.link/20260727-avb-root-key-pluggable-v1-1-7e27b2b92cc0@gmail.com Signed-off-by: Mattijs Korpershoek

Kconfig: common: restyle

2026-06-25T20:13:36Z

Restyle all Kconfigs for "common": Menu entries : no space left Menu attributes: 1 TAB Help text : 1 TAB + 2 spaces Replace '---help---' by 'help' Signed-off-by: Johan Jonker

simplify NET_LEGACY || NET_LWIP condition with NET condition

2026-04-27T17:26:40Z

Since the move to make NET a menuconfig and NO_NET a synonym of NET=n, when NET is enabled, NET_LEGACY || NET_LWIP is necessarily true, so let's simplify the various checks across the codebase. SPL_NET_LWIP doesn't exist but SPL_NET_LEGACY is an alias for SPL_NET so the proper symbol is still defined in SPL whenever needed. Signed-off-by: Quentin Schulz Reviewed-by: Simon Glass Reviewed-by: Peter Robinson Reviewed-by: Tom Rini

rename NET to NET_LEGACY

2026-04-27T17:26:40Z

Highlight that NET really is the legacy networking stack by renaming the option to NET_LEGACY. This requires us to add an SPL_NET_LEGACY alias to SPL_NET as otherwise CONFIG_IS_ENABLED(NET_LEGACY) will not work for SPL. The "depends on !NET_LWIP" for SPL_NET clearly highlights that it is using the legacy networking app so this seems fine to do. This also has the benefit of removing potential confusion on NET being a specific networking stack instead of "any" network stack. Signed-off-by: Quentin Schulz Acked-by: Ilias Apalodimas Reviewed-by: Peter Robinson Reviewed-by: Tom Rini

Merge tag 'v2026.04-rc3' into next

2026-02-23T19:45:55Z

Prepare v2026.04-rc3

test: cmd: Add test for zip/unzip/gzwrite commands

2026-02-18T21:02:58Z

Add simple test for zip/unzip/gzwrite commands. The test works as follows. First, create three buffers with a bit of space between each of them, fill them with random data, then compress data in buffer 1 into buffer 2, decompress data in buffer 2 either directly into buffer 3 or into MMC 1 and then read them back into buffer 3, and finally compare buffer 1 and buffer 3, they have to be identical. The buffers are filled with random data to detect out of bounds writes. Test for various sizes, both small and large and unaligned. The test uses ut_assert_skip_to_line() to skip over gzwrite progress bar. Since the progress bar updates fill up the console record buffer, increase the size of it to compensate. Reviewed-by: Mattijs Korpershoek Tested-by: Mattijs Korpershoek Signed-off-by: Marek Vasut

Replace TARGET namespace and cleanup properly

2026-02-14T17:06:46Z

TARGET namespace is for machines / boards / what-have-you that building U-Boot for. Simply replace from TARGET to ARCH make things more clear and proper for ALL SoCFPGA. Signed-off-by: Brian Sune Reviewed-by: Tien Fong Chee # Conflicts: # drivers/ddr/altera/Makefile

common: default CONFIG_CONSOLE_RECORD_OUT_SIZE=0x6000

2025-11-21T18:18:22Z

For some tests the current default of 0x400 for CONFIG_CONSOLE_RECORD_OUT_SIZE is too small. Raise the value to 0x6000 which is already the most common value. Reviewed-by: Simon Glass Reviewed-by: Ilias Apalodimas Signed-off-by: Heinrich Schuchardt