From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v4 03/11] optee-examples-stm32mp15x: Fix parsing error for non-stm32mp15x machines
Date: Mon, 31 Jul 2023 14:17:21 +0200 [thread overview]
Message-ID: <20230731121729.16972-4-ubely@ilbers.de> (raw)
In-Reply-To: <20230731121729.16972-1-ubely@ilbers.de>
From: Jan Kiszka <jan.kiszka@siemens.com>
Hard-code the machine name so that parsing will not fail if a machine
does not provide optee-os-tadevkit-${MACHINE} or
optee-client-${MACHINE}.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
.../optee-examples/optee-examples-stm32mp15x_3.21.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-isar/recipes-bsp/optee-examples/optee-examples-stm32mp15x_3.21.0.bb b/meta-isar/recipes-bsp/optee-examples/optee-examples-stm32mp15x_3.21.0.bb
index 2a64a86b..e10654e8 100644
--- a/meta-isar/recipes-bsp/optee-examples/optee-examples-stm32mp15x_3.21.0.bb
+++ b/meta-isar/recipes-bsp/optee-examples/optee-examples-stm32mp15x_3.21.0.bb
@@ -16,7 +16,7 @@ SRC_URI[sha256sum] = "9b965f829adc532b5228534d3b9b38ae1fc4f2ac55d73159a39d43e597
S = "${WORKDIR}/optee_examples-${PV}"
-OPTEE_NAME = "${MACHINE}"
+OPTEE_NAME = "stm32mp15x"
OPTEE_PLATFORM = "stm32mp1"
TA_DEV_KIT_DIR = "/usr/lib/optee-os/${OPTEE_NAME}/export-ta_arm32"
--
2.20.1
next prev parent reply other threads:[~2023-07-31 12:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 12:17 [PATCH v4 00/11] Fixes, cleanups and updates for OP-TEE and TAs Uladzimir Bely
2023-07-31 12:17 ` [PATCH v4 01/11] optee-client: Add missing runtime dependency Uladzimir Bely
2023-07-31 12:17 ` [PATCH v4 02/11] optee-client: Unbind ftpm, rather than remove its driver Uladzimir Bely
2023-07-31 12:17 ` Uladzimir Bely [this message]
2023-07-31 12:17 ` [PATCH v4 04/11] linux-mainline: Add fTPM support Uladzimir Bely
2023-07-31 12:17 ` [PATCH v4 05/11] initramfs-tee-{ftpm,supplicant}-hook: Move sync loop to ftpm-hook Uladzimir Bely
2023-07-31 12:17 ` [PATCH v4 06/11] initramfs-tee-supplicant-hook: Account for modular optee Uladzimir Bely
2023-07-31 12:17 ` [PATCH v4 07/11] initramfs-tee-ftpm-hook: Lift timeout to 30 s Uladzimir Bely
2023-07-31 12:17 ` [PATCH v4 08/11] Drop stm32mp15x-initramfs in favor of image enabling Uladzimir Bely
2023-07-31 12:17 ` [PATCH v4 09/11] optee-ftpm-stm32mp15x: Recipe cleanups Uladzimir Bely
2023-07-31 12:17 ` [PATCH v4 10/11] optee-ftpm-stm32mp15x: Update WolfSSL to 5.6.3 Uladzimir Bely
2023-07-31 12:17 ` [PATCH v4 11/11] optee-ftpm-stm32mp15x: Add patch to fix parallel build issues Uladzimir Bely
2023-08-02 4:11 ` [PATCH v4 00/11] Fixes, cleanups and updates for OP-TEE and TAs Uladzimir Bely
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=20230731121729.16972-4-ubely@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox