From: emekcan.aras@arm.com
To: meta-arm@lists.yoctoproject.org
Cc: Emekcan Aras <Emekcan.Aras@arm.com>
Subject: [PATCH 0/3] arm-bsp: corstone1000: Change MM buffer location and enable
Date: Fri, 12 Apr 2024 11:05:24 +0100 [thread overview]
Message-ID: <20240412100527.991610-1-emekcan.aras@arm.com> (raw)
From: Emekcan Aras <Emekcan.Aras@arm.com>
MM Communicate buffer is accessed by normal world but at the moment it's
allocated in the secure ram. This moves mm communicate buffer to the DDR and
configures the host firewall in secure-enclave (for FVP) to ensure that
secure-ram is not accesible by normal-world.
Emekcan Aras (3):
arm-bsp/u-boot: corstone1000: Change MMCOMM buffer location
arm-bsp/trusted-services: corstone1000: Change MM comm buffer location
arm-bsp/trusted-firmware-m: corstone1000: Enable host firewall in FVP
...tone1000-Enable-host-firewall-in-FVP.patch | 177 ++++++++++++++++++
.../trusted-firmware-m-corstone1000.inc | 1 +
.../u-boot/u-boot-corstone1000.inc | 1 +
...ne1000-Change-MMCOMM-buffer-location.patch | 47 +++++
.../trusted-services/libts_%.bbappend | 2 +-
.../ts-sp-se-proxy_%.bbappend | 2 +-
.../ts-sp-smm-gateway_%.bbappend | 2 +-
7 files changed, 229 insertions(+), 3 deletions(-)
create mode 100644 meta-arm-bsp/recipes-bsp/trusted-firmware-m/files/corstone1000/0008-Platform-Corstone1000-Enable-host-firewall-in-FVP.patch
create mode 100644 meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/0045-Corstone1000-Change-MMCOMM-buffer-location.patch
--
2.25.1
next reply other threads:[~2024-04-12 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 10:05 emekcan.aras [this message]
2024-04-12 10:05 ` [PATCH 1/3] arm-bsp/u-boot: corstone1000: Change MMCOMM buffer location emekcan.aras
2024-04-12 10:05 ` [PATCH 2/3] arm-bsp/trusted-services: corstone1000: Change MM comm " emekcan.aras
2024-04-12 10:05 ` [PATCH 3/3] arm-bsp/trusted-firmware-m: corstone1000: Enable host firewall in FVP emekcan.aras
2024-04-16 2:17 ` [PATCH 0/3] arm-bsp: corstone1000: Change MM buffer location and enable Jon Mason
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=20240412100527.991610-1-emekcan.aras@arm.com \
--to=emekcan.aras@arm.com \
--cc=meta-arm@lists.yoctoproject.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).