another input/output question (libinput / pulseaudio / ....)
mclasen at redhat.com
Tue Feb 10 19:09:55 UTC 2015
On Mon, 2015-02-09 at 08:44 +1000, Peter Hutterer wrote:
> However, especially for libinput, it gets hazy and also mostly pointless.
> aside from some special processing required for touchpads and tablets, we
> don't care much _what_ a device is, we just pass on the events. If a device
> has keys, it'll be a keyboard. if it sents KEY_MUTE we pass that on, the
> compositor/X stack will then handle that however need be. There's no real
> benefit to us trying to figure out what is a headset and what isn't, we'd
> still just pass on the keys.
Fair enough. One thing that is important, though, is to preserve enough
information about the originating device (and the general device
topology) that higher levels have a chance to do the right thing (e.g.
mute the headset and not the speakers, if that is where the mute button
More information about the devel