[alsa-devel] how to mandate the use of PCM plugin?
broonie at opensource.wolfsonmicro.com
Tue Sep 28 00:00:12 CEST 2010
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
> 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
More information about the Alsa-devel