March 2026 - Concept - U-Boot List

[PATCH 00/11] patman: Add workflow tracking for patch series
by Simon Glass 29 Mar '26

29 Mar '26

From: Simon Glass <sjg(a)chromium.org> This series adds workflow tracking to patman, allowing developers to track the status of their patch series and get reminders to follow up on reviews. It starts with a few prerequisite fixes: using a PTY for output functions, capturing git send-email output to count sent patches, fixing branch-name version stripping and output ordering. The core feature adds a workflow table to the database with support for todo entries and sent records. Series can be marked for follow-up after a given number of days, and sending a series automatically creates a reminder. A new 'workflow' command provides subcommands for managing todos and listing workflow history. This is really only the beginning, but it lays the foundation for properly keeping track of pending work. Furture series will flesh this out a little more, e.g. a query to find out what series to work on next and detecting which have been applied upstream. Simon Glass (11): u_boot_pylib: Use PIPE_PTY when an output function is given u_boot_pylib: Capture send-output to count sent patches patman: Strip version suffix in get_series_upstream() patman: Fix output ordering when running git send-email patman: Use actual send count to determine likely_sent patman: Add workflow table to the database patman: Add series-todo workflow feature patman: Add 'workflow' command with todo subcommands patman: Record series send in the workflow table patman: Add 'workflow list' command to show workflow history patman: Record ser_ver in workflow sent entries tools/patman/cmdline.py | 39 ++++- tools/patman/control.py | 31 ++++ tools/patman/cser_helper.py | 10 +- tools/patman/cseries.py | 6 +- tools/patman/database.py | 132 +++++++++++++++- tools/patman/func_test.py | 2 +- tools/patman/send.py | 9 +- tools/patman/test_cseries.py | 276 +++++++++++++++++++++++++++++++++- tools/patman/workflow.py | 155 +++++++++++++++++++ tools/u_boot_pylib/command.py | 15 +- tools/u_boot_pylib/gitutil.py | 37 +++-- 11 files changed, 685 insertions(+), 27 deletions(-) create mode 100644 tools/patman/workflow.py -- 2.43.0 base-commit: ad22002500f786fb777b53f2a6bd0f8fdca667c4 branch: path

1 11

[PATCH 0/4] vbe: Fix MMC clock handoff for VPL on rk3399
by Simon Glass 29 Mar '26

29 Mar '26

From: Simon Glass <sjg(a)chromium.org> Fix DW MMC card-enumeration failures when VPL lacks CLK framework support, by passing the source clock rate between boot phases via the bloblist. This also fixes a duplicate log_msg_ret() tag in the abrec VBE method, to aid debugging.END Simon Glass (4): vbe: abrec: Use unique log_msg_ret() tag for blk_get_from_parent() bloblist: Add tag for MMC clock rate handoff mmc: rockchip_dw_mmc: Pass clock rate via bloblist rk3399-generic-ddr3: Enable MMC clock-rate handoff boot/vbe_abrec_fw.c | 2 +- common/bloblist.c | 1 + configs/rk3399-generic-ddr3_defconfig | 1 + drivers/mmc/Kconfig | 9 ++++++++ drivers/mmc/rockchip_dw_mmc.c | 33 ++++++++++++++++++++++++++- include/bloblist.h | 1 + 6 files changed, 45 insertions(+), 2 deletions(-) -- 2.43.0 base-commit: 8c1321e1b9ab73a0f220a9210852ca0735d66623 branch: vbeb

1 4

[PATCH 0/7] qconfig: Use kconfiglib for database build and defconfig sync
by Simon Glass 29 Mar '26

29 Mar '26

From: Simon Glass <sjg(a)chromium.org> The -b (build database) and -s (sync defconfigs) options currently spawn make subprocesses for every board, requiring cross-compiler toolchains and taking several minutes. This series replaces both paths with direct kconfiglib evaluation, reducing the time to under two seconds for ~1500 boards with no toolchain requirement. It also fixes a long-standing kconfiglib bug where backslash sequences in string values (like \n in CONFIG_AUTOBOOT_PROMPT) were silently corrupted during round-trips, and adds support for syncing defconfigs that use #include directives. With all operations now using kconfiglib, the old make-based infrastructure (move_config(), Slot, Slots, KconfigParser, DatabaseThread, and related helpers) is removed, dropping ~500 lines. Simon Glass (7): qconfig: Use kconfiglib to build the CONFIG database qconfig: Auto-rebuild stale database for -f queries qconfig: Use kconfiglib for defconfig sync buildman: Fix kconfiglib string-value escaping qconfig: Handle #include defconfigs in kconfiglib sync qconfig: Remove dead database-build code from move_config() qconfig: Use kconfiglib for -r (git-ref) sync path doc/develop/qconfig.rst | 68 ++- tools/buildman/kconfiglib.py | 32 +- tools/qconfig.py | 969 ++++++++++++++++++----------------- 3 files changed, 572 insertions(+), 497 deletions(-) -- 2.43.0 base-commit: 06e5589821b8e073da12b8630c66c7fa3f1f91ba branch: qconfig

