[Buildroot] [RFC, 1/1] configs/am62x-sk: Add fragment for TI tree integration

[Andreas Dannenberg]

On Tue, Apr 30, 2024 at 09:54:48AM -0500, Bryan Brattlof via buildroot wrote:
> On April 29, 2024 thus sayeth Paresh Bhagat via buildroot:
> > This commit introduces a new fragment config aimed at integration of TI trees
> > into the existing configuration for am62x-sk. The fragment config is designed 
> > to be merged with the current ti_am62x_sk_defconfig, enabling transition from 
> > mainline to TI versions for U-boot and kernel.
> > 
> > The fragment config will be merged with existing ti_my_am62x_sk_defconfig
> > using merge-config.sh script present in support/kconfig using following
> > command.
> > 
> > ./support/kconfig/merge-config.sh configs/ti_am62x_sk_defconfig configs/ti_am62x_sk.config

This should be "merge_config.sh".

> > It effectively changes uboot and kernel source from mainline version to TI 
> > version hosted here
> > 
> > https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/?h=ti-linux-6.1.y
> > https://git.ti.com/cgit/ti-u-boot/ti-u-boot/?h=ti-u-boot-2023.04
> > 
> > Furthermore, as ti-uboot 2023.04 is used, kernel Image and dtb is expected 
> > in rootfs/boot/ and rootfs/boot/dtb/ti respectively. So add a new post-build
> > script to copy these files to desired location. 
> > 
> > Signed-off-by: Paresh Bhagat <p-bhagat at ti.com>
> 
> Thanks for the patch. My worry is these changes will only be needed for 
> the brief time the 9.2 SDK is relevant. The 10.X SDK is just around the 
> corner and will break all of this with its new baseline.
> 
> It may be easier to keep these configs all in a custom BR2_EXTERNAL 
> overlay and keep buildroot pointed to pure sources of these packages

Yes Paresh also from my side thanks for the effort you put into this.
After spending some more time on this I tend to agree with Brian that
this should probably not be directly in the official tree to minimize
churn, plus keeping the official Buildroot upstream-only will motivate
us even more to make sure all our device support goes upstream...

All this being said, there is a very common "real world" customer need/
request for a Buildroot-based solution more closely aligned with TI's
official Yocto SDKs. Ideally I'd like to see us providing something via
BR2_EXTERNAL that is well maintained (like other vendors provide), but
until we can close on the best path forward I've updated my already-
existing E2E FAQ [1] to help customers today setting up such a TI Yocto
SDK v9.2 Baseline Equivalent by adding a simple patch to the tree by
themselves. I plan on maintaining this as needed to accommodate for new
SDK releases (and also so people don't always have to resolve merge
conflicts when applying that patch).

--
Andreas Dannenberg
Texas Instruments Inc

[1] https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1226815/faq-buildroot-support-for-sitara-am62x-am62ax-am62px-am64x-devices

> 
> ~Bryan
> 
> _______________________________________________
> buildroot mailing list
> buildroot at buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot