August 2025 - Concept

[PATCH 00/26] Continue development of the EFI app (part A)
by Simon Glass 08 Aug '25

08 Aug '25

From: Simon Glass <sjg(a)chromium.org> This series expand the EFI app to include more of the required functionality for booting: - access to device-path functions - disable networking (to be dealt with later) - rename BOOTMETH_EFI_LOADER since this should be usable by the app - move towards getting EFI booting going in the app - various script improvemens to support continued development Simon Glass (26): scripts: Adjust EFI script to support an OS scripts: build-qemu: Move memory size to the helper scripts: build-qemu: Move qemu program-name to the helper scripts: build-qemu: Move virtiofsd code into the helper scripts: build-qemu: Support Tianocore on ARM scripts: build-qemu: Correct networking scripts: build-qemu: Enable the display on ARM scripts: build-qemu: Always call the run() function scripts: build-efi: Enable the display on ARM scripts: Correct virtio-sci typo ide: Allow IDE_BUS() to be used without CONFIG_IDE efi_client: Provide generic malloc() and free() functions efi: Disable networking for the ARM EFI app efi: arm: Allow --gc-sections in the EFI app efi: Use variables in dp_size() efi: Move most of efi_device_path into lib/efi efi: Move EFI_FDT_USE_INTERNAL to a common header efi: Move efi_bootflow_run() to a common file efi_loader: Split out efi_binary_run_dp() et all efi_client: Allow access to the parent image efi_client: Support running an app efi: Rename BOOTMETH_EFILOADER to BOOTMETH_EFI efi: Move EFI_BINARY_EXEC to lib/efi boot: Update BOOTM_EFI to depend on EFI_LOADER fs: Avoid calling efi_set_bootdev() from the app boot: Pass the maximum size to efiload_read_file() arch/arm/config.mk | 2 - arch/arm/lib/elf_aarch64_efi.lds | 2 +- boot/Kconfig | 6 +- boot/Makefile | 2 +- boot/bootmeth_efi.c | 7 +- configs/efi-arm_app64_defconfig | 4 +- configs/khadas-vim3_android_ab_defconfig | 2 +- configs/khadas-vim3_android_defconfig | 2 +- configs/khadas-vim3l_android_ab_defconfig | 2 +- configs/khadas-vim3l_android_defconfig | 2 +- fs/fs_legacy.c | 8 +- include/blk.h | 1 + include/efi.h | 59 ++ include/efi_loader.h | 3 - include/ide.h | 4 +- lib/efi/Kconfig | 10 + lib/efi/Makefile | 2 + lib/efi/device_path.c | 1165 +++++++++++++++++++++ lib/efi/run.c | 136 +++ lib/efi_client/Makefile | 2 +- lib/efi_client/app_run.c | 90 ++ lib/efi_client/efi.c | 20 + lib/efi_loader/Kconfig | 9 - lib/efi_loader/Makefile | 2 + lib/efi_loader/efi_bootbin.c | 201 ---- lib/efi_loader/efi_device_path.c | 1132 -------------------- lib/efi_loader/efi_image_loader.c | 9 - lib/efi_loader/efi_root_node.c | 2 - lib/efi_loader/loader_run.c | 67 ++ scripts/build-efi | 3 + scripts/build-qemu | 129 +-- scripts/build_helper.py | 102 +- 32 files changed, 1703 insertions(+), 1484 deletions(-) create mode 100644 lib/efi/device_path.c create mode 100644 lib/efi/run.c create mode 100644 lib/efi_client/app_run.c create mode 100644 lib/efi_loader/loader_run.c -- 2.43.0 base-commit: 091ac902b19008601ed47587f534ede7e531d6ed branch: loadi

1 26

[PATCH 0/7] efi: Support video output on ARM
by Simon Glass 08 Aug '25

08 Aug '25

From: Simon Glass <sjg(a)chromium.org> So far the EFI app supports video on x86 but not ARM. This series adds this feature, using EFI GOP's 'blt' feature. Support for bootstd is enabled at the same time, so that the app can boot an OS automatically. Simon Glass (7): video: efi: Store the GOP in priv data efi: Support the EFI GOP blit method efi: Add an enum for the GOP blt operation scripts: Adjust EFI script to support a root disk efi: Support bootstd and video with ARM app dm: core: Provide oftree_dispose() when OF_LIVE is disabled boot: Enable the VBE-OS bootmeth for EFI app and payload boot/Kconfig | 1 + configs/efi-arm_app64_defconfig | 13 ++-- drivers/video/efi.c | 113 +++++++++++++++++++++++++------- include/dm/ofnode.h | 22 ++++--- include/efi_api.h | 19 +++++- scripts/build-efi | 5 +- scripts/build_helper.py | 8 ++- 7 files changed, 130 insertions(+), 51 deletions(-) -- 2.43.0 base-commit: 9179000b5094fb2146e336c130e0d8ee35ef85e2

