On Fri, 2009-01-09 at 01:02 +0000, Mark Brown wrote: > Right now my feeling is that we probably want to do at least some > scenario stuff in kernel space and that what's sensible for a given > machine will depend on both the capabilities of the machine (having both > GSM and WiFi causes the number of use cases to get much larger, for > example) and if there's hardware restrictions that need to be enforced > (like not being able to use both speaker and headphones at the same > time, which is fairly common but easily enforced without scenarios as > such). My feeling is that kernel based scenario really should be minimal to non existent depending upon machine. If it has to be implemented then it must be consistent across all devices (probably worth creating a sound/core/scenario.c for others to use). Imho it's far better to do most scenario in userspace due to increasing driver complexity and slow driver scenario development speed (remember the OSS driver pain involved with this). Userspace will additionally give us a consistent API for applications and hopefully much better adoption (esp if merged into alsa-lib / salsa). Btw, I'll be releasing a new version of the ALSA scenario library early Feb. http://www.slimlogic.co.uk/?page_id=7 Liam _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
