[PATCH 0/9] CI: test qemu-riscv64_smode[_acpi]

Heinrich Schuchardt heinrich.schuchardt at canonical.com
Sun Nov 9 11:10:01 CET 2025


ACPI via QFW was broken since the 2025.01 release and we did not observe
it due to missing CI testing. This bug has been fixed in the meanwhile.

This series

* introduces prerequisite corrections of unit tests
* provides the necessary console record size for command line tests
* enables CI testing for qemu-riscv64_smode and qemu-riscv64_smode_acpi

The following patches are just resent to show how all belongs together:

* test: fdt_test_apply requires CONFIG_OF_LIBFDT_OVERLAY
* CI: test qemu-riscv64_smode[_acpi]

Heinrich Schuchardt (9):
  test: fdt_test_apply requires CONFIG_OF_LIBFDT_OVERLAY
  test: cmd/fdt: do not assume RNG device exists
  test: cmd/bdinfo: make no flash assumption
  test: cmd/bdinfo: consider arch_print_bdinfo() output
  test: common/print: do not use fixed buffer addresses
  test: cmd/fdt: do not use fixed buffer addresses
  common: default CONFIG_CONSOLE_RECORD_OUT_SIZE=0x6000
  configs: CONFIG_CONSOLE_RECORD=y on qemu-riscv64_smode_acpi
  CI: test qemu-riscv64_smode[_acpi]

 .azure-pipelines.yml                      |  6 ++
 .gitlab-ci.yml                            | 12 ++++
 common/Kconfig                            |  2 +-
 configs/qemu-riscv64_smode_acpi_defconfig |  1 +
 test/cmd/bdinfo.c                         | 15 +++--
 test/cmd/fdt.c                            | 31 ++++++++--
 test/common/print.c                       | 71 +++++++++++------------
 7 files changed, 91 insertions(+), 47 deletions(-)

-- 
2.51.0



More information about the U-Boot mailing list