1 7

[PATCH 1/4] CI: Rename world build and testsuites stages
by Simon Glass 05 Aug '25

05 Aug '25

From: Simon Glass <sjg(a)chromium.org> We use 'testsuites' for the test suites and 'world build' for the world build. This is inconsistent. Use 'test_suites' and 'word_build' instead, to avoid confusion. Signed-off-by: Simon Glass <sjg(a)chromium.org> --- .gitlab-ci.yml | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 9d80029ed2b..5d750beb5b9 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -23,10 +23,10 @@ default: # We run some tests in different order, to catch some failures quicker. stages: - - testsuites + - test_suites - test.py - sjg-lab - - world build + - world_build - version_bump - release @@ -124,7 +124,7 @@ stages: expire_in: 1 week .world_build: - stage: world build + stage: world_build rules: - if: $LAB_ONLY != "1" when: always @@ -206,8 +206,8 @@ build all other platforms: exit $ret; fi; -.testsuites: - stage: testsuites +.test_suites: + stage: test_suites rules: - if: $LAB_ONLY != "1" when: always @@ -215,7 +215,7 @@ build all other platforms: when: never check for new CONFIG symbols outside Kconfig: - extends: .testsuites + extends: .test_suites script: - git config --global --add safe.directory "${CI_PROJECT_DIR}" # If grep succeeds and finds a match the test fails as we should @@ -228,7 +228,7 @@ check for new CONFIG symbols outside Kconfig: # build documentation docs: - extends: .testsuites + extends: .test_suites script: - python3 -m venv /tmp/venvhtml - . /tmp/venvhtml/bin/activate @@ -238,13 +238,13 @@ docs: # ensure all configs have MAINTAINERS entries Check for configs without MAINTAINERS entry: - extends: .testsuites + extends: .test_suites script: - ./tools/buildman/buildman --maintainer-check # Ensure host tools build Build tools-only and envtools: - extends: .testsuites + extends: .test_suites tags: - single script: @@ -252,8 +252,8 @@ Build tools-only and envtools: make mrproper; make tools-only_config envtools -j$(nproc) -Run binman, buildman, dtoc, Kconfig and patman testsuites: - extends: .testsuites +Run binman, buildman, dtoc, Kconfig and patman test suites: + extends: .test_suites script: - git config --global user.name "GitLab CI Runner"; git config --global user.email trini(a)konsulko.com; @@ -282,7 +282,7 @@ Run binman, buildman, dtoc, Kconfig and patman testsuites: # Check for any pylint regressions Run pylint: - extends: .testsuites + extends: .test_suites tags: - single script: @@ -306,7 +306,7 @@ Run pylint: # Check for pre-schema driver model tags Check for pre-schema tags: - extends: .testsuites + extends: .test_suites script: - git config --global --add safe.directory "${CI_PROJECT_DIR}"; # If grep succeeds and finds a match the test fails as we should @@ -315,7 +315,7 @@ Check for pre-schema tags: # Check we can package the Python tools Check packing of Python tools: - extends: .testsuites + extends: .test_suites script: - make pip -- 2.43.0 base-commit: 25cf278d2c0862e502396a35d5a382540d517d85

1 3

[PATCH 00/14] buildman: Introduce some order to config fragments
by Simon Glass 04 Aug '25

04 Aug '25

