From: Carlo Marcelo Arenas Belon <carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [RFC] modular dependencies for kvm's qemu
Date: Wed, 17 Oct 2007 09:43:57 -0500 [thread overview]
Message-ID: <20071017144357.GA23149@tapir> (raw)
In-Reply-To: <20071016153603.GB15903@tapir>
On Tue, Oct 16, 2007 at 10:36:03AM -0500, Carlo Marcelo Arenas Belon wrote:
> On Tue, Oct 16, 2007 at 04:20:37PM +0200, Avi Kivity wrote:
> > Carlo Marcelo Arenas Belon wrote:
> > >
> > >>It seems like rather
> > >>a bad idea to suddenly switch the configure script defaults in the way
> > >>you suggest for alsa. It really wouldn't be much harder to set
> > >>enable_alsa=1
> > >>in the top of configure, and then have the flag toggle it to off.
> > >
> > >ok, but if that is added to kvm's configure then the logic will be inversed
> > >when looking at qemu's configure, probably confusing users.
> >
> > If audio output is going to sdl anyway, then this has no effect on most
> > users, right?
>
> it probably wouldn't work out of the box, unless they change
>
> QEMU_AUDIO_DRV=alsa
>
> to :
>
> QEMU_AUDIO_DRV=sdl
> SDL_AUDIODRIVER=alsa
>
> but I never had sound support configured so I am no way expert and can't test
> if that is the case or if that is the way it fallsback (will take a closer
> look at the code later though).
for the cases where qemu doesn't have alsa support but the environment
variables point to using alsa, then it will complain with :
audio: Unknown audio driver 'alsa'
audio: Run with -audio-help to list available drivers
but then it will scan for an available audio driver it can use by default and
configure SDL instead, probably with alsa support if that is available, as
done explicitly by the second set of environment variables.
tested it with a 64bit linux host running a 32bit windows 2000 advanced server
guest using -soundhw sb16.
in a hopefully unrelated note, using alsa directly wouldn't work as well as
using alsa through SDL, so I guess that the impact on the users is actually
positive if using SDL is also more reliable.
anyone with more audio experience care to comment?
Carlo
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
prev parent reply other threads:[~2007-10-17 14:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 9:22 [RFC] modular dependencies for kvm's qemu Carlo Marcelo Arenas Belon
2007-10-16 10:38 ` Avi Kivity
2007-10-16 13:39 ` Daniel P. Berrange
[not found] ` <20071016133930.GB2107-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-10-16 14:21 ` Carlo Marcelo Arenas Belon
2007-10-16 14:20 ` Avi Kivity
[not found] ` <4714C8B5.60104-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-16 14:54 ` Anthony Liguori
2007-10-16 15:36 ` Carlo Marcelo Arenas Belon
2007-10-16 15:34 ` Avi Kivity
2007-10-16 15:48 ` Anthony Liguori
2007-10-17 14:43 ` Carlo Marcelo Arenas Belon [this message]
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=20071017144357.GA23149@tapir \
--to=carenas-kledwsohozojb6fo7hg9ng@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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