From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [PATCH 0/3] alsa-lib: UCM - Use Case Manager Date: Thu, 23 Sep 2010 11:06:00 +0100 Message-ID: <20100923100600.GB25663@rakim.wolfsonmicro.main> References: <20100922132052.GC32476@sirena.org.uk> <20100922151419.GF26395@rakim.wolfsonmicro.main> <20100922184817.GT26395@rakim.wolfsonmicro.main> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from opensource2.wolfsonmicro.com (opensource.wolfsonmicro.com [80.75.67.52]) by alsa0.perex.cz (Postfix) with ESMTP id 102C0103803 for ; Thu, 23 Sep 2010 12:06:03 +0200 (CEST) Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Niels Mayer Cc: Chris Winter , ALSA development List-Id: alsa-devel@alsa-project.org On Thu, Sep 23, 2010 at 12:18:33AM -0700, Niels Mayer wrote: > On Wed, Sep 22, 2010 at 11:48 AM, Mark Brown > > If we make everything procedural now it will become much harder to back > > out of it later, and I would hope that one of the things that use case > > management can do is ensure that users only need to specify their goal > > states and don't need to deal with the mechanics of how to achieve them > > except in exceptional circumstances. > I completely agree. This problem seems best solved by "logic > programming" and ontologies describing both hardware capabilities, > constraints, as well as the applications needs and requirements. Such A strong note of caution here: this is a very difficult task which nobody is currently attempting to do except for very constrained sets of systems such as standard PC hardware. Nothing anyone is discussing here involves the automatic generation of settings, it's all about how we manage sets of explicitly defined settings.