diff mbox series

[meta-ti,master] conf: beagley-ai: add beagley-ai-ti configuration

Message ID 20260223202236.3642261-1-rs@ti.com
State New
Headers show
Series [meta-ti,master] conf: beagley-ai: add beagley-ai-ti configuration | expand

Commit Message

Randolph Sapp Feb. 23, 2026, 8:22 p.m. UTC 
From: Randolph Sapp <rs@ti.com>

Add a TI configuration for the BeagleY-AI development board.

Signed-off-by: Randolph Sapp <rs@ti.com>
---
 meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf |  7 +++++++
 meta-ti-bsp/conf/machine/beagley-ai-ti.conf      | 16 ++++++++++++++++
 2 files changed, 23 insertions(+)
 create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
 create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti.conf

Comments

PRC Automation Feb. 23, 2026, 8:32 p.m. UTC | #1 
meta-ti / na / 20260223202236.3642261-1-rs

PRC Results: PASS

=========================================================
  check-yocto-patches: PASS
=========================================================
Patches
----------------------------------------
WARN - [meta-ti][master][PATCH] conf: beagley-ai: add beagley-ai-ti configuration
    WARN: Commit message does not include file/recipe name: conf: beagley-ai: add beagley-ai-ti configuration. (COMMIT-MESSAGE-2)
        patch
    
    WARN: Commit message should not include directory path to recipe: conf: beagley-ai: add beagley-ai-ti configuration.
              conf (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] conf: beagley-ai: add beagley-ai-ti configuration
- Submitter: From: <rs@ti.com>
From: Randolph Sapp <rs@ti.com>
- Date: Date: Mon, 23 Feb 2026 14:22:36 -0600
- Num Patches: 1
- Mailing List (public inbox) Commit SHA: 5e49c9ea6de3d4ba49e571b2247d66879c820473

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: bbc4f137e10f7654cd3247cb811d42fb7f59fe7b

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



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



=========================================================
  yocto-check-layers: PASS
=========================================================
master - PASS
=====================
All checks passed
Andrew Davis Feb. 23, 2026, 9:51 p.m. UTC | #2 
On 2/23/26 2:22 PM, Randolph Sapp via lists.yoctoproject.org wrote:
> From: Randolph Sapp <rs@ti.com>
> 
> Add a TI configuration for the BeagleY-AI development board.
> 
> Signed-off-by: Randolph Sapp <rs@ti.com>
> ---
>   meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf |  7 +++++++
>   meta-ti-bsp/conf/machine/beagley-ai-ti.conf      | 16 ++++++++++++++++
>   2 files changed, 23 insertions(+)
>   create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>   create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti.conf
> 
> diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
> new file mode 100644
> index 00000000..88d0888b
> --- /dev/null
> +++ b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
> @@ -0,0 +1,7 @@
> +#@TYPE: Machine
> +#@NAME: BeagleY-AI (R5F)
> +#@DESCRIPTION: Machine configuration for the BeagleY-AI (R5F core)
> +
> +require conf/machine/include/k3r5.inc
> +
> +UBOOT_MACHINE = "am67a_beagley_ai_r5_defconfig"
> diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti.conf b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
> new file mode 100644
> index 00000000..088cbd62
> --- /dev/null
> +++ b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
> @@ -0,0 +1,16 @@
> +#@TYPE: Machine
> +#@NAME: BeagleY-AI (A53)
> +#@DESCRIPTION: Machine configuration for the BeagleY-AI (A53)
> +
> +require conf/machine/include/j722s.inc
> +
> +KERNEL_DEVICETREE_PREFIX = " \
> +    ti/k3-am67a \
> +    ti/k3-j722s \
> +"
> +
> +KERNEL_DEVICETREE = " \
> +    ti/k3-am67a-beagley-ai.dtb \
> +"
> +
> +UBOOT_MACHINE = "am67a_beagley_ai_a53_defconfig"

This defconfig doesn't work if you select an older BSP.

Thinking on this, the only difference we should have between this machine
config and the one already in meta-beagle is the default selected BSP
(bsp-ti-6_12 vs bb_org-6_12). Why can't we just have the one config and
select the BSP with TI_PREFERRED_BSP? We could do that externally
from the build env, or with a branding.

The issue with this patch is we would now have two configs for the same
hardware, and there is no TI produced BeagleY, so having the machine
config for it in this layer just seems wrong. I have the same complaint
for beagleplay-ti and beaglebadge-ti, we should drop those too and fix
them in the same way.

Andrew

> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#19562): https://lists.yoctoproject.org/g/meta-ti/message/19562
> Mute This Topic: https://lists.yoctoproject.org/mt/117964418/3619733
> Group Owner: meta-ti+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [afd@ti.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
Ryan Eatmon Feb. 23, 2026, 9:54 p.m. UTC | #3 
On 2/23/2026 3:51 PM, Andrew Davis wrote:
> On 2/23/26 2:22 PM, Randolph Sapp via lists.yoctoproject.org wrote:
>> From: Randolph Sapp <rs@ti.com>
>>
>> Add a TI configuration for the BeagleY-AI development board.
>>
>> Signed-off-by: Randolph Sapp <rs@ti.com>
>> ---
>>   meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf |  7 +++++++
>>   meta-ti-bsp/conf/machine/beagley-ai-ti.conf      | 16 ++++++++++++++++
>>   2 files changed, 23 insertions(+)
>>   create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>   create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>
>> diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf 
>> b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>> new file mode 100644
>> index 00000000..88d0888b
>> --- /dev/null
>> +++ b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>> @@ -0,0 +1,7 @@
>> +#@TYPE: Machine
>> +#@NAME: BeagleY-AI (R5F)
>> +#@DESCRIPTION: Machine configuration for the BeagleY-AI (R5F core)
>> +
>> +require conf/machine/include/k3r5.inc
>> +
>> +UBOOT_MACHINE = "am67a_beagley_ai_r5_defconfig"
>> diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti.conf 
>> b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>> new file mode 100644
>> index 00000000..088cbd62
>> --- /dev/null
>> +++ b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>> @@ -0,0 +1,16 @@
>> +#@TYPE: Machine
>> +#@NAME: BeagleY-AI (A53)
>> +#@DESCRIPTION: Machine configuration for the BeagleY-AI (A53)
>> +
>> +require conf/machine/include/j722s.inc
>> +
>> +KERNEL_DEVICETREE_PREFIX = " \
>> +    ti/k3-am67a \
>> +    ti/k3-j722s \
>> +"
>> +
>> +KERNEL_DEVICETREE = " \
>> +    ti/k3-am67a-beagley-ai.dtb \
>> +"
>> +
>> +UBOOT_MACHINE = "am67a_beagley_ai_a53_defconfig"
> 
> This defconfig doesn't work if you select an older BSP.
> 
> Thinking on this, the only difference we should have between this machine
> config and the one already in meta-beagle is the default selected BSP
> (bsp-ti-6_12 vs bb_org-6_12). Why can't we just have the one config and
> select the BSP with TI_PREFERRED_BSP? We could do that externally
> from the build env, or with a branding.
> 
> The issue with this patch is we would now have two configs for the same
> hardware, and there is no TI produced BeagleY, so having the machine
> config for it in this layer just seems wrong. I have the same complaint
> for beagleplay-ti and beaglebadge-ti, we should drop those too and fix
> them in the same way.

The difference between the two platforms is that one is supported by TI 
and one is not.  We do not answer questions or support the meta-beagle 
boards.  Those are supported by the community (aka Denys).  But the 
beagleplay-ti board using the TI kernel and TI uboot is supported.  We 
will answer questions about them.

It was a decision from Sitara management to do this.

That's why we name them differently to draw a distinction between the two.


> Andrew
> 
>>
>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> View/Reply Online (#19562): 
>> https://lists.yoctoproject.org/g/meta-ti/message/19562
>> Mute This Topic: https://lists.yoctoproject.org/mt/117964418/3619733
>> Group Owner: meta-ti+owner@lists.yoctoproject.org
>> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [afd@ti.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
>
Randolph Sapp Feb. 23, 2026, 10:10 p.m. UTC | #4 
On Mon Feb 23, 2026 at 3:51 PM CST, Andrew Davis wrote:
> On 2/23/26 2:22 PM, Randolph Sapp via lists.yoctoproject.org wrote:
>> From: Randolph Sapp <rs@ti.com>
>> 
>> Add a TI configuration for the BeagleY-AI development board.
>> 
>> Signed-off-by: Randolph Sapp <rs@ti.com>
>> ---
>>   meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf |  7 +++++++
>>   meta-ti-bsp/conf/machine/beagley-ai-ti.conf      | 16 ++++++++++++++++
>>   2 files changed, 23 insertions(+)
>>   create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>   create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>> 
>> diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>> new file mode 100644
>> index 00000000..88d0888b
>> --- /dev/null
>> +++ b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>> @@ -0,0 +1,7 @@
>> +#@TYPE: Machine
>> +#@NAME: BeagleY-AI (R5F)
>> +#@DESCRIPTION: Machine configuration for the BeagleY-AI (R5F core)
>> +
>> +require conf/machine/include/k3r5.inc
>> +
>> +UBOOT_MACHINE = "am67a_beagley_ai_r5_defconfig"
>> diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti.conf b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>> new file mode 100644
>> index 00000000..088cbd62
>> --- /dev/null
>> +++ b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>> @@ -0,0 +1,16 @@
>> +#@TYPE: Machine
>> +#@NAME: BeagleY-AI (A53)
>> +#@DESCRIPTION: Machine configuration for the BeagleY-AI (A53)
>> +
>> +require conf/machine/include/j722s.inc
>> +
>> +KERNEL_DEVICETREE_PREFIX = " \
>> +    ti/k3-am67a \
>> +    ti/k3-j722s \
>> +"
>> +
>> +KERNEL_DEVICETREE = " \
>> +    ti/k3-am67a-beagley-ai.dtb \
>> +"
>> +
>> +UBOOT_MACHINE = "am67a_beagley_ai_a53_defconfig"
>
> This defconfig doesn't work if you select an older BSP.

Yeah, I've famously voiced concerns about the BSP provider logic in general, but
6.6 and it's associated BSP profile is frozen. Though the beagley-ai.conf uses
j722s_evm_a53_config, the 'k3-j722s-evm.dts' in that profile defines 8GB of DDR,
which is clearly wrong. I don't want to see that blow up later.

> Thinking on this, the only difference we should have between this machine
> config and the one already in meta-beagle is the default selected BSP
> (bsp-ti-6_12 vs bb_org-6_12). Why can't we just have the one config and
> select the BSP with TI_PREFERRED_BSP? We could do that externally
> from the build env, or with a branding.
>
> The issue with this patch is we would now have two configs for the same
> hardware, and there is no TI produced BeagleY, so having the machine
> config for it in this layer just seems wrong. I have the same complaint
> for beagleplay-ti and beaglebadge-ti, we should drop those too and fix
> them in the same way.
>
> Andrew
>

The only thing this solution does is obscure this behavior with a new variable
and deduplicate what should be static configuration files. I don't really think
it's an improvement.

- Randolph
Randolph Sapp Feb. 23, 2026, 10:27 p.m. UTC | #5 
On Mon Feb 23, 2026 at 3:54 PM CST, Ryan Eatmon wrote:
>
>
> On 2/23/2026 3:51 PM, Andrew Davis wrote:
>> On 2/23/26 2:22 PM, Randolph Sapp via lists.yoctoproject.org wrote:
>>> From: Randolph Sapp <rs@ti.com>
>>>
>>> Add a TI configuration for the BeagleY-AI development board.
>>>
>>> Signed-off-by: Randolph Sapp <rs@ti.com>
>>> ---
>>>   meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf |  7 +++++++
>>>   meta-ti-bsp/conf/machine/beagley-ai-ti.conf      | 16 ++++++++++++++++
>>>   2 files changed, 23 insertions(+)
>>>   create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>>   create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>>
>>> diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf 
>>> b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>> new file mode 100644
>>> index 00000000..88d0888b
>>> --- /dev/null
>>> +++ b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>> @@ -0,0 +1,7 @@
>>> +#@TYPE: Machine
>>> +#@NAME: BeagleY-AI (R5F)
>>> +#@DESCRIPTION: Machine configuration for the BeagleY-AI (R5F core)
>>> +
>>> +require conf/machine/include/k3r5.inc
>>> +
>>> +UBOOT_MACHINE = "am67a_beagley_ai_r5_defconfig"
>>> diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti.conf 
>>> b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>> new file mode 100644
>>> index 00000000..088cbd62
>>> --- /dev/null
>>> +++ b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>> @@ -0,0 +1,16 @@
>>> +#@TYPE: Machine
>>> +#@NAME: BeagleY-AI (A53)
>>> +#@DESCRIPTION: Machine configuration for the BeagleY-AI (A53)
>>> +
>>> +require conf/machine/include/j722s.inc
>>> +
>>> +KERNEL_DEVICETREE_PREFIX = " \
>>> +    ti/k3-am67a \
>>> +    ti/k3-j722s \
>>> +"
>>> +
>>> +KERNEL_DEVICETREE = " \
>>> +    ti/k3-am67a-beagley-ai.dtb \
>>> +"
>>> +
>>> +UBOOT_MACHINE = "am67a_beagley_ai_a53_defconfig"
>> 
>> This defconfig doesn't work if you select an older BSP.
>> 
>> Thinking on this, the only difference we should have between this machine
>> config and the one already in meta-beagle is the default selected BSP
>> (bsp-ti-6_12 vs bb_org-6_12). Why can't we just have the one config and
>> select the BSP with TI_PREFERRED_BSP? We could do that externally
>> from the build env, or with a branding.
>> 
>> The issue with this patch is we would now have two configs for the same
>> hardware, and there is no TI produced BeagleY, so having the machine
>> config for it in this layer just seems wrong. I have the same complaint
>> for beagleplay-ti and beaglebadge-ti, we should drop those too and fix
>> them in the same way.
>
> The difference between the two platforms is that one is supported by TI 
> and one is not.  We do not answer questions or support the meta-beagle 
> boards.  Those are supported by the community (aka Denys).  But the 
> beagleplay-ti board using the TI kernel and TI uboot is supported.  We 
> will answer questions about them.
>
> It was a decision from Sitara management to do this.
>
> That's why we name them differently to draw a distinction between the two.
>

That really is unfortunate. Inclusion of meta-beagle in meta-ti does not make
that clear, and the layer README(s) don't offer that information freely either.

- Randolph
Ryan Eatmon Feb. 23, 2026, 10:31 p.m. UTC | #6 
On 2/23/2026 4:27 PM, Randolph Sapp wrote:
> On Mon Feb 23, 2026 at 3:54 PM CST, Ryan Eatmon wrote:
>>
>>
>> On 2/23/2026 3:51 PM, Andrew Davis wrote:
>>> On 2/23/26 2:22 PM, Randolph Sapp via lists.yoctoproject.org wrote:
>>>> From: Randolph Sapp <rs@ti.com>
>>>>
>>>> Add a TI configuration for the BeagleY-AI development board.
>>>>
>>>> Signed-off-by: Randolph Sapp <rs@ti.com>
>>>> ---
>>>>    meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf |  7 +++++++
>>>>    meta-ti-bsp/conf/machine/beagley-ai-ti.conf      | 16 ++++++++++++++++
>>>>    2 files changed, 23 insertions(+)
>>>>    create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>>>    create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>>>
>>>> diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>>> b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>>> new file mode 100644
>>>> index 00000000..88d0888b
>>>> --- /dev/null
>>>> +++ b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>>> @@ -0,0 +1,7 @@
>>>> +#@TYPE: Machine
>>>> +#@NAME: BeagleY-AI (R5F)
>>>> +#@DESCRIPTION: Machine configuration for the BeagleY-AI (R5F core)
>>>> +
>>>> +require conf/machine/include/k3r5.inc
>>>> +
>>>> +UBOOT_MACHINE = "am67a_beagley_ai_r5_defconfig"
>>>> diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>>> b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>>> new file mode 100644
>>>> index 00000000..088cbd62
>>>> --- /dev/null
>>>> +++ b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>>> @@ -0,0 +1,16 @@
>>>> +#@TYPE: Machine
>>>> +#@NAME: BeagleY-AI (A53)
>>>> +#@DESCRIPTION: Machine configuration for the BeagleY-AI (A53)
>>>> +
>>>> +require conf/machine/include/j722s.inc
>>>> +
>>>> +KERNEL_DEVICETREE_PREFIX = " \
>>>> +    ti/k3-am67a \
>>>> +    ti/k3-j722s \
>>>> +"
>>>> +
>>>> +KERNEL_DEVICETREE = " \
>>>> +    ti/k3-am67a-beagley-ai.dtb \
>>>> +"
>>>> +
>>>> +UBOOT_MACHINE = "am67a_beagley_ai_a53_defconfig"
>>>
>>> This defconfig doesn't work if you select an older BSP.
>>>
>>> Thinking on this, the only difference we should have between this machine
>>> config and the one already in meta-beagle is the default selected BSP
>>> (bsp-ti-6_12 vs bb_org-6_12). Why can't we just have the one config and
>>> select the BSP with TI_PREFERRED_BSP? We could do that externally
>>> from the build env, or with a branding.
>>>
>>> The issue with this patch is we would now have two configs for the same
>>> hardware, and there is no TI produced BeagleY, so having the machine
>>> config for it in this layer just seems wrong. I have the same complaint
>>> for beagleplay-ti and beaglebadge-ti, we should drop those too and fix
>>> them in the same way.
>>
>> The difference between the two platforms is that one is supported by TI
>> and one is not.  We do not answer questions or support the meta-beagle
>> boards.  Those are supported by the community (aka Denys).  But the
>> beagleplay-ti board using the TI kernel and TI uboot is supported.  We
>> will answer questions about them.
>>
>> It was a decision from Sitara management to do this.
>>
>> That's why we name them differently to draw a distinction between the two.
>>
> 
> That really is unfortunate. Inclusion of meta-beagle in meta-ti does not make
> that clear, and the layer README(s) don't offer that information freely either.

I would rather drop the beagleboard-ti and all TI versions of the beagle 
boards and just rely on meta-beagle and what beagle officially supports.


> - Randolph
Randolph Sapp Feb. 23, 2026, 10:35 p.m. UTC | #7 
On Mon Feb 23, 2026 at 4:31 PM CST, Ryan Eatmon wrote:
>
>
> On 2/23/2026 4:27 PM, Randolph Sapp wrote:
>> On Mon Feb 23, 2026 at 3:54 PM CST, Ryan Eatmon wrote:
>>>
>>>
>>> On 2/23/2026 3:51 PM, Andrew Davis wrote:
>>>> On 2/23/26 2:22 PM, Randolph Sapp via lists.yoctoproject.org wrote:
>>>>> From: Randolph Sapp <rs@ti.com>
>>>>>
>>>>> Add a TI configuration for the BeagleY-AI development board.
>>>>>
>>>>> Signed-off-by: Randolph Sapp <rs@ti.com>
>>>>> ---
>>>>>    meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf |  7 +++++++
>>>>>    meta-ti-bsp/conf/machine/beagley-ai-ti.conf      | 16 ++++++++++++++++
>>>>>    2 files changed, 23 insertions(+)
>>>>>    create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>>>>    create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>>>>
>>>>> diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>>>> b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>>>> new file mode 100644
>>>>> index 00000000..88d0888b
>>>>> --- /dev/null
>>>>> +++ b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>>>> @@ -0,0 +1,7 @@
>>>>> +#@TYPE: Machine
>>>>> +#@NAME: BeagleY-AI (R5F)
>>>>> +#@DESCRIPTION: Machine configuration for the BeagleY-AI (R5F core)
>>>>> +
>>>>> +require conf/machine/include/k3r5.inc
>>>>> +
>>>>> +UBOOT_MACHINE = "am67a_beagley_ai_r5_defconfig"
>>>>> diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>>>> b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>>>> new file mode 100644
>>>>> index 00000000..088cbd62
>>>>> --- /dev/null
>>>>> +++ b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>>>> @@ -0,0 +1,16 @@
>>>>> +#@TYPE: Machine
>>>>> +#@NAME: BeagleY-AI (A53)
>>>>> +#@DESCRIPTION: Machine configuration for the BeagleY-AI (A53)
>>>>> +
>>>>> +require conf/machine/include/j722s.inc
>>>>> +
>>>>> +KERNEL_DEVICETREE_PREFIX = " \
>>>>> +    ti/k3-am67a \
>>>>> +    ti/k3-j722s \
>>>>> +"
>>>>> +
>>>>> +KERNEL_DEVICETREE = " \
>>>>> +    ti/k3-am67a-beagley-ai.dtb \
>>>>> +"
>>>>> +
>>>>> +UBOOT_MACHINE = "am67a_beagley_ai_a53_defconfig"
>>>>
>>>> This defconfig doesn't work if you select an older BSP.
>>>>
>>>> Thinking on this, the only difference we should have between this machine
>>>> config and the one already in meta-beagle is the default selected BSP
>>>> (bsp-ti-6_12 vs bb_org-6_12). Why can't we just have the one config and
>>>> select the BSP with TI_PREFERRED_BSP? We could do that externally
>>>> from the build env, or with a branding.
>>>>
>>>> The issue with this patch is we would now have two configs for the same
>>>> hardware, and there is no TI produced BeagleY, so having the machine
>>>> config for it in this layer just seems wrong. I have the same complaint
>>>> for beagleplay-ti and beaglebadge-ti, we should drop those too and fix
>>>> them in the same way.
>>>
>>> The difference between the two platforms is that one is supported by TI
>>> and one is not.  We do not answer questions or support the meta-beagle
>>> boards.  Those are supported by the community (aka Denys).  But the
>>> beagleplay-ti board using the TI kernel and TI uboot is supported.  We
>>> will answer questions about them.
>>>
>>> It was a decision from Sitara management to do this.
>>>
>>> That's why we name them differently to draw a distinction between the two.
>>>
>> 
>> That really is unfortunate. Inclusion of meta-beagle in meta-ti does not make
>> that clear, and the layer README(s) don't offer that information freely either.
>
> I would rather drop the beagleboard-ti and all TI versions of the beagle 
> boards and just rely on meta-beagle and what beagle officially supports.
>

I don't necessarily hate that idea. Guessing this is hinging on Andrew's idea of
overriding the BSP provider variable directly for our internal testing?
Andrew Davis Feb. 23, 2026, 10:43 p.m. UTC | #8 
On 2/23/26 3:54 PM, Ryan Eatmon wrote:
> 
> 
> On 2/23/2026 3:51 PM, Andrew Davis wrote:
>> On 2/23/26 2:22 PM, Randolph Sapp via lists.yoctoproject.org wrote:
>>> From: Randolph Sapp <rs@ti.com>
>>>
>>> Add a TI configuration for the BeagleY-AI development board.
>>>
>>> Signed-off-by: Randolph Sapp <rs@ti.com>
>>> ---
>>>   meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf |  7 +++++++
>>>   meta-ti-bsp/conf/machine/beagley-ai-ti.conf      | 16 ++++++++++++++++
>>>   2 files changed, 23 insertions(+)
>>>   create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>>   create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>>
>>> diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>> new file mode 100644
>>> index 00000000..88d0888b
>>> --- /dev/null
>>> +++ b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>> @@ -0,0 +1,7 @@
>>> +#@TYPE: Machine
>>> +#@NAME: BeagleY-AI (R5F)
>>> +#@DESCRIPTION: Machine configuration for the BeagleY-AI (R5F core)
>>> +
>>> +require conf/machine/include/k3r5.inc
>>> +
>>> +UBOOT_MACHINE = "am67a_beagley_ai_r5_defconfig"
>>> diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti.conf b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>> new file mode 100644
>>> index 00000000..088cbd62
>>> --- /dev/null
>>> +++ b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>> @@ -0,0 +1,16 @@
>>> +#@TYPE: Machine
>>> +#@NAME: BeagleY-AI (A53)
>>> +#@DESCRIPTION: Machine configuration for the BeagleY-AI (A53)
>>> +
>>> +require conf/machine/include/j722s.inc
>>> +
>>> +KERNEL_DEVICETREE_PREFIX = " \
>>> +    ti/k3-am67a \
>>> +    ti/k3-j722s \
>>> +"
>>> +
>>> +KERNEL_DEVICETREE = " \
>>> +    ti/k3-am67a-beagley-ai.dtb \
>>> +"
>>> +
>>> +UBOOT_MACHINE = "am67a_beagley_ai_a53_defconfig"
>>
>> This defconfig doesn't work if you select an older BSP.
>>
>> Thinking on this, the only difference we should have between this machine
>> config and the one already in meta-beagle is the default selected BSP
>> (bsp-ti-6_12 vs bb_org-6_12). Why can't we just have the one config and
>> select the BSP with TI_PREFERRED_BSP? We could do that externally
>> from the build env, or with a branding.
>>
>> The issue with this patch is we would now have two configs for the same
>> hardware, and there is no TI produced BeagleY, so having the machine
>> config for it in this layer just seems wrong. I have the same complaint
>> for beagleplay-ti and beaglebadge-ti, we should drop those too and fix
>> them in the same way.
> 
> The difference between the two platforms is that one is supported by TI and one is not.  We do not answer questions or support the meta-beagle boards.  Those are supported by the community (aka Denys).  But the beagleplay-ti board using the TI kernel and TI uboot is supported.  We will answer questions about them.
> 

And selecting TI kernel and TI uboot is done by simply setting
TI_PREFERRED_BSP = "ti-6_12", why do we need to clone files for this?

> It was a decision from Sitara management to do this.
> 

To do what? Support BeagleY, sure that is fine, we also support Wayland
for instance, but we don't go and clone it and rebrand it Wayland-TI™.

We support community projects by working in those communities, in this
case the community project is "meta-beagle". So let's add support for
our TI BSP to that project, not fork bits of it into our meta-ti project.

Anyway to close the loop on the two threads,

> I don't necessarily hate that idea. Guessing this is hinging on Andrew's idea of
> overriding the BSP provider variable directly for our internal testing?

We could at very least start with this "beagley-ai-ti.conf" do nothing but
the following two lines:

require meta-beagle/conf/machine/beagley-ai.conf
TI_PREFERRED_BSP = "ti-6_18"

This would remove any duplication at least, but does introduce a reverse
dependency from meta-ti towards meta-beagle. So the first option of a
BSP provider override as needed is still my strong preference.

Andrew

> That's why we name them differently to draw a distinction between the two.
> 
> 
>> Andrew
>>
>>>
>>>
>>>
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>> Links: You receive all messages sent to this group.
>>> View/Reply Online (#19562): https://lists.yoctoproject.org/g/meta-ti/message/19562
>>> Mute This Topic: https://lists.yoctoproject.org/mt/117964418/3619733
>>> Group Owner: meta-ti+owner@lists.yoctoproject.org
>>> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [afd@ti.com]
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>>
>>
>
Randolph Sapp Feb. 23, 2026, 10:44 p.m. UTC | #9 
On Mon Feb 23, 2026 at 4:35 PM CST, Randolph Sapp via lists.yoctoproject.org wrote:
> On Mon Feb 23, 2026 at 4:31 PM CST, Ryan Eatmon wrote:
>>
>>
>> On 2/23/2026 4:27 PM, Randolph Sapp wrote:
>>> On Mon Feb 23, 2026 at 3:54 PM CST, Ryan Eatmon wrote:
>>>>
>>>>
>>>> On 2/23/2026 3:51 PM, Andrew Davis wrote:
>>>>> On 2/23/26 2:22 PM, Randolph Sapp via lists.yoctoproject.org wrote:
>>>>>> From: Randolph Sapp <rs@ti.com>
>>>>>>
>>>>>> Add a TI configuration for the BeagleY-AI development board.
>>>>>>
>>>>>> Signed-off-by: Randolph Sapp <rs@ti.com>
>>>>>> ---
>>>>>>    meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf |  7 +++++++
>>>>>>    meta-ti-bsp/conf/machine/beagley-ai-ti.conf      | 16 ++++++++++++++++
>>>>>>    2 files changed, 23 insertions(+)
>>>>>>    create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>>>>>    create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>>>>>
>>>>>> diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>>>>> b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>>>>> new file mode 100644
>>>>>> index 00000000..88d0888b
>>>>>> --- /dev/null
>>>>>> +++ b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>>>>> @@ -0,0 +1,7 @@
>>>>>> +#@TYPE: Machine
>>>>>> +#@NAME: BeagleY-AI (R5F)
>>>>>> +#@DESCRIPTION: Machine configuration for the BeagleY-AI (R5F core)
>>>>>> +
>>>>>> +require conf/machine/include/k3r5.inc
>>>>>> +
>>>>>> +UBOOT_MACHINE = "am67a_beagley_ai_r5_defconfig"
>>>>>> diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>>>>> b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>>>>> new file mode 100644
>>>>>> index 00000000..088cbd62
>>>>>> --- /dev/null
>>>>>> +++ b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>>>>> @@ -0,0 +1,16 @@
>>>>>> +#@TYPE: Machine
>>>>>> +#@NAME: BeagleY-AI (A53)
>>>>>> +#@DESCRIPTION: Machine configuration for the BeagleY-AI (A53)
>>>>>> +
>>>>>> +require conf/machine/include/j722s.inc
>>>>>> +
>>>>>> +KERNEL_DEVICETREE_PREFIX = " \
>>>>>> +    ti/k3-am67a \
>>>>>> +    ti/k3-j722s \
>>>>>> +"
>>>>>> +
>>>>>> +KERNEL_DEVICETREE = " \
>>>>>> +    ti/k3-am67a-beagley-ai.dtb \
>>>>>> +"
>>>>>> +
>>>>>> +UBOOT_MACHINE = "am67a_beagley_ai_a53_defconfig"
>>>>>
>>>>> This defconfig doesn't work if you select an older BSP.
>>>>>
>>>>> Thinking on this, the only difference we should have between this machine
>>>>> config and the one already in meta-beagle is the default selected BSP
>>>>> (bsp-ti-6_12 vs bb_org-6_12). Why can't we just have the one config and
>>>>> select the BSP with TI_PREFERRED_BSP? We could do that externally
>>>>> from the build env, or with a branding.
>>>>>
>>>>> The issue with this patch is we would now have two configs for the same
>>>>> hardware, and there is no TI produced BeagleY, so having the machine
>>>>> config for it in this layer just seems wrong. I have the same complaint
>>>>> for beagleplay-ti and beaglebadge-ti, we should drop those too and fix
>>>>> them in the same way.
>>>>
>>>> The difference between the two platforms is that one is supported by TI
>>>> and one is not.  We do not answer questions or support the meta-beagle
>>>> boards.  Those are supported by the community (aka Denys).  But the
>>>> beagleplay-ti board using the TI kernel and TI uboot is supported.  We
>>>> will answer questions about them.
>>>>
>>>> It was a decision from Sitara management to do this.
>>>>
>>>> That's why we name them differently to draw a distinction between the two.
>>>>
>>> 
>>> That really is unfortunate. Inclusion of meta-beagle in meta-ti does not make
>>> that clear, and the layer README(s) don't offer that information freely either.
>>
>> I would rather drop the beagleboard-ti and all TI versions of the beagle 
>> boards and just rely on meta-beagle and what beagle officially supports.
>>
>
> I don't necessarily hate that idea. Guessing this is hinging on Andrew's idea of
> overriding the BSP provider variable directly for our internal testing?

I've been informed that both paths should be easily traversable. It's not just
for testing purposes. As to what should be the default behavior, I'm getting
mixed messages. If we want to unify to a single machine configuration then the
default behavior must be defined.
Randolph Sapp Feb. 23, 2026, 10:59 p.m. UTC | #10 
On Mon Feb 23, 2026 at 4:43 PM CST, Andrew Davis wrote:
> On 2/23/26 3:54 PM, Ryan Eatmon wrote:
>> 
>> 
>> On 2/23/2026 3:51 PM, Andrew Davis wrote:
>>> On 2/23/26 2:22 PM, Randolph Sapp via lists.yoctoproject.org wrote:
>>>> From: Randolph Sapp <rs@ti.com>
>>>>
>>>> Add a TI configuration for the BeagleY-AI development board.
>>>>
>>>> Signed-off-by: Randolph Sapp <rs@ti.com>
>>>> ---
>>>>   meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf |  7 +++++++
>>>>   meta-ti-bsp/conf/machine/beagley-ai-ti.conf      | 16 ++++++++++++++++
>>>>   2 files changed, 23 insertions(+)
>>>>   create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>>>   create mode 100644 meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>>>
>>>> diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>>> new file mode 100644
>>>> index 00000000..88d0888b
>>>> --- /dev/null
>>>> +++ b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
>>>> @@ -0,0 +1,7 @@
>>>> +#@TYPE: Machine
>>>> +#@NAME: BeagleY-AI (R5F)
>>>> +#@DESCRIPTION: Machine configuration for the BeagleY-AI (R5F core)
>>>> +
>>>> +require conf/machine/include/k3r5.inc
>>>> +
>>>> +UBOOT_MACHINE = "am67a_beagley_ai_r5_defconfig"
>>>> diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti.conf b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>>> new file mode 100644
>>>> index 00000000..088cbd62
>>>> --- /dev/null
>>>> +++ b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
>>>> @@ -0,0 +1,16 @@
>>>> +#@TYPE: Machine
>>>> +#@NAME: BeagleY-AI (A53)
>>>> +#@DESCRIPTION: Machine configuration for the BeagleY-AI (A53)
>>>> +
>>>> +require conf/machine/include/j722s.inc
>>>> +
>>>> +KERNEL_DEVICETREE_PREFIX = " \
>>>> +    ti/k3-am67a \
>>>> +    ti/k3-j722s \
>>>> +"
>>>> +
>>>> +KERNEL_DEVICETREE = " \
>>>> +    ti/k3-am67a-beagley-ai.dtb \
>>>> +"
>>>> +
>>>> +UBOOT_MACHINE = "am67a_beagley_ai_a53_defconfig"
>>>
>>> This defconfig doesn't work if you select an older BSP.
>>>
>>> Thinking on this, the only difference we should have between this machine
>>> config and the one already in meta-beagle is the default selected BSP
>>> (bsp-ti-6_12 vs bb_org-6_12). Why can't we just have the one config and
>>> select the BSP with TI_PREFERRED_BSP? We could do that externally
>>> from the build env, or with a branding.
>>>
>>> The issue with this patch is we would now have two configs for the same
>>> hardware, and there is no TI produced BeagleY, so having the machine
>>> config for it in this layer just seems wrong. I have the same complaint
>>> for beagleplay-ti and beaglebadge-ti, we should drop those too and fix
>>> them in the same way.
>> 
>> The difference between the two platforms is that one is supported by TI and one is not.  We do not answer questions or support the meta-beagle boards.  Those are supported by the community (aka Denys).  But the beagleplay-ti board using the TI kernel and TI uboot is supported.  We will answer questions about them.
>> 
>
> And selecting TI kernel and TI uboot is done by simply setting
> TI_PREFERRED_BSP = "ti-6_12", why do we need to clone files for this?
>
>> It was a decision from Sitara management to do this.
>> 
>
> To do what? Support BeagleY, sure that is fine, we also support Wayland
> for instance, but we don't go and clone it and rebrand it Wayland-TI™.
>
> We support community projects by working in those communities, in this
> case the community project is "meta-beagle". So let's add support for
> our TI BSP to that project, not fork bits of it into our meta-ti project.
>
> Anyway to close the loop on the two threads,
>
>> I don't necessarily hate that idea. Guessing this is hinging on Andrew's idea of
>> overriding the BSP provider variable directly for our internal testing?
>
> We could at very least start with this "beagley-ai-ti.conf" do nothing but
> the following two lines:
>
> require meta-beagle/conf/machine/beagley-ai.conf
> TI_PREFERRED_BSP = "ti-6_18"
>
> This would remove any duplication at least, but does introduce a reverse
> dependency from meta-ti towards meta-beagle. So the first option of a
> BSP provider override as needed is still my strong preference.
>
> Andrew
>

I'd almost prefer we move all the beagle-ti configs back into meta-beagle and do
that override there. Makes the layer dependency tree more reasonable and
provides logical isolation from meta-ti and meta-beagle devices.

I'll draft that. Doesn't seem so awful.

>> That's why we name them differently to draw a distinction between the two.
diff mbox series

Patch

diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
new file mode 100644
index 00000000..88d0888b
--- /dev/null
+++ b/meta-ti-bsp/conf/machine/beagley-ai-ti-k3r5.conf
@@ -0,0 +1,7 @@ 
+#@TYPE: Machine
+#@NAME: BeagleY-AI (R5F)
+#@DESCRIPTION: Machine configuration for the BeagleY-AI (R5F core)
+
+require conf/machine/include/k3r5.inc
+
+UBOOT_MACHINE = "am67a_beagley_ai_r5_defconfig"
diff --git a/meta-ti-bsp/conf/machine/beagley-ai-ti.conf b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
new file mode 100644
index 00000000..088cbd62
--- /dev/null
+++ b/meta-ti-bsp/conf/machine/beagley-ai-ti.conf
@@ -0,0 +1,16 @@ 
+#@TYPE: Machine
+#@NAME: BeagleY-AI (A53)
+#@DESCRIPTION: Machine configuration for the BeagleY-AI (A53)
+
+require conf/machine/include/j722s.inc
+
+KERNEL_DEVICETREE_PREFIX = " \
+    ti/k3-am67a \
+    ti/k3-j722s \
+"
+
+KERNEL_DEVICETREE = " \
+    ti/k3-am67a-beagley-ai.dtb \
+"
+
+UBOOT_MACHINE = "am67a_beagley_ai_a53_defconfig"