From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH 00/11] Support for building TF-A and OP-TEE, add STM32MP15x board
Date: Tue, 13 Oct 2020 09:50:17 +0200 [thread overview]
Message-ID: <cover.1602575428.git.jan.kiszka@siemens.com> (raw)
This adds include files for building custom Trusted Firmware A and Open
Portable Trusted Execution Environment, similar to U-Boot. As a
demonstration target, support for the STM32MP15x board is added, and its
boot is enabled for both TF-a and OP-TEE.
Jan
Jan Kiszka (11):
meta-isar: Lift de0-nano-soc build to buster
meta-isar: linux-mainline: Update to latest 5.4.70
meta-isar: u-boot: Update to 2020.10
meta-isar: u-boot: Factor our de0-nano-soc recipe
meta-isar: example-raw: Purge securetty from target image
Add STM32MP15x eval board
Add recipe include for building custom Trusted Firmware A
stm32mp15x: Switch to TF-A based boot
Add recipe include for building custom OP-TEE
meta-isar: linux-mainline: Add patches for stm32mp15x target
meta-isar: Add OP-TEE to STM32MP15x board
meta-isar/conf/local.conf.sample | 3 +-
meta-isar/conf/machine/de0-nano-soc.conf | 1 +
meta-isar/conf/machine/stm32mp15x.conf | 19 +++++
.../conf/multiconfig/de0-nano-soc-buster.conf | 7 ++
.../multiconfig/de0-nano-soc-stretch.conf | 7 --
.../conf/multiconfig/stm32mp15x-buster.conf | 7 ++
.../recipes-app/example-raw/files/postinst | 3 +
.../optee-os/optee-os-stm32mp15x_3.10.0.bb | 19 +++++
.../trusted-firmware-a-stm32mp15x_2.3.bb | 21 +++++
.../recipes-bsp/u-boot/u-boot-2020.10.inc | 13 +++
.../u-boot/u-boot-de0-nano-soc_2020.10.bb | 9 +++
.../u-boot/u-boot-stm32mp15x_2020.10.bb | 6 ++
.../recipes-bsp/u-boot/u-boot_2018.09.bb | 14 ----
...d-OP-TEE-node-and-its-reserved-memor.patch | 79 +++++++++++++++++++
...move-reserve-memory-holes-on-stm32mp.patch | 65 +++++++++++++++
...ine_5.4.10.bb => linux-mainline_5.4.70.bb} | 6 +-
.../lib/wic/canned-wks/stm32mp15x.wks.in | 16 ++++
meta/recipes-bsp/optee-os/files/debian/compat | 1 +
.../optee-os/files/debian/control.tmpl | 10 +++
meta/recipes-bsp/optee-os/files/debian/rules | 19 +++++
meta/recipes-bsp/optee-os/optee-os-custom.inc | 43 ++++++++++
.../trusted-firmware-a/files/debian/compat | 1 +
.../files/debian/control.tmpl | 10 +++
.../trusted-firmware-a/files/debian/rules | 19 +++++
.../trusted-firmware-a-custom.inc | 43 ++++++++++
scripts/ci_build.sh | 5 +-
26 files changed, 420 insertions(+), 26 deletions(-)
create mode 100644 meta-isar/conf/machine/stm32mp15x.conf
create mode 100644 meta-isar/conf/multiconfig/de0-nano-soc-buster.conf
delete mode 100644 meta-isar/conf/multiconfig/de0-nano-soc-stretch.conf
create mode 100644 meta-isar/conf/multiconfig/stm32mp15x-buster.conf
create mode 100644 meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.10.0.bb
create mode 100644 meta-isar/recipes-bsp/trusted-firmware-a/trusted-firmware-a-stm32mp15x_2.3.bb
create mode 100644 meta-isar/recipes-bsp/u-boot/u-boot-2020.10.inc
create mode 100644 meta-isar/recipes-bsp/u-boot/u-boot-de0-nano-soc_2020.10.bb
create mode 100644 meta-isar/recipes-bsp/u-boot/u-boot-stm32mp15x_2020.10.bb
delete mode 100644 meta-isar/recipes-bsp/u-boot/u-boot_2018.09.bb
create mode 100644 meta-isar/recipes-kernel/linux/files/0001-ARM-dts-stm32-add-OP-TEE-node-and-its-reserved-memor.patch
create mode 100644 meta-isar/recipes-kernel/linux/files/0002-ARM-dts-stm32-remove-reserve-memory-holes-on-stm32mp.patch
rename meta-isar/recipes-kernel/linux/{linux-mainline_5.4.10.bb => linux-mainline_5.4.70.bb} (78%)
create mode 100644 meta-isar/scripts/lib/wic/canned-wks/stm32mp15x.wks.in
create mode 100644 meta/recipes-bsp/optee-os/files/debian/compat
create mode 100644 meta/recipes-bsp/optee-os/files/debian/control.tmpl
create mode 100755 meta/recipes-bsp/optee-os/files/debian/rules
create mode 100644 meta/recipes-bsp/optee-os/optee-os-custom.inc
create mode 100644 meta/recipes-bsp/trusted-firmware-a/files/debian/compat
create mode 100644 meta/recipes-bsp/trusted-firmware-a/files/debian/control.tmpl
create mode 100755 meta/recipes-bsp/trusted-firmware-a/files/debian/rules
create mode 100644 meta/recipes-bsp/trusted-firmware-a/trusted-firmware-a-custom.inc
--
2.26.2
next reply other threads:[~2020-10-13 7:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 7:50 Jan Kiszka [this message]
2020-10-13 7:50 ` [PATCH 01/11] meta-isar: Lift de0-nano-soc build to buster Jan Kiszka
2020-10-13 7:50 ` [PATCH 02/11] meta-isar: linux-mainline: Update to latest 5.4.70 Jan Kiszka
2020-10-13 7:50 ` [PATCH 03/11] meta-isar: u-boot: Update to 2020.10 Jan Kiszka
2020-10-13 7:50 ` [PATCH 04/11] meta-isar: u-boot: Factor our de0-nano-soc recipe Jan Kiszka
2020-10-13 7:50 ` [PATCH 05/11] meta-isar: example-raw: Purge securetty from target image Jan Kiszka
2020-10-13 7:50 ` [PATCH 06/11] Add STM32MP15x eval board Jan Kiszka
2020-10-13 7:50 ` [PATCH 07/11] Add recipe include for building custom Trusted Firmware A Jan Kiszka
2020-10-13 7:50 ` [PATCH 08/11] stm32mp15x: Switch to TF-A based boot Jan Kiszka
2020-10-13 7:50 ` [PATCH 09/11] Add recipe include for building custom OP-TEE Jan Kiszka
2020-10-13 7:50 ` [PATCH 10/11] meta-isar: linux-mainline: Add patches for stm32mp15x target Jan Kiszka
2020-10-13 7:50 ` [PATCH 11/11] meta-isar: Add OP-TEE to STM32MP15x board Jan Kiszka
2020-10-13 8:01 ` [PATCH 00/11] Support for building TF-A and OP-TEE, add " 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=cover.1602575428.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.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