Device management is currently very manual with things like machine specific recipes to tweak various features in settings files. We have two options to add more generic infrastructure: 1) Enhance Zaurusd into Zaurusd++/devmand - a daemon to handle hardware quirks across a range of boards and devices 2) Integrate alsa-state, the more generic recipe mechanism in use by OE already.
alsa-state can be more quickly integrated as a solution for audio only. Perhaps this issue should be two-phased with the immediate issue being addressed by alsa-state and devmand/zaurus++ development can occur at a more relaxed rate?
Just to contrast the difference, the zaurusd/whatever we want to call it solution allows for multiple variations of hardware to run from the same machine config. The alsa-state solution is more aimed at one config per MACHINE as far as I understand it. The mixer configuration control was already implemented in zaurusd so it shouldn't be too much work to tweak it...
Estimate of 1 perfect days work to integrate alsa-state for each of our BSP's. Zaurusd++/Devmand will hopefully be worked on later in the cycle.
signed off for simple alsa-state implementation, more details will be needed for the full devmand (or whatever it's called).
alsa-state recipe merged to master: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=c86797abdfc6db4b22710cca7924396c16eb6fc0 Adopted for the beagleboard BSP: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=9ea681fffb2944671369bcfd9661d503c0daba4f and the blacksand BSP: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/commit/?id=fad30a44da749bc966cb2d27dc75b4ead15f94f2
I did it