On 7 January, 2020 3:52:37 PM PST, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:
On Tue, 7 Jan 2020 at 11:04, nia <nia%netbsd.org@localhost> wrote:
On Tue, Jan 07, 2020 at 11:02:50AM +0100, Benny Siegert wrote:
When you say "Wayland turned on by default"...
This means that core toolkits can now talk the protocol without needing
to be recompiled.
does that mean you can run a Wayland display server instead of an X
server on NetBSD 9?
Is there such a server?
See wm/velox. Read MESSAGE.
Or would you run something like Weston in the existing X session?
Weston is pretty Linuxy. Might have another look at it at some point, but
I'm trying to rely on shims and compat as little as possible.
You might notice devel/wayland has been patched to use kqueue directly.
Similarly, velox has been patched to use wscons directly.
Just for fun I tried wm/velox on my intel 915 laptop with functioning
drm, as per the message in velox.
It starts, shows the screen fine, together with the status bar - which
then proceeds to load 100% one CPU thread and does not react to
anything else; I also can't switch to other cpnsole screens as with X,
but that is probably to be expected. I had to ssh to the system to
kill status_bar and velox to get the console back. I even installed
sakura, which by default is invoked as a terminal emulator, according
to the default configuration, but it didn't start (ALT+SHIFT+RETURN).
I guess it is early days. I wasn't aware at all that wayland is getting here.
But, again, I want to talk about this at FOSDEM... :)