| Summary: | Improve device management | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Joshua Lock - Disabled <josh> |
| Component: | meta-yocto | Assignee: | Joshua Lock - Disabled <josh> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | jessica.zhang, jiajun.xu, poky.bs.watcher, poky.watcher, richard.purdie, sgw, song.liu |
| Version: | unspecified | ||
| Target Milestone: | 1.2 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | (P2) (No QA Needed Currently) (Done) | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Joshua Lock - Disabled
2011-10-04 11:00:02 UTC
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 |