On Tue, Feb 24, 2026 at 12:31:27PM -0600, Andrew Davis via lists.yoctoproject.org wrote: > On 2/23/26 5:57 PM, [email protected] wrote: > >From: Randolph Sapp <[email protected]> > > > >Split the existing config into a beagley-ai-ti and beagley-ai that > >includes it, like the existing beagleplay machine. > > > >Signed-off-by: Randolph Sapp <[email protected]> > >--- > > meta-beagle/conf/machine/beagley-ai-k3r5.conf | 6 ++---- > > ...agley-ai-k3r5.conf => beagley-ai-ti-k3r5.conf} | 3 --- > > meta-beagle/conf/machine/beagley-ai-ti.conf | 15 +++++++++++++++ > > meta-beagle/conf/machine/beagley-ai.conf | 11 ++--------- > > 4 files changed, 19 insertions(+), 16 deletions(-) > > copy meta-beagle/conf/machine/{beagley-ai-k3r5.conf => > > beagley-ai-ti-k3r5.conf} (61%) > > create mode 100644 meta-beagle/conf/machine/beagley-ai-ti.conf > > > >diff --git a/meta-beagle/conf/machine/beagley-ai-k3r5.conf > >b/meta-beagle/conf/machine/beagley-ai-k3r5.conf > >index 06c74cf9..2d6948d5 100644 > >--- a/meta-beagle/conf/machine/beagley-ai-k3r5.conf > >+++ b/meta-beagle/conf/machine/beagley-ai-k3r5.conf > >@@ -2,10 +2,8 @@ > > #@NAME: BeagleY AI (R5F) > > #@DESCRIPTION: Machine configuration for the BeagleY AI (R5F core) > >-require conf/machine/include/k3r5.inc > >+require conf/machine/beagley-ai-ti-k3r5.conf > >+ > > require conf/machine/include/beagle-bsp.inc > >-UBOOT_MACHINE = "am67a_beagley_ai_r5_defconfig" > > UBOOT_MACHINE:bsp-bb_org-6_6 = "j722s_evm_r5_defconfig" > >-UBOOT_MACHINE:bsp-ti-6_6 = "j722s_evm_r5_defconfig" > >-UBOOT_MACHINE:bsp-ti-6_12 = "j722s_evm_r5_defconfig" > >diff --git a/meta-beagle/conf/machine/beagley-ai-k3r5.conf > >b/meta-beagle/conf/machine/beagley-ai-ti-k3r5.conf > >similarity index 61% > >copy from meta-beagle/conf/machine/beagley-ai-k3r5.conf > >copy to meta-beagle/conf/machine/beagley-ai-ti-k3r5.conf > >index 06c74cf9..eaab2d57 100644 > >--- a/meta-beagle/conf/machine/beagley-ai-k3r5.conf > >+++ b/meta-beagle/conf/machine/beagley-ai-ti-k3r5.conf > >@@ -3,9 +3,6 @@ > > #@DESCRIPTION: Machine configuration for the BeagleY AI (R5F core) > > require conf/machine/include/k3r5.inc > >-require conf/machine/include/beagle-bsp.inc > > UBOOT_MACHINE = "am67a_beagley_ai_r5_defconfig" > >-UBOOT_MACHINE:bsp-bb_org-6_6 = "j722s_evm_r5_defconfig" > > UBOOT_MACHINE:bsp-ti-6_6 = "j722s_evm_r5_defconfig" > >-UBOOT_MACHINE:bsp-ti-6_12 = "j722s_evm_r5_defconfig" > >diff --git a/meta-beagle/conf/machine/beagley-ai-ti.conf > >b/meta-beagle/conf/machine/beagley-ai-ti.conf > >new file mode 100644 > >index 00000000..d6d05264 > >--- /dev/null > >+++ b/meta-beagle/conf/machine/beagley-ai-ti.conf > >@@ -0,0 +1,15 @@ > >+#@TYPE: Machine > >+#@NAME: BeagleY AI (A53) > >+#@DESCRIPTION: Machine configuration for the BeagleY AI board (A53 core) > >+ > >+require conf/machine/include/j722s.inc > >+ > >+UBOOT_MACHINE = "am67a_beagley_ai_a53_defconfig" > >+UBOOT_MACHINE:bsp-ti-6_6 = "j722s_evm_a53_config" > >+ > >+KERNEL_DEVICETREE_PREFIX = " \ > >+ ti/k3-am67a \ > >+ ti/k3-j722s \ > >+" > >+ > >+MACHINE_GUI_CLASS = "bigscreen" > >diff --git a/meta-beagle/conf/machine/beagley-ai.conf > >b/meta-beagle/conf/machine/beagley-ai.conf > >index d73d0506..d2c68201 100644 > >--- a/meta-beagle/conf/machine/beagley-ai.conf > >+++ b/meta-beagle/conf/machine/beagley-ai.conf > >@@ -2,18 +2,11 @@ > > #@NAME: BeagleY AI (A53) > > #@DESCRIPTION: Machine configuration for the BeagleY AI board (A53 core) > >-require conf/machine/include/j722s.inc > >+require conf/machine/beagley-ai-ti.conf > >+ > > We should flip this around, `beagley-ai-ti.conf` should include > `beagley-ai.conf`, > not the other way around. `beagley-ai.conf` is the "deafult" config using the > Beagle kernel as one would expect of a Beagle product. The "-ti.conf" version > is > the odd ball in that it changes the default to something else. Plus that would > keep this patch more simple, only needing changes to the new "-ti.conf" file. > > Only downside would be this is done the other way around currently for > beagleplay, but that would be an easy fix to switch it too.
If you recall, one of the main goals for creating meta-beagle was to showcase and set an example of how downstream layers can build on top and extend the base meta-ti-bsp layer. So, meta-beagle is a downstream layer to meta-ti-bsp and that sets the layer dependency. The way beagleplay machines were originally placed in these 2 layers, you cannot include beagleplay.conf from "-ti.conf" file, only the other way around. > Andrew > > > require conf/machine/include/beagle-bsp.inc > >-UBOOT_MACHINE = "am67a_beagley_ai_a53_defconfig" > > UBOOT_MACHINE:bsp-bb_org-6_6 = "j722s_evm_a53_config" > >-UBOOT_MACHINE:bsp-ti-6_6 = "j722s_evm_a53_config" > >-UBOOT_MACHINE:bsp-ti-6_12 = "j722s_evm_a53_config" > >- > >-KERNEL_DEVICETREE_PREFIX = " \ > >- ti/k3-am67a \ > >- ti/k3-j722s \ > >-" > > KERNEL_DEVICETREE:bsp-bb_org-6_6 = " \ > > ti/k3-am67a-beagley-ai.dtb \
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19591): https://lists.yoctoproject.org/g/meta-ti/message/19591 Mute This Topic: https://lists.yoctoproject.org/mt/117968155/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
