From: Lee Revell <rlrevell@joe-job.com>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: Olivier Galibert <galibert@pobox.com>,
Adrian Bunk <bunk@stusta.de>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
perex@suse.cz, Olaf Hering <olh@suse.de>
Subject: Re: [Alsa-devel] OSS driver removal, 2nd round
Date: Sat, 01 Jul 2006 09:52:40 -0400 [thread overview]
Message-ID: <1151761961.11897.3.camel@mindpipe> (raw)
In-Reply-To: <44A6279C.3000100@superbug.co.uk>
On Sat, 2006-07-01 at 08:43 +0100, James Courtier-Dutton wrote:
> Olivier Galibert wrote:
> > On Fri, Jun 30, 2006 at 05:29:26PM -0400, Lee Revell wrote:
> >> Even if you reject this argument, the bug is in ALSA's in-kernel OSS
> >> emulation, not the emu10k1 driver.
> >
> > That's irrelevant. You can't remove the oss emu10k1 driver in favor
> > of alsa's until alsa provides an equivalent interface. That's a basic
> > compatibility requirement.
> >
> >
> >> ALSA's in-kernel OSS emulation does not have these features and
> >> never will.
> >
> > "Never" is terribly long.
> >
> > OG.
>
> "Never" probably only means terribly long. :-)
>
> If one takes the ALSA todo list, that is massive (it is so long in fact,
> that we have not had time to write it all down!), sort it by priority,
> then divide by the amount of ALSA developers time available, for this
> particular feature, the time to implementation is getting very close to
> "Never".
The reason I say "never" is because it would either require moving
alsa-lib into the kernel (long ago rejected), or devising some system to
redirect operations on /dev/dsp back into userspace to alsa-lib. It
seems insane for the audio path to be
userspace->kernel->userspace->kernel and I'm pretty sure this idea was
also rejected a while back.
Lee
next prev parent reply other threads:[~2006-07-01 14:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 19:21 OSS driver removal, 2nd round Adrian Bunk
2006-06-30 15:48 ` Ralf Baechle
2006-06-30 16:13 ` [Alsa-devel] " James Courtier-Dutton
2006-06-30 16:31 ` Olivier Galibert
2006-06-30 21:29 ` Lee Revell
2006-06-30 21:34 ` Arjan van de Ven
2006-06-30 21:54 ` Lee Revell
2006-07-01 8:54 ` Jan Engelhardt
2006-07-01 13:54 ` Lee Revell
2006-07-01 22:51 ` Jan Engelhardt
[not found] ` <200607010042.15765.ismail@pardus.org.tr>
2006-06-30 21:56 ` Lee Revell
[not found] ` <200607010249.05140.ismail@pardus.org.tr>
2006-07-03 22:38 ` Bill Davidsen
2006-07-05 7:27 ` Stefan Smietanowski
2006-07-05 19:34 ` Lee Revell
2006-07-05 21:56 ` Alan Cox
2006-07-01 7:31 ` [Alsa-devel] " Olivier Galibert
2006-07-01 7:43 ` James Courtier-Dutton
2006-07-01 13:52 ` Lee Revell [this message]
2006-07-02 6:55 ` James Courtier-Dutton
2006-07-02 9:58 ` Jan Engelhardt
2006-07-02 15:28 ` Lee Revell
2006-07-02 21:08 ` Jan Engelhardt
2006-07-02 21:16 ` Lee Revell
2006-07-03 9:26 ` Jan Engelhardt
2006-07-05 7:29 ` Stefan Smietanowski
2006-07-01 9:26 ` Jaroslav Kysela
2006-07-01 16:01 ` Adrian Bunk
2006-07-01 23:12 ` Adrian Bunk
2006-07-03 11:52 ` Benjamin Herrenschmidt
2006-07-03 19:42 ` Adrian Bunk
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=1151761961.11897.3.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=James@superbug.co.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=bunk@stusta.de \
--cc=galibert@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
--cc=perex@suse.cz \
/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