From: Gerd Hoffmann <kraxel@redhat.com>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/6] The windows 7 audio support patch series.
Date: Thu, 28 Oct 2010 10:47:16 +0200 [thread overview]
Message-ID: <4CC93894.3030008@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1010272142440.9050@linmac>
Hi,
> Nice timing there. I wonder how long it took bright folks at redhat to
> code this HDA stuff?
A bunch of days. Played with the usb-audio patch first. But I suspect
getting timing-sensitive isochronous usb devices emulated reasonable
well is pretty hard due to the latency requirements. And it isn't just
the usb subsytem, all qemu must improve here. Example: enabling the
threaded vnc server improves usb-audio sound quality, you don't get
dropouts on every bulky screen update then.
But for now I tried HDA route instead.
> Since yesterday i was contacted by folks who wanted
> to pay money to get VirtualBox's HDA ported to QEMU, and it took me from
> 16:00 today till basically 15 minutes ago to get the sound pumping from
> DOS and Linux..
Oh, there is a HDA driver for DOS? /me looks surprised ...
> Regardless of the answer to my question the NIH is such a nice thing, eh?
Sure ;) I don't do that just for fun though. I *have* looked at the
vbox driver first.
The fundamental problem is the qemu world didn't stop at the point where
vbox forked off, and of course in vbox things are changing too. We have
alot of infrastructure for drivers which isn't in vbox, and likewise the
other way around. Most notable difference is qemu's qdev is quite
useful to model the HDA bus.
So there are basically two options:
(1) Port the vbox driver to qemu, then to tons of changes and
cleanups to properly integrate into modern qemu.
(2) Start over from scratch.
I believe in the end it wouldn't have saved work to use the vbox code as
starting point.
cheers,
Gerd
next prev parent reply other threads:[~2010-10-28 8:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 16:04 [Qemu-devel] [PATCH 0/6] The windows 7 audio support patch series Gerd Hoffmann
2010-10-27 16:04 ` [Qemu-devel] [PATCH 1/6] pa: allow processing buffer pieces Gerd Hoffmann
2010-10-27 16:04 ` [Qemu-devel] [PATCH 2/6] pa: process 1/4 buffer max at once Gerd Hoffmann
2010-10-27 16:04 ` [Qemu-devel] [PATCH 3/6] pa: setup buffer attrs Gerd Hoffmann
2010-10-27 16:04 ` [Qemu-devel] [PATCH 4/6] pa: tweak config Gerd Hoffmann
2010-10-27 16:04 ` [Qemu-devel] [PATCH 5/6] Add support for a USB audio device model Gerd Hoffmann
2010-10-27 17:13 ` [Qemu-devel] " H. Peter Anvin
2010-10-28 8:01 ` Gerd Hoffmann
2010-10-28 15:23 ` H. Peter Anvin
2010-10-28 16:13 ` Gerd Hoffmann
2010-10-28 15:28 ` H. Peter Anvin
2010-10-28 15:29 ` H. Peter Anvin
2010-10-27 16:04 ` [Qemu-devel] [PATCH 6/6] Add Intel HD Audio support to qemu Gerd Hoffmann
2010-10-27 17:46 ` [Qemu-devel] [PATCH 0/6] The windows 7 audio support patch series malc
2010-10-27 17:51 ` malc
2010-10-28 8:47 ` Gerd Hoffmann [this message]
2010-10-28 9:46 ` malc
2010-10-28 10:06 ` malc
2010-10-28 10:06 ` Gerd Hoffmann
2010-10-28 22:21 ` 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=4CC93894.3030008@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).