Files
DroidDeck/tools/gamescope/PATCHES.md
T
The412Banner 55b30fbf1d Non-Adreno round 3: bridge images, Venus GL, shared buffers, Steam GPU drawing
- vkbridge: the memory model skips lazily allocated types. Mali-G615 lists
  DEVICE_LOCAL|LAZILY_ALLOCATED first; taken as the device-local type it left
  images with no memory type (self-test "image clear/draw: setup" FAIL,
  gamescope "No compatible image memory type").
- Session: a bridge self-test that fails images or draws falls back to the
  runtime's driver pair for that session (BL_VKBRIDGE_FALLBACK_ICD); Setup
  and the graphics report say so.
- Venus: the Mali compatibility layer runs in every process but gamescope
  (DROIDDECK_MALI_COMPAT=1), so Zink in Steam and Xwayland gets
  nullDescriptor; null texel-buffer views get stand-ins too. Without
  nullDescriptor the session's GL goes to llvmpipe.
- gamescope 0129: a refused compute pipeline is named with its SPIR-V
  capabilities.
- Compositor: a buffer on two surfaces at once (gamescope's planes while a
  notification is up) is released only when the last one lets go.
- Open driver pairs: processes.txt timeline for the first three minutes;
  Setup "Steam interface: GPU drawing" turns off software web compositing.
2026-10-13 08:44:45 -04:00

6.7 KiB

gamescope patches carried by the app

Built by .github/workflows/build-gamescope.yml on top of the exact gamescope the Linux runtime ships (3.16.29, Arch Linux ARM's package, same build options), and staged from the apk over /usr/local/bin/gamescope at each session start - the hosted runtime image is never touched. The binary's shared-library needs are checked against runtime-sonames.txt, the runtime's own library list, before anything is published.

  • 0002-steamcompmgr-fallback-appid-focus.patch - Armada (armada-os/armada), verbatim.
  • 0009-fix-arm64-steam-night-mode.patch - Armada, verbatim: the ARM64 client packs the night-mode property differently; the slider did nothing.
  • 0019-steamcompmgr-arm64-virtual-white.patch - Armada, verbatim: the colour-temperature slider's (x, y) arrives as one 64-bit element from the ARM64 client; y is recovered from x.
  • 0020-color-p3-red-is-wide-gamut.patch - Armada, verbatim.
  • 0100-realtime-queue-and-gamepad-cursor.patch - this app, two of Armada's ported by hand onto 3.16.29: realtime-priority Vulkan queues on request (GAMESCOPE_FORCE_VULKAN_REALTIME=1) without CAP_SYS_NICE, which proot can never have (a no-op on KGSL Turnip, which has a single submit-queue priority); and the gamepad-driven cursor sprite following the X pointer that XTest moves (it sat frozen). The X pointer is asked for only while a cursor image is drawn - every vblank while shown, every 50 ms while hidden for inactivity - since each ask is a blocking round trip to Xwayland on the paint thread; with no image, wlserver's position is used as upstream does.
  • 0110-wayland-backend-touch.patch - this app: the nested Wayland backend bound only the host's pointer and keyboard, so a finger on the phone's screen never reached Steam. It now binds wl_touch too and hands each finger to wlserver's touch path (wlserver_touchdown / motion / up) - the one a Steam Deck's touchscreen drives - so what a touch does follows the client's touch mode (Steam's Big Picture sets Passthrough: a real touch, rows scroll under a finger). Finger ids are offset by one, since the nested pointer already moves wlserver's touch 0.
  • 0111-wayland-pointer-warps-in-passthrough.patch - this app: the nested pointer's motion goes to wlserver as touch 0, and in Passthrough (Big Picture's touch mode) a motion for a touch that is not down moves nothing - so in the app's touchpad mode the Steam client saw no hover and a click landed wherever the pointer had last been. The motion now always warps the real pointer as well (bAlwaysWarpCursor), which the other touch modes did already.
  • 0112-restore-iconified-game-on-resume.patch - this app: the Steam menu is an overlay that takes input without changing the focus window, and a fullscreen wine game minimizes itself when it loses input. gamescope only takes a window out of iconic when the focus window changes, and wine will not activate a window it believes iconic, so after Resume the game stayed minimized: a black screen with its small caption in the top-left corner (Titanfall 2, GE-Proton 11). The iconify request is remembered and the window goes back to NormalState before input returns to it, then focus is handed over again. GAMESCOPE_RESTORE_FOCUS_WINDOW on the root window asks for the same restore from outside (the session script's resume watcher).
  • 0114-take-override-redirect-from-mapnotify.patch - upstream (ValveSoftware/gamescope 3829340), verbatim; drop it once the runtime's gamescope includes it. Wine creates a game's window override-redirect and makes it managed before mapping it, which sends no X event. When gamescope read the window's attributes first, it kept the window as override-redirect and left it out of GAMESCOPE_FOCUSABLE_WINDOWS, so the client kept its loading screen over the running game (Skyrim SE, A Plague Tale: Innocence, on the games' own Xwayland). MapNotify now refreshes the flag.

