beaglebone-yocto: prefer u-boot
PATCH 1/2 beaglebone-yocto: prefer u-boot
If BBLAYERS contains a layer providing a package for virtual/bootloader, building for the beaglebone-yocto machine will fail. Setting u-boot as the preferred provider for virtual/bootloader ensures u-boot is choosen and the build succeeds.
--- meta-yocto-bsp/conf/machine/beaglebone-yocto.conf | 2 ++ 1 file changed, 2 insertions(+)
meta-yocto-bsp/conf/machine/beaglebone-yocto.conf +2 -0
@@ -30,6 +30,8 @@ KERNEL_IMAGETYPE = "zImage" KERNEL_DEVICETREE = "am335x-bone.dtb am335x-boneblack.dtb am335x-bonegreen.dtb" KERNEL_EXTRA_ARGS += "LOADADDR=${UBOOT_ENTRYPOINT}" +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot" + SPL_BINARY = "MLO" UBOOT_SUFFIX = "img" UBOOT_MACHINE = "am335x_evm_defconfig"
Signature · 1 line
2.34.1
PATCH 2/2 beaglebone-yocto: move kernel and dtb to packagegroup-core-boot
Appending IMAGE_INSTALL with the kernel and device tree is a bad idea because it will bring these packages to every images, like a container image or sysroot image to pivot to, where the kernel artifacts are not wanted.
Instead use the MACHINE_ESSENTIAL_EXTRA_RDEPENDS which results in having the kernel artifacts where they should be, part of packagegroup-core-boot.
--- meta-yocto-bsp/conf/machine/beaglebone-yocto.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta-yocto-bsp/conf/machine/beaglebone-yocto.conf +1 -1
@@ -17,7 +17,7 @@ include conf/machine/include/arm/armv7a/tune-cortexa8.inc IMAGE_FSTYPES += "tar.bz2 jffs2 wic wic.bmap" EXTRA_IMAGECMD:jffs2 = "-lnp " WKS_FILE ?= "beaglebone-yocto.wks" -IMAGE_INSTALL:append = " kernel-devicetree kernel-image-zimage" +MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "kernel-image kernel-devicetree" do_image_wic[depends] += "mtools-native:do_populate_sysroot dosfstools-native:do_populate_sysroot virtual/bootloader:do_deploy" SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyO0 115200;ttyAMA0"
Signature · 1 line
2.34.1
Re: [meta-yocto][PATCH 2/2] beaglebone-yocto: move kernel and dtb to packagegroup-core-boot
Hi all,
Quoted 10 lines · On Mon, 10 Jan 2022 11:56:40 -0500 Vivien Didelot <[email protected]>…
Appending
IMAGE_INSTALLwith the kernel and device tree is a bad idea because it will bring these packages to every images, like a container image or sysroot image to pivot to, where the kernel artifacts are not wanted.Instead use the
MACHINE_ESSENTIAL_EXTRA_RDEPENDSwhich results in having the kernel artifacts where they should be, part of packagegroup-core-boot.Signed-off-by Vivien Didelot <[email protected]>
Do you guys get a chance to review this series?
Thanks,
Vivien