summaryrefslogtreecommitdiffstats
path: root/meta-ti-bsp/recipes-ti
diff options
context:
space:
mode:
authorAndrew Davis <afd@ti.com>2022-03-25 13:41:48 -0500
committerRyan Eatmon <reatmon@ti.com>2022-03-29 07:33:57 -0500
commit8cc837d2384d441e56b5006acf9b60503a0a5c8c (patch)
tree29de60889b65d8e511b583e5feb8be0a1ed9c1bc /meta-ti-bsp/recipes-ti
parentf1b6ff15039c9f0b8e93d70856fb566a16cb099b (diff)
downloadmeta-ti-8cc837d2384d441e56b5006acf9b60503a0a5c8c.tar.gz
meta-ti: rename j7-evm to j721e-evm
In many places we use "j7" the family when we should be using a specific SoC or EVM and vice-versa. For instance when including graphics drivers we add for all "j7" family, but what we really want is only for some specific j7 SoC. First step in untangling this is to make it clear that there is no SoC called j7. There is a SoC called j721e with a j721e-evm. Fix up this naming here. Signed-off-by: Andrew Davis <afd@ti.com> Tested-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Diffstat (limited to 'meta-ti-bsp/recipes-ti')
-rw-r--r--meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb2
1 files changed, 1 insertions, 1 deletions
diff --git a/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb b/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
index 8aa823cc..03408528 100644
--- a/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
+++ b/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
@@ -49,7 +49,7 @@ LEGACY_DM_FW_DIR = "${D}${nonarch_base_libdir}/firmware/pdk-ipc/"
49DM_FIRMWARE = "ipc_echo_testb_mcu1_0_release_strip.xer5f" 49DM_FIRMWARE = "ipc_echo_testb_mcu1_0_release_strip.xer5f"
50 50
51# J7 HS support 51# J7 HS support
52do_install:prepend:j7-hs-evm() { 52do_install:prepend:j721e-hs-evm() {
53 export TI_SECURE_DEV_PKG=${TI_SECURE_DEV_PKG} 53 export TI_SECURE_DEV_PKG=${TI_SECURE_DEV_PKG}
54 ( cd ${RTOS_DM_FW_DIR}; \ 54 ( cd ${RTOS_DM_FW_DIR}; \
55 mv ${DM_FIRMWARE} ${DM_FIRMWARE}.unsigned; \ 55 mv ${DM_FIRMWARE} ${DM_FIRMWARE}.unsigned; \