Updated the value(s) for:
ti-linux-fw: TI_DM_FW_VERSION,TI_LINUX_FW_SRCREV
u-boot-ti-staging_2023.04: SRCREV
linux-ti-staging-rt_6.1: SRCREV
linux-ti-staging_6.1: SRCREV
Signed-off-by: LCPD Automation Script
---
meta-ti-bsp/recipes-bsp/ti-linux-fw/ti-linux-fw.inc | 4 ++--
Copy the same KERNEL_LOCALVERSION change to the upcoming 6.6 kernel.
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.6.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.6.bb
Stop using UBOOT_LOCALVERSION, and copy what is done in the kernel recipe. This
allows us to set the correct SHA into the version string even if AUTOREV is used
since SRCPV is no longer set in oe-core.
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc | 9 ++---
1
The use of KERNEL_LOCALVERSION for controlling the kernel version has
changed recently. Placing the value of KERNEL_LOCALVERSION in
.scmversion was causing it to duplicate the string in the final version.
Instead, drop KERNEL_LOCALVERSION to just identify that it comes from
TI, and that it is an
From: Denys Dmytriyenko
A change in master from last year [1] dropped setting SRCPV. Since it is now
empty,
we do not need to use when setting PV.
[1]
https://git.openembedded.org/openembedded-core/commit/?id=a8e7b0f932b9ea69b3a218fca18041676c65aba0
Signed-off-by: Ryan Eatmon
