summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJonas Ã…dahl <jadahl@gmail.com>2023-02-01 10:07:53 +0100
committerMarge Bot <marge-bot@gnome.org>2023-03-02 23:49:15 +0000
commit9abce2fca7d7105d50b9471e1b179c6610c6a9b0 (patch)
treef772b0c4c4099d051cce1fb80923345d745935e8
parent2c85eb7254c3b6b3721ea74e4b5f5fc8f2887ea2 (diff)
downloadmutter-9abce2fca7d7105d50b9471e1b179c6610c6a9b0.tar.gz
gpu/kms: Report that we can have outputs if we have connectors
As part of https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/525 (introduction of transactional KMS API), the logic determining whether a GPU can have outputs was changed from whether any connectors existed to whether any connected connectors existed. That effectively meant that we wouldn't attempt to start at all if there were no monitors connected while starting up. This was unintentional, so lets revert back the expected behavior. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2821>
-rw-r--r--src/backends/native/meta-gpu-kms.c13
1 files changed, 1 insertions, 12 deletions
diff --git a/src/backends/native/meta-gpu-kms.c b/src/backends/native/meta-gpu-kms.c
index 84ea6baa2..7d46955a3 100644
--- a/src/backends/native/meta-gpu-kms.c
+++ b/src/backends/native/meta-gpu-kms.c
@@ -364,18 +364,7 @@ meta_gpu_kms_read_current (MetaGpu *gpu,
gboolean
meta_gpu_kms_can_have_outputs (MetaGpuKms *gpu_kms)
{
- GList *l;
- int n_connected_connectors = 0;
-
- for (l = meta_kms_device_get_connectors (gpu_kms->kms_device); l; l = l->next)
- {
- MetaKmsConnector *kms_connector = l->data;
-
- if (meta_kms_connector_get_current_state (kms_connector))
- n_connected_connectors++;
- }
-
- return n_connected_connectors > 0;
+ return !!meta_kms_device_get_connectors (gpu_kms->kms_device);
}
MetaGpuKms *