From: "Keith Packard" <keithp@keithp.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Simon Ser <contact@emersion.fr>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>, nd <nd@arm.com>
Subject: Re: Expose more EDID fields to userspace
Date: Thu, 17 Jan 2019 11:45:18 -0800 [thread overview]
Message-ID: <87y37jukz5.fsf@keithp.com> (raw)
In-Reply-To: <20190117092816.GC3271@phenom.ffwll.local>
[-- Attachment #1.1: Type: text/plain, Size: 605 bytes --]
Daniel Vetter <daniel@ffwll.ch> writes:
> Connector properties are documented here:
>
> https://dri.freedesktop.org/docs/drm/gpu/drm-kms.html#standard-connector-properties
Cool. Seems like we might want a bit more organization here to make it
clear which of these are derived from the connected monitor.
It would be good to read through the source code to find other EDID-ish
data being used within the kernel. Things like the vendor and model info
might be useful as properties, especially if there might be quirks to
'fix' the edid values and drive other kernel behavior.
--
-keith
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-01-17 19:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 9:16 Expose more EDID fields to userspace Simon Ser
2018-12-24 10:23 ` Daniel Vetter
2018-12-31 12:57 ` Simon Ser
2019-01-07 10:02 ` Daniel Vetter
2019-01-07 15:57 ` Keith Packard
2019-01-07 17:07 ` Brian Starkey
2019-01-16 18:35 ` Pekka Paalanen
2019-01-16 19:11 ` Ville Syrjälä
2019-01-16 19:40 ` Adam Jackson
2019-01-16 20:32 ` Keith Packard
2019-01-17 9:28 ` Daniel Vetter
2019-01-17 19:45 ` Keith Packard [this message]
2019-01-17 19:59 ` Alex Deucher
2019-01-17 20:33 ` Daniel Vetter
2019-01-17 21:23 ` Stéphane Marchesin
2019-01-17 21:36 ` Keith Packard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y37jukz5.fsf@keithp.com \
--to=keithp@keithp.com \
--cc=contact@emersion.fr \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=nd@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.