public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: baocheng.su@siemens.com
To: isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, felix.moessbauer@siemens.com,
	christian.storm@siemens.com, quirin.gylstorff@siemens.com,
	baocheng_su@163.com, henning.schild@siemens.com,
	baocheng.su@siemens.com
Subject: [PATCH v3 1/7] stm32mp15x: Bump optee-os to 3.21.0
Date: Wed,  5 Jul 2023 13:33:34 +0800	[thread overview]
Message-ID: <20230705053340.1158024-2-baocheng.su@siemens.com> (raw)
In-Reply-To: <20230705053340.1158024-1-baocheng.su@siemens.com>

From: Baocheng Su <baocheng.su@siemens.com>

Signed-off-by: Baocheng Su <baocheng.su@siemens.com>
---
 ...s-stm32mp15x_3.11.0.bb => optee-os-stm32mp15x_3.21.0.bb} | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
 rename meta-isar/recipes-bsp/optee-os/{optee-os-stm32mp15x_3.11.0.bb => optee-os-stm32mp15x_3.21.0.bb} (77%)

diff --git a/meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.11.0.bb b/meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.21.0.bb
similarity index 77%
rename from meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.11.0.bb
rename to meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.21.0.bb
index 08676be..14485f4 100644
--- a/meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.11.0.bb
+++ b/meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.21.0.bb
@@ -1,16 +1,16 @@
 #
-# Copyright (c) Siemens AG, 2020
+# Copyright (c) Siemens AG, 2020-2023
 #
 # SPDX-License-Identifier: MIT
 
 require recipes-bsp/optee-os/optee-os-custom.inc
 
 SRC_URI += "https://github.com/OP-TEE/optee_os/archive/${PV}.tar.gz"
-SRC_URI[sha256sum] = "3c34eda1052fbb9ed36fcfdfaecfd2685023b9290670c1a5982f8a0457bfd2cb"
+SRC_URI[sha256sum] = "92a16e841b0bdb4bfcb1c20b6a1bd3309092203d534ed167dfdb5a5f395bf60b"
 
 S = "${WORKDIR}/optee_os-${PV}"
 
-DEBIAN_BUILD_DEPENDS += ", device-tree-compiler"
+DEBIAN_BUILD_DEPENDS += ", device-tree-compiler, python3-cryptography:native"
 
 OPTEE_PLATFORM = "stm32mp1"
 OPTEE_EXTRA_BUILDARGS = " \
-- 
2.39.2


  reply	other threads:[~2023-07-05  5:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05  5:33 [PATCH v3 0/7] Add optee family and friends baocheng.su
2023-07-05  5:33 ` baocheng.su [this message]
2023-07-05  5:33 ` [PATCH v3 2/7] Add recipe for optee TA devkit baocheng.su
2023-07-05  5:33 ` [PATCH v3 3/7] Add recipe for optee-client baocheng.su
2023-07-06  5:35   ` Uladzimir Bely
2023-07-06  6:56     ` Jan Kiszka
2023-07-12 12:17   ` Jan Kiszka
2023-07-05  5:33 ` [PATCH v3 4/7] Add recipe for optee examples baocheng.su
2023-07-05  5:33 ` [PATCH v3 5/7] Add recipe for optee ftpm baocheng.su
2023-07-12 12:16   ` Jan Kiszka
2023-07-05  5:33 ` [PATCH v3 6/7] initramfs: Add recipe for tee-supplicant hook baocheng.su
2023-07-17 16:09   ` Jan Kiszka
2023-07-05  5:33 ` [PATCH v3 7/7] initramfs: Add recipe for tee-ftpm hook baocheng.su
2023-07-11  6:43 ` [PATCH v3 0/7] Add optee family and friends 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=20230705053340.1158024-2-baocheng.su@siemens.com \
    --to=baocheng.su@siemens.com \
    --cc=baocheng_su@163.com \
    --cc=christian.storm@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=quirin.gylstorff@siemens.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