| Message ID | 20260319175402.2517003-1-jm@ti.com |
|---|---|
| State | Accepted |
| Delegated to: | Ryan Eatmon |
| Headers | show |
| Series | [meta-ti,master] RFC: meta-beagle: Fix TF-A machine name for badge | expand |
meta-ti / na / 20260319175402.2517003-1-jm
PRC Results: PASS
=========================================================
check-yocto-patches: PASS
=========================================================
Patches
----------------------------------------
WARN - [meta-ti][master][PATCH] RFC: meta-beagle: Fix TF-A machine name for badge
WARN: Commit message does not include file/recipe name: RFC: meta-beagle: Fix TF-A machine name for badge. (COMMIT-MESSAGE-2)
patch
WARN: Commit message should not include directory path to recipe: RFC: meta-beagle: Fix TF-A machine name for badge.
meta-beagle (COMMIT-MESSAGE-3)
patch
For details on the above errors/warnings visit: https://lists.yoctoproject.org/g/meta-ti/wiki/40887
=========================================================
apply-yocto-patch: PASS
=========================================================
master
=====================
Summary:
- Patch Series: [meta-ti][master][PATCH] RFC: meta-beagle: Fix TF-A machine name for badge
- Submitter: From: Judith Mendez <jm@ti.com>
- Date: Date: Thu, 19 Mar 2026 12:54:02 -0500
- Num Patches: 1
- Mailing List (public inbox) Commit SHA: 9dddc443113b35444373ca3e03bd028c4fc2a43c
Applied to:
- Repository: lcpd-prc-meta-ti
- Base Branch: master-wip
- Commit Author: Randolph Sapp <rs@ti.com>
- Commit Subject: k3: set console parameter to KERNEL_CONSOLE
- Commit SHA: 83573186e74241b5646a43a64c31396a009fa368
Patches
----------------------------------------
All patches applied
=========================================================
check-yocto-repo: PASS
=========================================================
master
=====================
PASS
=========================================================
yocto-check-layers: PASS
=========================================================
master - PASS
=====================
All checks passed
On Thu, Mar 19, 2026 at 12:54:02PM -0500, Mendez, Judith via lists.yoctoproject.org wrote: > BeagleBadge board has been renamed to am62l3-badge > in the new TFA ti-tfa-2.14.y branch [0], so update > recipe TFA_BOARD accordingly. > > [0] https://github.com/TexasInstruments/arm-trusted-firmware/commit/d203b8453905178252094416448de009931087e0 > Signed-off-by: Judith Mendez <jm@ti.com> > --- > Due to build errors with arago-master-config, this patch > has not been built tested, thus sending as RFC. > --- > meta-beagle/conf/machine/beaglebadge-ti.conf | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/meta-beagle/conf/machine/beaglebadge-ti.conf b/meta-beagle/conf/machine/beaglebadge-ti.conf > index d62730ed..78525030 100644 > --- a/meta-beagle/conf/machine/beaglebadge-ti.conf > +++ b/meta-beagle/conf/machine/beaglebadge-ti.conf > @@ -18,4 +18,4 @@ KERNEL_DEVICETREE = "" > > UBOOT_MACHINE = "am62lx_badge_defconfig" > > -TFA_BOARD = "am62l-badge" > +TFA_BOARD = "am62l3-badge" This looks reasonable, on the surface at least. Andrew, Praneeth, How stable is the API around TFA? Do we want to keep multiple versions of TFA and select the corresponding one based on which BSP is in use (6.6, 6.12, 6.18)? I realize it's not specific to the kernel version, but to other low-level boot pieces, which all get updated at the same time, even though U-boot and kernel may be old...
On 3/19/2026 12:54 PM, Judith Mendez wrote: > BeagleBadge board has been renamed to am62l3-badge > in the new TFA ti-tfa-2.14.y branch [0], so update > recipe TFA_BOARD accordingly. > > [0] https://github.com/TexasInstruments/arm-trusted-firmware/commit/d203b8453905178252094416448de009931087e0 > Signed-off-by: Judith Mendez <jm@ti.com> > --- > Due to build errors with arago-master-config, this patch > has not been built tested, thus sending as RFC. > --- > meta-beagle/conf/machine/beaglebadge-ti.conf | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/meta-beagle/conf/machine/beaglebadge-ti.conf b/meta-beagle/conf/machine/beaglebadge-ti.conf > index d62730ed..78525030 100644 > --- a/meta-beagle/conf/machine/beaglebadge-ti.conf > +++ b/meta-beagle/conf/machine/beaglebadge-ti.conf > @@ -18,4 +18,4 @@ KERNEL_DEVICETREE = "" > > UBOOT_MACHINE = "am62lx_badge_defconfig" > > -TFA_BOARD = "am62l-badge" > +TFA_BOARD = "am62l3-badge" Build works so long as I include the SRCREV change sitting on master-next.
On 3/19/26 1:53 PM, Denys Dmytriyenko wrote: > On Thu, Mar 19, 2026 at 12:54:02PM -0500, Mendez, Judith via lists.yoctoproject.org wrote: >> BeagleBadge board has been renamed to am62l3-badge >> in the new TFA ti-tfa-2.14.y branch [0], so update >> recipe TFA_BOARD accordingly. >> >> [0] https://github.com/TexasInstruments/arm-trusted-firmware/commit/d203b8453905178252094416448de009931087e0 >> Signed-off-by: Judith Mendez <jm@ti.com> >> --- >> Due to build errors with arago-master-config, this patch >> has not been built tested, thus sending as RFC. >> --- >> meta-beagle/conf/machine/beaglebadge-ti.conf | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/meta-beagle/conf/machine/beaglebadge-ti.conf b/meta-beagle/conf/machine/beaglebadge-ti.conf >> index d62730ed..78525030 100644 >> --- a/meta-beagle/conf/machine/beaglebadge-ti.conf >> +++ b/meta-beagle/conf/machine/beaglebadge-ti.conf >> @@ -18,4 +18,4 @@ KERNEL_DEVICETREE = "" >> >> UBOOT_MACHINE = "am62lx_badge_defconfig" >> >> -TFA_BOARD = "am62l-badge" >> +TFA_BOARD = "am62l3-badge" > > This looks reasonable, on the surface at least. > > Andrew, Praneeth, > > How stable is the API around TFA? > > Do we want to keep multiple versions of TFA and select the corresponding one > based on which BSP is in use (6.6, 6.12, 6.18)? > The API "should" be stable, the only pain here is that until this is upstream our names might change, hopefully that isn't a long-term issue. Since we are using versioned TFA for each BSP (scarthgap (6.12) will use a different TFA branch than 6.18 (ti-tfa-2.14.y)), it might have made sense to have made versioned TFA recipes. But I don't see a huge need to go back and add that now. Andrew > I realize it's not specific to the kernel version, but to other low-level boot > pieces, which all get updated at the same time, even though U-boot and kernel > may be old... >
diff --git a/meta-beagle/conf/machine/beaglebadge-ti.conf b/meta-beagle/conf/machine/beaglebadge-ti.conf index d62730ed..78525030 100644 --- a/meta-beagle/conf/machine/beaglebadge-ti.conf +++ b/meta-beagle/conf/machine/beaglebadge-ti.conf @@ -18,4 +18,4 @@ KERNEL_DEVICETREE = "" UBOOT_MACHINE = "am62lx_badge_defconfig" -TFA_BOARD = "am62l-badge" +TFA_BOARD = "am62l3-badge"
BeagleBadge board has been renamed to am62l3-badge in the new TFA ti-tfa-2.14.y branch [0], so update recipe TFA_BOARD accordingly. [0] https://github.com/TexasInstruments/arm-trusted-firmware/commit/d203b8453905178252094416448de009931087e0 Signed-off-by: Judith Mendez <jm@ti.com> --- Due to build errors with arago-master-config, this patch has not been built tested, thus sending as RFC. --- meta-beagle/conf/machine/beaglebadge-ti.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)