From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Gerd Hoffmann" <kraxel@redhat.com>,
qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Brad Smith" <brad@comstyle.com>,
"Kamil Rytarowski" <kamil@netbsd.org>
Subject: Re: [Qemu-devel] [PATCH 4/4] [RfC] audio: probe audio drivers by default
Date: Wed, 23 Jan 2019 10:12:38 +0000 [thread overview]
Message-ID: <20190123101238.GD27270@redhat.com> (raw)
In-Reply-To: <d7c274a7-00ac-d767-69fc-238b88cfd61b@redhat.com>
On Wed, Jan 23, 2019 at 10:50:18AM +0100, Thomas Huth wrote:
> On 2019-01-23 10:36, Daniel P. Berrangé wrote:
> > On Wed, Jan 23, 2019 at 09:27:48AM +0100, Thomas Huth wrote:
> >> On 2019-01-23 09:00, Gerd Hoffmann wrote:
> >>>
> >>> This is RfC because we might look at the ordering. On linux we probably
> >>> want prefer alsa over oss.
> >> Yes, please! I've run into the trap a couple of times already: OSS
> >> headers were available, but these days the OSS compatibility kernel
> >> modules are not loaded anymore by default. So you compile QEMU with OSS
> >> support and then wonder why you do not get any audio output at all...
> >>
> >> IMHO we should put OSS as last item in the list on Linux nowadays.
> >
> > Given our targetted platform list[1], are there even any platforms
> > where we would *not* have alsa, but still have OSS ? If not, then
> > we could just drop the OSS driver entirely on the ground that it is
> > obsolete.
>
> We likely could drop OSS on Linux, but it is still required on FreeBSD
> and NetBSD, isn't it? So unless we can drop it there, too, we can also
> simply keep it as last option in the list on Linux as well.
Ah ok, I didn't realize that BSD implemneted the OSS subsystem too.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-01-23 10:13 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é [this message]
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
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=20190123101238.GD27270@redhat.com \
--to=berrange@redhat.com \
--cc=brad@comstyle.com \
--cc=kamil@netbsd.org \
--cc=kraxel@redhat.com \
--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).