From: Britton <fsblk@aurora.uaf.edu>
To: linux-sound@vger.kernel.org
Subject: how to find the maximum fragment size for SNDCTL_DSP_SETFRAGMENT?
Date: Thu, 08 Jun 2000 18:26:45 +0000 [thread overview]
Message-ID: <marc-linux-sound-96049072503276@msgid-missing> (raw)
The guide of 4front's web page says total_buffer_size/2. I know the
kernel buffer size used to be defined at kernel compile time. How does
one go about determining it now? DSP_GETBLKSZ? Does DSP_GETBLKSZ still
fix the block size so that the device must be closed and opened again in
order to set the fragment size?
Britton Kerin
next reply other threads:[~2000-06-08 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-08 18:26 Britton [this message]
2000-06-08 21:59 ` how to find the maximum fragment size for SNDCTL_DSP_SETFRAGMENT? Hannu Savolainen
2000-06-08 22:25 ` Britton
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-96049072503276@msgid-missing \
--to=fsblk@aurora.uaf.edu \
--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