From: Andre Tomt <andre@tomt.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Bill Davidsen <davidsen@tmr.com>
Subject: Re: Does OSS sound work in 2.6 or not?
Date: Fri, 09 Apr 2004 00:25:25 +0200 [thread overview]
Message-ID: <4075D155.2030603@tomt.net> (raw)
In-Reply-To: <4075BDE0.6050302@tmr.com>
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.
>
> if this really works, could someone point me to a working example? I
> have copied the Documentation/sound config for OSS, changing only the
> sound card type, and it totally doesn't work. It looks like it plays but
> it doesn't make any sound.
>
> I know that if I convert to ALSA I have to use their mixer to turn up
> the sound and disable mute, if all the people telling me they do it with
> the OSS mixer and emulation are wrong, I'll just leave the machines on
> 2.4 until I get some time to waste.
>
> I have read the docs I can find, this is a yes/no question, will OSS
> work or not. I am not asking how to convert to ALSA, did that once, took
> more time than the benefit justifies.
OSS works just fine here in 2.6, on all the machines I have. I don't use
ALSA's OSS emulation layer, just the "native" OSS thats in the kernel.
It's used just like in 2.4, same module names and all. No black magic
involved.
--
Cheers,
André Tomt
next prev parent reply other threads:[~2004-04-08 22:25 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 [this message]
2004-04-13 17:04 ` Bill Davidsen
2004-04-13 22:51 ` Tom Sightler
2004-04-08 22:37 ` Tom Sightler
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=4075D155.2030603@tomt.net \
--to=andre@tomt.net \
--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