From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Thomas Sailer <sailer@ife.ee.ethz.ch>, linux-kernel@vger.kernel.org
Subject: Re: Poll and OSS API
Date: Sat, 04 Nov 2000 02:26:46 -0500 [thread overview]
Message-ID: <3A03BA36.3296AF2D@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10011032237270.25382-100000@penguin.transmeta.com>
Linus Torvalds wrote:
> Considering that about 100% of the sound drivers do not follow that
> particular API damage anyway (they can't, as has been pointed out: the
> driver doesn't even receive enough information to be _able_ to follow the
> documented API), I doubt that there are all that many programs that depend
> on it.
While I'm thinking about the subject.. even after updating the API, the
drivers still need to know what events to poll for.
AFAIK 99% of the drivers currently select to block on
read/write/read+write based on file->f_mode, which works, but isn't
really correct.
Jeff
--
Jeff Garzik | Dinner is ready when
Building 1024 | the smoke alarm goes off.
MandrakeSoft | -/usr/games/fortune
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-11-04 7:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-02 14:03 Poll and OSS API Thomas Sailer
2000-11-02 14:23 ` Richard B. Johnson
2000-11-02 14:27 ` Thomas Sailer
2000-11-02 14:47 ` Richard B. Johnson
2000-11-02 14:35 ` Jeff Garzik
2000-11-02 14:50 ` Jeff Garzik
2000-11-02 17:38 ` Linus Torvalds
2000-11-02 17:59 ` Alan Cox
2000-11-04 6:18 ` Jeff Garzik
2000-11-04 6:39 ` Linus Torvalds
2000-11-04 7:18 ` Jeff Garzik
2000-11-04 7:26 ` Jeff Garzik [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=3A03BA36.3296AF2D@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sailer@ife.ee.ethz.ch \
--cc=torvalds@transmeta.com \
/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