From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Why do I get broken pipe on write to a pcm in statePREPARED? Date: Tue, 08 Oct 2002 11:54:17 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <3DA178F1.769C6FFA@libero.it> <200210071319.g97DJJ008659@d1o87.telia.com> <3DA1C884.C8283CE6@libero.it> Mime-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <3DA1C884.C8283CE6@libero.it> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Abramo Bagnara Cc: Anders Torger , alsa-devel@lists.sourceforge.net, Clemens Ladisch List-Id: alsa-devel@alsa-project.org At Mon, 07 Oct 2002 19:46:44 +0200, Abramo Bagnara wrote: > > > > but the current behavior is incorrect from the interpretation of > > > > POSIX. so this must be a bug. > > > > if we have to change it, then i would choose the new one, because > > > > it's more intuitive without exception. > > > > > > As pointed by Clemens the current is the proper POSIX behaviour. > > > > Perhaps you should reread Single Unix Specification, I quote > http://www.opengroup.org/onlinepubs/007904975/functions/poll.html > > POLLIN > Data other than high-priority data may be read without > blocking. > > > POLLOUT > Normal data may be written without blocking. > > > No data may be read/written in current stream state in the case we are > discussing. these flags are the conditions how read/write behaves when poll() returns. no problem that poll() itself is blocked in the prepare state because it does NOT return until the pcm is ready. Takashi ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf