From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: qemu-arm@nongnu.org
Cc: qemu-devel@nongnu.org, "Beraldo Leal" <bleal@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Leif Lindholm" <quic_llindhol@quicinc.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Radoslaw Biernacki" <rad@semihalf.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Cleber Rosa" <crosa@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>
Subject: [PATCH v2 0/1] tests/avocado: update firmware to enable OpenBSD test on sbsa-ref
Date: Wed, 27 Sep 2023 14:00:49 +0200 [thread overview]
Message-ID: <20230927120050.210187-1-marcin.juszkiewicz@linaro.org> (raw)
I noticed that neither OpenBSD nor FreeBSD ran properly so this change
adds OpenBSD into testing. Instead of adding tests on all cpu cores I
decided to go with small set:
- Cortex-A57 as it is the oldest
- Neoverse-N1 as it is the default one
- max as this one was broken in past
There was a lot of going on in firmware space for SBSA Reference
Platform recently. Updates prebuilt firmware images got new stuff:
- Neoverse V1/N2 cpu support
- non-secure EL2 virtual timer
- XHCI controller in DSDT
With those changes we can now run OpenBSD as part of sbsa-ref tests.
Changes since v1:
- added OpenBSD test
- decided to not run Neoverse-V1 tests
Marcin Juszkiewicz (1):
tests/avocado: update firmware to enable OpenBSD test on sbsa-ref
tests/avocado/machine_aarch64_sbsaref.py | 68 ++++++++++++++++++++----
1 file changed, 58 insertions(+), 10 deletions(-)
--
2.41.0
next reply other threads:[~2023-09-27 12:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 12:00 Marcin Juszkiewicz [this message]
2023-09-27 12:00 ` [PATCH v2 1/1] tests/avocado: update firmware to enable OpenBSD test on sbsa-ref Marcin Juszkiewicz
2023-10-09 13:53 ` Alex Bennée
2023-10-09 15:09 ` Philippe Mathieu-Daudé
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=20230927120050.210187-1-marcin.juszkiewicz@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quic_llindhol@quicinc.com \
--cc=rad@semihalf.com \
--cc=wainersm@redhat.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).