From: Stas Sergeev <stsp@aknet.ru>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: ALSA devel <alsa-devel@alsa-project.org>
Subject: Re: how to mandate the use of PCM plugin?
Date: Mon, 27 Sep 2010 08:48:29 +0400 [thread overview]
Message-ID: <4CA0221D.6030208@aknet.ru> (raw)
In-Reply-To: <20100927005858.GD21247@sirena.org.uk>
Hello.
27.09.2010 04:58, Mark Brown wrote:
>> Is it possible to somehow mandate the
>> use of a PCM plugin? For example, the
>> PC-Speaker.conf defines the use of softvol
>> plugin for "default" and "front" devices.
>> It is still possible for the software to bypass
>> it by the use of "hw", and some software
>> does exactly that.
>> Is it possible to somehow make some
>> plugin a mandatory?
> What is the actual problem you are trying to solve here? It's not
> possible to *mandate* anything to all users, if nothing else someone
> with administrative access can always rebuild whatever part of the
> system is trying to restrict them.
What I am trying to solve, is the problem
that people have with my snd-pcsp driver.
Pulseaudio uses "hw" to bypass some pcm
plugins, and then people are left with the
non-functional softvol control, and they blame
my driver.
I am looking for the way to mandate the
softvol plugin even for the "hw" device.
Is this possible?
next prev parent reply other threads:[~2010-09-27 4:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 15:17 how to mandate the use of PCM plugin? Stas Sergeev
2010-09-27 0:58 ` Mark Brown
2010-09-27 4:48 ` Stas Sergeev [this message]
2010-09-27 5:54 ` Mark Brown
2010-09-27 6:53 ` Stas Sergeev
2010-09-27 22:00 ` Mark Brown
2010-09-28 5:38 ` Stas Sergeev
2010-09-28 9:36 ` Raymond Yau
2010-09-27 14:40 ` Stas Sergeev
2010-09-27 17:57 ` Colin Guthrie
2010-09-28 1:01 ` Raymond Yau
2010-09-28 4:07 ` Raymond Yau
2010-09-29 9:28 ` David Henningsson
2010-10-02 2:11 ` Raymond Yau
2010-10-04 7:51 ` Alsamixertest (was: how to mandate the use of PCM plugin?) David Henningsson
2010-10-04 12:01 ` Alsamixertest Clemens Ladisch
2010-10-04 12:25 ` Alsamixertest David Henningsson
2010-10-04 12:34 ` Alsamixertest Clemens Ladisch
2010-10-06 4:08 ` Alsamixertest Raymond Yau
2010-10-05 1:50 ` Alsamixertest Raymond Yau
2010-10-12 14:33 ` Alsamixertest Raymond Yau
2010-10-21 4:36 ` Alsamixertest Raymond Yau
2010-10-21 7:50 ` Alsamixertest David Henningsson
2010-10-22 1:53 ` Alsamixertest Raymond Yau
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=4CA0221D.6030208@aknet.ru \
--to=stsp@aknet.ru \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.