[gta02] Correct alsastatefile fits all Neos

[Mark Brown]

On Fri, Feb 13, 2009 at 06:43:32AM +0100, Joerg Reisenweber wrote:

> First step would be the name of alsa soundcard devicedriver should represent 
> the differences in hardware.

That should already be the case, hopefully.

> Next we could think about a straight way to make alsamixer, alsactl etc use 
> the right alsa.state file (section?) matching the actually loaded 
> devicedriver.

Probably all you need here is to have the config files stored separately
and then set up a symlink pointing at those for the particular device
during boot.  At runtime everything just uses the symlink.

> usually is done via `amixer` cmd. A script comprising a number of amixer cmds 
> would be an alternative way to `alsactl -f scenario.state restore` for 
> setting up a mixer route. Advantage would be you could overlap multiple such 
> settings as each script leaves controls untouched that are not involved in 
> the particular setting.

The secenario API at:

	http://www.slimlogic.co.uk/?p=40

is still under development but it's intended to help address issues like
this.  It will also deal with things like allowing applications to know
which controls should be presented to end user applications.