From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stas Sergeev <stsp@aknet.ru>
Cc: ALSA devel <alsa-devel@alsa-project.org>
Subject: Re: how to mandate the use of PCM plugin?
Date: Mon, 27 Sep 2010 15:00:12 -0700 [thread overview]
Message-ID: <20100927220012.GA7817@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4CA03F7D.8040602@aknet.ru>
On Mon, Sep 27, 2010 at 10:53:49AM +0400, Stas Sergeev wrote:
> 27.09.2010 09:54, Mark Brown wrote:
> >Why not work on fixing the actual problem if it's not already been
> >fixed?
> I am not sure what's the actual fix would
> look like. I wasn't followed the alsa development
I can't really comment since I've no idea what the problem is; if it's
not understood what has gone wrong then some diagnosis will be needed.
> So the question is: can _all_ the plugins be safely
> replaced by the software that opens "hw", or,
> maybe, some are not, and then, they should be
> somehow mandated?
The entire plugin stack is subject to customisation.
> So what the real fix do you think of?
Like I say, I've no idea what the actual problem is so can't really
comment.
next prev parent reply other threads:[~2010-09-27 21:59 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
2010-09-27 5:54 ` Mark Brown
2010-09-27 6:53 ` Stas Sergeev
2010-09-27 22:00 ` Mark Brown [this message]
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=20100927220012.GA7817@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=stsp@aknet.ru \
/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;
as well as URLs for NNTP newsgroup(s).