From: Adrian Bunk <bunk@stusta.de>
To: "Adam Tlałka" <atlka@pg.gda.pl>
Cc: Jaroslav Kysela <perex@suse.cz>,
alsa-devel@alsa-project.org, rlrevell@joe-job.com,
galibert@pobox.com, alan@lxorguk.ukuu.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: [Alsa-devel] OSS driver removal, 2nd round (v2)
Date: Tue, 11 Jul 2006 12:28:22 +0200 [thread overview]
Message-ID: <20060711102822.GK13938@stusta.de> (raw)
In-Reply-To: <20060711110811.947e15ed.atlka@pg.gda.pl>
On Tue, Jul 11, 2006 at 11:08:10AM +0200, Adam Tlałka wrote:
> On Tue, 11 Jul 2006 09:58:26 +0200 (CEST)
> Jaroslav Kysela <perex@suse.cz> wrote:
>...
> > You're a bit mixing things:
> >
> > a) we're not trying to be more compatible than OSS code in kernel, if you
> > like to do the mixing in kernel, simply write a new ALSA lowlevel
> > driver which will do it; I'm sure when the quality of your code will be
> > good, we'll include it to the ALSA tree, but we are not going this
> > way unless someone else will maintain this code
>
> OSS kernel compatibility is only partial and aoss method is not fully compatible either
Except for some corner cases, ALSA is capable of emulating the
in-kernel OSS.
And considering the low number of applications that are still OSS-only,
I doubt it's really that important improving the OSS emulation even
further.
But this is open source software, so feel free to send patches.
> I will try to write some code but I have very little free time for that so I am trying
> to convince people to rethinking the case
>...
This is not how open source software works.
If you think something is missing, you have to implement it.
If you spend your "very little free time" on such discussions instead,
you are not only wasting the time you could spend on implementing what
you are thinking of but also the limited time of other developers.
> Regards
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-11 10:28 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
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 [this message]
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=20060711102822.GK13938@stusta.de \
--to=bunk@stusta.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=atlka@pg.gda.pl \
--cc=galibert@pobox.com \
--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