From: Andrew Davis <afd@ti.com>
To: Denys Dmytriyenko <denys@konsulko.com>,
Ryan Eatmon <reatmon@ti.com>, <meta-ti@lists.yoctoproject.org>
Cc: Andrew Davis <afd@ti.com>
Subject: [meta-ti][master/kirkstone][PATCH 8/8] ti-rtos-firmware: Deploy secure firmware unconditionally
Date: Tue, 7 Feb 2023 17:42:39 -0600 [thread overview]
Message-ID: <20230207234239.30720-8-afd@ti.com> (raw)
In-Reply-To: <20230207234239.30720-1-afd@ti.com>
Having signed firmware is needed for the HS platforms, but does not
cause any issues for non-HS. To keep things simple, let's deploy
both sets unconditionally. This prevents mistakes when adding HS
support and further reduces the image delta between the two types.
Signed-off-by: Andrew Davis <afd@ti.com>
---
.../ti-rtos-bin/ti-rtos-firmware.bb | 38 ++-----------------
1 file changed, 4 insertions(+), 34 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 feff39ea..9931cab0 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
@@ -187,7 +187,7 @@ ALTERNATIVE:${PN}:am62xx = "\
am62-main-r5f0_0-fw \
"
-ALTERNATIVE:${PN}:j721e-hs-evm = "\
+ALTERNATIVE:${PN}:j721e = "\
j7-mcu-r5f0_0-fw \
j7-mcu-r5f0_1-fw \
j7-main-r5f0_0-fw \
@@ -206,26 +206,7 @@ ALTERNATIVE:${PN}:j721e-hs-evm = "\
j7-c71_0-fw-sec \
"
-ALTERNATIVE:${PN}:j721e-evm = "\
- j7-mcu-r5f0_0-fw \
- j7-mcu-r5f0_1-fw \
- j7-main-r5f0_0-fw \
- j7-main-r5f0_1-fw \
- j7-main-r5f1_0-fw \
- j7-main-r5f1_1-fw \
- j7-c66_0-fw \
- j7-c66_1-fw \
- j7-c71_0-fw\
- "
-
-ALTERNATIVE:${PN}:j7200-evm = "\
- j7200-mcu-r5f0_0-fw \
- j7200-mcu-r5f0_1-fw \
- j7200-main-r5f0_0-fw \
- j7200-main-r5f0_1-fw \
- "
-
-ALTERNATIVE:${PN}:j7200-hs-evm = "\
+ALTERNATIVE:${PN}:j7200 = "\
j7200-mcu-r5f0_0-fw \
j7200-mcu-r5f0_1-fw \
j7200-main-r5f0_0-fw \
@@ -234,18 +215,7 @@ ALTERNATIVE:${PN}:j7200-hs-evm = "\
j7200-main-r5f0_1-fw-sec \
"
-ALTERNATIVE_${PN}:j721s2-evm = "\
- j721s2-mcu-r5f0_0-fw \
- j721s2-mcu-r5f0_1-fw \
- j721s2-main-r5f0_0-fw \
- j721s2-main-r5f0_1-fw \
- j721s2-main-r5f1_0-fw \
- j721s2-main-r5f1_1-fw \
- j721s2-c71_0-fw \
- j721s2-c71_1-fw \
- "
-
-ALTERNATIVE:${PN}:j721s2-hs-evm = "\
+ALTERNATIVE:${PN}:j721s2 = "\
j721s2-mcu-r5f0_0-fw \
j721s2-mcu-r5f0_1-fw \
j721s2-main-r5f0_0-fw \
@@ -262,7 +232,7 @@ ALTERNATIVE:${PN}:j721s2-hs-evm = "\
j721s2-c71_1-fw-sec \
"
-ALTERNATIVE:${PN}:j784s4-evm = "\
+ALTERNATIVE:${PN}:j784s4 = "\
j784s4-mcu-r5f0_0-fw \
j784s4-mcu-r5f0_1-fw \
j784s4-main-r5f0_0-fw \
--
2.39.1
next prev parent reply other threads:[~2023-02-07 23:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 23:42 [meta-ti][master/kirkstone][PATCH 1/8] ti-rtos-firmware: Use ti-k3-secdev if TI_SECURE_DEV_PKG_K3 not defined Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 2/8] ti-rtos-firmware: Remove unneeded per-machine TARGET defines Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 3/8] ti-rtos-firmware: Fix name for AM64x and AM62x firmware Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 4/8] ti-rtos-firmware: Do not break the source directory by renaming files Andrew Davis
2023-02-10 21:07 ` Denys Dmytriyenko
2023-02-10 21:14 ` Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 5/8] ti-rtos-firmware: Use defines to set firmware names Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 6/8] ti-rtos-firmware: Use a table instead of a list of copy commands Andrew Davis
2023-02-09 13:29 ` Ryan Eatmon
2023-02-09 18:11 ` Andrew Davis
2023-02-10 1:46 ` Ryan Eatmon
2023-02-10 21:23 ` Denys Dmytriyenko
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 7/8] ti-rtos-firmware: Fix use of base_libdir with nonarch_base_libdir Andrew Davis
2023-02-07 23:42 ` Andrew Davis [this message]
2023-02-10 21:02 ` [meta-ti][master/kirkstone][PATCH 1/8] ti-rtos-firmware: Use ti-k3-secdev if TI_SECURE_DEV_PKG_K3 not defined Denys Dmytriyenko
2023-02-10 21:13 ` Andrew Davis
2023-02-10 21:50 ` Denys Dmytriyenko
2023-02-14 9:45 ` Jose Quaresma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230207234239.30720-8-afd@ti.com \
--to=afd@ti.com \
--cc=denys@konsulko.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.