Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: ALSA development <alsa-devel@alsa-project.org>
Subject: Any issues with GETOSPACE OSS ioctl?
Date: Wed, 05 Nov 2008 09:41:16 -0600	[thread overview]
Message-ID: <4911BE9C.8010607@freescale.com> (raw)

I have a customer who reports that when his OSS application makes several
write() followed by SNDCTL_DSP_GETOSPACE, the returned value is not decreasing,
which implies that the write() commands are not going through.

I've looked at the OSS documentation for this ioctl
(http://manuals.opensound.com/developer/SNDCTL_DSP_GETOSPACE.html), and it
implies that it is not reliable.  But since the customer is using ALSA (i.e.
ALSA's OSS emulation), I don't know if that applies.

So I'd like to know how the 'bytes' return value is calculate in ALSA.

-- 
Timur Tabi
Linux kernel developer at Freescale

             reply	other threads:[~2008-11-05 15:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-05 15:41 Timur Tabi [this message]
2008-11-06 12:31 ` Any issues with GETOSPACE OSS ioctl? Clemens Ladisch

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=4911BE9C.8010607@freescale.com \
    --to=timur@freescale.com \
    --cc=alsa-devel@alsa-project.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