The system PowerVR driver uses the existing SDL/Wayland swapchain backend. Its additional patches are:

  • 0120-nested-swapchain-capability-fallback.patch: negotiate the surface's usages, mutable-format support, image count, alpha and extent; use offscreen composition and GPU copies when required.
  • 0121-powervr-single-pixel-rcas.patch: use the existing single-pixel RCAS shader on PowerVR, where the quad variant fails compilation.
  • 0122-powervr-linear-dmabuf-import.patch: retain the explicit linear layout when PowerVR rejects the mutable-format query, and intersect imported-image and FD memory-type masks.
  • 0123-powervr-rgba-copy-surface.patch: require an advertised RGBA SDR copy surface matching the shader's rgba8 storage view. The tested workaround leaves other vendors, HDR and direct composition unchanged; it does not restrict game-facing BGRA formats.
  • 0124-sdl-preserve-explicit-refresh.patch and 0125-sdl-wait-before-present.patch: preserve configured refresh across SDL events and finish composition before presenting without a render-finished semaphore. The build runs the focused capability, format and refresh tests.

Sixteen more of Armada's patches are DRM/lease/HDR-on-KMS work for a native display, which this app's Wayland-hosted gamescope never reaches, or need a newer gamescope than the runtime has.

  • 0126-explicit-sync-switch.patch: GAMESCOPE_DISABLE_EXPLICIT_SYNC=1 makes the nested (Wayland and SDL) backends report no explicit sync, so gamescope does not offer wp_linux_drm_syncobj_manager_v1 and clients use implicit sync. The app sets it on a GPU that is not an Adreno when the kernel is older than 6.6 (no DRM_IOCTL_SYNCOBJ_EVENTFD: an Exynos 2400e on 6.1 logged hundreds of "timeline: DRM_IOCTL_SYNCOBJ_EVENTFD failed" and a game hung at a black screen) or when the render node is Mali's stand-in (/dev/mali0 has no DRM syncobjs).
  • 0127-shm-buffers-upload-every-commit.patch (David Cimo, for Mali through Venus; his 0114): with no DRM node, Xwayland has no glamor and commits a few wl_shm buffers over and over with new pixels. gamescope memoizes one texture per wlr_buffer, and a shm buffer's texture is a copy taken at import, so the screen cycled through the first few frames forever while Steam ran on behind them. Only dma-buf textures are memoized now; a shm buffer is uploaded on every commit. Adreno never takes this path, since its Xwayland hands over dma-bufs. Also what XWAYLAND_NO_GLAMOR sessions need.
  • 0129-log-failing-compute-pipeline.patch: when vkCreateComputePipelines fails, one extra line per shader type names the pipeline (shader type, layer count, ycbcr/colorspace masks, fp16) and the SPIR-V capabilities its shader declares. A Mali-G615 through Venus refused all 119 composite pipelines with VK_ERROR_INITIALIZATION_FAILED and nothing said which feature it objected to.