u-boot.git/test/boot, branch v2025.01-rc1

boot: Introduce BOOTSTD_MENU to control bootflow menu build

2024-10-24T17:19:55Z

The bootflow_menu.c code depends on e.g. scene_txt_set_font(), which is only built when CONFIG_EXPO is enabled. Introduce new Kconfig symbol BOOTSTD_MENU which depends on EXPO to prevent triggering errors like these in case e.g. CONFIG_VIDEO=n : " boot/bootflow_menu.c:158:(.text+0x8851): undefined reference to `scene_txt_set_font' " Make the symbol depend on BOOTSTD_FULL as well to get rid of the Makefile dependency workaround. Since BOOTSTD_FULL is not available in SPL, do not define SPL variant of BOOTSTD_MENU. Fix up bootflow test accordingly. Signed-off-by: Marek Vasut Reviewed-by: Simon Glass

expo: Drop scene_title_set()

2024-10-18T20:10:22Z

This function is really just an assignment, so serves no useful purpose. Drop it. Signed-off-by: Simon Glass

expo: Support menu-item values in cedit

2024-10-18T20:10:22Z

Update the cedit read/write functions to support menu items with values. Signed-off-by: Simon Glass

expo: Allow menu items to have values

2024-10-18T20:10:22Z

At present menu items are stored according to their sequence number in the menu. In some cases we may want to have holes in that sequence, or not use a sequence at all. Add a new 'value' property for menu items. This will be used for reading and writing, if present. If there is no 'value' property, then the normal sequence number will be used instead. Signed-off-by: Simon Glass

expo: Use standard numbering for save and discard

2024-10-18T20:10:22Z

Set aside some expo IDs for 'save' and 'discard' buttons. This avoids needing to store the IDs for these. Adjust the documentation and expo tool for the new EXPOID_BASE_ID value. Ignore these objects when saving and loading the cedit, since they do not contain real data. Adjust 'cedit run' to return failure when the user exits the expo without saving. Update the test for this change as well. Signed-off-by: Simon Glass

expo: Set the initial next_id to 1

2024-10-18T20:10:22Z

If expo_set_dynamic_start() is never called, the first scene created will have an ID of 0, which is invalid. Correct this by setting a default value. Add a test to check this. Signed-off-by: Simon Glass

test: boot: fix bootflow_cmd_label for when DSA_SANDBOX is disabled

2024-10-16T17:11:56Z

When DSA_SANDBOX is not set, the sandbox tests fail as follows: $ ./test/py/test.py --build-dir=$(pwd) -k bootdev_test_any [...] Scanning for bootflows with label '9' [...] Cannot find '9' (err=-19) This is due to the device list containing two less entries than expected. Therefore, look for label '7' when DSA_SANDBOX is disabled. The actual use case is NET_LWIP=y (to be introduced in later patches) which implies DSA_SANDBOX=n for the time being. Signed-off-by: Jerome Forissier

test: boot: fix bootdev_test_any for when DSA_SANDBOX is disabled

2024-10-16T17:11:56Z

When DSA_SANDBOX is not set, the sandbox tests fail as follows: $ ./test/py/test.py --build-dir=$(pwd) -k bootdev_test_any [...] Test: bootdev_test_any: bootdev.c test/boot/bootdev.c:156, bootdev_test_any(): "mmc2" = media->name: Expected "mmc2", got "mmc0" [...] This is due to the device list containing two less entries than expected. Therefore, adjust the expected index to be two less when DSA_SANDBOX is disabled. The actual use case is NET_LWIP=y (to be introduced in later patches) which implies DSA_SANDBOX=n for the time being. Signed-off-by: Jerome Forissier Reviewed-by: Simon Glass

test: Add tests for the bootmeth set command

2024-10-15T17:38:43Z

We have added a "set" sub command to bootmeth, add some tests to check it's operation. Signed-off-by: Martyn Welch Reviewed-by: Simon Glass

Merge patch series "Fix various bugs"

2024-09-18T19:07:19Z

Simon Glass says: This series includes the patches needed to make make the EFI 'boot' test work. That test has now been split off into a separate series along with the EFI patches. This series fixes these problems: - sandbox memory-mapping conflict with PCI - the fix for that causes the mbr test to crash as it sets up pointers instead of addresses for its 'mmc' commands - the mmc and read commands which cast addresses to pointers - a tricky bug to do with USB keyboard and stdio - a few other minor things