Add barebox bootloader support (and testing)
v6 cover Add barebox bootloader support (and testing)
This adds support for the barebox bootloader (and tools) to oe-core.
In order to have proper testing, this extends oe-selftest to allow basic testing of bootloaders. While at it, cover both u-boot and barebox.
v6:
* replace barebox.inc by barebox.bbclass (move content of barebox-common.inc into .bbclass and .bb files)
* support for UNPACKDIR
Enrico Jorns (5):
barebox: set default BAREBOX_CONFIG for qemu machines oeqa/utils/qemurunner: support ignoring vt100 escape sequences
oeqa: support passing custom boot patterns to runqemu oeqa/selftest/cases: add basic u-boot test oeqa/selftest/cases: add basic barebox tests
Marco Felsch (2):
barebox: add initial support
barebox-tools: add initial barebox tools support
meta/classes-recipe/barebox.bbclass | 160 ++++++++++++++++++ meta/conf/distro/include/maintainers.inc | 2 + meta/conf/machine/qemuarm.conf | 1 + meta/conf/machine/qemuarm64.conf | 1 + meta/conf/machine/qemux86-64.conf | 1 + meta/lib/oeqa/selftest/cases/barebox.py | 43 +++++ meta/lib/oeqa/selftest/cases/uboot.py | 42 +++++ meta/lib/oeqa/targetcontrol.py | 5 +- meta/lib/oeqa/utils/commands.py | 5 +- meta/lib/oeqa/utils/qemurunner.py | 6 +- .../barebox/barebox-tools_2024.08.0.bb | 59 +++++++ meta/recipes-bsp/barebox/barebox_2024.08.0.bb | 14 ++ 12 files changed, 333 insertions(+), 6 deletions(-) create mode 100644 meta/classes-recipe/barebox.bbclass create mode 100644 meta/lib/oeqa/selftest/cases/barebox.py create mode 100644 meta/lib/oeqa/selftest/cases/uboot.py create mode 100644 meta/recipes-bsp/barebox/barebox-tools_2024.08.0.bb create mode 100644 meta/recipes-bsp/barebox/barebox_2024.08.0.bb
Signature · 1 line
2.39.2
PATCH v6 1/7 barebox: add initial support
From: Marco Felsch <[email protected]>
This adds the support for the barebox bootloader to oe-core. The recipe is inspired by meta-ptx [1] but is a major rework of the one found there.
Barebox comes with a wide range of supported architectures and follows the concepts of Linux in various aspects like the driver model, the shell, or the virtual file system.
This not only eases porting Linux drivers but also makes barebox a developer-friendly and feature-rich bootloader alternative [2].
For barebox (like for the kernel or other bootloaders) it is quite likely that people will not just build the original recipe but need to adapt it, point to custom repositories, apply patch stacks, COMPATIBLE_MACHINE etc. They may also choose to have different recipe names for different variants.
Having only a single .bb file and requiring to copy or .bbappend it is inconvenient and results in unnecessary code duplication. Therefore, the base support for building barebox is encapsulated in barebox.bbclass (like kernel.bbclass for the kernel).
[1] https://github.com/pengutronix/meta-ptx/tree/master/recipes-bsp/barebox
[2] https://www.barebox.org/demo/?graphic=0
--- meta/classes-recipe/barebox.bbclass | 160 ++++++++++++++++++ meta/conf/distro/include/maintainers.inc | 1 + meta/recipes-bsp/barebox/barebox_2024.08.0.bb | 14 ++ 3 files changed, 175 insertions(+) create mode 100644 meta/classes-recipe/barebox.bbclass create mode 100644 meta/recipes-bsp/barebox/barebox_2024.08.0.bb
meta/classes-recipe/barebox.bbclass new file +160 -0
@@ -0,0 +1,160 @@ +# +# Copyright OpenEmbedded Contributors +# +# SPDX-License-Identifier: MIT +# + +inherit kernel-arch deploy cml1 pkgconfig + +LICENSE ?= "GPL-2.0-only" + +PROVIDES += "virtual/bootloader" + +PACKAGE_ARCH = "${MACHINE_ARCH}" + +DEPENDS += "bison-native flex-native" + +S = "${WORKDIR}/barebox-${PV}" +B = "${WORKDIR}/build" + +require conf/image-uefi.conf + +# For some platforms and configuration, the barebox build process will require +# additional host tools that can be activated/deactivated here. +PACKAGECONFIG ??= "openssl libusb fit" + +PACKAGECONFIG[openssl] = ",,openssl-native" +PACKAGECONFIG[libusb] = ",,libusb1-native" +PACKAGECONFIG[fit] = ",,u-boot-tools-native dtc-native" + +export KBUILD_BUILD_USER ?= "oe-user" +export KBUILD_BUILD_HOST ?= "oe-host" + +# unlike the kernel, barebox may build against host tools like openssl +export HOST_EXTRACFLAGS + +def get_layer_rev(path): + try: + rev, _ = bb.process.run("git describe --match='' --always --dirty --broken", cwd=path) + except bb.process.ExecutionError: + rev = "" + return rev.strip() + +BAREBOX_BUILDSYSTEM_VERSION[doc] = "Build system version to add to the barebox image. By default this is the git description of the containing layer." +BAREBOX_BUILDSYSTEM_VERSION ??= "${@get_layer_rev(os.path.dirname(d.getVar('FILE')))}" + +BAREBOX_FIRMWARE_DIR[doc] = "Overwrite barebox' firmware blobs search directory (CONFIG_EXTRA_FIRMWARE_DIR) with this path, default ${B}/firmware" +BAREBOX_FIRMWARE_DIR ??= "${B}/firmware" + +EXTRA_OEMAKE = " \ + CROSS_COMPILE=${TARGET_PREFIX} -C ${S} O=${B} \ + BUILDSYSTEM_VERSION=${BAREBOX_BUILDSYSTEM_VERSION} \ + CONFIG_EXTRA_FIRMWARE_DIR=${BAREBOX_FIRMWARE_DIR} \ + PKG_CONFIG=pkg-config-native \ + CROSS_PKG_CONFIG=pkg-config \ +" + +BAREBOX_CONFIG[doc] = "The barebox kconfig defconfig file. Not used if a file called defconfig is added to the SRC_URI." +BAREBOX_CONFIG ?= "" + +# set sensible default configs for some of oe-core's QEMU MACHINEs +BAREBOX_CONFIG:qemuarm = "multi_v7_defconfig" +BAREBOX_CONFIG:qemuarm64 = "multi_v8_defconfig" +BAREBOX_CONFIG:qemux86-64 = "efi_defconfig" + +# prevent from acting as non-buildable provider +python () { + bareboxconfig = d.getVar('BAREBOX_CONFIG') + bareboxdefconfig = 'file://defconfig' in d.getVar('SRC_URI') + + if not bareboxconfig and not bareboxdefconfig: + raise bb.parse.SkipRecipe("BAREBOX_CONFIG must be set in the %s machine configuration or file://defconfig must be given in SRC_URI." % d.getVar("MACHINE")) +} + +barebox_do_configure() { + if [ -e ${UNPACKDIR}/defconfig ]; then + cp ${UNPACKDIR}/defconfig ${B}/.config + else + if [ -n "${BAREBOX_CONFIG}" ]; then + oe_runmake ${BAREBOX_CONFIG} + else + bbfatal "No defconfig given. Either add file 'file://defconfig' to SRC_URI or set BAREBOX_CONFIG" + fi + fi + + ${S}/scripts/kconfig/merge_config.sh -m .config ${@" ".join(find_cfgs(d))} + cml1_do_configure +} + +BAREBOX_ENV_DIR[doc] = "Overlay the barebox built-in environment with the environment provided by the BSP if specified." +BAREBOX_ENV_DIR ??= "${UNPACKDIR}/env/" + +barebox_do_compile () { + export userccflags="${TARGET_LDFLAGS}${HOST_CC_ARCH}${TOOLCHAIN_OPTIONS}" + unset LDFLAGS + unset CFLAGS + unset CPPFLAGS + unset CXXFLAGS + unset MACHINE + # Allow to use ${UNPACKDIR} in kconfig options to include additionally fetched files + export UNPACKDIR=${UNPACKDIR} + + if [ -d ${BAREBOX_ENV_DIR} ]; then + BAREBOX_DEFAULT_ENV="$(grep ^CONFIG_DEFAULT_ENVIRONMENT_PATH .config | cut -d '=' -f 2 | tr -d '"')" + oe_runmake CONFIG_DEFAULT_ENVIRONMENT_PATH="\"${BAREBOX_DEFAULT_ENV} ${BAREBOX_ENV_DIR}\"" + else + oe_runmake + fi +} + +BAREBOX_BINARY[doc] = "Specify the barebox binary to install. If not specified all barebox artifacts are installed." +BAREBOX_BINARY ??= "${@'barebox.efi' if d.getVar('EFI_PROVIDER') == 'barebox' else ''}" +BAREBOX_SUFFIX[doc] = "Specify the suffix for ${BAREBOX_IMAGE}." +BAREBOX_SUFFIX ??= "img" +BAREBOX_IMAGE[doc] = "A unique barebox image name. Unused if ${BAREBOX_BINARY} is not set." +BAREBOX_IMAGE_DEFAULT ?= "${PN}-${MACHINE}-${PV}-${PR}.${BAREBOX_SUFFIX}" +BAREBOX_IMAGE ?= "${@'${EFI_BOOT_IMAGE}' if d.getVar('EFI_PROVIDER') == 'barebox' else '${BAREBOX_IMAGE_DEFAULT}'}" + +BAREBOX_INSTALL_PATH ?= "${@'${EFI_FILES_PATH}' if d.getVar('EFI_PROVIDER') == 'barebox' else '/boot'}" + +barebox_do_install () { + if [ -n "${BAREBOX_BINARY}" ]; then + + BAREBOX_BIN=${B}/${BAREBOX_BINARY} + if [ ! -f "${BAREBOX_BIN}" ]; then + BAREBOX_BIN=${B}/images/${BAREBOX_BINARY} + fi + if [ ! -f "${BAREBOX_BIN}" ]; then + bbfatal "Failed to locate ${BAREBOX_BINARY}" + fi + + install -D -m 644 ${BAREBOX_BIN} ${D}${BAREBOX_INSTALL_PATH}/${BAREBOX_IMAGE} + ln -sf ${BAREBOX_IMAGE} ${D}${BAREBOX_INSTALL_PATH}/${BAREBOX_BINARY} + else + install -d ${D}${BAREBOX_INSTALL_PATH}/ + for image in $(cat ${B}/barebox-flash-images); do + install -m 644 ${B}/${image} ${D}${BAREBOX_INSTALL_PATH}/ + done + fi +} +FILES:${PN} = "${BAREBOX_INSTALL_PATH}" + +barebox_do_deploy () { + if [ -n "${BAREBOX_BINARY}" ]; then + + BAREBOX_BIN=${B}/${BAREBOX_BINARY} + if [ ! -f "${BAREBOX_BIN}" ]; then + BAREBOX_BIN=${B}/images/${BAREBOX_BINARY} + fi + + install -D -m 644 ${BAREBOX_BIN} ${DEPLOYDIR}/${BAREBOX_IMAGE} + ln -sf ${BAREBOX_IMAGE} ${DEPLOYDIR}/${BAREBOX_BINARY} + else + for image in $(cat ${B}/barebox-flash-images); do + cp ${B}/${image} ${DEPLOYDIR} + done + fi +} +addtask deploy after do_compile + +EXPORT_FUNCTIONS do_configure do_compile do_install do_deploy
meta/conf/distro/include/maintainers.inc +1 -0
@@ -54,6 +54,7 @@ RECIPE_MAINTAINER:pn-automake = "Robert Yang <[email protected]>" RECIPE_MAINTAINER:pn-avahi = "Yi Zhao <[email protected]>" RECIPE_MAINTAINER:pn-babeltrace = "Alexander Kanavin <[email protected]>" RECIPE_MAINTAINER:pn-babeltrace2 = "Alexander Kanavin <[email protected]>" +RECIPE_MAINTAINER:pn-barebox = "Enrico Jörns <[email protected]>" RECIPE_MAINTAINER:pn-baremetal-helloworld = "Alejandro Hernandez <[email protected]>" RECIPE_MAINTAINER:pn-base-files = "Anuj Mittal <[email protected]>" RECIPE_MAINTAINER:pn-base-passwd = "Anuj Mittal <[email protected]>"
meta/recipes-bsp/barebox/barebox_2024.08.0.bb new file +14 -0
@@ -0,0 +1,14 @@ +SUMMARY = "barebox is a bootloader designed for embedded systems. It runs on a variety of architectures including x86, ARM, MIPS, PowerPC and others." +DESCRIPTION = "barebox aims to be a versatile and flexible bootloader not only for booting embedded Linux systems, \ +but also for initial hardware bringup and development. \ +Users should feel right at home with a shell with UNIX-like virtual file system access to hardware, \ +Linux kernel driver API for making driver porting easier, \ +and a subset of the POSIX C library for writing more command-line utilities." +SECTION = "bootloaders" + +LIC_FILES_CHKSUM = "file://COPYING;md5=f5125d13e000b9ca1f0d3364286c4192" + +inherit barebox + +SRC_URI = "https://barebox.org/download/barebox-${PV}.tar.bz2" +SRC_URI[sha256sum] = "b08a762da8d63dd18b4f2d9f5d0a8da001b6e608d1b3eff6dcebc6a2e575d535"
Signature · 1 line
2.39.2
PATCH v6 2/7 barebox-tools: add initial barebox tools support
In reply to Enrico JörnsFrom: Marco Felsch <[email protected]>
Add initial support to build the barebox tools for the host and the target.
Some of the tools are generic barebox utilities (like 'bareboximd' for image meta data inspection or 'bareboxenv' for accessing the barebox environment) some are SoC family-specific specific utilities (like 'imx-usb-loader' or 'omap3-usb-loader').
--- meta/conf/distro/include/maintainers.inc | 1 + .../barebox/barebox-tools_2024.08.0.bb | 59 +++++++++++++++++++ 2 files changed, 60 insertions(+) create mode 100644 meta/recipes-bsp/barebox/barebox-tools_2024.08.0.bb
meta/conf/distro/include/maintainers.inc +1 -0
@@ -55,6 +55,7 @@ RECIPE_MAINTAINER:pn-avahi = "Yi Zhao <[email protected]>" RECIPE_MAINTAINER:pn-babeltrace = "Alexander Kanavin <[email protected]>" RECIPE_MAINTAINER:pn-babeltrace2 = "Alexander Kanavin <[email protected]>" RECIPE_MAINTAINER:pn-barebox = "Enrico Jörns <[email protected]>" +RECIPE_MAINTAINER:pn-barebox-tools = "Enrico Jörns <[email protected]>" RECIPE_MAINTAINER:pn-baremetal-helloworld = "Alejandro Hernandez <[email protected]>" RECIPE_MAINTAINER:pn-base-files = "Anuj Mittal <[email protected]>" RECIPE_MAINTAINER:pn-base-passwd = "Anuj Mittal <[email protected]>"
meta/recipes-bsp/barebox/barebox-tools_2024.08.0.bb new file +59 -0
59 lines not on this page · raw message
Signature · 1 line
2.39.2
PATCH v6 3/7 barebox: set default BAREBOX_CONFIG for qemu machines
In reply to Enrico JörnsFrom: Enrico Jorns <[email protected]>
These are set in the barebox recipe rather in the corresponding machines (where they would belong otherwise) to keep the impact of barebox to oe-core minimal for now.
"multi_v7_defconfig" is used for qemuarm since this is the default barebox armv7 config that just enables all supported platforms.
"multi_v8_defconfig" is used for qemuarm64 sine this is the default barebox armv8 config that just enables all supported platforms.
"efi_defconfig" is used for qemux86-64 which is the primary platform where barebox will not be the first stage bootloader but an EFI payload.
Since these changes make barebox a provider for virtual/bootloader, explicitly default to u-boot in the corresponding MACHINE configs to not unnecessarily surprise users.
--- meta/conf/machine/qemuarm.conf | 1 + meta/conf/machine/qemuarm64.conf | 1 + meta/conf/machine/qemux86-64.conf | 1 + 3 files changed, 3 insertions(+)
meta/conf/machine/qemuarm.conf +1 -0
@@ -7,6 +7,7 @@ require conf/machine/include/qemu.inc KERNEL_IMAGETYPE = "zImage" +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot" UBOOT_MACHINE ?= "qemu_arm_defconfig" SERIAL_CONSOLES ?= "115200;ttyAMA0 115200;hvc0"
meta/conf/machine/qemuarm64.conf +1 -0
@@ -7,6 +7,7 @@ require conf/machine/include/qemu.inc KERNEL_IMAGETYPE = "Image" +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot" UBOOT_MACHINE ?= "qemu_arm64_defconfig" SERIAL_CONSOLES ?= "115200;ttyAMA0 115200;hvc0"
meta/conf/machine/qemux86-64.conf +1 -0
@@ -13,6 +13,7 @@ DEFAULTTUNE ?= "core2-64" require conf/machine/include/x86/tune-x86-64-v3.inc require conf/machine/include/x86/qemuboot-x86.inc +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot" UBOOT_MACHINE ?= "qemu-x86_64_defconfig" KERNEL_IMAGETYPE = "bzImage"
Signature · 1 line
2.39.2
Re: [OE-core] [PATCH v6 3/7] barebox: set default BAREBOX_CONFIG for qemu machines
Quoted 19 lines · Enrico Jörns via lists.openembedded.org
From: Enrico Jorns <[email protected]>
These are set in the barebox recipe rather in the corresponding machines (where they would belong otherwise) to keep the impact of barebox to oe-core minimal for now.
"
multi_v7_defconfig" is used for qemuarm since this is the default barebox armv7 config that just enables all supported platforms."
multi_v8_defconfig" is used for qemuarm64 sine this is the default barebox armv8 config that just enables all supported platforms."
efi_defconfig" is used for qemux86-64 which is the primary platform where barebox will not be the first stage bootloader but an EFI payload.Since these changes make barebox a provider for virtual/bootloader, explicitly default to u-boot in the corresponding MACHINE configs to not unnecessarily surprise users.
Quoted 6 lines
Signed-off-by Enrico Jorns <[email protected]>---
meta/conf/machine/qemuarm.conf | 1 +
meta/conf/machine/qemuarm64.conf | 1 +
meta/conf/machine/qemux86-64.conf | 1 +3 files changed, 3 insertions(+)
This patch needs the commit message updating as it no longer matches the changes below!
Things did pass in automated testing so I think we're close with this.
Cheers,
Richard
Quoted 45 lines
meta/conf/machine/qemuarm.conf +0
-0@@ -7,6 +7,7 @@ require conf/machine/include/qemu.inc
KERNEL_IMAGETYPE = "zImage"
+PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot"UBOOT_MACHINE?= "qemu_arm_defconfig"
SERIAL_CONSOLES ?= "115200;ttyAMA0 115200;hvc0"meta/conf/machine/qemuarm64.conf +0
-0@@ -7,6 +7,7 @@ require conf/machine/include/qemu.inc
KERNEL_IMAGETYPE = "Image"
+PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot"UBOOT_MACHINE?= "qemu_arm64_defconfig"
SERIAL_CONSOLES ?= "115200;ttyAMA0 115200;hvc0"meta/conf/machine/qemux86-64.conf +0
-0@@ -13,6 +13,7 @@ DEFAULTTUNE ?= "core2-64"require conf/machine/include/x86/tune-x86-64-v3.inc require conf/machine/include/x86/qemuboot-x86.inc
+PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot"UBOOT_MACHINE?= "qemu-x86_64_defconfig"
KERNEL_IMAGETYPE = "bzImage"-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#204432): https://lists.openembedded.org/g/openembedded-core/message/204432
Mute This Topic: https://lists.openembedded.org/mt/108410146/1686473
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH v6 3/7] barebox: set default BAREBOX_CONFIG for qemu machines
In reply to Enrico JörnsQuoted 19 lines · Enrico Jörns via lists.openembedded.org
From: Enrico Jorns <[email protected]>
These are set in the barebox recipe rather in the corresponding machines (where they would belong otherwise) to keep the impact of barebox to oe-core minimal for now.
"
multi_v7_defconfig" is used for qemuarm since this is the default barebox armv7 config that just enables all supported platforms."
multi_v8_defconfig" is used for qemuarm64 sine this is the default barebox armv8 config that just enables all supported platforms."
efi_defconfig" is used for qemux86-64 which is the primary platform where barebox will not be the first stage bootloader but an EFI payload.Since these changes make barebox a provider for virtual/bootloader, explicitly default to u-boot in the corresponding MACHINE configs to not unnecessarily surprise users.
Quoted 6 lines
Signed-off-by Enrico Jorns <[email protected]>---
meta/conf/machine/qemuarm.conf | 1 +
meta/conf/machine/qemuarm64.conf | 1 +
meta/conf/machine/qemux86-64.conf | 1 +3 files changed, 3 insertions(+)
This patch needs the commit message updating as it no longer matches the changes below!
Things did pass in automated testing so I think we're close with this.
Cheers,
Richard
Quoted 45 lines
meta/conf/machine/qemuarm.conf +0
-0@@ -7,6 +7,7 @@ require conf/machine/include/qemu.inc
KERNEL_IMAGETYPE = "zImage"
+PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot"UBOOT_MACHINE?= "qemu_arm_defconfig"
SERIAL_CONSOLES ?= "115200;ttyAMA0 115200;hvc0"meta/conf/machine/qemuarm64.conf +0
-0@@ -7,6 +7,7 @@ require conf/machine/include/qemu.inc
KERNEL_IMAGETYPE = "Image"
+PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot"UBOOT_MACHINE?= "qemu_arm64_defconfig"
SERIAL_CONSOLES ?= "115200;ttyAMA0 115200;hvc0"meta/conf/machine/qemux86-64.conf +0
-0@@ -13,6 +13,7 @@ DEFAULTTUNE ?= "core2-64"require conf/machine/include/x86/tune-x86-64-v3.inc require conf/machine/include/x86/qemuboot-x86.inc
+PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot"UBOOT_MACHINE?= "qemu-x86_64_defconfig"
KERNEL_IMAGETYPE = "bzImage"-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#204432): https://lists.openembedded.org/g/openembedded-core/message/204432
Mute This Topic: https://lists.openembedded.org/mt/108410146/1686473
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH v6 3/7] barebox: set default BAREBOX_CONFIG for qemu machines
Am Freitag, dem 11.10.2024 um 12:08 +0100 schrieb Richard Purdie:
Quoted 27 lines · Enrico Jörns via lists.openembedded.org
Quoted 19 lines
From: Enrico Jorns <[email protected]>
These are set in the barebox recipe rather in the corresponding machines (where they would belong otherwise) to keep the impact of barebox to oe-core minimal for now.
"
multi_v7_defconfig" is used for qemuarm since this is the default barebox armv7 config that just enables all supported platforms."
multi_v8_defconfig" is used for qemuarm64 sine this is the default barebox armv8 config that just enables all supported platforms."
efi_defconfig" is used for qemux86-64 which is the primary platform where barebox will not be the first stage bootloader but an EFI payload.Since these changes make barebox a provider for virtual/bootloader, explicitly default to u-boot in the corresponding MACHINE configs to not unnecessarily surprise users.
Quoted 6 lines
Signed-off-by Enrico Jorns <[email protected]>---
meta/conf/machine/qemuarm.conf | 1 +
meta/conf/machine/qemuarm64.conf | 1 +
meta/conf/machine/qemux86-64.conf | 1 +3 files changed, 3 insertions(+)
Quoted 2 lines
This patch needs the commit message updating as it no longer matches the changes below!
Indeed. This hunk accidentally moved to "barebox: add initial support" when merging the .inc and the .bb file.
I'd simply restore the original split so that the commit messages matches again and we preserve the explicit explanation of defconfigs that Alex requested.
Quoted 1 line
Things did pass in automated testing so I think we're close with this.
This sounds really, really great!
Thanks a lot for your effort!
Regards, Enrico
Quoted 52 lines
Cheers,
Richard
Quoted 46 lines
meta/conf/machine/qemuarm.conf +0
-0@@ -7,6 +7,7 @@ require conf/machine/include/qemu.inc
KERNEL_IMAGETYPE = "zImage"
+PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot"UBOOT_MACHINE?= "qemu_arm_defconfig"
SERIAL_CONSOLES ?= "115200;ttyAMA0 115200;hvc0"meta/conf/machine/qemuarm64.conf +0
-0@@ -7,6 +7,7 @@ require conf/machine/include/qemu.inc
KERNEL_IMAGETYPE = "Image"
+PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot"UBOOT_MACHINE?= "qemu_arm64_defconfig"
SERIAL_CONSOLES ?= "115200;ttyAMA0 115200;hvc0"meta/conf/machine/qemux86-64.conf +0
-0@@ -13,6 +13,7 @@ DEFAULTTUNE ?= "core2-64"require conf/machine/include/x86/tune-x86-64-v3.inc require conf/machine/include/x86/qemuboot-x86.inc
+PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot"UBOOT_MACHINE?= "qemu-x86_64_defconfig"
KERNEL_IMAGETYPE = "bzImage"-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#204432): https://lists.openembedded.org/g/openembedded-core/message/204432
Mute This Topic: https://lists.openembedded.org/mt/108410146/1686473
Group Owner: [email protected]
Unsubscribe:
https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Signature · 4 lines
Pengutronix e.K. | Enrico Jörns | Embedded Linux Consulting & Support | https://www.pengutronix.de/ | Steuerwalder Str. 21 | Phone: +49-5121-206917-180 | 31137 Hildesheim, Germany | Fax: +49-5121-206917-9 |
PATCH v6 4/7 oeqa/utils/qemurunner: support ignoring vt100 escape sequences
In reply to Enrico JörnsFrom: Enrico Jorns <[email protected]>
If we talk to terminals that like colors, we need to ignore the vt100 escape sequences when matching strings.
An unprocessed barebox console prompt would e.g. look like:
ESC[1;32mbarebox@ESC[1;36mARM QEMU virt64:/ESC[0m
where we cannot match for something like "barebox@ARM QEMU virt64:/". The same applies to colored Linux terminal output of course.
The "\x1b\[" from the regex catches the standard start of ANSI escape sequence while the rest catches the actual command code executed.
--- meta/lib/oeqa/utils/qemurunner.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
meta/lib/oeqa/utils/qemurunner.py +3 -1
@@ -30,6 +30,8 @@ control_range = list(range(0,32))+list(range(127,160)) control_chars = [chr(x) for x in control_range if chr(x) not in string.printable] re_control_char = re.compile('[%s]' % re.escape("".join(control_chars))) +# Regex to remove the ANSI (color) control codes from console strings in order to match the text only +re_vt100 = re.compile(r'(\x1b\[|\x9b)[^@-_a-z]*[@-_a-z]|\x1b[@-_a-z]') def getOutput(o): import fcntl
@@ -681,7 +683,7 @@ class QemuRunner: time.sleep(0.1) answer = self.server_socket.recv(1024) if answer: - data += answer.decode('utf-8') + data += re_vt100.sub("", answer.decode('utf-8')) # Search the prompt to stop if re.search(self.boot_patterns['search_cmd_finished'], data): break
Signature · 1 line
2.39.2
PATCH v6 5/7 oeqa: support passing custom boot patterns to runqemu
In reply to Enrico JörnsFrom: Enrico Jorns <[email protected]>
This allows defining non-standard patterns from QEMU tests just as they are already supported by the testimage.bbclass.
Will allow testing non-Linux shells in QEMU, too (e.g. a U-Boot shell or another bootloader shell).
--- meta/lib/oeqa/targetcontrol.py | 5 +++-- meta/lib/oeqa/utils/commands.py | 5 +++-- meta/lib/oeqa/utils/qemurunner.py | 2 +- 3 files changed, 7 insertions(+), 5 deletions(-)
meta/lib/oeqa/targetcontrol.py +3 -2
@@ -88,7 +88,7 @@ class QemuTarget(BaseTarget): supported_image_fstypes = ['ext3', 'ext4', 'cpio.gz', 'wic'] - def __init__(self, d, logger, image_fstype=None): + def __init__(self, d, logger, image_fstype=None, boot_patterns=None): import oe.types
@@ -141,7 +141,8 @@ class QemuTarget(BaseTarget): dump_dir = dump_dir, logger = logger, tmpfsdir = d.getVar("RUNQEMU_TMPFS_DIR"), - serial_ports = len(d.getVar("SERIAL_CONSOLES").split())) + serial_ports = len(d.getVar("SERIAL_CONSOLES").split()), + boot_patterns = boot_patterns) self.monitor_dumper = MonitorDumper(dump_monitor_cmds, dump_dir, self.runner) if (self.monitor_dumper):
meta/lib/oeqa/utils/commands.py +3 -2
@@ -312,7 +312,7 @@ def create_temp_layer(templayerdir, templayername, priority=999, recipepathspec= f.write('LAYERSERIES_COMPAT_%s = "%s"\n' % (templayername, corenames)) @contextlib.contextmanager -def runqemu(pn, ssh=True, runqemuparams='', image_fstype=None, launch_cmd=None, qemuparams=None, overrides={}, discard_writes=True): +def runqemu(pn, ssh=True, runqemuparams='', image_fstype=None, launch_cmd=None, qemuparams=None, overrides={}, boot_patterns = {}, discard_writes=True): """ Starts a context manager for a 'oeqa.targetcontrol.QemuTarget' resource. The underlying Qemu will be booted into a shell when the generator yields
@@ -330,6 +330,7 @@ def runqemu(pn, ssh=True, runqemuparams='', image_fstype=None, launch_cmd=None, image_fstype (str): IMAGE_FSTYPE to use launch_cmd (str): directly run this command and bypass automatic runqemu parameter generation overrides (dict): dict of "'<bitbake-variable>': value" pairs that allows overriding bitbake variables + boot_patterns (dict): dict of "'<pattern-name>': value" pairs to override default boot patterns, e.g. when not booting Linux discard_writes (boolean): enables qemu -snapshot feature to prevent modifying original image """
@@ -361,7 +362,7 @@ def runqemu(pn, ssh=True, runqemuparams='', image_fstype=None, launch_cmd=None, logdir = recipedata.getVar("TEST_LOG_DIR") - qemu = oeqa.targetcontrol.QemuTarget(recipedata, targetlogger, image_fstype) + qemu = oeqa.targetcontrol.QemuTarget(recipedata, targetlogger, image_fstype, boot_patterns=boot_patterns) finally: # We need to shut down tinfoil early here in case we actually want # to run tinfoil-using utilities with the running QEMU instance.
meta/lib/oeqa/utils/qemurunner.py +1 -1
@@ -103,7 +103,7 @@ class QemuRunner: # Only override patterns that were set e.g. login user TESTIMAGE_BOOT_PATTERNS[send_login_user] = "webserver\n" for pattern in accepted_patterns: - if not self.boot_patterns[pattern]: + if pattern not in self.boot_patterns or not self.boot_patterns[pattern]: self.boot_patterns[pattern] = default_boot_patterns[pattern] def create_socket(self):
Signature · 1 line
2.39.2
PATCH v6 6/7 oeqa/selftest/cases: add basic u-boot test
In reply to Enrico JörnsFrom: Enrico Jorns <[email protected]>
This adds basic tests for qemuarm and qemuarm64.
--- meta/lib/oeqa/selftest/cases/uboot.py | 42 +++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 meta/lib/oeqa/selftest/cases/uboot.py
meta/lib/oeqa/selftest/cases/uboot.py new file +42 -0
@@ -0,0 +1,42 @@ +# Qemu-based u-boot bootloader integration testing +# +# Copyright OpenEmbedded Contributors +# +# SPDX-License-Identifier: MIT +# + +from oeqa.selftest.case import OESelftestTestCase +from oeqa.utils.commands import bitbake, runqemu +from oeqa.core.decorator.data import skipIfNotArch +from oeqa.core.decorator import OETestTag + +uboot_boot_patterns = { + 'search_reached_prompt': "stop autoboot", + 'search_login_succeeded': "=>", + 'search_cmd_finished': "=>" + } + + +class UBootTest(OESelftestTestCase): + + @skipIfNotArch(['arm', 'aarch64']) + @OETestTag("runqemu") + def test_boot_uboot(self): + """ + Tests building u-boot and booting it with QEMU + """ + + self.write_config(""" +QB_DEFAULT_BIOS = "u-boot.bin" +PREFERRED_PROVIDER_virtual/bootloader = "u-boot" +""") + bitbake("virtual/bootloader core-image-minimal") + + with runqemu('core-image-minimal', ssh=False, runqemuparams='nographic', + boot_patterns=uboot_boot_patterns) as qemu: + + # test if u-boot console works + cmd = "version" + status, output = qemu.run_serial(cmd) + self.assertEqual(status, 1, msg=output) + self.assertTrue("U-Boot" in output, msg=output)
Signature · 1 line
2.39.2
PATCH v6 7/7 oeqa/selftest/cases: add basic barebox tests
In reply to Enrico JörnsFrom: Enrico Jorns <[email protected]>
This adds basic tests for qemuarm and qemuarm64.
--- meta/lib/oeqa/selftest/cases/barebox.py | 43 +++++++++++++++++++++++++ 1 file changed, 43 insertions(+) create mode 100644 meta/lib/oeqa/selftest/cases/barebox.py
meta/lib/oeqa/selftest/cases/barebox.py new file +43 -0
@@ -0,0 +1,43 @@ +# Qemu-based barebox bootloader integration testing +# +# Copyright OpenEmbedded Contributors +# +# SPDX-License-Identifier: MIT +# + +from oeqa.selftest.case import OESelftestTestCase +from oeqa.utils.commands import bitbake, runqemu +from oeqa.core.decorator.data import skipIfNotArch +from oeqa.core.decorator import OETestTag + +barebox_boot_patterns = { + 'search_reached_prompt': r"stop autoboot", + 'search_login_succeeded': r"barebox@[^:]+:[^ ]+ ", + 'search_cmd_finished': r"barebox@[a-zA-Z0-9\-\s]+:/" + } + + +class BareboxTest(OESelftestTestCase): + + @skipIfNotArch(['arm', 'aarch64']) + @OETestTag("runqemu") + def test_boot_barebox(self): + """ + Tests building barebox and booting it with QEMU + """ + + self.write_config(""" +QB_DEFAULT_KERNEL = "barebox-dt-2nd.img" +PREFERRED_PROVIDER_virtual/bootloader = "barebox" +""") + + bitbake("virtual/bootloader core-image-minimal") + + with runqemu('core-image-minimal', ssh=False, runqemuparams='nographic', + boot_patterns=barebox_boot_patterns) as qemu: + + # test if barebox console works + cmd = "version" + status, output = qemu.run_serial(cmd) + self.assertEqual(status, 1, msg=output) + self.assertTrue("barebox" in output, msg=output)
Signature · 1 line
2.39.2
Quoted 17 lines · Enrico Jörns via lists.openembedded.org
This adds support for the barebox bootloader (and tools) to oe-core.
In order to have proper testing, this extends oe-selftest to allow basic testing of bootloaders. While at it, cover both u-boot and barebox.
v6:
* replace barebox.inc by barebox.bbclass (move content of barebox-common.inc into .bbclass and .bb files)
* support for UNPACKDIREnrico Jorns (5):
barebox: set defaultBAREBOX_CONFIGfor qemu machines oeqa/utils/qemurunner: support ignoring vt100 escape sequences
oeqa: support passing custom boot patterns to runqemu oeqa/selftest/cases: add basic u-boot test oeqa/selftest/cases: add basic barebox tests
Quoted 3 lines
Marco Felsch (2):
barebox: add initial support
barebox-tools: add initial barebox tools support
We had some testing capacity so I ran this through automated testing. The one issue that showed up so far was:
https://valkyrie.yoctoproject.org/#/builders/29/builds/174/steps/13/logs/warnings
which is at least easily fixed! The rest of the build is still going.
Cheers,
Richard
Hi Richard,
Am Mittwoch, dem 18.09.2024 um 11:11 +0100 schrieb Richard Purdie:
Quoted 22 lines · Enrico Jörns via lists.openembedded.org
Quoted 17 lines
This adds support for the barebox bootloader (and tools) to oe-core.
In order to have proper testing, this extends oe-selftest to allow basic testing of bootloaders. While at it, cover both u-boot and barebox.
v6:
* replace barebox.inc by barebox.bbclass (move content of barebox-common.inc into .bbclass and .bb files)
* support for UNPACKDIREnrico Jorns (5):
barebox: set defaultBAREBOX_CONFIGfor qemu machines oeqa/utils/qemurunner: support ignoring vt100 escape sequences
oeqa: support passing custom boot patterns to runqemu oeqa/selftest/cases: add basic u-boot test oeqa/selftest/cases: add basic barebox testsQuoted 3 lines
Marco Felsch (2):
barebox: add initial support
barebox-tools: add initial barebox tools support
Quoted 6 lines
We had some testing capacity so I ran this through automated testing. The one issue that showed up so far was:
https://valkyrie.yoctoproject.org/#/builders/29/builds/174/steps/13/logs/warnings
which is at least easily fixed! The rest of the build is still going.
thanks for the test run and the first result.
Indeed, looks easily fixable 😉
Is it worth a v7 or should I wait for other results to show up?
Regards, Enrico
Quoted 4 lines
Cheers,
Richard
Signature · 4 lines
Pengutronix e.K. | Enrico Jörns | Embedded Linux Consulting & Support | https://www.pengutronix.de/ | Steuerwalder Str. 21 | Phone: +49-5121-206917-180 | 31137 Hildesheim, Germany | Fax: +49-5121-206917-9 |
Quoted 35 lines · Enrico Jörns
Hi Richard,
Am Mittwoch, dem 18.09.2024 um 11:11 +0100 schrieb Richard Purdie:
Quoted 32 lines
Quoted 20 lines · Enrico Jörns via lists.openembedded.org
This adds support for the barebox bootloader (and tools) to oe- core.
In order to have proper testing, this extends oe-selftest to allow
basic testing of bootloaders. While at it, cover both u-boot and barebox.v6:
* replace barebox.inc by barebox.bbclass (move content of barebox-common.inc into .bbclass and .bb files)
* support for UNPACKDIREnrico Jorns (5):
barebox: set defaultBAREBOX_CONFIGfor qemu machines oeqa/utils/qemurunner: support ignoring vt100 escape sequences
oeqa: support passing custom boot patterns to runqemu oeqa/selftest/cases: add basic u-boot test oeqa/selftest/cases: add basic barebox testsQuoted 3 lines
Marco Felsch (2):
barebox: add initial support
barebox-tools: add initial barebox tools supportWe had some testing capacity so I ran this through automated testing.
The one issue that showed up so far was:https://valkyrie.yoctoproject.org/#/builders/29/builds/174/steps/13/logs/warnings
Quoted 7 lines
Quoted 2 lines
which is at least easily fixed! The rest of the build is still going.
thanks for the test run and the first result.
Indeed, looks easily fixable 😉
Is it worth a v7 or should I wait for other results to show up?
Most of the tests have run and there were other issues in the build but there was one other issue I noticed:
https://valkyrie.yoctoproject.org/#/builders/54/builds/149/steps/14/logs/stdio
which is a missing maintainers entry. Probably worth a v7 with those two things fixed.
Cheers,
Richard
Am Mittwoch, dem 18.09.2024 um 12:21 +0100 schrieb Richard Purdie:
Quoted 44 lines · Enrico Jörns
Quoted 35 lines
Hi Richard,
Am Mittwoch, dem 18.09.2024 um 11:11 +0100 schrieb Richard Purdie:
Quoted 32 lines
Quoted 20 lines · Enrico Jörns via lists.openembedded.org
This adds support for the barebox bootloader (and tools) to oe- core.
In order to have proper testing, this extends oe-selftest to allow
basic testing of bootloaders. While at it, cover both u-boot and barebox.v6:
* replace barebox.inc by barebox.bbclass (move content of barebox-common.inc into .bbclass and .bb files)
* support for UNPACKDIREnrico Jorns (5):
barebox: set defaultBAREBOX_CONFIGfor qemu machines oeqa/utils/qemurunner: support ignoring vt100 escape sequences
oeqa: support passing custom boot patterns to runqemu oeqa/selftest/cases: add basic u-boot test oeqa/selftest/cases: add basic barebox testsQuoted 3 lines
Marco Felsch (2):
barebox: add initial support
barebox-tools: add initial barebox tools supportWe had some testing capacity so I ran this through automated testing.
The one issue that showed up so far was:https://valkyrie.yoctoproject.org/#/builders/29/builds/174/steps/13/logs/warnings
Quoted 7 lines
Quoted 2 lines
which is at least easily fixed! The rest of the build is still going.
thanks for the test run and the first result.
Indeed, looks easily fixable 😉
Is it worth a v7 or should I wait for other results to show up?
Quoted 7 lines
Most of the tests have run and there were other issues in the build but there was one other issue I noticed:
https://valkyrie.yoctoproject.org/#/builders/54/builds/149/steps/14/logs/stdio
which is a missing maintainers entry. Probably worth a v7 with those two things fixed.
The test output says
Quoted 2 lines
Unable to find recipes for the following entries in maintainers.inc:
barebox
Could you give me a hint what that means? The barebox_2024.08.0.bb and the change in maintainers.inc are in the same commit. So I am unsure why it does not find the recipe.
Thanks in advance and regards
Enrico
Quoted 4 lines
Cheers,
Richard
Signature · 4 lines
Pengutronix e.K. | Enrico Jörns | Embedded Linux Consulting & Support | https://www.pengutronix.de/ | Steuerwalder Str. 21 | Phone: +49-5121-206917-180 | 31137 Hildesheim, Germany | Fax: +49-5121-206917-9 |
Quoted 61 lines · Enrico Jörns
Am Mittwoch, dem 18.09.2024 um 12:21 +0100 schrieb Richard Purdie:
Quoted 52 lines · Enrico Jörns
Quoted 39 lines
Hi Richard,
Am Mittwoch, dem 18.09.2024 um 11:11 +0100 schrieb Richard Purdie:
Quoted 35 lines
Quoted 23 lines · Enrico Jörns via lists.openembedded.org
This adds support for the barebox bootloader (and tools) to oe-
core.In order to have proper testing, this extends oe-selftest to allow
basic testing of bootloaders. While at it, cover both u-boot and
barebox.v6:
* replace barebox.inc by barebox.bbclass (move content of barebox-common.inc into .bbclass and .bb files)
* support for UNPACKDIREnrico Jorns (5):
barebox: set defaultBAREBOX_CONFIGfor qemu machines oeqa/utils/qemurunner: support ignoring vt100 escape sequences
oeqa: support passing custom boot patterns to runqemu oeqa/selftest/cases: add basic u-boot test oeqa/selftest/cases: add basic barebox testsQuoted 3 lines
Marco Felsch (2):
barebox: add initial support
barebox-tools: add initial barebox tools supportWe had some testing capacity so I ran this through automated testing.
The one issue that showed up so far was:https://valkyrie.yoctoproject.org/#/builders/29/builds/174/steps/13/logs/warnings
Quoted 7 lines
Quoted 2 lines
which is at least easily fixed! The rest of the build is still going.
thanks for the test run and the first result.
Indeed, looks easily fixable 😉
Is it worth a v7 or should I wait for other results to show up?Most of the tests have run and there were other issues in the build but
there was one other issue I noticed:Quoted 5 lines
https://valkyrie.yoctoproject.org/#/builders/54/builds/149/steps/14/logs/stdio
which is a missing maintainers entry. Probably worth a v7 with those
two things fixed.The test output says
Quoted 8 lines
Quoted 3 lines
Unable to find recipes for the following entries in maintainers.inc:
bareboxCould you give me a hint what that means? The barebox_2024.08.0.bb and the change in maintainers.inc
are in the same commit. So I am unsure why it does not find the recipe.
It means the recipe is being skipped in the context of the QA test. This means there is a maintainers entry but the test can't see any recipe to match against it due to the skip.
The test is there to ensure when we delete recipes, we don't have stale entries in the file.
Can we provide a config that makes sense for qemux86-64?
Cheers,
Richard
Am Mittwoch, dem 18.09.2024 um 22:37 +0100 schrieb Richard Purdie:
Quoted 66 lines · Enrico Jörns
Quoted 65 lines
Am Mittwoch, dem 18.09.2024 um 12:21 +0100 schrieb Richard Purdie:
Quoted 52 lines · Enrico Jörns
Quoted 39 lines
Hi Richard,
Am Mittwoch, dem 18.09.2024 um 11:11 +0100 schrieb Richard Purdie:
Quoted 35 lines
Quoted 23 lines · Enrico Jörns via lists.openembedded.org
This adds support for the barebox bootloader (and tools) to oe-
core.In order to have proper testing, this extends oe-selftest to allow
basic testing of bootloaders. While at it, cover both u-boot and
barebox.v6:
* replace barebox.inc by barebox.bbclass (move content of barebox-common.inc into .bbclass and .bb files)
* support for UNPACKDIREnrico Jorns (5):
barebox: set defaultBAREBOX_CONFIGfor qemu machines oeqa/utils/qemurunner: support ignoring vt100 escape sequences
oeqa: support passing custom boot patterns to runqemu oeqa/selftest/cases: add basic u-boot test oeqa/selftest/cases: add basic barebox testsQuoted 3 lines
Marco Felsch (2):
barebox: add initial support
barebox-tools: add initial barebox tools supportWe had some testing capacity so I ran this through automated testing.
The one issue that showed up so far was:https://valkyrie.yoctoproject.org/#/builders/29/builds/174/steps/13/logs/warnings
Quoted 7 lines
Quoted 2 lines
which is at least easily fixed! The rest of the build is still going.
thanks for the test run and the first result.
Indeed, looks easily fixable 😉
Is it worth a v7 or should I wait for other results to show up?Most of the tests have run and there were other issues in the build but
there was one other issue I noticed:Quoted 5 lines
https://valkyrie.yoctoproject.org/#/builders/54/builds/149/steps/14/logs/stdio
which is a missing maintainers entry. Probably worth a v7 with those
two things fixed.The test output says
Quoted 3 lines
Unable to find recipes for the following entries in maintainers.inc:
barebox
Quoted 8 lines
Quoted 4 lines
Could you give me a hint what that means? The barebox_2024.08.0.bb and the change in maintainers.inc
are in the same commit. So I am unsure why it does not find the recipe.It means the recipe is being skipped in the context of the QA test. This means there is a maintainers entry but the test can't see any recipe to match against it due to the skip.
Thanks. I was not sure if the recipes are just evaluated and skipped based on normal bitbake parsing or if there is a special mechanism that just looks for .bb files.
Quoted 4 lines
The test is there to ensure when we delete recipes, we don't have stale entries in the file.
Can we provide a config that makes sense for qemux86-64?
The reason it is skipped from default parsing is
PREFERRED_PROVIDER_virtual/bootloader = "u-boot"
I put in meta/conf/machine/qemux86-64.conf since we have two competing providers of virtaul/bootloader now (and that's what the mechanism is actually made for I guess 😉).
Not sure if there is a way to remove the provider for just that check?
Or should I add it to the exception list in distrodata.py like its done for similar other recipes that have competing providers (e.g. musl, newlib for virtual/libc; linux-yocto, linux-dummy for virtual/kernel)?.
Regards, Enrico
Quoted 6 lines
Cheers,
Richard
Signature · 4 lines
Pengutronix e.K. | Enrico Jörns | Embedded Linux Consulting & Support | https://www.pengutronix.de/ | Steuerwalder Str. 21 | Phone: +49-5121-206917-180 | 31137 Hildesheim, Germany | Fax: +49-5121-206917-9 |
Quoted 88 lines · Enrico Jörns
Am Mittwoch, dem 18.09.2024 um 22:37 +0100 schrieb Richard Purdie:
Quoted 66 lines · Enrico Jörns
Quoted 65 lines
Am Mittwoch, dem 18.09.2024 um 12:21 +0100 schrieb Richard Purdie:
Quoted 52 lines · Enrico Jörns
Quoted 39 lines
Hi Richard,
Am Mittwoch, dem 18.09.2024 um 11:11 +0100 schrieb Richard Purdie:
Quoted 35 lines
Quoted 23 lines · Enrico Jörns via lists.openembedded.org
This adds support for the barebox bootloader (and tools) to oe-
core.In order to have proper testing, this extends oe-selftest to allow
basic testing of bootloaders. While at it, cover both u-boot and
barebox.v6:
* replace barebox.inc by barebox.bbclass (move content of barebox-common.inc into .bbclass and .bb files)
* support for UNPACKDIREnrico Jorns (5):
barebox: set defaultBAREBOX_CONFIGfor qemu machines oeqa/utils/qemurunner: support ignoring vt100 escape sequences
oeqa: support passing custom boot patterns to runqemu oeqa/selftest/cases: add basic u-boot test oeqa/selftest/cases: add basic barebox testsQuoted 3 lines
Marco Felsch (2):
barebox: add initial support
barebox-tools: add initial barebox tools supportWe had some testing capacity so I ran this through automated testing.
The one issue that showed up so far was:https://valkyrie.yoctoproject.org/#/builders/29/builds/174/steps/13/logs/warnings
Quoted 7 lines
Quoted 2 lines
which is at least easily fixed! The rest of the build is still going.
thanks for the test run and the first result.
Indeed, looks easily fixable 😉
Is it worth a v7 or should I wait for other results to show up?Most of the tests have run and there were other issues in the build but
there was one other issue I noticed:Quoted 5 lines
https://valkyrie.yoctoproject.org/#/builders/54/builds/149/steps/14/logs/stdio
which is a missing maintainers entry. Probably worth a v7 with those
two things fixed.The test output says
Quoted 3 lines
Unable to find recipes for the following entries in maintainers.inc:
bareboxQuoted 8 lines
Quoted 4 lines
Could you give me a hint what that means? The barebox_2024.08.0.bb and the change in maintainers.inc
are in the same commit. So I am unsure why it does not find the recipe.It means the recipe is being skipped in the context of the QA test. This means there is a maintainers entry but the test can't see any recipe to match against it due to the skip.
Thanks. I was not sure if the recipes are just evaluated and skipped based on normal bitbake parsing or if there is a special mechanism that just looks for .bb files.
Quoted 4 lines
The test is there to ensure when we delete recipes, we don't have stale entries in the file.
Can we provide a config that makes sense for qemux86-64?
The reason it is skipped from default parsing is
PREFERRED_PROVIDER_virtual/bootloader = "u-boot"
Quoted 8 lines
I put in
meta/conf/machine/qemux86-64.confsince we have two competing providers of virtaul/bootloader now (and that's what the mechanism is actually made for I guess 😉).Not sure if there is a way to remove the provider for just that check?
Or should I add it to the exception list in
distrodata.pylike its done for similar other recipes that have competing providers (e.g. musl, newlib for virtual/libc; linux-yocto, linux-dummy for virtual/kernel)?.
I think it will just have to go into the exception list. We really need to find a better way to do this but you're right, that is how we're doing it for the other cases.
Cheers,
Richard