From: Simon Glass <sjg(a)chromium.org> U-Boot supports config fragments, separate files which can be used to amend the config for an existing board. So far, buildman has not supported this feature. It is not been possible to buildman boards with fragments, nor has there been any file which describes which fragments are valid with which boards. This series attempts to improve this situation. It updates buildman in two ways: - Provides an option to pass fragment files to the buildman build - Provides a file which associates boards with supported fragments With this, extended boards are built in CI (Gitlab only). Heinrich Schuchardt (3): buildman: allow specifying configuration fragments buildman: unit test for configuration fragments doc/buildman: describe using fragments Simon Glass (11): buildman: Document the format for extended boards buildman: Add a parser for the extended-board file qconfig: Refactor to allow buildman to read the database qconfig: Rename do_build_db() qconfig: Drop args from KconfigParser qconfig: Document cmdline args used by some functions qconfig: Allow buildman to obtain the qconfig database buildman: Add a option to include extended boards buildman: Support building an extended board Provide a basic .buildman file CI: Checking building of extended boards .gitlab-ci.yml | 16 +-- configs/acpi.config | 1 + configs/extended.buildman | 12 +++ tools/buildman/board.py | 8 +- tools/buildman/boards.py | 181 +++++++++++++++++++++++++++++++- tools/buildman/builder.py | 5 +- tools/buildman/builderthread.py | 26 +++-- tools/buildman/buildman.rst | 80 +++++++++++--- tools/buildman/cmdline.py | 4 + tools/buildman/control.py | 9 +- tools/buildman/func_test.py | 104 ++++++++++++++++++ tools/buildman/test.py | 2 +- tools/qconfig.py | 94 +++++++++++++---- 13 files changed, 488 insertions(+), 54 deletions(-) create mode 100644 configs/acpi.config create mode 100644 configs/extended.buildman -- 2.43.0 base-commit: 05840f9593b476d7500e1641723a899c57b26233 branch: bui

1 14

[PATCH 00/24] boot: Enhance VBE to support a separate devicetree FIT
by Simon Glass 02 Aug '25

02 Aug '25

From: Simon Glass <sjg(a)chromium.org> It is sometimes desirable to have the devicetrees packaged with firware, or in a different FIT from the OS. This series adds support for this, including a test. The new bootmeth can automatically locate a state file and use that to decide what images to use when booting. The OS must update the file before rebooting, if a different selection is required. For now there is no logic to deal with boot failures. Simon Glass (24): Correct implementation of Spawn() in ConsoleBase test: Rename test_vboot() to test_vboot_base() sandbox: Increase the number of bootstage records boot: Tidy up fit_get_desc() boot: Use a common index in fit_conf_print boot: Show messages when using FIT best-match boot: Add a constant for the FIT-configuration compatible boot: Show compatible strings with FIT information sandbox: Enable FIT best-match mkimage: Remove an unused argument from fdt_property_file() mkimage: Add compatible strings to configuration node mkimage: Support a load-only FIT mkimage: Set the timestamp with -f auto test: Allow inspection of input filesystems test: Drop double removal of the FS image on failure boot: Move PXE-parsing logic out to a separate file boot: Remove blank lines in pxe_parse boot: pxe: Add a token for FIT boot: Use provided filename with bootmeth_alloc_other() boot: Support restarting a bootm sequence from PXE boot: Add comments for struct pxe_label boot: Add support for VBE for the OS boot: test: Add a test for the VBE OS flow boot: Add documentation for the VBE-OS bootmeth arch/sandbox/dts/test.dts | 11 + boot/Kconfig | 14 + boot/Makefile | 2 +- boot/bootflow.c | 2 + boot/bootmeth-uclass.c | 3 +- boot/bootmeth_extlinux.c | 3 +- boot/bootmeth_pxe.c | 2 +- boot/ext_pxe_common.c | 3 +- boot/image-board.c | 3 +- boot/image-fit.c | 75 ++- boot/pxe_parse.c | 659 +++++++++++++++++++++++ boot/pxe_utils.c | 711 +------------------------ boot/vbe_abrec.c | 2 +- boot/vbe_abrec.h | 5 + boot/vbe_abrec_fw.c | 1 + boot/vbe_abrec_os.c | 293 ++++++++++ configs/sandbox_defconfig | 1 + doc/develop/bootstd/index.rst | 1 + doc/develop/bootstd/vbe_os.rst | 61 +++ doc/develop/vbe.rst | 2 + doc/mkimage.1 | 13 + include/bootflow.h | 8 +- include/extlinux.h | 4 +- include/image.h | 15 +- include/pxe_utils.h | 63 ++- include/vbe.h | 13 + test/boot/Makefile | 1 + test/boot/bootflow.c | 75 ++- test/boot/bootmeth.c | 19 +- test/boot/vbe_abrec_os.c | 138 +++++ test/py/console_base.py | 15 +- test/py/console_board.py | 2 +- test/py/test.py | 4 + test/py/tests/fs_helper.py | 74 ++- test/py/tests/img/vbe.py | 167 ++++++ test/py/tests/test_ut.py | 3 +- test/py/tests/test_vbe.py | 22 + test/py/tests/test_vboot.py | 4 +- test/py/tests/vboot/sandbox-kernel.dts | 3 +- tools/fit_image.c | 114 ++-- tools/imagetool.h | 15 +- tools/mkimage.c | 12 +- 42 files changed, 1757 insertions(+), 881 deletions(-) create mode 100644 boot/pxe_parse.c create mode 100644 boot/vbe_abrec_os.c create mode 100644 doc/develop/bootstd/vbe_os.rst create mode 100644 test/boot/vbe_abrec_os.c create mode 100644 test/py/tests/img/vbe.py -- 2.43.0 base-commit: 05840f9593b476d7500e1641723a899c57b26233 branch: loadg

