[Fwd: Why do I get broken pipe on write to a pcm in statePREPARED?]

[Fwd: Why do I get broken pipe on write to a pcm in statePREPARED?]

[Abramo Bagnara]

[-- Attachment #1: Type: text/plain, Size: 193 bytes --]


-- 
Abramo Bagnara                       mailto:abramo.bagnara@libero.it

Opera Unica                          Phone: +39.546.656023
Via Emilia Interna, 140
48014 Castel Bolognese (RA) - Italy

[-- Attachment #2: Type: message/rfc822, Size: 2508 bytes --]

From: Paul Davis <pbd@op.net>
To: Abramo Bagnara <abramo.bagnara@libero.it>
Cc: Takashi Iwai <tiwai@suse.de>, Anders Torger <torger@ludd.luth.se>, Jaroslav Kysela <perex@suse.cz>, Tim Goetze <tim@quitte.de>, alsa-devel@lists.sourceforge.net
Subject: Re: [Alsa-devel] Why do I get broken pipe on write to a pcm in statePREPARED?
Date: Fri, 04 Oct 2002 17:19:42 -0400
Message-ID: <3D98769A000FAA05@ims5a.libero.it> (added by postmaster@libero.it)

 
 [ abramo: please forward to alsa-devel@lists.sourceforge.net. thanks. ]

>I'm strongly convinced that to have poll waiting for something that
>cannot happens is a big mistake (also as an optional behaviour).

there are several, perhaps even lots, of other device drivers in the
linux kernel that do this.

>That apart I'm sure that to make a change in actual behaviour between
>rcX and 1.0 is a professional suicide. However it's _your_ professional
>suicide so... ;-)))

not *one* person on alsa-devel has described software that would be
broken by this change. 

given that jaroslav is already changing the API between rcX and rcZ,
this doesn't seem like much of a problem, anyway.

>To resume, if you ask me, the answer is no.

well, he did ask you, but my answer is yes :))

--p