Wayland work status
johannes at brilliantservice.co.jp
Thu Aug 11 23:19:00 UTC 2016
Here's a status update of my work and some questions.
FreeBSD 12-CURRENT (
Package installed from this tree
graphics/wayland (built without modification)
x11/libinput (removed udev-stubs and linked to libudev-devd)
Mesa-related (libEGL libGL libglesv2 libglapi libdrm)
Needed to update patches a bit to have them patch cleanly.
I'm using this compositor library and the example implementation that comes
with it. I've patched it to run on FreeBSD and will try to push the changes
upstream this week. Maybe we can even make a port for this very excellent
I will not do any work on porting Weston.
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
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 easily. Will
share patch for 3.8 branch when done.
My personal Wayland clients (built on Linux) compile and run nicely with
udev and libinput in a Wayland window with X11 backend (wlc-based
There is a problem with rendering updates when running with drm backend but
will most likely be solved soon.
Input devices and rendering is functional in native KMS (no X11), just a
few small issues to iron out related to kqueue and linuxkpi.
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 "video" group is
being used for rights to access /dev/drm devices?
CONFIDENTIALITY NOTE: The information in this email is confidential
and intended solely for the addressee.
Disclosure, copying, distribution or any other action of use of this
email by person other than intended recipient, is prohibited.
If you are not the intended recipient and have received this email in
error, please destroy the original message.
More information about the freebsd-current