From: Adam Jackson <ajax@redhat.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: DRI@freedesktop.org,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/edid: adjust double-clocked cea modes
Date: Mon, 14 May 2012 13:37:11 -0400 [thread overview]
Message-ID: <1337017031.20580.148.camel@atropine> (raw)
In-Reply-To: <1336860471-7129-1-git-send-email-daniel.vetter@ffwll.ch>
[-- Attachment #1.1: Type: text/plain, Size: 898 bytes --]
On Sun, 2012-05-13 at 00:07 +0200, Daniel Vetter wrote:
> The problem left is that the CEA spec specifies these modes with
> timings as they get transmitted, but because the double-clocking is
> just to make the HDMI phy happy, the TV actually drops every 2nd
> pixel. So e.g. a 1440x576 mode in our CEA mode list is actually a
> 720x576 mode.
Well, okay, but...
> /* 9 - 1440x240@60Hz */
> - { DRM_MODE("1440x240", DRM_MODE_TYPE_DRIVER, 27000, 1440, 1478,
> + { DRM_MODE("720x240", DRM_MODE_TYPE_DRIVER, 27000, 1440, 1478,
> 1602, 1716, 0, 240, 244, 247, 262, 0,
> DRM_MODE_FLAG_NHSYNC | DRM_MODE_FLAG_NVSYNC |
> DRM_MODE_FLAG_DBLCLK) },
... right after this are the 2800x480 modes. Are they really 720, 1440,
or 2880 wide? Both before and after this change they're 2880 wide, but
the logic of this change makes me believe they should not be.
- ajax
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2012-05-14 17:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 22:07 [PATCH 1/2] drm/edid: adjust double-clocked cea modes Daniel Vetter
2012-05-12 22:07 ` [PATCH 2/2] drm/i915: properly implement doubleclocked hdmi modes Daniel Vetter
2012-05-14 17:37 ` Adam Jackson [this message]
2012-05-14 19:29 ` [PATCH 1/2] drm/edid: adjust double-clocked cea modes Paulo Zanoni
2012-05-14 19:43 ` Paulo Zanoni
2012-05-15 15:33 ` Adam Jackson
2012-05-15 18:50 ` mesa compile error Kong, Bertrand C
2012-05-16 1:47 ` Eugeni Dodonov
2012-05-18 20:28 ` Kong, Bertrand C
2012-05-19 18:29 ` [PATCH 1/2] drm/edid: adjust double-clocked cea modes Daniel Vetter
2012-05-14 19:55 ` Paulo Zanoni
2012-05-20 15:59 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2012-05-12 22:02 Daniel Vetter
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=1337017031.20580.148.camel@atropine \
--to=ajax@redhat.com \
--cc=DRI@freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@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.