search

probonopd / wayland-x11-compat-protocols

The missing Wayland protocols for features that are available in X11 (but are denied by the official Wayland protocols)
115 stars 3 forks source link

Proprietary drivers #2

Open ytrezq opened 10 months ago

ytrezq commented 10 months ago

1 thing Xwayland doesn t solve is proprietary drivers.

In my case, I have a Aspeed as2500 video card. It s driver is now only maintained on Windows. On linux and Freebsd it s a full userspace driver consisting of a shared object blob for Xorg named ast_drv.so that can be used with nomodeset and allow playing drm videos.

The removal of the support of Xorg for major desktop environments from Fedora leave getting a black screen as the only option or use a lightweight desktop environment that doesn t let configure things like printers or the systems timezone.

probonopd commented 10 months ago

Agree.

But this probably cannot be solved by adding an unofficial protocol to Wayland, can it?

ytrezq commented 10 months ago

It seems you re right.

I just found this https://en.wikipedia.org/wiki/Rio_(windowing_system). Filesystem oriented so run on network if the Filesystem itself is networked.

probonopd commented 10 months ago

If it comes from Plan 9 it's probably good, but I guess there aren't many applications that support it because frameworks like Qt don't run there?

ytrezq commented 10 months ago

This makes Wayland yet an other example of designing something new from scratch instead of trying to revive something better.

Outside qtk and gtk, I doubt it even support OpenGl.

marcthe12 commented 10 months ago

Well technicaly the solution would be a system compositor. Wayland compositor (aleast occurring to the docs) allows nested. There was provision of a system wide compositor (as root like XORG) if one chooses but was never implemented (except maybe cage). In theory a system compositor can be a user space driver.