qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH] docs/system/deprecated: Move lm32 and unicore32 to the right section
Date: Wed, 23 Sep 2020 10:32:44 +0200	[thread overview]
Message-ID: <4586da8f-d5de-4edb-8d70-6bf143bc7adc@redhat.com> (raw)
In-Reply-To: <20200923080015.77373-1-thuth@redhat.com>

On 9/23/20 10:00 AM, Thomas Huth wrote:
> lm32 and unicore32 are softmmut targets, and not linux-user targets.

Typo "softmmu" (else it sounds like soft mammoth targets).

Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>

> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  docs/system/deprecated.rst | 32 ++++++++++++++++----------------
>  1 file changed, 16 insertions(+), 16 deletions(-)
> 
> diff --git a/docs/system/deprecated.rst b/docs/system/deprecated.rst
> index 0cb8b01424..e3dcf1f149 100644
> --- a/docs/system/deprecated.rst
> +++ b/docs/system/deprecated.rst
> @@ -329,6 +329,22 @@ The ``compat`` property used to set backwards compatibility modes for
>  the processor has been deprecated. The ``max-cpu-compat`` property of
>  the ``pseries`` machine type should be used instead.
>  
> +``lm32`` CPUs (since 5.2.0)
> +'''''''''''''''''''''''''''
> +
> +The ``lm32`` guest CPU support is deprecated and will be removed in
> +a future version of QEMU. The only public user of this architecture
> +was the milkymist project, which has been dead for years; there was
> +never an upstream Linux port.
> +
> +``unicore32`` CPUs (since 5.2.0)
> +''''''''''''''''''''''''''''''''
> +
> +The ``unicore32`` guest CPU support is deprecated and will be removed in
> +a future version of QEMU. Support for this CPU was removed from the
> +upstream Linux kernel, and there is no available upstream toolchain
> +to build binaries for it.
> +
>  System emulator devices
>  -----------------------
>  
> @@ -408,22 +424,6 @@ The above, converted to the current supported format::
>  linux-user mode CPUs
>  --------------------
>  
> -``lm32`` CPUs (since 5.2.0)
> -'''''''''''''''''''''''''''
> -
> -The ``lm32`` guest CPU support is deprecated and will be removed in
> -a future version of QEMU. The only public user of this architecture
> -was the milkymist project, which has been dead for years; there was
> -never an upstream Linux port.
> -
> -``unicore32`` CPUs (since 5.2.0)
> -''''''''''''''''''''''''''''''''
> -
> -The ``unicore32`` guest CPU support is deprecated and will be removed in
> -a future version of QEMU. Support for this CPU was removed from the
> -upstream Linux kernel, and there is no available upstream toolchain
> -to build binaries for it.
> -
>  ``tilegx`` CPUs (since 5.1.0)
>  '''''''''''''''''''''''''''''
>  
> 



  reply	other threads:[~2020-09-23  8:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23  8:00 [PATCH] docs/system/deprecated: Move lm32 and unicore32 to the right section Thomas Huth
2020-09-23  8:32 ` Philippe Mathieu-Daudé [this message]
2020-09-23 17:20 ` Laurent Vivier

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=4586da8f-d5de-4edb-8d70-6bf143bc7adc@redhat.com \
    --to=philmd@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).