From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [RFC] Default audio_drv_list to "sdl" on Win32
Date: Wed, 31 Dec 2008 12:55:33 +0200 [thread overview]
Message-ID: <495B4FA5.3000703@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0812302139280.2178@linmac.oyster.ru>
malc wrote:
> On Mon, 29 Dec 2008, Anthony Liguori wrote:
>
>> Malc,
>>
>> Do you have a problem with this? QEMU requires SDL by default on
>> Windows so I see no reason not to use it for audio too.
>>
>
> Well last time i tried SDL audio on windows (admittedly years ago) it
> was such a disaster that i probably omitted for this reason, then again
> if it goes after dsound (which becomes the default) i see no harm in
> including it.
Qemu's response times have improved greatly. It's worth trying again.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2008-12-31 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 17:17 [Qemu-devel] [RFC] Default audio_drv_list to "sdl" on Win32 Anthony Liguori
2008-12-30 18:41 ` [Qemu-devel] " malc
2008-12-31 2:22 ` François Revol
2008-12-31 10:55 ` Avi Kivity [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=495B4FA5.3000703@redhat.com \
--to=avi@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).