[meta-ti][master][PATCH 0/3] uniform beagle machine definitions

[meta-ti][master][PATCH 0/3] uniform beagle machine definitions

[rs]

From: Randolph Sapp <rs@ti.com>

Attempt to make beagle machine definitions uniform. Move all beagle definitions
to meta-beagle. Make the hierarchy clear; if there is a TI specific
configuration for a device, that will contain all common arguments. Only the
beagle machine configuration will include beagle BSP specific arguments.

This is the result of a thread [1] where some people were displeased with the
current organization of the machine configurations. Aside from adding a
beagley-ti configuration, this series basically just glitter to satiate some
opinions.

I'm sure this certainly won't spark other discussion.

[1] https://lists.yoctoproject.org/g/meta-ti/topic/117964418

Randolph Sapp (3):
  meta-beagle: move all beagle board configurations
  beagley-ai: add beagley-ai-ti
  beagleplay-ti: use the am62xx.inc

 .../conf/machine/beaglebadge-ti.conf              |  0
 .../conf/machine/beagleplay-ti-k3r5.conf          |  0
 .../conf/machine/beagleplay-ti.conf               | 15 +--------------
 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 ++---------
 7 files changed, 20 insertions(+), 30 deletions(-)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebadge-ti.conf (100%)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti-k3r5.conf (100%)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti.conf (68%)
 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

--
2.53.0

[meta-ti][master][PATCH 1/3] meta-beagle: move all beagle board configurations

[rs]

From: Randolph Sapp <rs@ti.com>

Move all beagle board configurations to meta-beagle. There are 2 skews
currently:

1. A base TI configuration setting all the default variables required to
   use the device with meta-ti-bsp provided packages.

2. An override that uses meta-beagle BSP components. This includes all
   the values defined in the TI skew as well as any meta-beagle specific
   configuration.

