From: Peter Maydell <peter.maydell@linaro.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Janusz Krzysztofik <jmkrzyszt@gmail.com>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Daniel Mack <daniel@zonque.org>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Thomas Huth <thuth@redhat.com>
Subject: Re: possible deprecation and removal of some old QEMU Arm machine types (pxa2xx, omap, sa1110)
Date: Tue, 15 Oct 2024 18:13:00 +0100 [thread overview]
Message-ID: <CAFEAcA95QmpcsrgCj5uE-Ng8ahNir3MuVEHWBCvjb3UwBbOFRA@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA_-eTfF8tVaLk4yLgWMSA1+KjPBYyS3EjMQNC+59hT0Aw@mail.gmail.com>
On Fri, 8 Mar 2024 at 15:41, Peter Maydell <peter.maydell@linaro.org> wrote:
> Thanks to everybody for your input on this thread. My
> proposal is to drop from QEMU:
> * all the PXA2xx machines
> * all the OMAP2 machines
> * the cheetah OMAP1 machine
>
> leaving (at least for now) sx1, sx1-v1, collie.
This has now gone through. I'm now looking for test images
for these remaining boards, so we can keep them from breaking
when we do refactoring and code cleanup/modernization.
Specifically, I'm looking for:
* QEMU command line
* all the binary blobs that go with it (hosted somewhere that
doesn't mind when our CI downloads all the images to run
its tests...)
* ideally, exercising the SD card interface if present
Could the people who are still using/testing these boards
help here ?
thanks
-- PMM
next prev parent reply other threads:[~2024-10-15 17:14 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 12:32 possible deprecation and removal of some old QEMU Arm machine types (pxa2xx, omap, sa1110) Peter Maydell
2024-02-12 14:03 ` Guenter Roeck
2024-02-12 14:36 ` Guenter Roeck
2024-02-13 13:42 ` Marcin Juszkiewicz
2024-02-13 14:36 ` Guenter Roeck
2024-02-13 15:14 ` Peter Maydell
2024-02-13 15:36 ` Guenter Roeck
2024-02-13 20:11 ` Arnd Bergmann
2024-02-13 21:21 ` Linus Walleij
2024-02-14 10:14 ` Arnd Bergmann
2024-02-14 12:26 ` Dmitry Baryshkov
2024-02-14 13:39 ` Marcin Juszkiewicz
2024-02-14 22:15 ` Andrea Adami
2024-02-14 22:42 ` Arnd Bergmann
2024-02-15 8:31 ` Andreas Kemnade
2024-02-15 8:45 ` Arnd Bergmann
2024-02-15 8:52 ` Dmitry Baryshkov
2024-02-15 10:06 ` Marcin Juszkiewicz
2024-02-15 11:31 ` H. Nikolaus Schaller
2024-02-14 1:27 ` Aaro Koskinen
2024-02-14 5:53 ` Tony Lindgren
2024-02-14 14:57 ` Arnd Bergmann
2024-02-14 9:08 ` Daniel Mack
2024-03-08 15:41 ` Peter Maydell
2024-03-08 15:50 ` Guenter Roeck
2024-10-15 17:13 ` Peter Maydell [this message]
2024-10-15 17:30 ` Guenter Roeck
2024-10-15 17:35 ` Peter Maydell
2024-10-15 18:12 ` Guenter Roeck
2024-10-17 12:42 ` Peter Maydell
2024-10-17 14:12 ` Guenter Roeck
2024-10-17 14:29 ` Peter Maydell
2024-10-17 15:29 ` Guenter Roeck
2024-10-17 16:07 ` Peter Maydell
2024-10-17 17:53 ` Philippe Mathieu-Daudé
2024-02-14 7:37 ` Philippe Mathieu-Daudé
2024-02-14 7:49 ` 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=CAFEAcA95QmpcsrgCj5uE-Ng8ahNir3MuVEHWBCvjb3UwBbOFRA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=aaro.koskinen@iki.fi \
--cc=arnd@arndb.de \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=jmkrzyszt@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=marcin.juszkiewicz@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=robert.jarzmik@free.fr \
--cc=thuth@redhat.com \
--cc=tony@atomide.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).