On Thu, May 04, 2023 at 08:06:32PM +0530, Nitin Yadav wrote: > Hi Tom, > > TI has one SDK release per SoC. If we go this way we will have to release > multiple SDK release for each board. It doesn't seem feasible to release > different SDK based on same SoC as we have other boards based on AM62x SoC > which we planning to add upstream support in future. In past, we followed > similar for jacinto platforms. > > The Xilinx way you have mentioned won't work for TI as Xilinx has only one > platform for upstream support. > > I can evm.c changes to different files under board detection macro > "CONFIG_TI_I2C_BOARD_DETECT" in different file to keep board code clean and > easy to follow.
You lost the rest of my context, since this wasn't in reply to where I explained what I think will work better, long term, for everyone. But, I'm not sure you're right about needing to make multiple SDKs since they're OpenEmbedded based and there's already support for building multiple configs for a single MACHINE target, which is essentially what you would need to do to support N kits with a single more generic and easily re-usable board config. -- Tom
signature.asc
Description: PGP signature
