From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Guenter Roeck <linux@roeck-us.net>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: Is anybody still using the "highbank" or "midway" QEMU machines?
Date: Mon, 2 Jun 2025 18:20:16 +0200 [thread overview]
Message-ID: <1a5e1073-f624-4429-a7ca-6a5500fe036d@redhat.com> (raw)
In-Reply-To: <CAFEAcA_0Hu8+G50sy0FJ2rX-=cNymLddDdrS2nN5ZY-doKiT8w@mail.gmail.com>
On 02/06/2025 17.31, Peter Maydell wrote:
> On Mon, 2 Jun 2025 at 15:24, Guenter Roeck <linux@roeck-us.net> wrote:
>> On 5/30/25 07:23, Thomas Huth wrote:
>>> I was trying to create a functional test for the "highbank" and
>>> "midway" arm machines of QEMU, and only succeeded after lots of
>>> trial and error to boot something on the "highbank" machine.
>>> Peter mentioned on IRC that he also does not test these machines
>>> by default, so we started wondering whether anybody is still
>>> using these machines? If not, we should maybe start the
>>> deprecation process for those instead?
>
>> I don't try to boot midway anymore. Commit log shows:
>>
>> midway only works with an antique version of qemu. Stop testing it.
>>
>> That was back in 2021. The log shows that it needs qemu v3.0.
>
> Might have been fixed by QEMU commit 61b82973e in 2022, which says
> # This change fixes in passing booting on the 'midway' board model,
> # which has been completely broken since we added support for Hyp
> # mode to the Cortex-A15 CPU
FWIW, I can now boot the midway machine at least to a shell prompt with the
latest version of QEMU: Grab the "Trusty Midway" images that are linked from
https://wiki.ubuntu.com/ARM/Server/Install/Calxeda ... unfortunately, there
is no dtb available, but you can use dtc to compile
arch/arm/boot/dts/calxeda/ecx-2000.dts from the Linux kernel sources into a
dtb file that seems to work. Then run QEMU like this:
qemu-system-arm -M midway -nographic -kernel vmlinuz \
-initrd initrd.gz -m 2047 -dtb ecx-2000.dtb \
-append "console=ttyAMA0 init=/bin/sh"
>> I only test highbank manually (not in automated tests). I have this in my code:
>>
>> # highbank boots with updated (local version of) qemu,
>> # but generates warnings to the console due to ignored SMC calls.
>>
>> I have not run the manual test for ages, so I have no idea if it still works.
>> It also looks like I removed the local changes. Those were needed to enable basic
>> SMC support for highbank; maybe similar code is now upstream.
>
>> Ok for me to remove both. Not worth the trouble.
>
> Cool. I don't think these machine types provide anything to
> users that is particularly interesting (if you just want
> "boot an A15 or A9 Linux" then the virt board will do fine,
> and the original "test system software for this hardware"
> use case is long dead). So I'm in favour of deprecating
> these (and eventually dropping them).
>
> There's not actually a lot of highbank/midway specific code
> here (no complex SoC modelling, lots of stock Arm peripheral
> devices, so just 400 lines in hw/arm/highbank.c, plus another
> 450 in hw/net/xgmac.c for the ethernet controller), but
> if nobody's using it then there's no point keeping it around.
I think I could also try to create a functional test with above images, but
if nobody is really using these machines, deprecation likely makes more
sense, indeed ... do you want me to create one of those two patches?
Thomas
next prev parent reply other threads:[~2025-06-02 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 14:23 Is anybody still using the "highbank" or "midway" QEMU machines? Thomas Huth
2025-06-02 14:24 ` Guenter Roeck
2025-06-02 15:31 ` Peter Maydell
2025-06-02 16:20 ` Thomas Huth [this message]
2025-06-02 15:51 ` Warner Losh
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=1a5e1073-f624-4429-a7ca-6a5500fe036d@redhat.com \
--to=thuth@redhat.com \
--cc=linux@roeck-us.net \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).