[PATCH kdrive/ephyr v7 5/9] kdrive: add options to set default XKB properties

Peter Hutterer peter.hutterer at who-t.net
Tue Feb 9 21:46:30 UTC 2016

On Tue, Feb 09, 2016 at 10:23:05AM -0200, LaƩrcio de Sousa wrote:
> Em 9 de fev de 2016 02:24, "Peter Hutterer" <peter.hutterer at who-t.net>
> escreveu:
> > when we introduced the udev config backend we mostly agreed that we
> weren't
> > going to use udev as a config storage (which is how InputClass was
> > conceived). Debian ships them because there was some release timing
> conflict
> > where the udev patches where ready but the InputClass bits weren't but
> aside
> > from Debian I don't expect any distro to set the xkb config via udev.
> I wonder if kdrive could gain InputClass support, a new libinput driver or
> even share the same input drivers with Xorg itself, but I'm aware that
> hardware input direct support in kdrive is for a very particular use case
> (although it has a very large demand here in Brazil), so I would let this
> for a second moment.

theoretically yes, and should be relatively trivial with libinput.
The alternative would be to let kdrive use the xfree86 API hooks for input

That is orthogonal to the InputClass support though which comes from the
xorg.conf system. That would have to split out of hw/xfree86 and move into a
higher-level configuration.

all technically possible but it's a fair bit of work and no-one has done it
so far.


More information about the xorg-devel mailing list