Re:Sway 1.0 is not going to support the Nvidia proprietary d...
by ascent12 on Friday October 27, 2017 @06:43AM
(#15567160)
GBM already IS a userspace layer than abstracts over driver-specific kernel interfaces. That's the whole point.
You also seem to have missed the whole point of wayland's design. There is no separation between "window managers" and "display servers"; there are just "compositors". So naturally it is something that needs to be dealt with. wlc, libweston, wlroots (for which I am an author, responsible for the DRM/GBM code), etc., are designed to make it easier to write compositors and allow for more code reuse. So yes, someone using one of these libraries wouldn't need to deal with these details, but we're actually writing such a library.
Re:Sway 1.0 is not going to support the Nvidia proprietary d...
by badsectoracula on Friday October 27, 2017 @07:27AM
(#15567366)
> You also seem to have missed the whole point of wayland's design. There is no separation between "window managers" and "display servers"; there are just "compositors".
I think the point is that this design is bad.
Another note, a window manager author shouldn’t have to deal with these sorts of issues. Puts into question the “wayland way.” I guess this is what wlc and wlroots are for but seems like those approaches have flaws given there was a need for wlroots to even exist in the first place.