From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io, marcin.juszkiewicz@linaro.org
Cc: Leif Lindholm <quic_llindhol@quicinc.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>
Subject: Re: [edk2-devel] [PATCH edk2-non-osi 1/1] Qemu/Sbsa: Update TF-A binaries for Neoverse-V1 support
Date: Thu, 27 Jul 2023 16:27:19 +0200 [thread overview]
Message-ID: <CAMj1kXHQjmb_sG7bHMAjWDxfOt8NRRGFNuM2Tzk_LzSi3w+Dbw@mail.gmail.com> (raw)
In-Reply-To: <20230714130321.986014-1-marcin.juszkiewicz@linaro.org>
On Fri, 14 Jul 2023 at 15:03, Marcin Juszkiewicz
<marcin.juszkiewicz@linaro.org> wrote:
>
> Update the TF-A binaries to have Neoverse-V1 cpu support.
>
> This support was merged into TF-A:
>
> https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/21813
>
> This allows SBSA Reference Platform to boot Linux on "neoverse-v1" cpu.
>
> Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
> ---
> Platform/Qemu/Sbsa/Readme.md | 23 +++++++++++------------
> Platform/Qemu/Sbsa/bl1.bin | Bin 19413 -> 19557 bytes
> Platform/Qemu/Sbsa/fip.bin | Bin 58098 -> 66338 bytes
> 3 files changed, 11 insertions(+), 12 deletions(-)
>
Pushed as f0bb00937ad6bfdf..648aa9ee26926f33
Thanks,
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#107302): https://edk2.groups.io/g/devel/message/107302
Mute This Topic: https://groups.io/mt/100140603/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2023-07-27 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 13:03 [PATCH edk2-non-osi 1/1] Qemu/Sbsa: Update TF-A binaries for Neoverse-V1 support Marcin Juszkiewicz
2023-07-27 14:27 ` Ard Biesheuvel [this message]
[not found] <1771BD9CD048C62D.3749@groups.io>
2023-07-26 11:54 ` [edk2-devel] " Marcin Juszkiewicz
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=CAMj1kXHQjmb_sG7bHMAjWDxfOt8NRRGFNuM2Tzk_LzSi3w+Dbw@mail.gmail.com \
--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