Updated Home (markdown)

Home.md

@@ -806,6 +806,7 @@ Sometimes the kernel driver has trouble detecting hotplugged monitors on some po
 
 
 ### How do I utilize `wp-fractional-scale-v1` since Sway 1.9?
+
 [Fractional scale protocol](https://wayland.app/protocols/fractional-scale-v1)
 
 > This protocol allows a compositor to suggest for surfaces to render at fractional scales.
@@ -813,3 +814,30 @@ Sometimes the kernel driver has trouble detecting hotplugged monitors on some po
 * recent [versions of Chrome/Chromium/Blink Derivatives](https://www.phoronix.com/news/Chrome-fractional-scale-v1) utilize it automatically
 * [recent Firefox versions](https://bugzilla.mozilla.org/show_bug.cgi?id=1420259) require `about:config` `widget.wayland.fractional-scale.enabled=true`, which is as of 2024-03 having two bugs. [Context Menu Broken](https://bugzilla.mozilla.org/show_bug.cgi?id=1849109), [Blurred Windows when not maximized](https://bugzilla.mozilla.org/show_bug.cgi?id=1849092)
 * [mpv](https://github.com/mpv-player/mpv/issues/8514) in standard configuration/wayland mode will utilize it automatically and appears to have no known issues
+
+### No hardware acceleration since Sway 1.10
+
+Typically this results in error messages like these:
+
+```
+vulkan: No DRI3 support detected - required for presentation
+Note: you can probably enable DRI3 in your Xorg config
+```
+
+or
+
+```
+DRI3 not available
+```
+
+or VA-API fails to initialize.
+
+Sway 1.10 has removed support for the legacy `wl_drm` Wayland protocol, which is still used by Xwayland 23.2.4 and earlier, libva 2.20.0 and earlier, and AMDVLK.
+
+As a workaround, the legacy `wl_drm` Wayland protocol can be re-enabled manually by passing `-Dlegacy-wl-drm` to Sway.
+
+See:
+
+- [xserver!1236](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1236)
+- [libva#788](https://github.com/intel/libva/pull/788) and [libva#790](https://github.com/intel/libva/pull/790)
+- [AMDVLK#351](https://github.com/GPUOpen-Drivers/AMDVLK/issues/351)