From: Ion Badulescu <ionut@moisil.cs.columbia.edu>
To: Doug Ledford <dledford@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: esound (esd), 2.4.[12] chopped up sound -- solved
Date: Tue, 20 Mar 2001 15:20:39 -0800 [thread overview]
Message-ID: <200103202320.f2KNKdF22559@moisil.dev.hydraweb.com> (raw)
In-Reply-To: <3AB7BB59.9513514C@redhat.com>
On Tue, 20 Mar 2001 15:19:37 -0500, Doug Ledford <dledford@redhat.com> wrote:
> Why would esd get a short write() unless it is opening the file in non
> blocking mode (which I didn't see when I was working on the i810 sound
> driver)? If esd is writing to a file in blocking mode and that write is
> returning short, then that sounds like a driver bug to me.
No, it's not a bug. It would be a bug if esd was writing to a *real* file
or if the write() returned -1 and an errno of EAGAIN. But incomplete writes
are very much ok.
Just try opening /dev/tty and see how it won't take writes of more than
2k (iirc). And that's not just on Linux, I've tested on Solaris and BSD
as well -- though it was a while ago.
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
next prev parent reply other threads:[~2001-03-20 23:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-19 12:15 esound (esd), 2.4.[12] chopped up sound Peter Lund
2001-03-20 17:35 ` Pozsar Balazs
2001-03-20 18:34 ` esound (esd), 2.4.[12] chopped up sound -- solved Peter Lund
2001-03-20 19:50 ` David Ford
2001-03-20 20:19 ` Doug Ledford
2001-03-20 22:24 ` Tim Wright
2001-03-20 22:37 ` David Woodhouse
2001-03-20 23:20 ` Ion Badulescu [this message]
2001-03-21 3:36 ` David Ford
2001-03-21 6:45 ` Doug Ledford
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=200103202320.f2KNKdF22559@moisil.dev.hydraweb.com \
--to=ionut@moisil.cs.columbia.edu \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.