From: sven.schultschik@siemens.com
To: cip-dev@lists.cip-project.org
Cc: jan.kiszka@siemens.com, Sven Schultschik <sven.schultschik@siemens.com>
Subject: [isar-cip-core][PATCH 6/8] add kas files for building qemu secure boot images
Date: Mon, 24 Oct 2022 14:27:23 +0200 [thread overview]
Message-ID: <20221024122725.383791-7-sven.schultschik@siemens.com> (raw)
In-Reply-To: <20221024122725.383791-1-sven.schultschik@siemens.com>
From: Sven Schultschik <sven.schultschik@siemens.com>
The u-boot-efi-ebg-op-tee-qemu kas file combines the different recipes to create an image which can be booted with qemu and provides secure boot with EBG, TFA, u-boot, UEFI, EDK2, OPTEE and RPMB
Signed-off-by: Sven Schultschik <sven.schultschik@siemens.com>
---
kas/opt/u-boot-efi-ebg-op-tee-qemu.yml | 11 +++++++++++
1 file changed, 11 insertions(+)
create mode 100644 kas/opt/u-boot-efi-ebg-op-tee-qemu.yml
diff --git a/kas/opt/u-boot-efi-ebg-op-tee-qemu.yml b/kas/opt/u-boot-efi-ebg-op-tee-qemu.yml
new file mode 100644
index 000000000..0558c8e79
--- /dev/null
+++ b/kas/opt/u-boot-efi-ebg-op-tee-qemu.yml
@@ -0,0 +1,11 @@
+header:
+ version: 10
+ includes:
+ - kas/board/qemu-arm64.yml
+ - kas/opt/5.10.yml
+ - kas/opt/bullseye.yml
+ - kas/opt/ebg-secure-boot-snakeoil.yml
+
+local_conf_header:
+ trusted-firmware-a-qemu-arm64: |
+ IMAGE_INSTALL_append = " trusted-firmware-a-qemu-arm64"
\ No newline at end of file
--
2.30.2
next prev parent reply other threads:[~2022-10-24 12:28 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 12:27 [isar-cip-core][PATCH 0/8] Secureboot on QEMU with EDK2, OP-TEE and RPBM sven.schultschik
2022-10-24 12:27 ` [isar-cip-core][PATCH 1/8] add recipe for edk2 sven.schultschik
2022-10-25 8:23 ` Su, Bao Cheng
2022-10-26 14:44 ` AW: " Schultschik, Sven
2022-10-27 1:39 ` Su, Bao Cheng
2022-10-27 16:14 ` AW: " Schultschik, Sven
2022-10-27 17:08 ` Jan Kiszka
2022-10-25 8:40 ` Su, Bao Cheng
2022-10-24 12:27 ` [isar-cip-core][PATCH 2/8] add recipe for optee qemu arm64 sven.schultschik
2022-10-24 12:27 ` [isar-cip-core][PATCH 3/8] Include optee into u-boot sven.schultschik
2022-10-26 7:36 ` Su, Bao Cheng
2022-10-26 8:52 ` Jan Kiszka
2022-10-26 15:27 ` AW: " Schultschik, Sven
2022-10-26 16:00 ` Jan Kiszka
2022-11-07 16:57 ` AW: " Schultschik, Sven
2022-11-07 17:50 ` Jan Kiszka
2022-11-10 11:01 ` AW: " Schultschik, Sven
2022-11-10 13:38 ` Jan Kiszka
2022-10-24 12:27 ` [isar-cip-core][PATCH 4/8] add u-boot patch for qemu to support RPMB sven.schultschik
2022-10-24 12:27 ` [isar-cip-core][PATCH 5/8] add recipe for trusted firmware a qemu arm64 sven.schultschik
2022-10-28 5:50 ` Jan Kiszka
2022-10-28 15:46 ` AW: " Schultschik, Sven
2022-10-28 19:10 ` Jan Kiszka
2022-10-24 12:27 ` sven.schultschik [this message]
2022-10-27 17:17 ` [isar-cip-core][PATCH 6/8] add kas files for building qemu secure boot images Jan Kiszka
2022-11-07 10:43 ` AW: " Schultschik, Sven
2022-11-07 12:59 ` Jan Kiszka
2022-10-24 12:27 ` [isar-cip-core][PATCH 7/8] enhance start-qemu.sh for arm64 secure boot sven.schultschik
2022-10-24 12:27 ` [isar-cip-core][PATCH 8/8] no merge - manually instructions test " sven.schultschik
2022-10-25 8:36 ` Su, Bao Cheng
2022-10-25 15:23 ` AW: " Schultschik, Sven
2022-10-25 8:09 ` [isar-cip-core][PATCH 0/8] Secureboot on QEMU with EDK2, OP-TEE and RPBM Su, Bao Cheng
2022-10-25 8:16 ` 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=20221024122725.383791-7-sven.schultschik@siemens.com \
--to=sven.schultschik@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