From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Rui Sousa <rui.p.m.sousa@clix.pt>
Cc: "Morgan Collins [Ax0n]" <sirmorcant@morcant.org>,
kwijibo@zianet.com, bcrl@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: emu10k emits buzzing and crackling
Date: Sun, 04 Nov 2001 11:54:52 -0500 [thread overview]
Message-ID: <3BE572DC.4BD4958E@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111041743030.3150-100000@sophia-sousar2.nice.mindspeed.com>
Rui Sousa wrote:
> With the emu10k1 there is no need to use esd...
emu10k1 provides in-kernel support for multiple userspace apps sharing a
single /dev/dsp0 connection? :)
GNOME pretty much requires esd, like KDE requires arts.
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
next prev parent reply other threads:[~2001-11-04 16:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 1:09 emu10k emits buzzing and crackling Benjamin LaHaise
2001-11-02 8:10 ` Steven Spence
2001-11-02 10:07 ` Morgan Collins [Ax0n]
2001-11-04 16:48 ` Rui Sousa
2001-11-04 16:54 ` Jeff Garzik [this message]
2001-11-04 17:06 ` Alan Cox
2001-11-04 17:18 ` Rui Sousa
2001-11-04 17:29 ` Alan Cox
2001-11-04 17:31 ` Alex Buell
2001-12-09 21:54 ` emu10k1 - interrupt storm? Zlatko Calusic
2001-12-10 10:39 ` Rui Sousa
2001-12-10 10:52 ` Zlatko Calusic
2001-12-11 20:03 ` Zlatko Calusic
2001-12-12 10:26 ` Rui Sousa
2001-12-12 13:24 ` Marcelo ''Mosca'' de Paula Bezerra
2001-12-12 21:47 ` Zlatko Calusic
2001-12-12 22:23 ` Doug McNaught
2001-12-13 7:47 ` Zlatko Calusic
2001-12-12 22:41 ` Morgan Collins
2001-12-13 7:50 ` Zlatko Calusic
2001-12-14 7:38 ` Philipp Matthias Hahn
2001-12-12 21:54 ` Zlatko Calusic
2001-11-02 14:52 ` emu10k emits buzzing and crackling Paul Fulghum
2001-11-02 14:57 ` Benjamin LaHaise
2001-11-03 0:47 ` Steven Spence
2001-11-04 16:39 ` Rui Sousa
-- strict thread matches above, loose matches on Subject: below --
2001-11-09 21:36 Daniel Ceregatti
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=3BE572DC.4BD4958E@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=bcrl@redhat.com \
--cc=kwijibo@zianet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.p.m.sousa@clix.pt \
--cc=sirmorcant@morcant.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.