qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	qemu-devel@nongnu.org,
	"Alistair Francis" <alistair.francis@wdc.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	dirty.ice.hu@gmail.com, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Robert Hoo" <robert.hu@linux.intel.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: Let's remove some deprecated stuff
Date: Thu, 29 Apr 2021 15:46:12 +0200	[thread overview]
Message-ID: <20210429134612.rtnoy5yo3v36h4l7@sirius.home.kraxel.org> (raw)
In-Reply-To: <YIqwsUAGEvfazbvZ@merkur.fritz.box>

  Hi,

> Another option might be that you just nest things:
> 
> { 'struct': 'AudioConfig',
>   'data': {
>       'model': 'AudioDevice',
>       'backend': 'Audiodev' } }
> 
> Possibly instead of 'model' on the top level, you'll actually want to
> nest there, too, and accept device properties.

Hmm.  Not so easy I suspect.  While most sound cards map to a single
device there are exceptions.  pcspk is build-in and hda is two devices.

Where do we stand in terms of QAPI support for -device btw?

> If or when I finally get QAPI aliases merged, we can make this look nice
> on the command line again by simply mapping everything to the top level
> so that you don't necessarily need to use dotted keys like you would
> initially, e.g. -audio backend.driver=sdl,model=hda could be optionally
> reduced to -audio driver=sdl,model=hda.

Yes, with aliasing available this would be a reasonable option.

take care,
  Gerd



  reply	other threads:[~2021-04-29 13:52 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 [this message]
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
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=20210429134612.rtnoy5yo3v36h4l7@sirius.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=alistair.francis@wdc.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dirty.ice.hu@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=robert.hu@linux.intel.com \
    --cc=stefanha@redhat.com \
    --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).