Back

And then, I went and finally pushed my epoll reworking over the finish line — there was not that much work left, but it had to be done. Once it was, everything fell into place, and now long polls work, short polls work, polls with no interests (basically using epoll as a sleep) work, signals work (including pwait and pwait2 atomically changing the signal mask), and everything seems to just work.

Also apparently my epoll is going into the Hurd upstream soon? Exciting!

Next, I took my "portable" Wayland patchset and rebased it onto latest upstream main. It's both better and worse; the upstream have done some BSD portability work, so equivalents of some of my changes have effectively been upstreamed, but also they added eventfd usage, so, yay, more things to patch out.

Anyway, so I got Wayland building on the Hurd once again. The tests don't yet pass, I'll need to look into that tomorrow.

After that: Owl, and gtk with its Wayland backend.

@bugaevc congrats. Wayland doesn't depend on linux DRM

@bugaevc I know you work on that in the past. But I want to know if Wayland can work without DRM support

@gfleury it can! But Wayland is just a protocol, you also need clients & a compositor, and those are likely to want DRM. Owl doesn't, but more advanced ones like Weston and Mutter will. Which is why we probably want DRM on the Hurd, if we can port it.