diff mbox series

[2/2] u-boot: enable tf-a support for genericarm64

Message ID 20260401102931.781169-2-mikko.rapeli@linaro.org
State New
Headers show
Series [1/2] trusted-firmware-a: support genericarm64 like qemuarm64 | expand

Commit Message

Mikko Rapeli April 1, 2026, 10:29 a.m. UTC
genericarm64 target HW uses separate vendor specific
UEFI firmware but for qemu testing tf-a support can
be enabled just like for qemuarm64. genericarm64
has the benefit that the same wic images will work on qemu
and on many Arm System Ready compatible devices from
different vendors.

Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
---
 meta-arm/recipes-bsp/u-boot/u-boot_%.bbappend | 1 +
 1 file changed, 1 insertion(+)

Comments

Ross Burton April 2, 2026, 4:42 p.m. UTC | #1
On 1 Apr 2026, at 11:29, Mikko Rapeli via lists.yoctoproject.org <mikko.rapeli=linaro.org@lists.yoctoproject.org> wrote:
> 
> +SRC_URI:append:genericarm64 = " file://qemuarm64.cfg”

Whilst I don’t disagree with the principle of the series, this line means we’d fail the compatibility testing (and if we didn’t, that’s a problem with the testing).

Simply adding layers shouldn’t impact things outside of them, and this will mean that adding meta-arm automatically pulls in TF-A to genericarm64 builds.

I’m not sure what the right solution here is. Maybe literally guarding the SRC_URI change with a variable (that defaults to off) would be sufficient.

Ross
Mikko Rapeli April 2, 2026, 5:56 p.m. UTC | #2
Hi,

On Thu, Apr 02, 2026 at 04:42:02PM +0000, Ross Burton wrote:
> On 1 Apr 2026, at 11:29, Mikko Rapeli via lists.yoctoproject.org <mikko.rapeli=linaro.org@lists.yoctoproject.org> wrote:
> > 
> > +SRC_URI:append:genericarm64 = " file://qemuarm64.cfg”
> 
> Whilst I don’t disagree with the principle of the series, this line means we’d fail the compatibility testing (and if we didn’t, that’s a problem with the testing).
> 
> Simply adding layers shouldn’t impact things outside of them, and this will mean that adding meta-arm automatically pulls in TF-A to genericarm64 builds.
> 
> I’m not sure what the right solution here is. Maybe literally guarding the SRC_URI change with a variable (that defaults to off) would be sufficient.

True. I did not want another machine variant which enables these. Maybe
MACHINE_FEATURE like "tf-a", which then for genericarm64 adds these
qemuarm64 configs. Using other custom variables doesn't feel right either.

These do not impact anything in systemd-boot, kernel or userspace
or in the wic image which is compatible with a lot of HW.

Cheers,

-Mikko
diff mbox series

Patch

diff --git a/meta-arm/recipes-bsp/u-boot/u-boot_%.bbappend b/meta-arm/recipes-bsp/u-boot/u-boot_%.bbappend
index 8ddc53619560..403260a2bc2f 100644
--- a/meta-arm/recipes-bsp/u-boot/u-boot_%.bbappend
+++ b/meta-arm/recipes-bsp/u-boot/u-boot_%.bbappend
@@ -2,6 +2,7 @@  FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
 
 SRC_URI:append:qemuarm64-secureboot = " file://qemuarm64.cfg"
 SRC_URI:append:qemuarm-secureboot = " file://qemuarm.cfg"
+SRC_URI:append:genericarm64 = " file://qemuarm64.cfg"
 
 require ${@bb.utils.contains('MACHINE_FEATURES', 'uefi-secureboot', 'u-boot-uefi-secureboot.inc', '', d)}