At Wed, 18 Oct 2006 13:31:39 +0200, Assaf Hoffman wrote: > > Hi > Thank you for your answer. > Could you please address the question below with no relevance to CMIPCI > driver? Then it depends on the driver implementation. Usually the driver provides "IEC958 Capture xxx" control elements (either IFACE_PCM or IFACE_MIXER attribute) so that the apps can extract the SPDIF status bits via control API. Takashi > Many thanks. > > -----Original Message----- > From: Takashi Iwai [mailto:tiwai@xxxxxxx] > Sent: Wednesday, October 18, 2006 1:28 PM > To: Assaf Hoffman > Cc: Rita Shtern; alsa-devel@xxxxxxxxxxxxxxxxxxxxx > Subject: Re: [BULK] Re: CMIPCI driver. IEC958 user data and > channel status > Importance: Low > > 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 _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-devel