1 7

[PATCH] riscv: dts: jh7110: Exclude PLL clock controller from SPL
by Simon Glass 27 Mar '26

27 Mar '26

From: Simon Glass <sjg(a)chromium.org> Adding bootph-pre-ram to the pllclk node causes it to be included in the SPL device tree. The PLL clock controller is not previously present in SPL, and its inclusion changes the clock-tree behaviour during early boot: the clock framework now resolves and configures PLL-based clock parents for syscrg, which disrupts MMC clock setup and causes a partition-read failure (error -ENOSYS) when SPL tries to boot from MMC. Remove the bootph-pre-ram property from pllclk via the U-Boot DTS overlay so that the SPL clock tree matches the previous working state. Fixes: 7f5174739645f ("riscv: dts: starfive: jh7110: bootph-pre-ram hinting needed by boot loader") Signed-off-by: Simon Glass <sjg(a)chromium.org> --- arch/riscv/dts/starfive-visionfive2-u-boot.dtsi | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/arch/riscv/dts/starfive-visionfive2-u-boot.dtsi b/arch/riscv/dts/starfive-visionfive2-u-boot.dtsi index 33a58349752..2e079867b4b 100644 --- a/arch/riscv/dts/starfive-visionfive2-u-boot.dtsi +++ b/arch/riscv/dts/starfive-visionfive2-u-boot.dtsi @@ -49,3 +49,7 @@ &sys_syscon { bootph-pre-ram; }; + +&pllclk { + /delete-property/ bootph-pre-ram; +}; -- 2.43.0 base-commit: ea4a68919f578ae785d7a4c8a2eb7bd56a60cdd0 branch: fix-riscv

1 0

[PATCH] CI: Use ln -sf to avoid failure on existing symlinks
by Simon Glass 26 Mar '26

26 Mar '26

From: Simon Glass <sjg(a)chromium.org> The before_script creates symlinks for the qemu_arm64_lwip config and for mapping the runner hostname to the travis-ci directory. With plain ln -s, these fail if the symlinks already exist from a cached workspace or a previous job, causing intermittent INTERNALERROR failures in pytest. Use -sf for file symlinks and -sfn for directory symlinks to overwrite any stale entries. Signed-off-by: Simon Glass <sjg(a)chromium.org> --- .gitlab-ci.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 03153ea505f..3ca5a62b877 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -64,10 +64,10 @@ stages: - git config --global --add safe.directory "${CI_PROJECT_DIR}" # qemu_arm64_lwip_defconfig is the same as qemu_arm64 but with NET_LWIP enabled. # The test config and the boardenv file from qemu_arm64 can be re-used so create symlinks - - ln -s conf.qemu_arm64 test/hooks/bin/travis-ci/conf.qemu_arm64_lwip_na - - ln -s u_boot_boardenv_qemu_arm64_na.py test/hooks/py/travis-ci/u_boot_boardenv_qemu_arm64_lwip_na.py - - ln -s travis-ci test/hooks/bin/`hostname` - - ln -s travis-ci test/hooks/py/`hostname` + - ln -sf conf.qemu_arm64 test/hooks/bin/travis-ci/conf.qemu_arm64_lwip_na + - ln -sf u_boot_boardenv_qemu_arm64_na.py test/hooks/py/travis-ci/u_boot_boardenv_qemu_arm64_lwip_na.py + - ln -sfn travis-ci test/hooks/bin/`hostname` + - ln -sfn travis-ci test/hooks/py/`hostname` - if [[ "${TEST_PY_BD}" == "qemu-riscv32_spl" ]] || [[ "${TEST_PY_BD}" == "xilinx_mbv32_smode" ]]; then wget -O - https://github.com/riscv-software-src/opensbi/releases/download/v1.3.1/open… | tar -C /tmp -xJ; export OPENSBI=/tmp/opensbi-1.3.1-rv-bin/share/opensbi/ilp32/generic/firmware/fw_dynamic.bin; -- 2.43.0 base-commit: 2a454d1037d690ebc62686ae65df302f1479854a branch: lwip-fix

1 0

