Update to v2.4 tag merge from upstream to keep TF-A in sync. For major changes in trusted-firmware-a, See: https://trustedfirmware-a.readthedocs.io/en/latest/change-log.html#version-2-4 TI specific fi

aha... ofcourse.. Gee thanks. V2 coming right up.

Update to v2.4 tag merge from upstream to keep TF-A in sync. For major changes in trusted-firmware-a, See: https://trustedfirmware-a.readthedocs.io/en/latest/change-log.html#version-2-4 TI specific fi

Update to v2.4 tag merge from upstream to keep TF-A in sync. For major changes in trusted-firmware-a, See: https://trustedfirmware-a.readthedocs.io/en/latest/change-log.html#version-2-4 TI specific fi

ROFL... that will help.. hehe.. I am getting the hard way into learning OE layers :).. Thanks for looking out for us. s/LIC_FILES_CHKSUM/LIC_FILES_CHKSUM_k3 coming right up..

Update to v2.4 tag merge from upstream to keep TF-A in sync. For major changes in trusted-firmware-a, See: https://trustedfirmware-a.readthedocs.io/en/latest/change-log.html#version-2-4 TI specific fi

Hmm.. good idea.. but it was'nt present before.. so i could state something as follows in the commit message: ---- While at it, update to include PV_k3 as 2.4. We use PV_k3 instead of PV since this al

I did check.. https://github.com/ARM-software/arm-trusted-firmware/commits/master/license.rst There is nothing changed since the original inception other than document optimization, definitely nothing

Update to v2.4 tag merge from upstream to keep TF-A in sync. For major changes in trusted-firmware-a, See: https://trustedfirmware-a.readthedocs.io/en/latest/change-log.html#version-2-4 TI specific fi

This would need to be https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2020.01&id=c32cf0dd6bc60911927548ad20973c71fce95661 please update.

Should be https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/commit/?h=ti-linux-firmware&id=078c1bbf3d0a05b4045d4091c32e91ee1ae15ff8 Also Noticed in the recipes-bsp/ti-sci-fw/ti-sci-fw_git.b

Dan, Assuming you have taken care of all the topics we have discussed in thread.. we should be good.

Hi, A series of minimal patches to bump up recision to the latest kernel -> we will need to maintain upstream-tools and kernel in sync on all branches involved ofcourse. NOTE: with kernels > 5.9 (aka

Bump up our recipe version for ti-upstream-tools for updates in config files needed for latest kernel Signed-off-by: Nishanth Menon <nm@...> --- recipes-kernel/linux/linux-ti-mainline_git.bb | 2 +-

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

hehe.. indeed. I had intended PR as in Pull Request[2] to indicate the specific pull request, I now realize it is easy to mix it up against product revision as well.. ooops.. Yup, that was my thought

"evm" prefix messes up the pattern matchup for J7200 and falls back into default, as a result, we attempt to pull [1] instead of [2]. [1] https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jac

^^ above link should have been: https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/firmware/07_03_00_10/coresdk_rtos_j7200_07_03_00_10_firmware.tar.xz if you need me to send a v2 with

I believe _j7 does matchup j7200, hence it works and adding _j7200 will be redundant.. DEFAULT_RTOS_WEBLINK_j7 = "https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/firmware/${CORESDK

Probably addressed in u-boot instead by [1] ? [1] https://source.denx.de/u-boot/u-boot/-/commit/20c37fb1bfb9f20804645b2199699cd815a4d55c