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, [email protected] wrote: >>>> From: Randolph Sapp <[email protected]> >>>> >>>> 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 <[email protected]> >>>> --- >>>> {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.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19590): https://lists.yoctoproject.org/g/meta-ti/message/19590 Mute This Topic: https://lists.yoctoproject.org/mt/117968156/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
