qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Alistair Francis <alistair23@gmail.com>,
	Markus Armbruster <armbru@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	"Robert Hoo" <robert.hu@linux.intel.com>,
	"Alistair Francis" <alistair.francis@wdc.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	dirty.ice.hu@gmail.com, "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: Let's remove some deprecated stuff
Date: Mon, 3 May 2021 06:49:07 +0200	[thread overview]
Message-ID: <17b136e5-5811-27e2-224a-47795eb68bb5@redhat.com> (raw)
In-Reply-To: <CAKmqyKPYu1Y5EaAvVgB9U4kCh4yBJG_75r6ivdvMuZDN6F3ZcQ@mail.gmail.com>

On 03/05/2021 03.41, Alistair Francis wrote:
> On Thu, Apr 29, 2021 at 8:00 PM Markus Armbruster <armbru@redhat.com> wrote:
>>
>> If you're cc'ed, you added a section to docs/system/deprecated.rst that
>> is old enough to permit removal.  This is *not* a demand to remove, it's
>> a polite request to consider whether the time for removal has come.
>> Extra points for telling us in a reply.  "We should remove, but I can't
>> do it myself right now" is a valid answer.  Let's review the file:
>>
>>      System emulator command line arguments
>>      --------------------------------------
>>
>> Kővágó, Zoltán:
>>
>>      ``QEMU_AUDIO_`` environment variables and ``-audio-help`` (since 4.0)
>>      '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
>>
>>      The ``-audiodev`` argument is now the preferred way to specify audio
>>      backend settings instead of environment variables.  To ease migration to
>>      the new format, the ``-audiodev-help`` option can be used to convert
>>      the current values of the environment variables to ``-audiodev`` options.
>>
>> Kővágó, Zoltán:
>>
>>      Creating sound card devices and vnc without ``audiodev=`` property (since 4.2)
>>      ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
>>
>>      When not using the deprecated legacy audio config, each sound card
>>      should specify an ``audiodev=`` property.  Additionally, when using
>>      vnc, you should specify an ``audiodev=`` property if you plan to
>>      transmit audio through the VNC protocol.
>>
>> Gerd Hoffmann:
>>
>>      Creating sound card devices using ``-soundhw`` (since 5.1)
>>      ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
>>
>>      Sound card devices should be created using ``-device`` instead.  The
>>      names are the same for most devices.  The exceptions are ``hda`` which
>>      needs two devices (``-device intel-hda -device hda-duplex``) and
>>      ``pcspk`` which can be activated using ``-machine
>>      pcspk-audiodev=<name>``.
>>
>> [...]
>>
>> Alistair Francis:
>>
>>      RISC-V ``-bios`` (since 5.1)
>>      ''''''''''''''''''''''''''''
>>
>>      QEMU 4.1 introduced support for the -bios option in QEMU for RISC-V for the
>>      RISC-V virt machine and sifive_u machine. QEMU 4.1 had no changes to the
>>      default behaviour to avoid breakages.
>>
>>      QEMU 5.1 changes the default behaviour from ``-bios none`` to ``-bios default``.
>>
>>      QEMU 5.1 has three options:
>>       1. ``-bios default`` - This is the current default behavior if no -bios option
>>            is included. This option will load the default OpenSBI firmware automatically.
>>            The firmware is included with the QEMU release and no user interaction is
>>            required. All a user needs to do is specify the kernel they want to boot
>>            with the -kernel option
>>       2. ``-bios none`` - QEMU will not automatically load any firmware. It is up
>>            to the user to load all the images they need.
>>       3. ``-bios <file>`` - Tells QEMU to load the specified file as the firmwrae.
>>
> 
> This has already been acted upon in the code, we now default to
> including a "bios" with RISC-V softmmu which is what this is
> describing.
> 
> Do we need to take any action to indicate that it's already in effect?

deprecated.rst is mainly thought for the things that only have been marked 
as deprecated, but not changed yet. Once it's done, the items normally get 
moved to docs/system/removed-features.rst instead.

  Thomas



  reply	other threads:[~2021-05-03  4:50 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29  9:59 Let's remove some deprecated stuff Markus Armbruster
2021-04-29 10:18 ` Gerd Hoffmann
2021-04-29 10:24   ` Daniel P. Berrangé
2021-04-29 10:29     ` Peter Maydell
2021-04-29 10:35       ` Daniel P. Berrangé
2021-04-29 10:55         ` Gerd Hoffmann
2021-04-30 10:47           ` Markus Armbruster
2021-04-29 11:07         ` Paolo Bonzini
2021-04-29 10:25 ` Peter Maydell
2021-04-29 10:32 ` Daniel P. Berrangé
2021-04-30  6:47   ` Markus Armbruster
2021-04-29 11:06 ` Paolo Bonzini
2021-04-29 12:40   ` Gerd Hoffmann
2021-04-29 13:12     ` Kevin Wolf
2021-04-29 13:46       ` Gerd Hoffmann
2021-04-29 15:05         ` Philippe Mathieu-Daudé
2021-04-30  7:01           ` Markus Armbruster
2021-04-30  7:01           ` Gerd Hoffmann
2021-05-03 15:10     ` Paolo Bonzini
2021-04-29 11:17 ` Thomas Huth
2021-04-29 11:24   ` Peter Maydell
2021-05-03 10:39     ` Markus Armbruster
2021-04-29 14:49 ` Stefan Hajnoczi
2021-04-29 16:32 ` Eduardo Habkost
2021-04-30  3:22 ` Robert Hoo
2021-05-03  1:41 ` Alistair Francis
2021-05-03  4:49   ` Thomas Huth [this message]
2021-05-03  7:12     ` Alistair Francis
2021-05-03 15:13       ` Paolo Bonzini
2021-05-03 22:57         ` Alistair Francis
2021-05-03 13:14 ` Philippe Mathieu-Daudé
2021-05-03 18:21 ` Eric Blake
2021-05-04 13:59   ` Peter Krempa

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=17b136e5-5811-27e2-224a-47795eb68bb5@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=alistair.francis@wdc.com \
    --cc=alistair23@gmail.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dirty.ice.hu@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=robert.hu@linux.intel.com \
    --cc=stefanha@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).