All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Thomas Huth <thuth@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: Deprecation of the LM32 target
Date: Sat, 26 Dec 2020 12:50:32 +0100	[thread overview]
Message-ID: <57299bc6cf222a3e9b71fd26d81cd3e3@walle.cc> (raw)
In-Reply-To: <d8bbe81c-3446-8d83-3f34-f29156cf4f01@physik.fu-berlin.de>

Hi,

Am 2020-12-26 10:06, schrieb John Paul Adrian Glaubitz:
> Hello!
> 
> On 12/26/20 9:39 AM, Thomas Huth wrote:
>> 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?
> 
> I'm not sure how you determine whether there are people using the code
> or not. There
> is no really user tracking in QEMU, is there?

That is correct, one cannot know if there are actually users of the
milkymist board or the lattice eval board. These are the two only
supported boards. The (or I should better say "my") main purpose to
add a qemu target for milkymist was to help the developers of the
board, e.g. to ease debugging, etc. But development has stopped
long time ago [1]. I've never seen a request to add a new board.

> And the maintainer's claim that RISC-V takes over makes no sense
> either.

I've meant the ecosystem around the SoC. LM32 on linux never took of,
mostly because there is no MMU (we've worked on one though). There is
no official lm32 support in linux and g++ support is broken (or never
even worked). While for RISC-V there is huge userbase building all sorts
of tooling.

There is a project called LiteX [2], some sort of toolbox to build your
own SoC, which supports the LM32 as a CPU component. But I've never seen
anyone trying to add a board to qemu.

> The point of
> emulators is to be able to run old and existing software. If a target 
> had only a
> justification to exist while it's commercially viable, you would have
> to remove 90% of the targets in QEMU.
> I mean, the whole point of an emulator is being able to run existing
> code on modern hardware,
> usually because the old hardware is no longer available. And as long
> as the target is
> functional, I don't see a point in taking away the functionality.

I'm not arguing against this. In fact, I'd also like to keep the lm32
qemu target, but I personally don't have any time for that anymore. And
I don't know if its fair to put the burdon of unmaintained boards to all
the qemu developers. There are a lot of test cases for the LM32
target, but these only cover the CPU instructions. The last time I've
looked audio was broken. So without anyone caring about the target, it
won't also be much help for the user either.

-michael

[1] 
https://github.com/m-labs/milkymist/commit/7d944d3dcffb5e528a44937b10123ff65a0aecbc
[2] https://github.com/enjoy-digital/litex


  reply	other threads:[~2020-12-26 11:57 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
2020-12-26  9:06   ` John Paul Adrian Glaubitz
2020-12-26 11:50     ` Michael Walle [this message]
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=57299bc6cf222a3e9b71fd26d81cd3e3@walle.cc \
    --to=michael@walle.cc \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=peter.maydell@linaro.org \
    --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 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.