NAK -> I know I authored these initial patches during silicon bringup, but please do squash and cleanup the patches prior to posting upstream.

There is also a public-inbox in kernel.org now at https://lore.kernel.org/yocto-meta-ti/ Thanks Denys and yoctoproject team for all the work in making this happen.

Needs a commit message please. See https://lore.kernel.org/all/20211223121650.26868-3-vigneshr@... The intent is to go with ttyS2 using aliases, however, will use main_usart8 (traditionally ttyS10

When we pickedup the update for u-boot to 2021.10, we needed to drop the hack we put in play for k3-image-gen for AM64x. While at it, we also should have bumped our kernel rev from 5.13 to 5.15. Since

From: Ryan Eatmon <reatmon@...> This adds up numerous fixes for various k3 platforms. While at it, bump the ti-upstream-tools repo as this sync up gives us: config: audio_display: Update cdns-mhdp

This reverts commit d5db41417295fe05a293f6d4d77a65ef6563f6ed. We should'nt have to carry patches for u-boot or kernel, since the upstream is now fixed since 5.14 kernel and u-boot 2021.10 tag onwards,

[1] I'd be guessing, but = instead of ?= ^^ weird "can't set" message.. meta-ti does'nt set the password for poky. [1] https://www.yoctoproject.org/docs/2.4/ref-manual/ref-manual.html#var-EXTRA_IMAGE_

That is because there is a sgx node in device tree, I dont think it has been introduced so far. I remember seeing this before.. I remember there was a bug of SGX support with the driver, essentially i

NAK. Lets not move the mainline meta-ti to RCs - just complete versions.

I dont think this series is sufficient (ti-ipc and ti-prueth pending), but for these specific patches: Reviewed-by: Nishanth Menon <nm@...>

I am not sure I understand how https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/commit/?h=ti-linux-firmware&id=db51751356e9266b330f7a3246c0a8c0d3531757 https://git.ti.com/cgit/processor-fi

If you are picking up eaidk board patches, it will need to be after this.

Update u-boot recipe to be on the latest official upstream tag. This introduces initial support for AM64x which works with v5.13 kernel tag. Reviewed-by: Denys Dmytriyenko <denys@...> Reviewe

Thanks, yes, that is misleading. respinning a v2 out in a moment..

Update u-boot recipe to be on the bleeding upstream tag. This introduces initial support for AM64x which works with v5.13 kernel tag. Signed-off-by: Nishanth Menon <nm@...> --- recipes-bsp/u-boot/u

Just updating imggen to a configuration compatible with latest firmware should not have been accepted, we should have ensured that firmware commit has moved correspondingly as well. Fix the same, else

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

hehe, the history of v5.12-rc1-dontuse comes to mind for now. I think we can leave as is for now.

Yes, this is temporary - at least for one u-boot and kernel window :( Honestly, I am really hoping this entire k3-image-gen stuff gets into u-boot as buildman based solution and we should get rid of t

And lets work with the latest kernel and while at it bump the system up to latest ti-upstream-tools repo to get: * AM65x SR1.0 overlay support * EFI configuration to allow for the eventual support * F