[PATCH 0/2] debian: Clean up qemu package targets
by Simon Glass 26 Mar '26

26 Mar '26

From: Simon Glass <sjg(a)chromium.org> Drop the uboot.elf stripped-ELF copy and the unnecessary u-boot.bin from x86 builds, simplifying the package and reducing its size. Simon Glass (2): debian: Drop the uboot.elf target from qemu builds debian: Drop u-boot.bin from x86 qemu targets debian/rules | 6 ------ debian/targets.mk | 16 ++++++++-------- debian/u-boot-concept-qemu.lintian-overrides | 8 +------- 3 files changed, 9 insertions(+), 21 deletions(-) -- 2.43.0 base-commit: b03ebd44ad163b78d0ebb8a92a8d1539a96e3bac branch: packb

1 2

[PATCH] x86: qemu: Enable the bootloader-specificaiton bootmeth
by Simon Glass 25 Mar '26

25 Mar '26

From: Simon Glass <sjg(a)chromium.org> This is useful for running boot tests, so enable it. Signed-off-by: Simon Glass <sjg(a)chromium.org> --- boot/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/boot/Kconfig b/boot/Kconfig index 50603143a05..d9e78fc8f2b 100644 --- a/boot/Kconfig +++ b/boot/Kconfig @@ -721,7 +721,7 @@ config BOOTMETH_BLS bool "Bootdev support for Boot Loader Specification (BLS) Type #1" select PXE_UTILS select PXE_INITRD_LIST - default y if SANDBOX + default y if SANDBOX || MACH_QEMU help Enables support for Boot Loader Specification (BLS) Type #1 entries. This makes bootdevs look for '*.conf' files in 'loader/entries/' -- 2.43.0 base-commit: ef2487d190c7b56b1eac217a7cca30b0f2fb2a48 branch: enable-bls

1 0

[PATCH 00/12] bootstd: Support multiple bootflows per partition
by Simon Glass 24 Mar '26

24 Mar '26

From: Simon Glass <sjg(a)chromium.org> Bootflow scanning currently assumes that each partition contributes at most one bootflow per bootmeth. In practice, formats like extlinux can define multiple labels in a single configuration file, each pointing to a different kernel. Similarly, BLS installations can have multiple .conf files in loader/entries/. This series adds multi-entry support to the bootflow iterator, building on the infrastructure from the prior series. A new BOOTMETHF_MULTI flag allows a bootmeth to declare that it can produce multiple bootflows from a single partition. The iterator tries incrementing a sub-entry index before advancing to the next bootmeth, with the entry passed to read_bootflow() via bflow->entry. Both extlinux and BLS bootmeths set BOOTMETHF_MULTI. The extlinux bootmeth uses parse_pxefile() with pxe_process_includes() to handle include directives during scanning, caching the result in the alist for reuse at boot time. A new pxe_boot_entry() function boots a specific label by index. The BLS bootmeth scans loader/entries/ for multiple .conf files. Bootflow info displays the entry number and name (extlinux label or BLS title) so users can distinguish entries from the same partition. Simon Glass (12): extlinux: Use pxe_parse() to extract bootflow info bootstd: Add BOOTMETHF_MULTI for multi-entry bootmeths extlinux: Enable multi-entry bootflow scanning test: bootstd: Add test for multi-entry bootflow scanning bls: Enable multi-entry bootflow scanning pxe: Add pxe_boot_entry() to boot a specific label by index doc: Update bootflow docs for encryption bootstd: Show entry number in bootflow info bootstd: Show entry name in bootflow info bootstd: Show entry column in bootflow list extlinux: Process and cache parsed config during scanning doc: bootstd: Document multi-entry bootflow scanning boot/bootdev-uclass.c | 1 + boot/bootflow.c | 33 +++++- boot/bootmeth_bls.c | 117 +++++++++++++++++++-- boot/bootmeth_extlinux.c | 140 ++++++++++++++++++------- boot/ext_pxe_common.c | 27 ++++- boot/pxe_utils.c | 40 +++++++ cmd/bootflow.c | 15 ++- doc/board/emulation/qemu-arm.rst | 4 +- doc/board/emulation/qemu-x86.rst | 4 +- doc/board/samsung/e850-96.rst | 6 +- doc/develop/bootstd/bls.rst | 4 + doc/develop/bootstd/extlinux.rst | 12 ++- doc/develop/bootstd/overview.rst | 37 ++++--- doc/usage/cmd/bootflow.rst | 122 ++++++++++++--------- doc/usage/cmd/bootstd.rst | 14 +-- doc/usage/cmd/history.rst | 8 +- include/bootflow.h | 9 ++ include/bootmeth.h | 5 + include/pxe_utils.h | 14 +++ test/boot/bootctl/bootctl.c | 8 ++ test/boot/bootdev.c | 13 ++- test/boot/bootflow.c | 175 +++++++++++++++++++++++++------ test/py/img/bls.py | 24 +++-- test/py/img/common.py | 11 +- test/py/img/ubuntu.py | 9 +- 25 files changed, 662 insertions(+), 190 deletions(-) -- 2.43.0 base-commit: a323092cbb41e116752e51772157e4a1d4bda955 branch: booe

