From: Wilmer van der Gaast <lintux@debian.org>
To: linux-sound@vger.kernel.org
Subject: Re: es1371 driver
Date: Thu, 21 Feb 2002 18:03:40 +0000 [thread overview]
Message-ID: <marc-linux-sound-101431472704282@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-101430199925056@msgid-missing>
Jaroslav Kysela (perex@suse.cz) wrote:
> If O_NONBLOCK is clear:
> The open() function will block the calling thread until the device
> is ready or available before returning.
>
Hmm.. Damn, looks like a *lot* of applications don't know about this.
Also, I checked a couple of other drivers (including GUS, the card I
used to have), they all return -EBUSY when the device in use, even when
O_NONBLOCK is clear. Why this inconsistency?
Greetings,
Wilmer van der Gaast.
--
+-------- .''`. - -- ---+ + - -- --- ---- ----- ------+
| lintux : :' : lintux.cx | | Unix and CGI @ IOI/NIO(Dutch)at |
| at `. `~' debian.org | | www.lintux.cx/ www.algoritme.nl |
+--- -- - ` ---------------+ +------ ----- ---- --- -- - +
prev parent reply other threads:[~2002-02-21 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 13:40 es1371 driver Wilmer van der Gaast
2002-02-21 14:30 ` Zwane Mwaikambo
2002-02-21 14:55 ` Jaroslav Kysela
2002-02-21 18:03 ` Wilmer van der Gaast [this message]
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=marc-linux-sound-101431472704282@msgid-missing \
--to=lintux@debian.org \
--cc=linux-sound@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox