At Fri, 15 Sep 2006 14:54:00 +0900, Junji Umeno wrote: > > I failed to record with the example code 'latency.c' written in the doxygen manual. > When it plays back and records at the same time, using snd_pcm_link, > should the hardware be implemented as full-duplex of i/o? snd_pcm_link() itself has nothing to do with full-duplexity. It's a command to link multiple streams. Here, "link" means the streams are triggered at the same time, and take the same clock if possible. For example, you can link two or more playback streams to achieve multi-channels (acatually PCM multi plugin does this internally). > As previous comments pointed in this lists, > some buffer length data are written into a playback handler, > and then reading starts. > They said, it should be needed to have 4096 bytes written in the write buffer. > But in my case, > 'writei' continues to return EAGAIN if more than 64byte are to be written. When EAGAIN is returned, the buffer is still full. It appears to be right behavior to me... More explanation or code snippet please? Takashi ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-devel
