From: Takashi Iwai <tiwai@suse.de>
To: Assaf Hoffman <hoffman@marvell.com>
Cc: alsa-devel@lists.sourceforge.net, Rita Shtern <rita@marvell.com>
Subject: Re: [BULK] Re: CMIPCI driver. IEC958 user data and channel status
Date: Wed, 18 Oct 2006 13:28:02 +0200 [thread overview]
Message-ID: <s5hhcy1amnx.wl%tiwai@suse.de> (raw)
In-Reply-To: <B9FFC3F97441D04093A504CEA31B7C41E91858@msilexch01.marvell.com>
At Tue, 17 Oct 2006 13:16:57 +0200,
Assaf Hoffman wrote:
>
> Hi,
> Thank you for your answer.
> I would be happy if you could address the following correlated
> questions:
> 1) According to your experience, is it correct to assume that once a PCM
>
> instance for playback/capture is prepared and triggered, the user
> data
> and channel status are constants during data transmit/receive?
> 2) In the case HW saves the user data and channel status in its internal
>
> registers, how would the ALSA stack know if any of them changed?
> 3) Is there a bridge application in the ALSA stack? I mean, in case
> I would like to capture ICE958 frames and route them to ICE958
> playback
> channel.
If you think of cmipci, the hardware doesn't create any IEC958 status
bits for _input_. What I explained about the SPDIF output.
Takashi
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2006-10-18 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 11:16 [BULK] Re: CMIPCI driver. IEC958 user data and channel status Assaf Hoffman
2006-10-18 11:28 ` Takashi Iwai [this message]
2006-10-18 15:34 ` Clemens Ladisch
-- strict thread matches above, loose matches on Subject: below --
2006-10-18 11:31 Assaf Hoffman
2006-10-18 11:35 ` Takashi Iwai
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=s5hhcy1amnx.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=hoffman@marvell.com \
--cc=rita@marvell.com \
/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