Clemens Ladisch wrote: > > Abramo Bagnara wrote: > > > >No data may be read/written in current stream state in the case we are > > > >discussing. > > (...) > > > > The point is that stream is in bad state wrt read/write, this is the > > reason why poll should return POLLERR. > > I think the stream is _not_ in a bad state because one buffer of data can > (and has) be written. The reason for not allowing further writes is that > the buffer is full, and not that the device wouldn't accept any data at > all. This is similar to the behaviour of a pipe with the reading end > opened by an application which currently doesn't read from the pipe, in > contrast to a pipe with the read end not opened at all.
??? With this message now I'm very confused about what you wish... Can you resume to me the comparison between current and wanted behaviour wrt poll for both playback and capture. Leave apart read/write at least for now. A table would be easier to understand ;-) -- Abramo Bagnara mailto:[EMAIL PROTECTED] Opera Unica Phone: +39.546.656023 Via Emilia Interna, 140 48014 Castel Bolognese (RA) - Italy ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
