Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/edid: adjust double-clocked cea modes
Date: Sun, 20 May 2012 17:59:42 +0200	[thread overview]
Message-ID: <20120520155942.GD5145@phenom.ffwll.local> (raw)
In-Reply-To: <CA+gsUGR=gBYWGuOML0sZCb1s88Qnwhtdy8tNMDRjMzzROF-vTA@mail.gmail.com>

On Mon, May 14, 2012 at 04:55:36PM -0300, Paulo Zanoni wrote:
> 2012/5/12 Daniel Vetter <daniel.vetter@ffwll.ch>:
> > The CEA spec has a bunch of very peculiar modes. For backwards
> > compatibility it specifies a bunch of modes that are suitable to
> > display old SD TV content. But these modes have such low pixel clocks
> > that pixels need to be doubled to reach the minimal clock of the HDMI
> > interface.
> >
> 
> I just tested the 2 patches. They don't work for me... My monitor
> complains the timings are not supported, and now I get a black screen
> instead of a screen with half of the vertical pixel columns.
> 
>                       HTOTAL_B: 0x035f02cf (720 active, 864 total)
>                       HBLANK_B: 0x035f02cf (720 start, 864 end)
>                        HSYNC_B: 0x031a02db (732 start, 795 end)
>                       VTOTAL_B: 0x026f023f (576 active, 624 total)
>                       VBLANK_B: 0x026f023f (576 start, 624 end)
>                        VSYNC_B: 0x02490243 (580 start, 586 end)
> 
> I believe the timings sent to the hardware must be the ones we were
> already sending before the patches...

Well, that is what actually _should_ happen. The crtc doubles every pixel,
so all horizontal timings should be twice what we program into the
registers. Looks like something is still amiss :(
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2012-05-20 15:59 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 ` [PATCH 1/2] drm/edid: adjust double-clocked cea modes Adam Jackson
2012-05-14 19:29   ` 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 [this message]
  -- 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=20120520155942.GD5145@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=przanoni@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox