From: Gerd Hoffmann <kraxel@redhat.com>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RfC PATCH 11/11] spice: add audio
Date: Fri, 16 Apr 2010 10:40:45 +0200 [thread overview]
Message-ID: <4BC8228D.10909@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1004150046460.1599@linmac>
On 04/14/10 22:51, malc wrote:
> On Wed, 14 Apr 2010, Gerd Hoffmann wrote:
>
> The code does not follow neither audio(which is passable should it be
> internally consistent) nor general QEMU code style (braces missing)
Will add the missing braces.
>> +static void *spice_audio_init(void)
>> +{
>> + if (!using_spice)
>> + return NULL;
>> + return qemu_malloc(42);
>
> Eh? The HGttG references should at least be given an explanation in
> the comments.
Just need return something non-NULL here to indicate success.
Also wanted to check how carefully the reviewers are looking ;)
> c. I have a really hard time following what rt clock (regardless
> of monotonicity is doing here at all)
Accept audio data with the correct rate. When sending directly to the
audio device the host hardware controls this. Spice sends the audio
data off to the network, so this doesn't work. The math used by spice
here looks like a old version of the noaudio code for rate control (/me
inherited that code so I don't know for sure), which makes sense to me.
cheers,
Gerd
next prev parent reply other threads:[~2010-04-16 8:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 9:55 [Qemu-devel] [RfC PATCH 00/11] Add spice support to qemu Gerd Hoffmann
2010-04-14 9:55 ` [Qemu-devel] [RfC PATCH 01/11] vgabios update to 0.6c, add bios for qxl/unstable Gerd Hoffmann
2010-04-14 9:55 ` [Qemu-devel] [RfC PATCH 02/11] add spice into the configure file Gerd Hoffmann
2010-04-14 9:55 ` [Qemu-devel] [RfC PATCH 03/11] spice: core bits Gerd Hoffmann
2010-04-14 9:55 ` [Qemu-devel] [RfC PATCH 04/11] spice: add keyboard Gerd Hoffmann
2010-04-14 9:55 ` [Qemu-devel] [RfC PATCH 05/11] spice: add mouse Gerd Hoffmann
2010-04-14 9:55 ` [Qemu-devel] [RfC PATCH 06/11] spice: simple display Gerd Hoffmann
2010-04-14 9:55 ` [Qemu-devel] [RfC PATCH 07/11] spice: tls support Gerd Hoffmann
2010-04-14 9:55 ` [Qemu-devel] [RfC PATCH 08/11] spice: add qxl device Gerd Hoffmann
2010-04-14 16:52 ` Blue Swirl
2010-04-14 23:08 ` [Qemu-devel] " Paolo Bonzini
2010-04-15 16:47 ` Blue Swirl
2010-04-15 19:27 ` Richard Henderson
2010-04-16 8:02 ` Gerd Hoffmann
2010-04-16 10:18 ` Paolo Bonzini
2010-04-16 10:34 ` Gerd Hoffmann
2010-04-16 12:53 ` Richard Henderson
2010-04-14 22:21 ` [Qemu-devel] " Alexander Graf
2010-04-16 8:08 ` Gerd Hoffmann
2010-04-14 9:55 ` [Qemu-devel] [RfC PATCH 09/11] qxl: local rendering for sdl/vnc Gerd Hoffmann
2010-04-14 9:55 ` [Qemu-devel] [RfC PATCH 10/11] spice: add tablet support Gerd Hoffmann
2010-04-14 9:55 ` [Qemu-devel] [RfC PATCH 11/11] spice: add audio Gerd Hoffmann
2010-04-14 20:51 ` malc
2010-04-14 23:14 ` [Qemu-devel] " Paolo Bonzini
2010-04-15 0:13 ` malc
2010-04-15 0:26 ` Paolo Bonzini
2010-04-15 0:29 ` malc
2010-04-16 8:40 ` Gerd Hoffmann [this message]
2010-04-16 11:13 ` [Qemu-devel] " 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=4BC8228D.10909@redhat.com \
--to=kraxel@redhat.com \
--cc=av1474@comtv.ru \
--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).