From: "Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>
To: devel@edk2.groups.io
Cc: Leif Lindholm <quic_llindhol@quicinc.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Graeme Gregory <graeme@xora.org.uk>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Subject: [edk2-devel] [PATCH edk2-non-osi 0/1] Qemu/Sbsa: Update TF-A binaries
Date: Wed, 20 Sep 2023 13:44:22 +0200 [thread overview]
Message-ID: <20230920114423.386360-1-marcin.juszkiewicz@linaro.org> (raw)
Update the TF-A binaries to have:
- fixed FIP size
- Neoverse-N2 cpu support
This support was merged into TF-A:
https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/23417
(align FIP base to BL1 size)
https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/23409
(add "neoverse-n2" cpu support)
FIP size was too small to fit TF-A debug builds with RME (WIP) support
enabled. We need it to merge fixed FIP size in EDK2-platforms.
CPU enablement allows SBSA Reference Platform to boot Linux on
"neoverse-n2" cpu.
Marcin Juszkiewicz (1):
Qemu/Sbsa: Update TF-A binaries
Platform/Qemu/Sbsa/License.txt | 2 +-
Platform/Qemu/Sbsa/Readme.md | 52 ++++++++++++++++++++++++---------
Platform/Qemu/Sbsa/bl1.bin | Bin 19557 -> 22933 bytes
Platform/Qemu/Sbsa/fip.bin | Bin 66338 -> 82722 bytes
4 files changed, 40 insertions(+), 14 deletions(-)
--
2.41.0
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#108906): https://edk2.groups.io/g/devel/message/108906
Mute This Topic: https://groups.io/mt/101476431/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~2023-09-20 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 11:44 Marcin Juszkiewicz [this message]
2023-09-20 11:44 ` [edk2-devel] [PATCH edk2-non-osi 1/1] Qemu/Sbsa: Update TF-A binaries Marcin Juszkiewicz
2023-09-20 19:26 ` [edk2-devel] [PATCH edk2-non-osi 0/1] " Leif Lindholm
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-list 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=20230920114423.386360-1-marcin.juszkiewicz@linaro.org \
--to=devel@edk2.groups.io \
/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