From: Rouven Czerwinski <r.czerwinski@pengutronix.de>
To: meta-arm@lists.yoctoproject.org
Cc: Rouven Czerwinski <r.czerwinski@pengutronix.de>
Subject: [PATCH 3/3] optee-test: add TA elfs to deploydir
Date: Fri, 30 Jun 2023 13:23:41 +0200 [thread overview]
Message-ID: <20230630112340.3314395-3-r.czerwinski@pengutronix.de> (raw)
In-Reply-To: <20230630112340.3314395-1-r.czerwinski@pengutronix.de>
Same as for OP-TEE client, this eases debugging and is required to use
the OP-TEE symbolize.py script.
Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
---
meta-arm/recipes-security/optee/optee-test.inc | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/meta-arm/recipes-security/optee/optee-test.inc b/meta-arm/recipes-security/optee/optee-test.inc
index 64b41a8e..90b72b9f 100644
--- a/meta-arm/recipes-security/optee/optee-test.inc
+++ b/meta-arm/recipes-security/optee/optee-test.inc
@@ -6,6 +6,7 @@ LICENSE = "BSD-2-Clause & GPL-2.0-only"
LIC_FILES_CHKSUM = "file://LICENSE.md;md5=daa2bcccc666345ab8940aab1315a4fa"
inherit python3native ptest
+inherit deploy
require optee.inc
DEPENDS = "optee-client optee-os-tadevkit python3-cryptography-native"
@@ -43,6 +44,13 @@ do_install () {
install -D -p -m0444 ${B}/supp_plugin/*.plugin ${D}${libdir}/tee-supplicant/plugins/
}
+do_deploy () {
+ install -d ${DEPLOYDIR}/${MLPREFIX}optee/ta
+ install -m 644 ${B}/ta/*/*.elf ${DEPLOYDIR}/${MLPREFIX}optee/ta
+}
+
+addtask deploy before do_build after do_install
+
FILES:${PN} += "${nonarch_base_libdir}/optee_armtz/ \
${libdir}/tee-supplicant/plugins/ \
"
--
2.39.2
next prev parent reply other threads:[~2023-06-30 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 11:23 [PATCH 1/3] optee-os: add optional optee-os-ta package Rouven Czerwinski
2023-06-30 11:23 ` [PATCH 2/3] optee-os: deploy ta elf files Rouven Czerwinski
2023-06-30 11:23 ` Rouven Czerwinski [this message]
2023-07-03 22:23 ` [PATCH 1/3] optee-os: add optional optee-os-ta package Jon Mason
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=20230630112340.3314395-3-r.czerwinski@pengutronix.de \
--to=r.czerwinski@pengutronix.de \
--cc=meta-arm@lists.yoctoproject.org \
/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.