From: Josh Haberman <joshua@haberman.com>
To: "alsa-devel@lists.sourceforge.net" <alsa-devel@lists.sourceforge.net>
Subject: Re: Re: [Jackit-devel] alsa_driver_wait -> libasound?
Date: 14 Jan 2003 10:55:55 -0800 [thread overview]
Message-ID: <1042570555.10960.133.camel@birdie> (raw)
In-Reply-To: <Pine.LNX.4.33.0301141728510.504-100000@pnote.perex-int.cz>
On Tue, 2003-01-14 at 08:31, Jaroslav Kysela wrote:
> I wonder why to implement this function when one can link more pcm streams
> with "snd_pcm_link()" together? Then polling one stream is sufficient when
> streams are hardware synchronized.
This reminds me of another question I had: can any two streams be linked
together or do they need to be on the same device? Is it reasonable to
assume that linking two streams will always succeed?
Josh
-------------------------------------------------------
This SF.NET email is sponsored by: Take your first step towards giving
your online business a competitive advantage. Test-drive a Thawte SSL
certificate - our easy online guide will show you how. Click here to get
started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en
next prev parent reply other threads:[~2003-01-14 18:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1042530370.10960.111.camel@birdie>
2003-01-14 14:38 ` [Jackit-devel] alsa_driver_wait -> libasound? Paul Davis
2003-01-14 16:31 ` Jaroslav Kysela
2003-01-14 16:42 ` Paul Davis
2003-01-14 19:35 ` Jaroslav Kysela
2003-01-14 20:23 ` Paul Davis
2003-01-16 0:14 ` Josh Haberman
2003-01-14 18:55 ` Josh Haberman [this message]
2003-01-14 19:25 ` Jaroslav Kysela
2003-01-14 16:32 ` Takashi Iwai
2003-01-14 16:47 ` Paul Davis
2003-01-14 17:03 ` Takashi Iwai
2003-01-14 19:04 ` Josh Haberman
2003-01-14 19:20 ` Paul Davis
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=1042570555.10960.133.camel@birdie \
--to=joshua@haberman.com \
--cc=alsa-devel@lists.sourceforge.net \
/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