qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: malc <av1474@comtv.ru>
Cc: "André Weidemann" <Andre.Weidemann@web.de>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] assigned EHCI USB headset not working
Date: Thu, 09 Jun 2011 17:24:32 +0200	[thread overview]
Message-ID: <4DF0E5B0.8030704@siemens.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1106091913020.1476@linmac>

On 2011-06-09 17:13, malc wrote:
> On Thu, 9 Jun 2011, Jan Kiszka wrote:
> 
>> On 2011-06-09 09:08, Andr? Weidemann wrote:
>>> Hi Jan,
>>>
>>> On 09.06.2011 08:53, Jan Kiszka wrote:
>>>> On 2011-06-09 08:19, Andr? Weidemann wrote:
>>>>> Hi Gerd,
>>>>>
>>>>> On 08.06.2011 14:49, Gerd Hoffmann wrote:
>>>>>> Hi,
>>>>>>
>>>>>>> The sound device shows up under Windows7 and drivers are installed
>>>>>>> automatically. Unfortunately it does not work. All the players I
>>>>>>> tried,
>>>>>>> did not even start playing the sound file, although they detected the
>>>>>>> DirectSound Device.
>>>>>>
>>>>>> iso xfer's from usb-linux via ehci are flaky for reasons not yet
>>>>>> tracked
>>>>>> down.
>>>>>>
>>>>>> Any reason why you don't just plug in a virtual sound card? The HDA
>>>>>> emulation should work fine with win7.
>>>>>
>>>>> Using the hda driver was my first attempt. But the result was not very
>>>>> convincing. When playing mp3s inside the VM, I could hear music coming
>>>>> from the speakers, but the sound was very choppy and too slow. It was no
>>>>> joy listening to it.
>>>>
>>>> Does "export QEMU_AUDIO_DAC_TRY_POLL=0" before invoking qemu helps? It
>>>> depends on your host-side interface. Using ALSA here, it is generally
>>>> required.
>>>>
>>>> Note that this discussion rather belongs on qemu-devel.
>>>
>>> Thank you very much. Setting the variable did the trick.
>>> Could this perhaps be included in the man page? I am sure there will be
>>> others who will eventually run into the same problem as I did.
>>
>> It is a long-standing issue of QEMU that I always wanted to understand
>> but never found the time for. CC'ing malc, maybe he has a good idea how
>> to finally attack this.
>>
> 
> Attack what exactly?

Sound output over (at least) ALSA is not smoothly working in polled
mode. It's similar to [1], which is yet unsolved.

Jan

[1] http://thread.gmane.org/gmane.comp.emulators.qemu/52365

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2011-06-09 15:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4DEF17C1.7000805@web.de>
     [not found] ` <4DEF6FC9.8040209@redhat.com>
     [not found]   ` <4DF065E9.4070605@web.de>
     [not found]     ` <4DF06DED.7030604@web.de>
     [not found]       ` <4DF07182.3060003@web.de>
2011-06-09  7:11         ` [Qemu-devel] assigned EHCI USB headset not working Jan Kiszka
2011-06-09 15:13           ` malc
2011-06-09 15:24             ` Jan Kiszka [this message]
2011-06-09 16:09               ` malc
2011-06-09 17:11                 ` Jan Kiszka
2011-06-10  6:23                   ` 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=4DF0E5B0.8030704@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=Andre.Weidemann@web.de \
    --cc=av1474@comtv.ru \
    --cc=kraxel@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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).