Signed-off-by: Randolph Sapp <rs@ti.com>
---
 {meta-ti-bsp => meta-beagle}/conf/machine/beaglebadge-ti.conf     | 0
 {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti-k3r5.conf | 0
 {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti.conf      | 0
 3 files changed, 0 insertions(+), 0 deletions(-)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebadge-ti.conf (100%)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti-k3r5.conf (100%)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti.conf (100%)

diff --git a/meta-ti-bsp/conf/machine/beaglebadge-ti.conf b/meta-beagle/conf/machine/beaglebadge-ti.conf
similarity index 100%
rename from meta-ti-bsp/conf/machine/beaglebadge-ti.conf
rename to meta-beagle/conf/machine/beaglebadge-ti.conf
diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf b/meta-beagle/conf/machine/beagleplay-ti-k3r5.conf
similarity index 100%
rename from meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
rename to meta-beagle/conf/machine/beagleplay-ti-k3r5.conf
diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti.conf b/meta-beagle/conf/machine/beagleplay-ti.conf
similarity index 100%
rename from meta-ti-bsp/conf/machine/beagleplay-ti.conf
rename to meta-beagle/conf/machine/beagleplay-ti.conf
-- 
2.53.0

Re: [meta-ti][master][PATCH 1/3] meta-beagle: move all beagle board configurations

[Ryan Eatmon]

On 2/23/2026 5:57 PM, rs@ti.com wrote:
> From: Randolph Sapp <rs@ti.com>
> 
> Move all beagle board configurations to meta-beagle. There are 2 skews
> currently:
> 
> 1. A base TI configuration setting all the default variables required to
>     use the device with meta-ti-bsp provided packages.
> 
> 2. An override that uses meta-beagle BSP components. This includes all
>     the values defined in the TI skew as well as any meta-beagle specific
>     configuration.
> 
> Signed-off-by: Randolph Sapp <rs@ti.com>
> ---
>   {meta-ti-bsp => meta-beagle}/conf/machine/beaglebadge-ti.conf     | 0
>   {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti-k3r5.conf | 0
>   {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti.conf      | 0
>   3 files changed, 0 insertions(+), 0 deletions(-)
>   rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebadge-ti.conf (100%)
>   rename {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti-k3r5.conf (100%)
>   rename {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti.conf (100%)
> 
> diff --git a/meta-ti-bsp/conf/machine/beaglebadge-ti.conf b/meta-beagle/conf/machine/beaglebadge-ti.conf
> similarity index 100%
> rename from meta-ti-bsp/conf/machine/beaglebadge-ti.conf
> rename to meta-beagle/conf/machine/beaglebadge-ti.conf
> diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf b/meta-beagle/conf/machine/beagleplay-ti-k3r5.conf
> similarity index 100%
> rename from meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
> rename to meta-beagle/conf/machine/beagleplay-ti-k3r5.conf
> diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti.conf b/meta-beagle/conf/machine/beagleplay-ti.conf
> similarity index 100%
> rename from meta-ti-bsp/conf/machine/beagleplay-ti.conf
> rename to meta-beagle/conf/machine/beagleplay-ti.conf

NAK.  There is nothing needed in meta-beagle to build beagleXXXX-ti 
since it uses the TI kernel/uboot.  So just moving it over there does 
not make sense.  I don't think this is the right thing to do.


-- 
Ryan Eatmon                reatmon@ti.com
-----------------------------------------
Texas Instruments, Inc.  -  LCPD  -  MGTS

Re: [meta-ti][master][PATCH 1/3] meta-beagle: move all beagle board configurations

[Randolph Sapp]

On Tue Feb 24, 2026 at 8:55 AM CST, Ryan Eatmon wrote:
>
>
> On 2/23/2026 5:57 PM, rs@ti.com wrote:
>> From: Randolph Sapp <rs@ti.com>
>> 
>> Move all beagle board configurations to meta-beagle. There are 2 skews
>> currently:
>> 
>> 1. A base TI configuration setting all the default variables required to
>>     use the device with meta-ti-bsp provided packages.
>> 
>> 2. An override that uses meta-beagle BSP components. This includes all
>>     the values defined in the TI skew as well as any meta-beagle specific
>>     configuration.
>> 
>> Signed-off-by: Randolph Sapp <rs@ti.com>
>> ---
>>   {meta-ti-bsp => meta-beagle}/conf/machine/beaglebadge-ti.conf     | 0
>>   {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti-k3r5.conf | 0
>>   {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti.conf      | 0
>>   3 files changed, 0 insertions(+), 0 deletions(-)
>>   rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebadge-ti.conf (100%)
>>   rename {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti-k3r5.conf (100%)
>>   rename {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti.conf (100%)
>> 
>> diff --git a/meta-ti-bsp/conf/machine/beaglebadge-ti.conf b/meta-beagle/conf/machine/beaglebadge-ti.conf
>> similarity index 100%
>> rename from meta-ti-bsp/conf/machine/beaglebadge-ti.conf
>> rename to meta-beagle/conf/machine/beaglebadge-ti.conf
>> diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf b/meta-beagle/conf/machine/beagleplay-ti-k3r5.conf
>> similarity index 100%
>> rename from meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
>> rename to meta-beagle/conf/machine/beagleplay-ti-k3r5.conf
>> diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti.conf b/meta-beagle/conf/machine/beagleplay-ti.conf
>> similarity index 100%
>> rename from meta-ti-bsp/conf/machine/beagleplay-ti.conf
>> rename to meta-beagle/conf/machine/beagleplay-ti.conf
>
> NAK.  There is nothing needed in meta-beagle to build beagleXXXX-ti 
> since it uses the TI kernel/uboot.  So just moving it over there does 
> not make sense.  I don't think this is the right thing to do.

Cool. I want a second opinion. Who the hell would look at a beagleplay machine
definition and not expect it to live in meta-beagle? If you bring up that this
is a generic definition using only TI layers and should therefore live in
meta-ti-bsp, are we going to start adopting all customer boards that use our
Kernel and U-Boot recipes?

I don't really know what you want, but I know what Andrew wants is dumb in that
it manufactures a circular layer dependency. I'm not doing that.

Re: [meta-ti][master][PATCH 1/3] meta-beagle: move all beagle board configurations

[Andrew Davis]

On 2/24/26 12:11 PM, Randolph Sapp wrote:
> On Tue Feb 24, 2026 at 8:55 AM CST, Ryan Eatmon wrote:
>>
>>
>> On 2/23/2026 5:57 PM, rs@ti.com wrote:
>>> From: Randolph Sapp <rs@ti.com>
>>>
>>> Move all beagle board configurations to meta-beagle. There are 2 skews
>>> currently:
>>>
>>> 1. A base TI configuration setting all the default variables required to
>>>      use the device with meta-ti-bsp provided packages.
>>>
>>> 2. An override that uses meta-beagle BSP components. This includes all
>>>      the values defined in the TI skew as well as any meta-beagle specific
>>>      configuration.
>>>
>>> Signed-off-by: Randolph Sapp <rs@ti.com>
>>> ---
>>>    {meta-ti-bsp => meta-beagle}/conf/machine/beaglebadge-ti.conf     | 0
>>>    {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti-k3r5.conf | 0
>>>    {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti.conf      | 0
>>>    3 files changed, 0 insertions(+), 0 deletions(-)
>>>    rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebadge-ti.conf (100%)
>>>    rename {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti-k3r5.conf (100%)
>>>    rename {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti.conf (100%)
>>>
>>> diff --git a/meta-ti-bsp/conf/machine/beaglebadge-ti.conf b/meta-beagle/conf/machine/beaglebadge-ti.conf
>>> similarity index 100%
>>> rename from meta-ti-bsp/conf/machine/beaglebadge-ti.conf
>>> rename to meta-beagle/conf/machine/beaglebadge-ti.conf
>>> diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf b/meta-beagle/conf/machine/beagleplay-ti-k3r5.conf
>>> similarity index 100%
>>> rename from meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
>>> rename to meta-beagle/conf/machine/beagleplay-ti-k3r5.conf
>>> diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti.conf b/meta-beagle/conf/machine/beagleplay-ti.conf
>>> similarity index 100%
>>> rename from meta-ti-bsp/conf/machine/beagleplay-ti.conf
>>> rename to meta-beagle/conf/machine/beagleplay-ti.conf
>>
>> NAK.  There is nothing needed in meta-beagle to build beagleXXXX-ti
>> since it uses the TI kernel/uboot.  So just moving it over there does
>> not make sense.  I don't think this is the right thing to do.
> 
> Cool. I want a second opinion. Who the hell would look at a beagleplay machine
> definition and not expect it to live in meta-beagle? If you bring up that this
> is a generic definition using only TI layers and should therefore live in
> meta-ti-bsp, are we going to start adopting all customer boards that use our
> Kernel and U-Boot recipes?
> 
> I don't really know what you want, but I know what Andrew wants is dumb in that
> it manufactures a circular layer dependency. I'm not doing that.

I think we replied at the same time :) Anyway, what I want is to not have
"-ti.conf" versions of the same board at all and just select the BSP external
to the .conf files. But my second place want would be this series as you have
posted it here.

Re: [meta-ti][master][PATCH 1/3] meta-beagle: move all beagle board configurations

[Randolph Sapp]

On Tue Feb 24, 2026 at 12:18 PM CST, Andrew Davis wrote:
> On 2/24/26 12:11 PM, Randolph Sapp wrote:
>> On Tue Feb 24, 2026 at 8:55 AM CST, Ryan Eatmon wrote:
>>>
>>>
>>> On 2/23/2026 5:57 PM, rs@ti.com wrote:
>>>> From: Randolph Sapp <rs@ti.com>
>>>>
>>>> Move all beagle board configurations to meta-beagle. There are 2 skews
>>>> currently:
>>>>
>>>> 1. A base TI configuration setting all the default variables required to
>>>>      use the device with meta-ti-bsp provided packages.
>>>>
>>>> 2. An override that uses meta-beagle BSP components. This includes all
>>>>      the values defined in the TI skew as well as any meta-beagle specific
>>>>      configuration.
>>>>
>>>> Signed-off-by: Randolph Sapp <rs@ti.com>
>>>> ---
>>>>    {meta-ti-bsp => meta-beagle}/conf/machine/beaglebadge-ti.conf     | 0
>>>>    {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti-k3r5.conf | 0
>>>>    {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti.conf      | 0
>>>>    3 files changed, 0 insertions(+), 0 deletions(-)
>>>>    rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebadge-ti.conf (100%)
>>>>    rename {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti-k3r5.conf (100%)
>>>>    rename {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti.conf (100%)
>>>>
>>>> diff --git a/meta-ti-bsp/conf/machine/beaglebadge-ti.conf b/meta-beagle/conf/machine/beaglebadge-ti.conf
>>>> similarity index 100%
>>>> rename from meta-ti-bsp/conf/machine/beaglebadge-ti.conf
>>>> rename to meta-beagle/conf/machine/beaglebadge-ti.conf
>>>> diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf b/meta-beagle/conf/machine/beagleplay-ti-k3r5.conf
>>>> similarity index 100%
>>>> rename from meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
>>>> rename to meta-beagle/conf/machine/beagleplay-ti-k3r5.conf
>>>> diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti.conf b/meta-beagle/conf/machine/beagleplay-ti.conf
>>>> similarity index 100%
>>>> rename from meta-ti-bsp/conf/machine/beagleplay-ti.conf
>>>> rename to meta-beagle/conf/machine/beagleplay-ti.conf
>>>
>>> NAK.  There is nothing needed in meta-beagle to build beagleXXXX-ti
>>> since it uses the TI kernel/uboot.  So just moving it over there does
>>> not make sense.  I don't think this is the right thing to do.
>> 
>> Cool. I want a second opinion. Who the hell would look at a beagleplay machine
>> definition and not expect it to live in meta-beagle? If you bring up that this
>> is a generic definition using only TI layers and should therefore live in
>> meta-ti-bsp, are we going to start adopting all customer boards that use our
>> Kernel and U-Boot recipes?
>> 
>> I don't really know what you want, but I know what Andrew wants is dumb in that
>> it manufactures a circular layer dependency. I'm not doing that.
>
> I think we replied at the same time :) Anyway, what I want is to not have
> "-ti.conf" versions of the same board at all and just select the BSP external
> to the .conf files. But my second place want would be this series as you have
> posted it here.

That's already a possibility using the TI_PREFERRED_BSP variable. My issue is,
what should be the default behavior then? Where is this functionality going to
be documented?

The values used in TI_PREFERRED_BSP will change and break between LTS (of which
I mean both Beagle and TI LTS). Overriding it in a local.conf would eventually
result in failure. That might not be that big of an issue to some people but
it's worth considering as it will need to be documented.

If a meta variable tries to wrap this behavior for the user, then we'll have
more dynamic configuration in a step that is usually declarative in other
layers. This solution feels too unique to us.

Re: [meta-ti][master][PATCH 1/3] meta-beagle: move all beagle board configurations

[Andrew Davis]

On 2/24/26 8:55 AM, Ryan Eatmon wrote:
> 
> 
> On 2/23/2026 5:57 PM, rs@ti.com wrote:
>> From: Randolph Sapp <rs@ti.com>
>>
>> Move all beagle board configurations to meta-beagle. There are 2 skews
>> currently:
>>
>> 1. A base TI configuration setting all the default variables required to
>>     use the device with meta-ti-bsp provided packages.
>>
>> 2. An override that uses meta-beagle BSP components. This includes all
>>     the values defined in the TI skew as well as any meta-beagle specific
>>     configuration.
>>
>> Signed-off-by: Randolph Sapp <rs@ti.com>
>> ---
>>   {meta-ti-bsp => meta-beagle}/conf/machine/beaglebadge-ti.conf     | 0
>>   {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti-k3r5.conf | 0
>>   {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti.conf      | 0
>>   3 files changed, 0 insertions(+), 0 deletions(-)
>>   rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebadge-ti.conf (100%)
>>   rename {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti-k3r5.conf (100%)
>>   rename {meta-ti-bsp => meta-beagle}/conf/machine/beagleplay-ti.conf (100%)
>>
>> diff --git a/meta-ti-bsp/conf/machine/beaglebadge-ti.conf b/meta-beagle/conf/machine/beaglebadge-ti.conf
>> similarity index 100%
>> rename from meta-ti-bsp/conf/machine/beaglebadge-ti.conf
>> rename to meta-beagle/conf/machine/beaglebadge-ti.conf
>> diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf b/meta-beagle/conf/machine/beagleplay-ti-k3r5.conf
>> similarity index 100%
>> rename from meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
>> rename to meta-beagle/conf/machine/beagleplay-ti-k3r5.conf
>> diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti.conf b/meta-beagle/conf/machine/beagleplay-ti.conf
>> similarity index 100%
>> rename from meta-ti-bsp/conf/machine/beagleplay-ti.conf
>> rename to meta-beagle/conf/machine/beagleplay-ti.conf
> 
> NAK.  There is nothing needed in meta-beagle to build beagleXXXX-ti since it uses the TI kernel/uboot.  So just moving it over there does not make sense.  I don't think this is the right thing to do.
> 
> 

We don't place the board configs based only on the lowest layer for which
we can satisfy all dependencies, I'd think we can place them where ever
it makes most sense. So Beagle boards going in meta-beagle seems correct.

Plus there is a dependency, `beagleplay-ti.conf` should depend on the base
`beagleplay.conf`. The "TI" versions of these boards should simply include
their base Beagle .confs and switch the default BSP over.

Andrew

[meta-ti][master][PATCH 2/3] beagley-ai: add beagley-ai-ti

[rs]

From: Randolph Sapp <rs@ti.com>

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 <rs@ti.com>
---
 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
+
 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 \
-- 
2.53.0

Re: [meta-ti][master][PATCH 2/3] beagley-ai: add beagley-ai-ti

[Andrew Davis]

On 2/23/26 5:57 PM, rs@ti.com wrote:
> From: Randolph Sapp <rs@ti.com>
> 
> 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 <rs@ti.com>
> ---
>   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.

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 \

Re: [meta-ti][master][PATCH 2/3] beagley-ai: add beagley-ai-ti

[Randolph Sapp]

On Tue Feb 24, 2026 at 12:31 PM CST, Andrew Davis wrote:
> On 2/23/26 5:57 PM, rs@ti.com wrote:
>> From: Randolph Sapp <rs@ti.com>
>> 
>> 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 <rs@ti.com>
>> ---
>>   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.
>
> Andrew

I agree that makes more sense from the outside looking in, but the current
version results in less variable overrides and less unused variables being
defined.

>>   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 \

Re: [meta-ti][master][PATCH 2/3] beagley-ai: add beagley-ai-ti

[Denys Dmytriyenko]

On Tue, Feb 24, 2026 at 12:31:27PM -0600, Andrew Davis via lists.yoctoproject.org wrote:
> On 2/23/26 5:57 PM, rs@ti.com wrote:
> >From: Randolph Sapp <rs@ti.com>
> >
> >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 <rs@ti.com>
> >---
> >  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 \

[meta-ti][master][PATCH 3/3] beagleplay-ti: use the am62xx.inc

[rs]

From: Randolph Sapp <rs@ti.com>

We should inherit the am62xx.inc and just override values as needed.

Signed-off-by: Randolph Sapp <rs@ti.com>
---
 meta-beagle/conf/machine/beagleplay-ti.conf | 15 +--------------
 1 file changed, 1 insertion(+), 14 deletions(-)

diff --git a/meta-beagle/conf/machine/beagleplay-ti.conf b/meta-beagle/conf/machine/beagleplay-ti.conf
index ca88fdfb..4e69c819 100644
--- a/meta-beagle/conf/machine/beagleplay-ti.conf
+++ b/meta-beagle/conf/machine/beagleplay-ti.conf
@@ -2,23 +2,10 @@
 #@NAME: BeaglePlay (A53)
 #@DESCRIPTION: Machine configuration for the BeaglePlay board (A53 core)
 
-require conf/machine/include/k3.inc
-require conf/machine/include/mc_k3r5.inc
-
-SOC_FAMILY:append = ":am62xx"
-
-MACHINE_FEATURES += "screen"
+require conf/machine/include/am62xx.inc
 
 SERIAL_CONSOLES = "115200;ttyS2"
 
-require conf/machine/include/mesa-pvr.inc
-PREFERRED_PROVIDER_virtual/gpudriver ?= "${BSP_ROGUE_DRIVER_PROVIDER}"
-
-TFA_BOARD = "lite"
-TFA_K3_SYSTEM_SUSPEND = "1"
-
-OPTEEMACHINE = "k3-am62x"
-
 UBOOT_MACHINE = "am62x_beagleplay_a53_defconfig"
 
 SPL_BINARY = "tispl.bin_unsigned"
-- 
2.53.0

Re: [meta-ti][master][PATCH 3/3] beagleplay-ti: use the am62xx.inc

[Andrew Davis]

On 2/23/26 5:57 PM, rs@ti.com wrote:
> From: Randolph Sapp <rs@ti.com>
> 
> We should inherit the am62xx.inc and just override values as needed.
> 
> Signed-off-by: Randolph Sapp <rs@ti.com>
> ---

This one looks valid even without moving it to meta-beagle and should
be done regardless of how we land on the other patches in this series.

Acked-by: Andrew Davis <afd@ti.com>

>   meta-beagle/conf/machine/beagleplay-ti.conf | 15 +--------------
>   1 file changed, 1 insertion(+), 14 deletions(-)
> 
> diff --git a/meta-beagle/conf/machine/beagleplay-ti.conf b/meta-beagle/conf/machine/beagleplay-ti.conf
> index ca88fdfb..4e69c819 100644
> --- a/meta-beagle/conf/machine/beagleplay-ti.conf
> +++ b/meta-beagle/conf/machine/beagleplay-ti.conf
> @@ -2,23 +2,10 @@
>   #@NAME: BeaglePlay (A53)
>   #@DESCRIPTION: Machine configuration for the BeaglePlay board (A53 core)
>   
> -require conf/machine/include/k3.inc
> -require conf/machine/include/mc_k3r5.inc
> -
> -SOC_FAMILY:append = ":am62xx"
> -
> -MACHINE_FEATURES += "screen"
> +require conf/machine/include/am62xx.inc
>   
>   SERIAL_CONSOLES = "115200;ttyS2"
>   
> -require conf/machine/include/mesa-pvr.inc
> -PREFERRED_PROVIDER_virtual/gpudriver ?= "${BSP_ROGUE_DRIVER_PROVIDER}"
> -
> -TFA_BOARD = "lite"
> -TFA_K3_SYSTEM_SUSPEND = "1"
> -
> -OPTEEMACHINE = "k3-am62x"
> -
>   UBOOT_MACHINE = "am62x_beagleplay_a53_defconfig"
>   
>   SPL_BINARY = "tispl.bin_unsigned"

Re: [meta-ti][master][PATCH 0/3] uniform beagle machine definitions

[PRC Automation]

meta-ti / na / 20260223235744.3928753-1-rs

PRC Results: PASS

=========================================================
  check-yocto-patches: PASS
=========================================================
Patches
----------------------------------------
WARN - [meta-ti][master][PATCH 1/3] meta-beagle: move all beagle board configurations
    WARN: Commit message does not include file/recipe name: meta-beagle: move all beagle board configurations. (COMMIT-MESSAGE-2)
        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 0/3] uniform beagle machine definitions
- Submitter: From: <rs@ti.com>
From: Randolph Sapp <rs@ti.com>
- Date: Date: Mon, 23 Feb 2026 17:57:41 -0600
- Num Patches: 3
- Mailing List (public inbox) Commit SHA: 95268f937c4ebc22963ca839fe28c6adfa2bd5dd

Applied to:
- Repository: lcpd-prc-meta-ti
- Base Branch: master-wip
- Commit Author: Ryan Eatmon <reatmon@ti.com>
- Commit Subject: conf: Add falcon support natively
- Commit SHA: a980abde977f53015d747b5feb6f06cddcf01eb9

Patches
----------------------------------------
All patches applied



=========================================================
  check-yocto-repo: PASS
=========================================================
master
=====================
PASS



=========================================================
  yocto-check-layers: PASS
=========================================================
master - PASS
=====================
All checks passed