From: Johannes Berg <johannes@sipsolutions.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: pcm hw parameters?
Date: Tue, 28 Mar 2006 14:11:49 +0200 [thread overview]
Message-ID: <1143547909.13615.26.camel@localhost> (raw)
In-Reply-To: <s5hodzrew57.wl%tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
On Mon, 2006-03-27 at 17:37 +0200, Takashi Iwai wrote:
> It's hard to restrict parameters on demands (although theoretically
> it's possible). We usually provide two different devices, one for
> the normal i/o and another for the digital i/o, to avoid such
> conflicts.
I'm doing something like that now... Mind taking a look at i2sbus-pcm.c
in my git repo http://johannes.sipsolutions.net/snd-aoa.git/ ?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]
prev parent reply other threads:[~2006-03-28 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 13:19 pcm hw parameters? Johannes Berg
2006-03-27 15:37 ` Takashi Iwai
2006-03-28 12:11 ` Johannes Berg [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=1143547909.13615.26.camel@localhost \
--to=johannes@sipsolutions.net \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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