From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Chris Winter <elwintro@gmail.com>,
ALSA development <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 0/3] alsa-lib: UCM - Use Case Manager
Date: Wed, 22 Sep 2010 16:20:28 +0100 [thread overview]
Message-ID: <1285168828.3107.108.camel@odin> (raw)
In-Reply-To: <alpine.LNX.2.00.1009221544480.6226@eeebox2.perex-int.cz>
On Wed, 2010-09-22 at 16:06 +0200, Jaroslav Kysela wrote:
>
> I just finished the implementation for all functions in my GIT tree
> (except card listing). Also, the "Value {}" section is implemented as I
> proposed - it means that users can pass any read-only values to the API
> user.
>
Not had a good look yet, I assume all the functionality from the old API
is preserved ?
> The code is not tested, I need to write a simple command line tool for
> testing the API and also move the control/mixer ID and value handling
> code from the alsa-utils/amixer utility to alsa-lib.
>
Fwiw, there is some command line code for the old API that may be useful
here :-
git://git.slimlogic.co.uk/alsa-utils.git ucm-upstream
Liam
next prev parent reply other threads:[~2010-09-22 15:20 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 16:17 [PATCH 0/3] alsa-lib: UCM - Use Case Manager Liam Girdwood
2010-08-23 16:17 ` [PATCH 1/3] ucm: header - ALSA " Liam Girdwood
2010-08-24 19:09 ` Chris Winter
2010-08-24 20:34 ` Liam Girdwood
2010-08-23 16:17 ` [PATCH 3/3] ucm: build - add build support for " Liam Girdwood
2010-08-23 17:47 ` [PATCH 0/3] alsa-lib: UCM - " Jaroslav Kysela
2010-08-23 17:50 ` Mark Brown
2010-08-23 17:51 ` Mark Brown
2010-08-24 9:09 ` Liam Girdwood
2010-08-25 8:28 ` Jaroslav Kysela
2010-08-25 9:26 ` Liam Girdwood
2010-08-25 9:35 ` Jaroslav Kysela
2010-08-25 10:43 ` Liam Girdwood
2010-08-25 16:34 ` Jaroslav Kysela
[not found] ` <1283864698.3048.26.camel@odin>
2010-09-07 14:42 ` Jaroslav Kysela
2010-09-07 15:53 ` Mark Brown
2010-09-07 18:17 ` Jaroslav Kysela
2010-09-07 18:53 ` Mark Brown
2010-09-08 7:54 ` Jaroslav Kysela
2010-09-08 9:47 ` Mark Brown
2010-09-08 8:19 ` Jaroslav Kysela
2010-09-09 12:16 ` Mark Brown
2010-09-07 20:02 ` Liam Girdwood
2010-09-07 22:43 ` Mark Brown
2010-09-20 16:26 ` Colin Guthrie
2010-09-21 17:13 ` Chris Winter
2010-09-21 17:40 ` Mark Brown
2010-09-21 18:11 ` Jaroslav Kysela
2010-09-22 11:47 ` Colin Guthrie
2010-09-22 13:20 ` Mark Brown
2010-09-22 14:06 ` Jaroslav Kysela
2010-09-22 15:14 ` Mark Brown
2010-09-22 18:05 ` Jaroslav Kysela
2010-09-22 18:48 ` Mark Brown
2010-09-23 7:18 ` Niels Mayer
2010-09-23 10:06 ` Mark Brown
2010-09-25 13:07 ` Colin Guthrie
2010-09-22 15:20 ` Liam Girdwood [this message]
2010-08-24 1:23 ` Raymond Yau
2010-08-24 9:41 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1285168828.3107.108.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=elwintro@gmail.com \
--cc=perex@perex.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.