From: Peter Maydell <peter.maydell@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Michael Walle" <michael@walle.cc>,
"Daniel P. Berrange" <berrange@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] Deprecate lm32 port
Date: Thu, 27 Aug 2020 15:19:15 +0100 [thread overview]
Message-ID: <CAFEAcA_3fiQ86aby8PALZNUukPE1RhgV+1+hjoEF+aCfCp3mbw@mail.gmail.com> (raw)
In-Reply-To: <8385e0cf-b955-e62d-dfdc-51380b7c5433@redhat.com>
On Thu, 27 Aug 2020 at 14:52, Thomas Huth <thuth@redhat.com> wrote:
> What's next? moxie? ... apart from the tree-wide clean-ups and trivial
> fixes, moxie did not have any major updates since 2013 when it has been
> added, as far as I can see ... is anybody still using it?
I was never very clear on how much use moxie had to start with...
An extremely rough-and-ready guide to how well-loved a target
is might be "did it get converted to TranslatorOps?". Unconverted:
* avr
* cris
* lm32 (deprecation in progress)
* microblaze (rth just posted patches for this)
* moxie
* nios2
* tilegx (deprecation in progress)
* unicore32 (deprecation in progress)
As I say, very rough-and-ready: we have had recent interest in nios2;
avr has just got into the tree so hopefully the maintainer will have
a look at TranslatorOps conversion; Edgar is still around for cris.
I think dropping the moxie maintainer an email to ask about the
architecture's status wouldn't be a bad idea if you wanted to start
that ball rolling.
thanks
-- PMM
next prev parent reply other threads:[~2020-08-27 14:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 11:32 [PATCH] Deprecate lm32 port Peter Maydell
2020-08-27 11:36 ` Daniel P. Berrangé
2020-08-27 12:02 ` Michael Walle
2020-08-31 20:08 ` Philippe Mathieu-Daudé
2020-08-27 13:52 ` Thomas Huth
2020-08-27 14:19 ` Peter Maydell [this message]
2020-08-27 14:50 ` Thomas Huth
2020-08-31 20:11 ` Philippe Mathieu-Daudé
2020-09-23 7:55 ` Thomas Huth
2020-09-23 9:47 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2020-10-12 15:33 [PATCH 00/10] target/arm: Various v8.1M minor features Peter Maydell
2020-10-12 15:33 ` [PATCH] Deprecate lm32 port Peter Maydell
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=CAFEAcA_3fiQ86aby8PALZNUukPE1RhgV+1+hjoEF+aCfCp3mbw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=berrange@redhat.com \
--cc=michael@walle.cc \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).