From: Phil <phillor@telstra.com>
To: linux-hams@vger.kernel.org
Subject: Re: /dev/dsp busy
Date: Tue, 2 Jun 2009 12:43:54 +1000 [thread overview]
Message-ID: <200906021243.54409.phillor@telstra.com> (raw)
In-Reply-To: <4A236947.8070602@radagast.org>
On Monday 01 June 2009 15:38:15 Dave Platt wrote:
<cut>
> I've observed something like this when:
>
> - The sound card has an ALSA driver, and
>
> - The sound card supports only a limited set of audio sample
> rates, and
>
Thank you for your detailed reply Dave.
I'll experiment further and see what results.
--
Regards,
Phil
prev parent reply other threads:[~2009-06-02 2:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 0:59 /dev/dsp busy Phil
2009-06-01 3:29 ` Dave Platt
2009-06-01 4:50 ` Phil
2009-06-01 5:38 ` Dave Platt
2009-06-02 2:43 ` Phil [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=200906021243.54409.phillor@telstra.com \
--to=phillor@telstra.com \
--cc=linux-hams@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