From: <paco@hydrofunk.org>
To: linux-sound@vger.kernel.org
Subject: fragment size using emu10k1
Date: Thu, 13 Apr 2000 17:36:36 +0000 [thread overview]
Message-ID: <marc-linux-sound-95565226702283@msgid-missing> (raw)
Hi...
I've noticed a problem using the ioctl SNDCTL_DSP_GETBLKSIZE with my
SBPCI512. I'm not familiar with the underlying workings of the sound
driver (emu10k1), and I really don't know if this is a kernel problem or a
driver problem.
The problem is simple, when you issue the GETBLKSIZE call, the value that
is reported back is wrong by a power of 2. The call will report that the
buffer size is "X" Bytes, but it is really only of size "X/2" Bytes.
This can cause problems in applications that attempt to use this
information for malloc calls, or for applications that need to write
data to the card in full fragments at a time.
--Paco
reply other threads:[~2000-04-13 17:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-sound-95565226702283@msgid-missing \
--to=paco@hydrofunk.org \
--cc=linux-sound@vger.kernel.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