From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: OSS driver cleanups.
Date: Mon, 03 Dec 2001 19:13:04 -0500 [thread overview]
Message-ID: <3C0C1510.DBDA6146@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0112031105230.28692-100000@netfinity.realnet.co.sz>
Zwane Mwaikambo wrote:
> I know OSS will be replaced with ALSA soon, but i've got a couple of OSS
> cleanup patches lined up (module usage count, power management patches
> for two cards) for both 2.4.x and 2.5.x, should i continue with them or is
> it not worthwhile?
IMHO they are useful for 2.5 series, perhaps backported to 2.4 later.
I'm sure people will continue using the OSS drivers even after they
become the "old" sound drivers... for a while at least.
Eventually we will have a pleasant future where we have a sane API that
is scalable for expensive sound hardware, with kernel changes mitigated
by a central userspace kind of libc-for-sound. a.k.a. alsa and
alsa-lib.
Also FWIW, I support getting ALSA into the 2.5 kernel sooner rather than
later. I had hoped to review alsa before it got in, but that kept
getting put off.
Getting ALSA into the kernel in early 2.5 will allow for a longer period
of public review, and a longer period to smooth out the rough spots and
finalize the kernel<->userspace interface.
I have style quibbles with ALSA but the ALSA guys much to their credit
are very responsive and tackle technical issues as soon as they are made
aware. And having alsa-lib sit between kernel and userspace is the
correct and right idea, opening up all sorts of new possibilities for
the future of Linux audio.
Jeff
--
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-12-04 1:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 9:11 OSS driver cleanups Zwane Mwaikambo
2001-12-03 9:30 ` Alan Cox
2001-12-04 0:13 ` Jeff Garzik [this message]
2001-12-04 16:49 ` Jamie Lokier
2001-12-04 16:55 ` Jeff Garzik
2001-12-04 17:29 ` [s-h] " Takashi Iwai
2001-12-04 16:34 ` gmack
2001-12-04 17:42 ` Alan Cox
2001-12-04 17:10 ` Alan Cox
2001-12-04 17:15 ` Jordan Breeding
2001-12-04 17:42 ` Jeff Garzik
2001-12-04 20:24 ` Dan Hollis
2001-12-05 6:23 ` J Sloan
2001-12-05 11:05 ` Takashi Iwai
2001-12-04 1:18 ` John Gluck
2001-12-04 9:50 ` Zwane Mwaikambo
2001-12-04 14:35 ` Jeff Garzik
2001-12-04 18:42 ` Piter Punk
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=3C0C1510.DBDA6146@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linux.realnet.co.sz \
/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