From: Adrian Bunk <bunk@stusta.de>
To: "Adam Tlałka" <atlka@pg.gda.pl>
Cc: Lee Revell <rlrevell@joe-job.com>,
alan@lxorguk.ukuu.org.uk, alsa-devel@alsa-project.org,
ak@suse.de, perex@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [Alsa-devel] OSS driver removal, 2nd round (v2)
Date: Mon, 10 Jul 2006 15:57:02 +0200 [thread overview]
Message-ID: <20060710135702.GZ13938@stusta.de> (raw)
In-Reply-To: <20060710132810.551a4a8d.atlka@pg.gda.pl>
On Mon, Jul 10, 2006 at 01:28:10PM +0200, Adam Tlałka wrote:
> On Sun, 09 Jul 2006 11:18:19 -0400
> Lee Revell <rlrevell@joe-job.com> wrote:
>
> > On Sat, 2006-07-08 at 01:50 +0200, Andi Kleen wrote:
> > > Adrian Bunk <bunk@stusta.de> writes:
> > > >
> > > > Q: What about the OSS emulation in ALSA?
> > > > A: The OSS emulation in ALSA is not affected by my patches
> > > > (and it's not in any way scheduled for removal).
> > >
> > > I again object to removing the old ICH sound driver.
> > > It does the same as the Alsa driver in much less code and is ideal
> > > for generic monolithic kernels
> >
> > It doesn't do the same thing - software mixing is impossible with OSS.
>
> Only GPL'ed version has this limitation - its just not implemented because all this
> GPL'ed OSS is abandoned.
> The commercial version from www.opensound.com does input/output mixing
> in software in kernel space.
>...
When we are talking about OSS, we are talking about what is under
sound/oss/ in the kernel sources.
The commercial OSS might be much better, but it's not relevant since
it's not GPL'ed and therefore not a candidate for inclusion into the
kernel.
As you said yourself, the "GPL'ed OSS is abandoned".
And ALSA is it's successor in the kernel.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-07-10 13:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 23:17 OSS driver removal, 2nd round (v2) Adrian Bunk
2006-07-07 23:50 ` Andi Kleen
2006-07-08 0:00 ` Adrian Bunk
2006-07-08 1:30 ` Jeff Garzik
2006-07-09 15:18 ` [Alsa-devel] " Lee Revell
2006-07-09 16:08 ` Olivier Galibert
2006-07-10 11:28 ` Adam Tlałka
2006-07-10 13:18 ` James Courtier-Dutton
2006-07-10 13:57 ` Adrian Bunk [this message]
2006-07-10 22:48 ` Lee Revell
2006-07-10 23:38 ` Adam Tlałka
2006-07-10 23:51 ` Cloning sound output [was Re: [Alsa-devel] OSS driver removal, 2nd round (v2)] J.A. Magallón
2006-07-10 23:51 ` [Alsa-devel] OSS driver removal, 2nd round (v2) Lee Revell
2006-07-10 23:59 ` Olivier Galibert
2006-07-11 0:39 ` Lee Revell
2006-07-11 6:59 ` Adam Tlałka
2006-07-11 7:02 ` Andi Kleen
2006-07-11 7:58 ` Jaroslav Kysela
2006-07-11 9:08 ` Adam Tlałka
2006-07-11 9:52 ` Jaroslav Kysela
2006-07-11 11:18 ` Diego Calleja
2006-07-11 11:29 ` Adam Tlałka
2006-07-11 10:28 ` Adrian Bunk
2006-07-11 2:09 ` Valdis.Kletnieks
2006-07-11 6:15 ` Adam Tlałka
2006-07-11 14:30 ` Valdis.Kletnieks
2006-07-11 16:57 ` Lee Revell
2006-07-11 22:31 ` Adam Tlałka
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=20060710135702.GZ13938@stusta.de \
--to=bunk@stusta.de \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=atlka@pg.gda.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=rlrevell@joe-job.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