Hacker News new | ask | show | jobs
by klooney 483 days ago
FreeBSD already ported it, I don't know a about the rest. Why do you think it's particularly tied to Linux?
2 comments
jmclnx 483 days ago
Because to get it working, something like udev, edev, libinput needs to be brought over, polluting a clean system. Some quotes from:

https://xenocara.org/Wayland_on_OpenBSD.html

>Input is more complex to get working since Wayland applications expect Linux input model with udev, evdev and libinput.

>seatd and libseat provide support for non-systemd based systems. A basic port to OpenBSD/wscons is needed

So Wayland requires Linux specific items to be ported to BSD. Maybe FreeBSD did all that work themselves. Was that work accepted into upstream ? Based on how Linux works these days, I doubt it. So maybe each new Wayland Release will need to be patched for FreeBSD.

link
wkat4242 483 days ago
That patching is nothing new. It's pretty automated on FreeBSD. It has a ports system that does just that.

I don't think udev is ported though. Some linuxisms are, like dbus because several desktops need it. But FreeBSD has its own udev alternative called devd. Wayland is probably configured to just use that.

link
ahartmetz 483 days ago
The compositor needs to talk to the hardware using kernel API and there's a bit of plumbing required, like for OpenGL / Vulkan apps to get a context under Wayland. Which isn't really "particularly" tied.
link