1 12

[PATCH 00/14] bootstd: Infrastructure for multi-entry bootflow support
by Simon Glass 22 Mar '26

22 Mar '26

From: Simon Glass <sjg(a)chromium.org> This series prepares the bootstd infrastructure for supporting multiple bootflows from a single partition. Formats like extlinux can define several labels in one configuration file, and BLS installations can have multiple .conf files in loader/entries/ A follow-up series will add the actual multi-entry scanning. In summary: - Fix two iter->err inconsistencies in the bootflow scanning code that would prevent multi-entry iteration from working correctly - Add a free_bootflow() method to bootmeth_ops so bootmeths can properly clean up bflow->bootmeth_priv. Fix memory leaks in the cros, android and rauc drivers - Refactor the extlinux bootmeth to pass the PXE context explicitly and move it from platform data to a new private data struct - Convert the single PXE context to an alist of contexts, indexed by a new bootmeth_id field on the bootflow. This allows multiple parsed configurations to coexist - Add alist_add_placeholder() zeroing and suppress PXE parser warnings during non-interactive parsing Simon Glass (14): mcheck: Increase registry size alist: Zero new entries in alist_add_placeholder() bootstd: Set iter->err before BOOTFLOWIF_ALL early return bootstd: Clear iter->err on successful bootflow check pxe: Allow the parser to suppress warning messages bootstd: Add free_bootflow() method for bootmeths cros: Implement free_bootflow to fix memory leak android: Implement free_bootflow to fix memory leak rauc: Implement free_bootflow to fix memory leak extlinux: Pass pxe_context to extlinux_boot() and extlinux_read_all() extlinux: Move pxe_context to new extlinux_priv struct extlinux: Add remove() to fix pxe_context leak bootstd: Add bootmeth_id to struct bootflow extlinux: Convert pxe_context to an alist with bootmeth_id lookup boot/bootflow.c | 11 ++++-- boot/bootmeth-uclass.c | 10 ++++++ boot/bootmeth_android.c | 9 +++++ boot/bootmeth_cros.c | 9 +++++ boot/bootmeth_extlinux.c | 51 ++++++++++++++++++++++++--- boot/bootmeth_pxe.c | 27 ++++++++++++--- boot/bootmeth_rauc.c | 13 ++++++- boot/ext_pxe_common.c | 54 ++++++++++++++++++++--------- boot/pxe_parse.c | 27 +++++++++------ boot/pxe_utils.c | 1 + boot/vbe_abrec.h | 4 +++ boot/vbe_abrec_os.c | 13 ++++--- common/mcheck_core.inc.h | 2 +- doc/develop/bootstd/overview.rst | 12 ++++++- include/alist.h | 7 ++-- include/bootflow.h | 8 ++++- include/bootmeth.h | 24 +++++++++++++ include/extlinux.h | 59 ++++++++++++++++++++++++++++---- lib/alist.c | 8 ++++- test/boot/bootflow.c | 2 ++ test/lib/alist.c | 10 ++++++ 21 files changed, 299 insertions(+), 62 deletions(-) -- 2.43.0 base-commit: db6764b499965b88191ecd2419282087fdfe36c9 branch: bood

1 14

[PATCH 0/2] pickman: Fix robustness issues with error handling and large prompts
by Simon Glass 16 Mar '26

16 Mar '26

From: Simon Glass <sjg(a)chromium.org> Fix two bugs in pickman: one where broad exception handling causes data loss in the database migration path, and another where embedding large CI log tails in the prompt exceeds the Linux argument-size limit. Simon Glass (2): pickman: Write pipeline-fix log tails to temp files pickman: Only treat missing table as fresh database tools/pickman/agent.py | 82 +++++++++++++++++------ tools/pickman/database.py | 14 +++- tools/pickman/ftest.py | 134 +++++++++++++++++++++++++++++++++++--- 3 files changed, 198 insertions(+), 32 deletions(-) -- 2.43.0 base-commit: e1c2d707a19641df66a1c60b66909cb99d2627d9 branch: pickh

1 2