From: Joakim Plate <joakim.plate@ecce.se>
To: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/4] drm/edid: Recognize 60Hz and 59.94Hz CEA modes
Date: Fri, 10 May 2013 09:46:51 +0000 (UTC) [thread overview]
Message-ID: <loom.20130510T114603-468@post.gmane.org> (raw)
In-Reply-To: 20130418153130.GT4469@intel.com
Ville Syrjälä <ville.syrjala <at> linux.intel.com> writes:
> I think I'll defer on that one until we decide whether we want add
> both 60Hz and 59.94HZ versions to the connector's mode list. Daniel
> suggested we do it, but I disagree slightly since CEA-861 says that
> monitors should only advertise one variant in their detailed timings.
> I was thinking that we'd follow that rule here as well. But I can
> be easily convinced otherwise, in case someone else has an
> opinion...
>
Please add both. From a video player's perspective. The choice matters a lot.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2013-05-10 10:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 17:37 [PATCH 0/4] drm/edid: Recognize 60Hz and 59.94Hz CEA modes ville.syrjala
2013-04-17 17:37 ` [PATCH 1/4] drm: Remove explicit vrefresh initialization from DRM_MODE() ville.syrjala
2013-04-17 17:37 ` [PATCH 2/4] drm: Add drm_mode_equal_no_clocks() ville.syrjala
2013-04-17 19:32 ` Paulo Zanoni
2013-04-17 17:37 ` [PATCH 3/4] drm/edid: Populate vrefresh for CEA modes ville.syrjala
2013-04-17 17:37 ` [PATCH 4/4] drm/edid: Check both 60Hz and 59.94Hz when looking for a CEA mode ville.syrjala
2013-04-17 20:38 ` [PATCH 0/4] drm/edid: Recognize 60Hz and 59.94Hz CEA modes Paulo Zanoni
2013-04-18 15:31 ` Ville Syrjälä
2013-05-10 9:46 ` Joakim Plate [this message]
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=loom.20130510T114603-468@post.gmane.org \
--to=joakim.plate@ecce.se \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox