[alsa-devel] Jack event API - decision needed
broonie at opensource.wolfsonmicro.com
Mon Jun 20 19:07:40 CEST 2011
On Mon, Jun 20, 2011 at 03:37:25PM +0200, David Henningsson wrote:
> I'm still new in the community in that sense that I'm not sure how
> decisions are made. But I could use the outcome of such a decision.
So, I'm still not 100% sure what the actual technical issue is here?
> As part of that I wrote a udev patch a few days ago, which nobody
> commented on in alsa-devel , but was somewhat disliked by at
Having dug out the mailing list archive I guess the fact that you just
posted it to the list and didn't CC anyone on the patch didn't help
here. Looking at the patch the main thing that jumps out at me without
any knowledge of the udev code is that the patch will end up classifying
video output jacks as audio even if they've no audio capability which is
obviously not correct.
I still don't entirely understand the technical issue you're trying to
address here - this doesn't seem specific to audio. As far as I can
tell the issue is that some of the input devices on the system aren't
being made available to the console user, presumably because there are
some that shouldn't be made available to them, so the issue is that the
heuristics that udev uses to decide if an input device should be root
only aren't working correctly in at least this case. It feels like if
we understood why the heuristics are making a bad call here we might be
able to come up with a better solution.
> least Kay Sievers who maintains udev , who preferred we would
> rewrite our input layer to do something else within ALSA.
It seems like Kay's issues are based on a misunderstanding about what a
jack might be.
> 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...?
There's a reasonable amount of usage in the embedded space.
More information about the Alsa-devel