public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
Cc: John Gluck <jgluck@rogers.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: OSS driver cleanups.
Date: Tue, 04 Dec 2001 09:35:38 -0500	[thread overview]
Message-ID: <3C0CDF3A.2B1AFC56@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0112041146480.24822-100000@netfinity.realnet.co.sz>

Zwane Mwaikambo wrote:
> 
> On Mon, 3 Dec 2001, John Gluck wrote:
> 
> > Hi
> >
> > Out of curiosity, will ALSA also be available on the 24..xx kernels??
> > Will there be a choice of useing OSS or ALSA??
> > Will the ALSA drivers be the 0.9 series or the old 0.5 series??? AFAIK they
> > are very very different in architecture.
> >
> > I welcome the use of ALSA, as it appears to be a more flexibile solution and
> > can be used with OSS compatibility from an application point of view. My only
> > concern is that there is a potential for looseing support for some sound
> > cards.
> 
> I doubt ALSA will get into 2.4 since its maintenance only, but i'm not the
> final authority on this ;) Also when ALSA starts getting incorporated
> into the kernel, they will use their more upto date tree, i would
> presume, so they wouldn't start at 0.5. But as everyone else says, i'm
> sure we'll be backporting fixes and perhaps even additional card support
> into 2.4-OSS as they appear.

IMHO ALSA should -never- go into 2.4.  It's fine as a patch but 2.5 is
the time for big merges, and since it's already available for 2.4
outside the kernel there shouldn't be any need for backporting

	Jeff


-- 
Jeff Garzik      | Only so many songs can be sung
Building 1024    | with two lips, two lungs, and one tongue.
MandrakeSoft     |         - nomeansno


  reply	other threads:[~2001-12-04 14:44 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
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 [this message]
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=3C0CDF3A.2B1AFC56@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=jgluck@rogers.com \
    --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