@@ -122,6 +122,8 @@ BSP_MESA_PVR_VERSION ?= ""
# ==========
PREFERRED_PROVIDER_virtual/kernel ?= "${BSP_KERNEL_PROVIDER}"
PREFERRED_VERSION_${BSP_KERNEL_PROVIDER} ?= "${BSP_KERNEL_VERSION}"
+PREFERRED_VERSION_${BSP_KERNEL_PROVIDER}-rt ?= "${BSP_KERNEL_VERSION}"
+PREFERRED_VERSION_${BSP_KERNEL_PROVIDER}-systest ?= "${BSP_KERNEL_VERSION}"
PREFERRED_PROVIDER_virtual/bootloader ?= "${BSP_BOOTLOADER_PROVIDER}"
PREFERRED_PROVIDER_u-boot ?= "${BSP_BOOTLOADER_PROVIDER}"
PREFERRED_VERSION_${BSP_BOOTLOADER_PROVIDER} ?= "${BSP_BOOTLOADER_VERSION}"
We were missing controlling the versions for linux-ti-staging-rt and linux-ti-staging-systest using the BSP framework. Since the PREFERRED_VERSION is not tied to the virtual/kernel we need two additional settings for those alternate kernel package names. For BSPs that do not have the -rt and -systest recipes then the two new variable settings should effectively be ignored and cause no issues. Signed-off-by: Ryan Eatmon <reatmon@ti.com> --- v3: Typo in commit message. v2: Remove the extra variables and just set PREFERRED_VERSION. meta-ti-bsp/conf/machine/include/ti-bsp.inc | 2 ++ 1 file changed, 2 insertions(+)