All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	QEMU Developers <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Michael Walle <michael@walle.cc>
Subject: Re: Deprecation of the LM32 target
Date: Sat, 26 Dec 2020 09:39:49 +0100	[thread overview]
Message-ID: <86690c16-3bc9-9c77-f720-64db14d0cf72@redhat.com> (raw)
In-Reply-To: <49c3d04e-a94c-cf77-4df9-5ceb8c9c7f80@physik.fu-berlin.de>

On 24/12/2020 10.53, John Paul Adrian Glaubitz wrote:
> Hello!
> 
> I was just browsing through the QEMU Christmas Calendar [1] and noticed
> the announcement for the deprecation of the LM32 target.
> 
> I'm not sure what the motivation of the deprecation is, but isn't one of
> the big selling points of QEMU to support deprecated targets?
> 
> If QEMU eventually ends up supporting commercially available targets only
> and kicking out everything that is obsolete, I'm not sure what the point
> of QEMU would be in the first place as products like VMWare and VirtualBox
> already provide virtualization functionality.
> 
> Please don't deprecate targets just because they're old.

  Hi,

the problem is not that the target CPU is old, but rather that according to 
the (former?) maintainer, there are no users left:

  https://www.mail-archive.com/qemu-devel@nongnu.org/msg605024.html

So it got marked as deprecated in this commit here:

  https://git.qemu.org/?p=qemu.git;a=commitdiff;h=d84980051229fa43c96b3

Without maintainer and without users, there is no point in keeping this 
target, is there?

  Thomas



  reply	other threads:[~2020-12-26  8:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24  9:53 Deprecation of the LM32 target John Paul Adrian Glaubitz
2020-12-26  8:39 ` Thomas Huth [this message]
2020-12-26  9:06   ` John Paul Adrian Glaubitz
2020-12-26 11:50     ` Michael Walle
2020-12-29 10:38     ` Thomas Huth
2020-12-30 16:34       ` 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=86690c16-3bc9-9c77-f720-64db14d0cf72@redhat.com \
    --to=thuth@redhat.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=michael@walle.cc \
    --cc=peter.maydell@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.