From: "Schultschik, Sven" <sven.schultschik@siemens.com>
To: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"Kiszka, Jan" <jan.kiszka@siemens.com>,
"baocheng.su@siemens.com" <baocheng.su@siemens.com>
Subject: Re: [cip-dev] [isar-cip-core][PATCH 1/8] add recipe for edk2
Date: Wed, 11 Jan 2023 08:47:26 +0000 [thread overview]
Message-ID: <78da801f45f5979321bd4654136bb18628d8a164.camel@siemens.com> (raw)
In-Reply-To: <8a77538b-7676-aeef-d7d3-724cb2edc532@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]
On Mon, 2023-01-09 at 08:40 +0100, Jan Kiszka wrote:
> On 09.01.23 07:42, Su, Bao Cheng (DI FA CTR IPC CN PRC4) wrote:
> > On Sun, 2022-11-20 at 21:47 +0100, Schultschik, Sven via lists.cip-
> > project.org wrote:
> > > From: Sven Schultschik <sven.schultschik@siemens.com>
> > >
> > > provide a recipe to create the BL32_AP_MM.fd binary by edk2 which
> > > is needed for the qemu optee generation as dependency.
>
> Should mention the StandaloneMm for RPMB, what it is and then mention
> where it will be used.
>
> Also adjust the subject - we are not building complete EDK2.
>
> > >
> > > Signed-off-by: Sven Schultschik <sven.schultschik@siemens.com>
> > > ---
> > > .../edk2/edk2-platformstandalonemmrpmb.inc | 56
> > > +++++++++++++++++
> > > .../edk2-platformstandalonemmrpmb_202205.bb | 12 ++++
>
> Recipe name became too unreadable. "edk2-standalonemm-rpmb" maybe? By
> convention, we don't use camel-cases in recipes, so this cannot help
> with separating words.
Made the changes yesterday, but as I can see you already did with the
other patch you send in.
>
> > >
>
> Would be good to clarify how these revisions were selected. Do they
> come
> from the EDK2 build manifest?
Those are submodules. So look into the edk2 repo on the specific
location which version they used in the submodul at the version you
want to use edk2.
>
> > >
>
> > > +export SHELL=/bin/bash
>
> Needed?
Yes. source edk2/edksetup.sh only works under bin/bash
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 7531 bytes --]
next prev parent reply other threads:[~2023-01-11 8:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 20:47 [isar-cip-core][PATCH 0/8] Secureboot on QEMU with EDK2, OP-TEE and RPMB sven.schultschik
2022-11-20 20:47 ` [isar-cip-core][PATCH 1/8] add recipe for edk2 sven.schultschik
2023-01-09 6:42 ` [cip-dev] " Su, Bao Cheng
2023-01-09 7:40 ` Jan Kiszka
2023-01-11 8:47 ` Schultschik, Sven [this message]
2023-01-11 8:37 ` Schultschik, Sven
2022-11-20 20:47 ` [isar-cip-core][PATCH 2/8] add recipe for optee qemu arm64 sven.schultschik
2022-11-20 20:47 ` [isar-cip-core][PATCH 3/8] Include optee into u-boot sven.schultschik
2022-11-20 20:47 ` [isar-cip-core][PATCH 4/8] add u-boot patch for qemu to support RPMB sven.schultschik
2022-11-20 20:47 ` [isar-cip-core][PATCH 5/8] add recipe for trusted firmware a qemu arm64 sven.schultschik
2022-11-20 20:47 ` [isar-cip-core][PATCH 6/8] change ebg sb signer and secrets to pk kek db sven.schultschik
2022-11-21 10:40 ` Jan Kiszka
2022-11-21 15:10 ` AW: " Schultschik, Sven
2022-11-21 17:25 ` Jan Kiszka
2022-11-20 20:47 ` [isar-cip-core][PATCH 7/8] enhance start-qemu.sh for arm64 secure boot sven.schultschik
2022-11-20 20:47 ` [isar-cip-core][PATCH 8/8] Use of snakeoil keys for qemu use case sven.schultschik
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=78da801f45f5979321bd4654136bb18628d8a164.camel@siemens.com \
--to=sven.schultschik@siemens.com \
--cc=baocheng.su@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@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