Mir Working On Evdev Device Detection

[phoronix]

Phoronix: Mir Working On Evdev Device Detection

Besides working on the legacy X11 support atop Mir, Canonical developers working on this display server have just implemented evdev device detection for Mir...

http://www.phoronix.com/scan.php?page=news_item&px=Mir-Evdev-Device-Detection

[gufide]

useless... libinput as been made to become the standard not only in wayland, but in X11 too. There's nothing preventing canonical to use it. Even if they want thier own display server stack, there is already something production ready for the input stack.

This is becoming ridiculus...

[Bestia]

Michael I don't know why you are looking at that particular branch for the libinput integration.

Andreas Pokorny is still actively working on it and the latest commits that he made are from yesterday.

https://code.launchpad.net/~andreas-pokorny/mir/libinput-platform

There is also:

https://code.launchpad.net/~andreas-pokorny/mir/libinput-package

[Bestia]

Also in the branch that you write about evdev device detection there is this:

Another split out of the libinput branch

Besides this is how libevdev fits into this whole thing:

https://en.wikipedia.org/wiki/Evdev

For Weston/Wayland, the stack would look like this:

Linux kernel → libevdev → libinput → Weston → Wayland client

[bregma]

useless... libinput as been made to become the standard not only in wayland, but in X11 too. There's nothing preventing canonical to use it. Even if they want thier own display server stack, there is already something production ready for the input stack.

I see an awful lot of contributions from Canonical to upstream libinput (eg. see http://lists.freedesktop.org/archive...er/thread.html where libinput development piggybacks on the Wayland infrastructure). What makes you think Canonical is not using it, and not actively involved in developing it?

Perhaps you don't realize evdev is the Linux kernel interface to input devices upon which higher-level userspace layers like libinput are built?

[gens]

I see an awful lot of contributions from Canonical to upstream libinput (eg. see http://lists.freedesktop.org/archive...er/thread.html where libinput development piggybacks on the Wayland infrastructure). What makes you think Canonical is not using it, and not actively involved in developing it?

Perhaps you don't realize evdev is the Linux kernel interface to input devices upon which higher-level userspace layers like libinput are built?

but how will one bash on canonical then ?

[FireBurn]

Let's not let facts get in the way of good flame bait...