From: Jan Kiszka <jan.kiszka@siemens.com>
To: baocheng_su@163.com, isar-users@googlegroups.com,
felix.moessbauer@siemens.com
Cc: christian.storm@siemens.com, quirin.gylstorff@siemens.com,
baocheng.su@siemens.com
Subject: Re: [PATCH v2 0/7] Add optee family and friends
Date: Thu, 22 Jun 2023 08:01:31 +0200 [thread overview]
Message-ID: <9f2f2ec7-b4fb-b7d2-6209-fbe98b4a313c@siemens.com> (raw)
In-Reply-To: <20230621192217.2045717-1-baocheng_su@163.com>
On 21.06.23 21:22, baocheng_su@163.com wrote:
> From: Baocheng Su <baocheng.su@siemens.com>
>
> This brings below optee family members:
> optee-ta-devkit, optee-client, optee-examples
> and a fTPM running in optee-os, plus some initramfs hooks for tee-supplicant and
> the optee-ftpm.
>
> The optee-ta-devkit is used to provide a sdk for building trusted application of
> optee.
>
> The optee-client provides the libteec1, the optee-client-dev, and the
> tee-supplicant daemon.
>
> The optee-examples provides both the optee TAs and host applications for
> demostrating how to use optee-ta-devkit and optee-client-dev.
>
> The initramfs hooks for tee-supplicant and optee-ftpm is used to support
> initramfs stage applications that needs the optee-ftpm or other TAs, such as the
> disk encryption based on TPM. An example is the LUKS2 implementation in
> isar-cip-core.
>
> Also bump the stm32mp15x optee-os version to 3.21.0 to ease the integration.
>
> Since these bits are the common foundation for applications based on ARM
> trustzone, isar should be the best place to hold them.
>
> The idea is partly inspired by the ARM trusted substrace.
substract :)
Looks generally good to me now. Maybe we could even move over [1] later
on by using the RPMB or RPMB emulation of the stm32mp15x board.
>
> This integration use stm32mp15x as the demo platform. However, I might need some
> help to verify on the real hardware, since I don't have one :)
We will try to organize this here, maybe even later today.
Thanks,
Jan
[1]
https://gitlab.com/cip-project/cip-core/isar-cip-core/-/tree/master/recipes-bsp/edk2
--
Siemens AG, Technology
Competence Center Embedded Linux
prev parent reply other threads:[~2023-06-22 6:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 19:22 baocheng_su
2023-06-21 19:22 ` [PATCH v2 1/7] stm32mp15x: Bump optee-os to 3.21.0 baocheng_su
2023-06-22 17:50 ` Henning Schild
2023-06-21 19:22 ` [PATCH v2 2/7] Add recipe for optee TA devkit baocheng_su
2023-06-21 19:22 ` [PATCH v2 3/7] Add recipe for optee-client baocheng_su
2023-06-22 5:52 ` Jan Kiszka
2023-06-22 18:00 ` Henning Schild
2023-06-22 18:36 ` Jan Kiszka
2023-06-22 18:43 ` Henning Schild
2023-06-22 20:10 ` Jan Kiszka
2023-06-22 18:02 ` Henning Schild
2023-06-22 18:34 ` Jan Kiszka
2023-06-21 19:22 ` [PATCH v2 4/7] Add recipe for optee examples baocheng_su
2023-06-21 19:22 ` [PATCH v2 5/7] Add recipe for optee ftpm baocheng_su
2023-06-22 6:02 ` Jan Kiszka
2023-06-22 6:21 ` Su Baocheng
2023-06-22 6:40 ` Jan Kiszka
2023-06-21 19:22 ` [PATCH v2 6/7] initramfs: Add recipe for tee-supplicant hook baocheng_su
2023-06-21 19:22 ` [PATCH v2 7/7] initramfs: Add recipe for tee-ftpm hook baocheng_su
2023-06-22 6:01 ` Jan Kiszka [this message]
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=9f2f2ec7-b4fb-b7d2-6209-fbe98b4a313c@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=baocheng.su@siemens.com \
--cc=baocheng_su@163.com \
--cc=christian.storm@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.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