From: Arvind R <arvino55@gmail.com>
To: Thomas Goirand <thomas@goirand.fr>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: Xen Qemu DM soundhw
Date: Wed, 10 Mar 2010 11:07:53 +0530 [thread overview]
Message-ID: <d799c4761003092137s1439bfd2m49357323deb4a0c9@mail.gmail.com> (raw)
In-Reply-To: <4B953D4A.1070607@goirand.fr>
On Mon, Mar 8, 2010 at 11:39 PM, Thomas Goirand <thomas@goirand.fr> wrote:
> Christian Motschke wrote:
>> Hi,
>>
>> it took me ages to find the error in the build scripts, why we have no -soundhw in qemu-dm. It is not your fault, but since month, the upstream sources have the error. all you need is the following patch:
>>
>> --- configure 2009-12-16 19:42:32.000000000 +0100
>> +++ ../xen-3.4-testing.hg/tools/ioemu-dir/configure 2010-03-08 16:06:43.000000000 +0100
>> @@ -1382,6 +1382,9 @@
>> echo "#define CONFIG_VDE 1" >> $config_h
>> echo "VDE_LIBS=-lvdeplug" >> $config_mak
>> fi
>> +if ! test -z "$audio_card_list"; then
>> + echo "CONFIG_AUDIO=yes" >> $config_mak
>> +fi
>> for card in $audio_card_list; do
>> def=CONFIG_`echo $card | tr '[:lower:]' '[:upper:]'`
>> echo "$def=yes" >> $config_mak
>>
>> That's all. This would also fix soundhw for a lot of other people who asked for it on several mailing lists if it would be included upstream. But i don't know who to ask. Do you?
>>
>> Viele Grüße.
>> Christian
>
> I sure do, forwarding this to the Xen devel list. Can this be added to
> the official Git of Qemu for Xen 3.4?
>
> Thomas
________________________________________
This is a much better patch than my hard-coded version.
And setting alsa buffer_size to 16384 in the alsa sound driver
is necessary for unchopped sound.
And it would be nice to load the present sound-driver rather than
the first in the list - now one has to edit the list order and compile
Arvind
prev parent reply other threads:[~2010-03-10 5:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A0B5E8A-272D-40E7-B8F7-FC2E5531F5B8@motschke.de>
2010-03-08 18:09 ` Xen Qemu DM soundhw Thomas Goirand
2010-03-10 5:37 ` Arvind R [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=d799c4761003092137s1439bfd2m49357323deb4a0c9@mail.gmail.com \
--to=arvino55@gmail.com \
--cc=thomas@goirand.fr \
--cc=xen-devel@lists.xensource.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).