From: Kamil Rytarowski <n54@gmx.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Brad Smith" <brad@comstyle.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Kamil Rytarowski" <kamil@netbsd.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 4/4] [RfC] audio: probe audio drivers by default
Date: Thu, 24 Jan 2019 11:06:52 +0100 [thread overview]
Message-ID: <bd206be0-3e7e-ad5c-f497-dc28b1904311@gmx.com> (raw)
In-Reply-To: <20190124063851.zhjlx5oigvri4r64@sirius.home.kraxel.org>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
On 24.01.2019 07:38, Gerd Hoffmann wrote:
> Hi,
>
>>> https://xkcd.com/927/
>>
>> There is a different context on BSD than on Linux. We can choose one
>> solution and switch to it literally all the software keeping everything
>> in a single ports tree.
>>
>> This is what happened on OpenBSD.
>>
>> The result is that almost everything uses sndio, and pulseaudio is far
>> behind in adoption in any distro.
>
> I'm not going to join the sndio vs. pulse discussion.
>
> But from a maintenance point of view it sucks big time to have a bunch
> of ways to play sound, and everybody uses a different one so you have to
> maintain a backend for each of those methods.
>
> Maybe we should outsource that problem. Write a gstreamer backend, then
> delete oss/alsa/sdl/pulse/whatever backends and let gstreamer handle
> that mess ...
>
Just please leave it to OS maintainers.
There is no fragmentation in BSD distributions so sndio isn't different
to native sound system on Darwin or Windows and I see no complains that
Windows does not adapt PulseAudio. (Probably the only practical
difference is BSD being open-source.)
> cheers,
> Gerd
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 850 bytes --]
next prev parent reply other threads:[~2019-01-24 10:21 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
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 [this message]
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=bd206be0-3e7e-ad5c-f497-dc28b1904311@gmx.com \
--to=n54@gmx.com \
--cc=brad@comstyle.com \
--cc=kamil@netbsd.org \
--cc=kraxel@redhat.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).