public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/i915: use mode values consistently when converting to sdvo dtd
Date: Fri, 4 May 2012 11:35:25 +0200	[thread overview]
Message-ID: <20120504093524.GD5443@phenom.ffwll.local> (raw)
In-Reply-To: <1335295491_40619@CP5-2952>

On Tue, Apr 24, 2012 at 08:24:20PM +0100, Chris Wilson wrote:
> On Tue, 24 Apr 2012 18:27:57 +0200, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > The drm_mode->dtd conversion used the crtc timings, whereas the
> > dtd->drm_mod did not set these. Use the standard mode information, not
> > the crtc timings, in both cases to make these two functions proper
> > inverses of each another.
> > 
> > Note that this also kills the risk that we handle interlaced timings
> > inconsistently because the drm core uses half-frames for crtc timings,
> > whereas we need full frames. But interlaced support is pretty decently
> > broken anyway for sdvo encoders, so no big deal.
> 
> So as I understand it, if we had interlacing or dblscan enabled on the
> incoming mode we would have been feeding the display timing into the
> magic black box of the SDVO encoder rather the mode line.
> 
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Queued for -next, thanks for the review.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

      reply	other threads:[~2012-05-04  9:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 16:27 [PATCH 1/2] drm/i915: use mode values consistently when converting to sdvo dtd Daniel Vetter
2012-04-24 16:27 ` [PATCH 2/2] drm/i915: properly handle interlaced bit for sdvo dtd conversion Daniel Vetter
2012-04-24 19:24 ` [PATCH 1/2] drm/i915: use mode values consistently when converting to sdvo dtd Chris Wilson
2012-05-04  9:35   ` Daniel Vetter [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=20120504093524.GD5443@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox