Re: Wayland work status

Thanks for the help Matthew.. Yeah, I can't believe it was working all along and a stupid copy/paste error gave us so much trouble... On Sat, Aug 13, 2016 at 12:26 AM, Matthew Macy wrote: > > > > > ​Wayland relies on kqueue which is not implemented in drm's 3.8 or 4.6 > >

Re: Wayland work status

> > ​Wayland relies on kqueue which is not implemented in drm's 3.8 or 4.6 > branches. I'm working on this now for drm-next-4.6 and it is almost > complete. > I will probably implement it also in the 3.8 ​branch to be able to run > Wayland on both to compare and find bugs in linuxkpi more

Re: Wayland work status

Hi I followed the instructions for evdev enabled kernel here https://github.com/wulf7/libudev-devd and it works fine! I needed to update libinput to latest version since it was required by xf86-input-libinput so I'm using latest version from https://github.com/jiixyj/libinput. As for the wsp

Re: Wayland work status

Hi, On 12.08.16 19:22, Lundberg, Johannes wrote: ​Where can I find xf86-input-libinput for FreeBSD? Will the original source build? Yes, the original source (https://cgit.freedesktop.org/xorg/driver/xf86-input-libinput/) will build unmodified. I've copied libinput_drv.so to

Re: Wayland work status

> > If you feel adventurous, you can try out the current state of the libinput > port here (1.4.0): > https://github.com/jiixyj/libinput > > ​Great! Will check it out. ​ > I haven't yet tested the port with the evdev kernel work, though. I've > been using my evdev implementation in userspace

Re: Wayland work status

> There is a similar problem for the drm devices (by default, users can’t > use 3D acceleration). A devfs.conf policy can change the permissions. I’d > suggest that we create a default group called something like console or > local, put new users there by default, and make drm and evdev devices

Re: Wayland work status

Hi, On 12.08.16 01:18, Lundberg, Johannes wrote: x11/libinput (removed udev-stubs and linked to libudev-devd) If you feel adventurous, you can try out the current state of the libinput port here (1.4.0): https://github.com/jiixyj/libinput I haven't yet tested the port with the evdev kernel

Re: Wayland work status

On 12 Aug 2016, at 00:18, Lundberg, Johannes wrote: > > Currently by default evdev create /dev/input/eventX devices with 600 > permission. These need to be accessible for non-root users. What is the > best solution? Should we create a "input" group similar to