From: Abramo Bagnara <abramo.bagnara@libero.it>
To: alsa-devel@lists.sourceforge.net
Subject: [Fwd: Why do I get broken pipe on write to a pcm in statePREPARED?]
Date: Sat, 05 Oct 2002 09:35:50 +0200 [thread overview]
Message-ID: <3D9E9656.2CB0AA01@libero.it> (raw)
[-- 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
reply other threads:[~2002-10-05 7:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D9E9656.2CB0AA01@libero.it \
--to=abramo.bagnara@libero.it \
--cc=alsa-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox