public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Su Baocheng <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 5/7] Add recipe for optee ftpm
Date: Thu, 22 Jun 2023 08:40:32 +0200	[thread overview]
Message-ID: <32057ee9-5986-eb43-bafb-44f80c681b80@siemens.com> (raw)
In-Reply-To: <9a5eccff-1747-f437-f802-9b09235e2f3e@163.com>

On 22.06.23 08:21, Su Baocheng wrote:
> 
> 
> On 2023/6/22 14:02, Jan Kiszka wrote:
>> On 21.06.23 21:22, baocheng_su@163.com wrote:
>>> From: Baocheng Su <baocheng.su@siemens.com>
>>>
>>> This integrate Microsoft's reference implementation of the TCG TPM2.0
>>> as an
>>> OPTee trusted application, see [1] and [2] for details, esp.
>>> meta-ts/layers/meta-arm/meta-arm/recipes-security/optee-ftpm
>>>
>>> Since the OPTee secure storage on IOT2050 is RPMB-based, and the RPMB
>>> accessing
>>> is provided by linux tee-supplicant, this TA is only discoverable when
>>> tee-supplicant is running.
>>>
>>> To help to gracefully manage the tee-supplicant, the kernel drive
>>> tpm_ftpm_tee should be compile as .ko and be loaded/unloaded
>>> dynamically.
>>>
>>> [1]: https://github.com/microsoft/ms-tpm-20-ref/
>>> [2]: https://gitlab.com/Linaro/trustedsubstrate/meta-ts
>>>
>>> Signed-off-by: Baocheng Su <baocheng.su@siemens.com>
>>> ---
>>>   .../files/0001-add-enum-to-ta-flags.patch     | 27 +++++++++++
>>>   .../optee-ftpm-stm32mp15x_0~230316+git.bb     | 35 ++++++++++++++
>>
>> The version should probably be 0~20230316+git when following Debian
>> suggestions.
>>
> 
> According to [1], there are two possoble version strings, YYYYMMDD or
> 0~YYMMDD, the later ensures a smooth transition to a normal 0.1 in the
> future when upstreaming starts to use normal version.
> 
> 1. https://www.debian.org/doc/manuals/debmake-doc/ch05.en.html#name-version

Ok, then keep it as it is.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux


  reply	other threads:[~2023-06-22  6:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21 19:22 [PATCH v2 0/7] Add optee family and friends 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 [this message]
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 ` [PATCH v2 0/7] Add optee family and friends Jan Kiszka

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=32057ee9-5986-eb43-bafb-44f80c681b80@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