From: Gerd Hoffmann <kraxel@redhat.com>
To: Kamil Rytarowski <n54@gmx.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Kamil Rytarowski" <kamil@netbsd.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Brad Smith" <brad@comstyle.com>
Subject: Re: [Qemu-devel] [PATCH 4/4] [RfC] audio: probe audio drivers by default
Date: Wed, 23 Jan 2019 13:20:15 +0100 [thread overview]
Message-ID: <20190123122015.uvyqe4vsxhhgugz7@sirius.home.kraxel.org> (raw)
In-Reply-To: <52937a07-9462-6910-610c-5b1ee5d2541a@gmx.com>
Hi,
> Pulseaudio uses OSS backend on NetBSD anyway and we keep an in-kernel
> mixer. So it adds nothing except additional intermediate layer.
>
> For non-professional audio purposes OSS is good enough for such
> applications.
What happens if pulseaudio is running and using the sound device? Can
qemu open and use the device in parallel? "in-kernel mixer" sounds like
this is works and the kernel mixes the streams from all applications
before sending it to the sound device. Or will qemu get a -EBUSY?
If parallel usage works we can default to oss I think. Otherwise we
should try pulse first, and in case it is not available (daemon not
running) try oss next.
What about sdl? Prefer oss over sdl I guess? Or the other way around?
What is the native sound interface for openbsd btw? oss doesn't
compile (missing sys/soundcard.h header).
cheers,
Gerd
next prev parent reply other threads:[~2019-01-23 12:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 8:00 [Qemu-devel] [PATCH 0/4] audio: rework driver probing Gerd Hoffmann
2019-01-23 8:00 ` [Qemu-devel] [PATCH 1/4] audio: use pkg-config Gerd Hoffmann
2019-01-23 8:30 ` Thomas Huth
2019-01-23 8:00 ` [Qemu-devel] [PATCH 2/4] audio: allow optional audio drivers Gerd Hoffmann
2019-01-23 8:00 ` [Qemu-devel] [PATCH 3/4] audio: use try-sdl and try-pa for openbsd Gerd Hoffmann
2019-01-23 8:00 ` [Qemu-devel] [PATCH 4/4] [RfC] audio: probe audio drivers by default Gerd Hoffmann
2019-01-23 8:27 ` Thomas Huth
2019-01-23 9:36 ` Daniel P. Berrangé
2019-01-23 9:50 ` Thomas Huth
2019-01-23 10:12 ` Daniel P. Berrangé
2019-01-23 10:36 ` Kamil Rytarowski
2019-01-23 10:59 ` Peter Maydell
2019-01-23 11:10 ` Kamil Rytarowski
2019-01-23 11:16 ` Peter Maydell
2019-01-23 11:30 ` Kamil Rytarowski
2019-01-23 12:20 ` Gerd Hoffmann [this message]
2019-01-23 12:45 ` Kamil Rytarowski
2019-01-23 13:59 ` Gerd Hoffmann
2019-01-23 14:45 ` Kamil Rytarowski
2019-01-23 14:54 ` Brad Smith
2019-01-23 15:12 ` Gerd Hoffmann
2019-01-23 15:20 ` Kamil Rytarowski
2019-01-24 6:38 ` Gerd Hoffmann
2019-01-24 6:51 ` Thomas Huth
2019-01-24 10:06 ` Kamil Rytarowski
2019-01-23 10:16 ` Kamil Rytarowski
2019-01-23 10:24 ` Gerd Hoffmann
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=20190123122015.uvyqe4vsxhhgugz7@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=berrange@redhat.com \
--cc=brad@comstyle.com \
--cc=kamil@netbsd.org \
--cc=n54@gmx.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--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 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).