1 24

[PATCH 00/21] mkimage: Start to tidy up mkimage and friends
by Simon Glass 01 Aug '25

01 Aug '25

The current mkimage code is a bit messy: - the main() function is very long - two similarly named structs are used throughout: the first (struct image_tool_params) is not actually just parameters, the second (struct image_type_params) is confusingly similar - quite a bit of FIT processing happens right at the start of main(), which can be hard to follow - the program calls exit() from many different places This series renames the main structures, avoiding using the common 'params' word. It breaks up part of main() into separate functions and starts the process of exiting in one place. It also reverts a patch which causes an invalid 'loadables' property to be added with '-f auto'. More remains to be done, but this is a start. Simon Glass (21): mkimage: Move copy_file() higher in the file mkimage: Move code from main() to a new function mkimage: Return the exist code from run_mkimage() mkimage: Update usage() to return a value mkimage: Rename struct image_type_params to imgtool_funcs mkimage: Return struct image_tool_params to struct imgtool mkimage: Use a consistent parameter for struct imgtool * mkimage: Pass struct imgtool out from main() mkimage: Update add_content() to take an imgtool parameter mkimage: Update process_args() to take an imgtool parameter mkimage: Update verify_image() to take an imgtool parameter mkimage: Update copy_file() etc. to take an imgtool parameter mkimage: Update run_mkimage() to take an imgtool parameter mkimage: Drop the global for struct imgtool mkimage: Update process_args() to return a value always mkimage: Update verify_image() to return a value always mkimage: Update copy_file() et al to return a value always mkimage: Split out initial checking and processing mkimage: Split out file-opening into its own function mkimage: Move the list-or-process code into a function Revert "tools: fit_image: Add the loadable property to configs" tools/aisimage.c | 57 ++- tools/atmelimage.c | 27 +- tools/default_image.c | 54 +-- tools/dumpimage.c | 8 +- tools/fit_common.c | 5 +- tools/fit_common.h | 7 +- tools/fit_image.c | 239 ++++++----- tools/gpheader.h | 2 +- tools/gpimage-common.c | 8 +- tools/gpimage.c | 8 +- tools/imagetool.c | 56 +-- tools/imagetool.h | 67 ++- tools/imx8image.c | 12 +- tools/imx8mimage.c | 8 +- tools/imximage.c | 41 +- tools/kwbimage.c | 164 +++---- tools/lpc32xximage.c | 6 +- tools/mkimage.c | 869 +++++++++++++++++++++----------------- tools/mtk_image.c | 26 +- tools/mxsimage.c | 37 +- tools/omapimage.c | 11 +- tools/pblimage.c | 40 +- tools/renesas_spkgimage.c | 35 +- tools/rkcommon.c | 109 +++-- tools/rkcommon.h | 20 +- tools/rkimage.c | 8 +- tools/rkspi.c | 17 +- tools/sfspl.c | 25 +- tools/socfpgaimage.c | 66 ++- tools/stm32image.c | 10 +- tools/sunxi_egon.c | 37 +- tools/sunxi_toc0.c | 29 +- tools/ublimage.c | 24 +- tools/vybridimage.c | 6 +- tools/zynqimage.c | 24 +- tools/zynqmpbif.c | 14 +- tools/zynqmpimage.c | 42 +- tools/zynqmpimage.h | 2 +- 38 files changed, 1138 insertions(+), 1082 deletions(-) -- 2.43.0 base-commit: 816236b75e1b9248d282fb81e0c77426add8385a branch: loadd

1 21