summaryrefslogtreecommitdiffstats
path: root/patches/packages/xorg-server-xwayland-21.1.4-x86_64-2_slack15.0.txt
diff options
context:
space:
mode:
Diffstat (limited to 'patches/packages/xorg-server-xwayland-21.1.4-x86_64-2_slack15.0.txt')
-rw-r--r--patches/packages/xorg-server-xwayland-21.1.4-x86_64-2_slack15.0.txt11
1 files changed, 11 insertions, 0 deletions
diff --git a/patches/packages/xorg-server-xwayland-21.1.4-x86_64-2_slack15.0.txt b/patches/packages/xorg-server-xwayland-21.1.4-x86_64-2_slack15.0.txt
new file mode 100644
index 000000000..44e18f2cf
--- /dev/null
+++ b/patches/packages/xorg-server-xwayland-21.1.4-x86_64-2_slack15.0.txt
@@ -0,0 +1,11 @@
+xorg-server-xwayland: xorg-server-xwayland (X Clients under Wayland)
+xorg-server-xwayland:
+xorg-server-xwayland: Wayland is a complete window system in itself, but even so, if we're
+xorg-server-xwayland: migrating away from X, it makes sense to have a good backwards
+xorg-server-xwayland: compatibility story. With a few changes, the Xorg server can be
+xorg-server-xwayland: modified to use Wayland input devices for input and forward either the
+xorg-server-xwayland: root window or individual top-level windows as wayland surfaces. The
+xorg-server-xwayland: server still runs the same 2D driver with the same acceleration code
+xorg-server-xwayland: as it does when it runs natively. The main difference is that Wayland
+xorg-server-xwayland: handles presentation of the windows instead of KMS.
+xorg-server-xwayland: