linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ookhoi <ookhoi@humilis.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ed Sweetman <ed.sweetman@wmich.edu>,
	ookhoi@humilis.net, Takashi Iwai <tiwai@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	eugene.teo@eugeneteo.net
Subject: Re: 2.6 sound drivers?
Date: Thu, 17 Jul 2003 15:11:12 +0200	[thread overview]
Message-ID: <20030717131112.GA31425@favonius> (raw)
In-Reply-To: <1058443806.8615.32.camel@dhcp22.swansea.linux.org.uk>

Alan Cox wrote (ao):
> On Iau, 2003-07-17 at 12:31, Ed Sweetman wrote:
> > > Wouldn't esd (the enlightment sound daemon) take care of this in
> > > userspace? I can have sound out of xmms, firebird, mpg321 and
> > > mplayer at the same time with esd.
> > 
> > Most people would rather not use esd, especially when you dont need
> > to use any userspace deamon to do the job.
> 
> There are lots of reasons for not using esd (its sucky frequency code
> for example)

I feel enlightened ;-)

> but you do need a userspace daemon because the alsa kernel side mixing
> stuff doesn't handle network connections - and nor would you want it
> to.
>
> X is a networked environment, Gnome is a networked desktop, therefore
> you need networked audio

What would be a better choice than esd?

  reply	other threads:[~2003-07-17 12:56 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16 22:58 2.6 sound drivers? Robert L. Harris
2003-07-16 23:10 ` Rudo Thomas
2003-07-16 23:29   ` Robert L. Harris
2003-07-16 23:46     ` Rudo Thomas
2003-07-16 23:10 ` Mike Fedyk
2003-07-16 23:30   ` Robert L. Harris
2003-07-16 23:39     ` Mike Fedyk
2003-07-16 23:46     ` David Ford
2003-07-17  0:08       ` Robert L. Harris
2003-07-17  1:07         ` Wes Janzen
2003-07-17  1:42         ` James H. Cloos Jr.
2003-07-17  7:26     ` Martin Schlemmer
2003-07-17  8:57       ` Eugene Teo
2003-07-17  9:22         ` Takashi Iwai
2003-07-17 11:19           ` Ookhoi
2003-07-17 11:31             ` Ed Sweetman
2003-07-17 12:10               ` Alan Cox
2003-07-17 13:11                 ` Ookhoi [this message]
2003-07-17 11:32             ` Takashi Iwai
2003-07-16 23:37 ` Jeff Garzik
2003-07-16 19:25   ` Max Valdez
2003-07-17  1:05     ` Jeff Garzik
2003-07-17  2:18       ` Norberto BENSA
2003-07-17 13:13         ` Ian Hastie
2003-07-17 13:25           ` Takashi Iwai
2003-07-17 13:19         ` Terje Kvernes
2003-07-17 16:08           ` Norberto BENSA
2003-07-17 11:22             ` Max Valdez
2003-07-17 16:54             ` Takashi Iwai
2003-07-17 18:43               ` Norberto BENSA
2003-07-17 19:44               ` Ian Hastie
2003-07-18  9:45                 ` Takashi Iwai
2003-07-17 18:46             ` dacin
2003-07-17 19:12               ` MONOLITHIC sound (was Re: 2.6 sound drivers?) Douglas J Hunley
2003-07-17 20:09                 ` dacin
2003-07-16 23:39   ` 2.6 sound drivers? Robert L. Harris
2003-07-16 23:57     ` Matt Reppert

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=20030717131112.GA31425@favonius \
    --to=ookhoi@humilis.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ed.sweetman@wmich.edu \
    --cc=eugene.teo@eugeneteo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).