From: Glenn Maynard <g_sf@zewt.org>
To: alsa-devel@lists.sourceforge.net
Subject: Detecting ALSA OSS emulation
Date: Mon, 8 Dec 2003 07:06:57 -0500 [thread overview]
Message-ID: <20031208120657.GD535@zewt.org> (raw)
Is there a reliable way to find out if /dev/dsp is being handled by
ALSA? I want to be able to detect this for diagnostics. (If /dev/dsp
is ALSA, the native alsa-lib code should have been used, and something
has gone wrong.) Currently, I'm checking for the existance of
/proc/asound/version, but at least one user had a configuration where
that file existed but /dev/dsp was really OSS.
(That's what it looked like, and what he claimed, at least; I havn't
tried to reproduce that configuration, with both ALSA and OSS loaded
and only OSS actually handling sound. It's possible something else
was happening and the user was wrong.)
--
Glenn Maynard
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
next reply other threads:[~2003-12-08 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 12:06 Glenn Maynard [this message]
2003-12-09 11:26 ` Detecting ALSA OSS emulation Jaroslav Kysela
-- strict thread matches above, loose matches on Subject: below --
2003-12-08 12:15 p z oooo
2003-12-08 21:16 ` Glenn Maynard
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=20031208120657.GD535@zewt.org \
--to=g_sf@zewt.org \
--cc=alsa-devel@lists.sourceforge.net \
/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