[PATCH] RFC drm: Do not leak connector_status_unknown to userspace

Adam Jackson ajax at redhat.com
Mon Jun 18 09:27:42 PDT 2012


On Sat, 2012-06-09 at 00:24 +0100, Chris Wilson wrote:
> A detect() probe may return 'unknown' to indicate that it was not able
> to successfully determine the connector status. However, exposing this
> to userspace just results in lots of confusion as it is uncertain
> whether or not that is a valid connection. The usual result is for X to
> create a mode that encompasses the unknown connector causing an abnormal
> setup on the known good outputs.

False!  Please refer to xf86CollectEnabledOutputs().  X first attempts
to set up on only definitely-connected outputs, and will only consider
unknown-connected outputs if no definitely-connected outputs are
available.

That was the intent, anyway.  There might be bugs in that, but those
would be X bugs, not kernel bugs.

- ajax
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20120618/7c03502d/attachment.pgp>


More information about the dri-devel mailing list