Commit 02a2433c ("ti-sci-fw: Update image gen to latest") switched to a newer commit in k3-image-gen that also picked up TISCI firmware release, However, does include a change where the SPL address ch

This series of updates has completely broken Upstream am64x support. I cant figure out (at least personally) how to make it work consistently. https://git.ti.com/cgit/k3-image-gen/k3-image-gen/commit/

OK. I see now. Thanks for explaining.

Does it make better if we do this in ti-soc.inc ?

^^^ Arrgh, good catch - we are indeed missing am64.. I think we need to drop k2 platforms - they are just bitrotting.. Hmmm.. Your point is to get the weak assignment to allows the critical mach confs

^^ You would want the default behavior as default dtb, not the bloated symbol loaded overlay capable dtb, no? [...] dtc changes are always incoming, does'nt make sense to keep that separated out?

Might be worthwhile to add that enabling overlay support increases the size of the dtb, hence it is done at a platform level rather than globally to allow custom boards derived from meta-ti to not pay

[...] Thinking again - should we make this a little easier in case the future dtc needs more flags? a) KERNEL_HAS_OVERLAYS as a single variable defined in machine.confs b) ti-kernel.inc which introduc

Dont we need to fix up am64x- build?

70 characters wrap please. how about mainline? We dont need this comment every where, do we? Should'nt this be in a common file [...] I wonder if this comes here. KERNEL_EXTRA_ARGS += "${EXTRA_DTC_FLA

Commit 159cdb159ad0 ("perf-tests: add bash into RDEPENDS (v5.12-rc5+)") in upstream openembedded-core layer. Copying over a snippet of description over: Commit 1dc481c0b0cf perf test: Change to use ba

On 19:26-20210503, Denys Dmytriyenko wrote: [..] > > > +RDEPENDS_${PN}-tests =+ "bash" > > Come to think of it, you might want to guard this change to meta-ti platforms: > > +RDEPENDS_${PN}-tests_ti-s

Commit 159cdb159ad0 ("perf-tests: add bash into RDEPENDS (v5.12-rc5+)") in upstream openembedded-core layer. Copying over a snippet of description over: Commit 1dc481c0b0cf perf test: Change to use ba

And lets work with the latest kernel Signed-off-by: Nishanth Menon <nm@...> --- recipes-kernel/linux/linux-ti-mainline_git.bb | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a

Update u-boot recipe to be on the bleeding upstream tag. While at it, also update the u-boot source url to point to the new server as per [1]. While it may be redundant, lets document the usage of URI

since meta-yocto, meta-arago etc use the same meta-ti layer, Could you explain how, in meta-arago/meta-ti am I generating two different wic files with the current patch series? I am probably missing s

Update u-boot recipe to be on the bleeding upstream tag. While at it, also update the u-boot source url to point to the new server as per [1]. [1] https://source.denx.de/u-boot/u-boot/-/commit/a3bbd0b

aah, yes, thanks for pointing it out. v2 incoming.

Update u-boot recipe to be on the bleeding upstream tag. Signed-off-by: Nishanth Menon <nm@...> --- recipes-bsp/u-boot/u-boot-ti-mainline_git.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletion

s/Updtae/Update/ Why are we doing this? What happens to the wic file image? What is the out of box experience for someone creating an SD image -> flash the image then modify the sd card? how would tha