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 state PREPARED? Date: Fri, 13 Sep 2002 14:37:04 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: Mime-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Tim Goetze Cc: "alsa-devel@lists.sourceforge.net" List-Id: alsa-devel@alsa-project.org At Fri, 13 Sep 2002 13:45:24 +0200 (CEST), Tim Goetze wrote: > > Takashi Iwai wrote: > > >if it's on the blocking mode, the driver should block if it's possible > >to do write in future _by any chance_. > >if it's not on the blocking mode, the driver should return -EAGAIN. > >and, the behavior of poll() depends on the behavior of write(). > >if it blocks, then poll blocks, too. > > sorry, i beg to differ. poll returning immediately with EAGAIN on a > nonblock fd doesn't make sense to me. yes, poll should block until it's ready. i meant that if we implement blocking write, poll should be implemented to block, too, unlike the current implementation. of course, poll should block regardless of blocking mode. sorry for confusing. Takashi ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf