From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Rob Landley <rob@landley.net>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Magnus Damm <magnus.damm@gmail.com>
Subject: [PATCH 0/2] Re-enable the sh4eb target
Date: Thu, 24 Oct 2024 10:27:33 +0200 [thread overview]
Message-ID: <20241024082735.42324-1-thuth@redhat.com> (raw)
There are binaries available for sh4 running in big endian mode,
so the assumption that there is no usable machine for sh4eb was
wrong. Thus revert the patch that disabled sh4eb and add a proper
regression test for our CI.
Thomas Huth (2):
Revert "Remove the unused sh4eb target"
tests/functional: Add a test for sh4eb
configs/devices/sh4eb-softmmu/default.mak | 3 +++
configs/targets/sh4eb-softmmu.mak | 2 ++
qapi/machine.json | 2 +-
tests/qtest/endianness-test.c | 1 +
tests/qtest/machine-none-test.c | 1 +
.gitlab-ci.d/buildtest.yml | 2 +-
.gitlab-ci.d/cirrus.yml | 2 +-
.gitlab-ci.d/crossbuilds.yml | 2 +-
.travis.yml | 2 +-
tests/functional/meson.build | 3 +++
tests/functional/test_sh4eb_r2d.py | 33 +++++++++++++++++++++++
tests/qemu-iotests/testenv.py | 1 +
tests/qtest/meson.build | 1 +
13 files changed, 50 insertions(+), 5 deletions(-)
create mode 100644 configs/devices/sh4eb-softmmu/default.mak
create mode 100644 configs/targets/sh4eb-softmmu.mak
create mode 100755 tests/functional/test_sh4eb_r2d.py
--
2.47.0
next reply other threads:[~2024-10-24 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 8:27 Thomas Huth [this message]
2024-10-24 8:27 ` [PATCH 1/2] Revert "Remove the unused sh4eb target" Thomas Huth
2024-10-24 8:46 ` Daniel P. Berrangé
2024-10-25 16:09 ` Rob Landley
2024-10-29 18:35 ` Thomas Huth
2024-10-24 8:27 ` [PATCH 2/2] tests/functional: Add a test for sh4eb Thomas Huth
2024-10-24 17:38 ` Philippe Mathieu-Daudé
2024-10-29 17:58 ` Rob Landley
2024-10-29 18:41 ` Thomas Huth
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=20241024082735.42324-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=magnus.damm@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rob@landley.net \
--cc=ysato@users.sourceforge.jp \
/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).