From: Tom Sightler <ttsig@tuxyturvy.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Does OSS sound work in 2.6 or not?
Date: Thu, 08 Apr 2004 18:37:17 -0400 [thread overview]
Message-ID: <1081463836.3223.123.camel@localhost.localdomain> (raw)
In-Reply-To: <4075BDE0.6050302@tmr.com>
On Thu, 2004-04-08 at 17:02, Bill Davidsen wrote:
> I have several user machines I would like to convert to 2.6 because they
> run threaded applications and would be happier if I did. However, being
> able to play forwarded wav files is also needed. I have been assurred by
> several people in Email that it does, *without* converting the whole
> machine from OSS to ALSA, but by running the ALSA+OSS emulation.
Can you clarify the question? What do you mean by "*without* converting
the whole machine from OSS to ALSA"? Do you mean you willing to convert
to the ALSA drivers but want to continue to use OSS applications? Or do
you mean you don't want to convert to ALSA at all? You obviously can't
use ALSA+OSS emulation if your not willing to convert to the ALSA
drivers since basically OSS emulation is just a few ALSA modules you
load *in addition* to the ALSA hardware drivers that allow ALSA to
provide an OSS emulation layer to OSS only applications.
Of course, OSS drivers are still available in 2.6, even though they are
deprecated. You can just continue to use these just like you always
have in 2.4, no ALSA at all.
Later,
Tom
next prev parent reply other threads:[~2004-04-08 22:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 21:02 Does OSS sound work in 2.6 or not? Bill Davidsen
2004-04-08 22:25 ` Andre Tomt
2004-04-13 17:04 ` Bill Davidsen
2004-04-13 22:51 ` Tom Sightler
2004-04-08 22:37 ` Tom Sightler [this message]
2004-04-13 18:24 ` Bill Davidsen
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=1081463836.3223.123.camel@localhost.localdomain \
--to=ttsig@tuxyturvy.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
/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