[alsa-devel] UCM questions
lrg at slimlogic.co.uk
Sat Jan 22 00:37:05 CET 2011
On Fri, 2011-01-21 at 14:53 -0600, pl bossart wrote:
> >> I am fine with a system-specific configuration file for each use case,
> >> but if I have to change the defines in alsa-lib it's a bit of a pain.
> >> It'll imply branches and specific packages just for a stupid include
> >> file.
> > If the define isn't there you should just be able to use a string - no
> > need to update the header file unless the thing being added is
> > sufficiently general that it seems like a good idea.
> I think I am missing something here.
> First I believe there's only one application (PulseAudio or resource
> management of some sort) that will talk to UCM. Player applications
> shouldn't know anything about UCM, right? You would end-up making
> conflicting decisions.
Yes, it's intended only Pulseaudio (or similar) will directly control
the use case.
> Next, if everyone can add #defines and craft new strings to represent
> verbs, this central application/module will either ask for use cases
> that are not supported everywhere, or limit itself to 'common' use
> cases. Or do we expect to rewrite this on each and every platform?
> Wouldn't it make sense to avoid branches and proliferation by limiting
> the definition of use cases and instead only allow for changes in
> configuration files?
The intention is to add all the reasonable use case types to the ucm
header. We should still support bespoke use cases, but we should aim to
include as many popular use cases as possible in ucm. I was only
thinking of phone related use cases when devising the original verbs.
Please do send a patch for any additional verbs you can think off :)
> Alsa-devel mailing list
> Alsa-devel at alsa-project.org
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
More information about the Alsa-devel