qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Zir Blazer <zir_blazer@hotmail.com>,
	Markus Armbruster <armbru@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] What is the status of the QEMU sound rework?
Date: Mon, 09 Oct 2017 11:37:16 +0200	[thread overview]
Message-ID: <1507541836.32088.8.camel@redhat.com> (raw)
In-Reply-To: <CY4PR15MB14645F1B82057940D068F009F3740@CY4PR15MB1464.namprd15.prod.outlook.com>

  Hi,

> The guy from reddit whose Thread I linked in the previous mail has
> done a bit more work, and his current status is this:
> https://www.reddit.com/r/VFIO/comments/74vokw/improved_pulse_audio_dr
> iver_for_qemu/
> 
> He identified some issues with the QEMU audio backend, and according
> to the testers, his fixes seems to be working.
> 
> As it is probable that he eventually upstreams something, you may
> want to be interesed in checking his work.

He asked me a few questions already and has the intention to send his
work upstream.

> I know that you just said that you don't have time, but since audio
> improvements for QEMU seems to have been stuck for some years, it may
> be important to be proactive now that there is people interesed
> and working in the issue, as to not lose this rare momentum.

Sure.  Typically I try hard to set aside time for helping people, this
often pays off long-term.

cheers,
  Gerd

      reply	other threads:[~2017-10-09  9:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-07  2:58 [Qemu-devel] What is the status of the QEMU sound rework? Zir Blazer
2017-10-09  5:49 ` Markus Armbruster
2017-10-09  7:33   ` Gerd Hoffmann
2017-10-09  8:25     ` Zir Blazer
2017-10-09  9:37       ` Gerd Hoffmann [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=1507541836.32088.8.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=armbru@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zir_blazer@hotmail.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).