From: Dylan Semler <dylan.semler@gmail.com>
To: dri-devel@lists.freedesktop.org
Subject: Enhance EDID quirks to allow forcing a mode
Date: Thu, 21 Mar 2013 17:36:13 -0400 [thread overview]
Message-ID: <1363901775-3510-1-git-send-email-dylan.semler@gmail.com> (raw)
The idea is setup a new quirk list with width, height, and refresh rates for
each monitor that needs this quirk. If a monitor is attached that matches one
in this list, the full modeline is calculated with drm_gtf_mode, the
DRM_MODE_TYPE_PREFERRED bit is set, and the new mode is added to the connector.
The patch also creates a new quirk bit: EDID_QUIRK_FORCE_MODE. This bit needs
to be set for the new quirk list discribed above to be checked.
The first patch enhances the quirk logic as described above. The second one
adds my new monitor to the quirk lists.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-03-21 21:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 21:36 Dylan Semler [this message]
2013-03-21 21:36 ` [PATCH 1/2] Enhances EDID quirks to allow for specifying and preferring a mode not reported in the EDID block Dylan Semler
2013-03-22 13:54 ` Alex Deucher
2013-03-21 21:36 ` [PATCH 2/2] Adds EDID force mode quirk for MMT Monitor2Go HD+ Dylan Semler
2013-03-21 21:42 ` Enhance EDID quirks to allow forcing a mode Dylan Semler
2013-03-22 8:48 ` Daniel Vetter
2013-03-22 13:46 ` Dylan Semler
2013-03-22 13:48 ` [PATCH v2 0/2] " Dylan Semler
2013-03-22 13:48 ` [PATCH v2 1/2] Enhances EDID quirks to allow for specifying and preferring a mode not reported in the EDID block Dylan Semler
2013-03-22 13:48 ` [PATCH v2 2/2] Adds EDID force mode quirk for MMT Monitor2Go HD+ Dylan Semler
2013-03-23 12:54 ` [PATCH v2 0/2] Enhance EDID quirks to allow forcing a mode Daniel Vetter
2013-03-22 13:50 ` Alex Deucher
2013-03-22 14:02 ` Dylan Semler
2013-03-22 14:41 ` Daniel Vetter
2013-03-22 15:29 ` Dylan Semler
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=1363901775-3510-1-git-send-email-dylan.semler@gmail.com \
--to=dylan.semler@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
/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.