From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, Radoslaw Biernacki <rad@semihalf.com>,
Leif Lindholm <quic_llindhol@quicinc.com>,
qemu-arm@nongnu.org
Subject: Re: [PATCH 1/1] tests/avocado: update sbsa-ref firmware
Date: Tue, 17 Dec 2024 08:10:29 +0100 [thread overview]
Message-ID: <7d5f349e-761c-459c-93db-cc32ec2a207d@linaro.org> (raw)
In-Reply-To: <CAFEAcA_SRU5UtttB=G2=L2YSK2D1U7Rumbc6eafioxR3yfnYUQ@mail.gmail.com>
W dniu 16.12.2024 o 13:46, Peter Maydell pisze:
> On Mon, 25 Nov 2024 at 13:25, Peter Maydell <peter.maydell@linaro.org> wrote:
>>
>> On Mon, 25 Nov 2024 at 12:54, Marcin Juszkiewicz
>> <marcin.juszkiewicz@linaro.org> wrote:
>>>
>>> Firmware is built using Debian 'bookworm' cross toolchain (gcc 12.2.0).
>>>
>>> Used versions:
>>>
>>> - Trusted Firmware v2.12.0
>>> - Tianocore EDK2 stable202411
>>> - Tianocore EDK2 Platforms code commit 4b3530d
>>>
>>> Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
>>
>> Hi; what's the benefit to taking this update? Would it be better
>> postponed until the 9.2 release is complete?
>
> We're now past the 9.2 release, but it would still be good
> to know what the benefit to updating the firmware images
> for this test is.
We tend to update firmware to the latest in all places it is used.
Previous one was built from pre-selected git commits due to changes done
during cycle.
Now we got both components (TF-A and EDK2) from stable releases.
next prev parent reply other threads:[~2024-12-17 7:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 12:54 [PATCH 1/1] tests/avocado: update sbsa-ref firmware Marcin Juszkiewicz
2024-11-25 13:25 ` Peter Maydell
2024-12-16 12:46 ` Peter Maydell
2024-12-17 7:10 ` Marcin Juszkiewicz [this message]
2024-12-17 15:24 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2024-05-28 18:29 Marcin Juszkiewicz
2024-05-29 13:12 ` Leif Lindholm
2024-05-29 13:37 ` Marcin Juszkiewicz
2024-05-29 15:34 ` Alex Bennée
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=7d5f349e-761c-459c-93db-cc32ec2a207d@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quic_llindhol@quicinc.com \
--cc=rad@semihalf.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;
as well as URLs for NNTP newsgroup(s).