qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Kővágó Zoltán" <dirty.ice.hu@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH] qapi for audio backends
Date: Thu, 04 Jun 2015 15:33:59 +0200	[thread overview]
Message-ID: <557053C7.5020704@gmail.com> (raw)
In-Reply-To: <1433403822.3736.30.camel@nilsson.home.kraxel.org>

2015-06-04 09:43 keltezéssel, Gerd Hoffmann írta:
>> +#
>> +# @mmap: #optional try using memory mapped access
>
> IIRC this doesn't work everywhere, especially when the oss api is
> implemented as library.
>
> Linux had that, but on linux everybody uses alsa these days ...
> Dunno about other platforms.

idk, the code tries to mmap first, and if it fails, falls back to non 
mmapped access. But something is broken there, as with QEMU_OSS_MMAP=1 
it fails (on linux with alsa oss emulation with pulseaudio alsa 
emulation...). But it ought to work on linux, according to the comments. 
Maybe it needs the native oss, and not the alsa emulation.

>
>> +# @exclusive: #optional open device in exclusive mode (vmix wont work)
>>
>> +# @dsp_policy: #optional set the timing policy of the device, -1 to use fragment
>> +#              mode (option ignored on some platforms)
>
> Would be interesting to know on which platforms this actually has an
> effect (both options) ...

 From a quick google it looks like whatever platform that have oss4 (the 
dsp_policy). exclusive just adds O_EXCL to open flags.

>
> IIRC 'vmix' was a feature of the commercial, ossaudio driver package.
>

      reply	other threads:[~2015-06-04 13:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 16:48 [Qemu-devel] [RFC PATCH] qapi for audio backends Kővágó, Zoltán
2015-06-03 19:17 ` Eric Blake
2015-06-03 19:57   ` Kővágó Zoltán
2015-06-04  7:43 ` Gerd Hoffmann
2015-06-04 13:33   ` Kővágó Zoltán [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=557053C7.5020704@gmail.com \
    --to=dirty.ice.hu@gmail.com \
    --cc=kraxel@redhat.com \
    --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).