mutter/data/61-mutter.rules

DRIVERS=="i915", SUBSYSTEM=="drm", TAG+="mutter-device-disable-kms-modifiers"
DRIVERS=="nouveau", SUBSYSTEM=="drm", TAG+="mutter-device-disable-kms-modifiers"
DRIVERS=="amdgpu", SUBSYSTEM=="drm", TAG+="mutter-device-disable-kms-modifiers"
DRIVER=="vkms", SUBSYSTEM=="platform", TAG+="mutter-device-ignore"
backend/native: Only disable KMS modifiers for i915 The intel DRM driver is known for not being able to handle multi head setups when KMS modifiers are enabled, due to the implicitly selected modifiers, while being more suitable for single head setups, cause bandwidth issues when a certain number of monitor times resolution and refresh rate is configured. We don't yet support automatically finding a combination of modifiers that work, and have because of this disabled KMS modifiers unless the driver actually needs it. Lets flip this configuration the other way around, changing the current udev rule to decide wen to disable KMS modifier support, as it so that only the Intel driver has this problem, while on the other hand, there several drivers that requires modifiers to function at all. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1792> 2021-03-19 07:08:21 -04:00			`DRIVERS=="i915", SUBSYSTEM=="drm", TAG+="mutter-device-disable-kms-modifiers"`
backend/native: Disable KMS modifiers for amdgpu and nouveau as well Lets wait until we have better ways to unredirect client buffers before we start enabling KMS modifiers for amdgpu and nouveau; we end up with mismatch between client buffer modifiers and primary plane modifier, which right now needs to be the same for unredirection. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1792> 2021-04-14 02:42:49 -04:00			`DRIVERS=="nouveau", SUBSYSTEM=="drm", TAG+="mutter-device-disable-kms-modifiers"`
			`DRIVERS=="amdgpu", SUBSYSTEM=="drm", TAG+="mutter-device-disable-kms-modifiers"`
backend/native: Add udev rule to ignore vkms devices Virtual Kernel Mode Setting (vkms) is a virtual /dev/dri/card* device not backed by any actual hardware. It's intended for testing purposes, e.g. to run tests suites with a reproducable setup, or in continuous integration pipelines. Currently mutter don't have any tests that can run on top of vkms, but will eventually get that. To prepare for the ability to do that, and having said kernel module loaded without causing wierd issues with any active session, add an udev rule that tells mutter to ignore any vkms device. Otherwise, when vkms is loaded, mutter would detect it, assume it's a regular monitor, configure it as such, thus add a region of the stage that ends up nowhere, which isn't very helpful. It might also conflict with running actual tests that need to interact with vkms if the active session has taken control of it. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1740> 2021-02-23 04:50:33 -05:00			`DRIVER=="vkms", SUBSYSTEM=="platform", TAG+="mutter-device-ignore"`