[alsa-devel] Jack event API - decision needed

Liam Girdwood lrg at ti.com
Tue Jun 28 18:34:28 CEST 2011

On 28/06/11 17:27, David Henningsson wrote:
> On 2011-06-27 13:07, Mark Brown wrote:
>> On Mon, Jun 20, 2011 at 03:37:25PM +0200, David Henningsson wrote:
>>> 1) We're continuing the path with /dev/input devices
>>> 2a) We'll rewrite these devices to be read-only ALSA mixer controls
>>> 2b) We'll rewrite these devices to be something within ALSA, but not
>>> exactly mixer controls.
>>> For options 2a) and 2b) I guess the existing /dev/input thing should be
>>> deprecated and/or removed. So part of decision should maybe be based on
>>> information about how widespread the usage of these devices are
>>> currently...?
>> So, this discussion seems to have ground to a halt.
> Yes, unfortunately, and without a clear consensus. That puts me in a 
> difficult position, because I'm trying to get the job done. And very 
> preferrable, in the next release of Ubuntu (which is to be released on 
> October this year). I've been talking to a few of my colleagues here at 
> Canonical, and here's how we reason currently:
> We have the input layer. We also have a set of patches for supporting 
> this in PulseAudio (although currently unmerged and I'm not sure about 
> their current quality/state).

I know that these are working on Panda and that Graeme is addressing review comments for upstream. Don't know his ETA yet though.


More information about the Alsa-devel mailing list