From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Jamie Lokier <lk@tantalophile.demon.co.uk>
Cc: Zwane Mwaikambo <zwane@linux.realnet.co.sz>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: OSS driver cleanups.
Date: Tue, 04 Dec 2001 11:55:49 -0500 [thread overview]
Message-ID: <3C0D0014.DE548F9A@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0112031105230.28692-100000@netfinity.realnet.co.sz> <3C0C1510.DBDA6146@mandrakesoft.com> <20011204164943.D28839@kushida.jlokier.co.uk>
Jamie Lokier wrote:
>
> Jeff Garzik wrote:
> > I'm sure people will continue using the OSS drivers even after they
> > become the "old" sound drivers... for a while at least.
>
> Not least because I have reports from my housemate that ALSA drivers are
> a b*tch to set up. To be done only if there isn't an OSS driver for
> your card. Whereis with OSS you just load a module and its done.
If "modprobe snd-card-via686" doesn't just-work that is a regression
from 2.4 and thus a bug. There should be no alsa-conf or anything else
required for these drivers to work.
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 16:58 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 [this message]
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=3C0D0014.DE548F9A@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@tantalophile.demon.co.uk \
--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