Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: properly handle interlaced bit for sdvo dtd conversion
Date: Sun, 13 May 2012 15:24:33 +0200	[thread overview]
Message-ID: <20120513132433.GB4720@phenom.ffwll.local> (raw)
In-Reply-To: <20120513015215.GA5480@01807177d60eb6f88a5ff38af2969ea7>

On Sun, May 13, 2012 at 11:52:15AM +1000, Peter Ross wrote:
> On Sat, May 12, 2012 at 10:22:58PM +0200, Daniel Vetter wrote:
> > We've simply ignored this, which isn't too great. With this, interlaced
> > 1080i works on my HDMI screen connected through sdvo. For no apparent
> > reason anything else still doesn't work as it should.
> > 
> > While at it, give these magic numbers in the dtd proper names and
> > add a comment that they match with EDID detailed timings.
> > 
> > v2: Actually use the right bit for interlaced.
> 
> Tested okay with SVDO-HDMI and HD CRT. Cheers,

Hi Peter!

Thanks for testing this on a hdmi sdvo card. Can you please grab the
latest version of intel-gpu-tools and attach the output of
tests/testdisplay -i and then mark those that actually work correctly?
For easier testing you can just run testdisplay without any args, it will
cycle through all modes. Note though that you need to be on a vt and X
needs to be stopped (the tool uses kms directly).

HDMI on sdvo seems to be made of almost complete fail still (I can only
drive a few modes here). So getting some more information about what works
and what doesn't exactly would be interesting.

Thanks, Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2012-05-13 13:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-12 20:22 [PATCH] drm/i915: properly handle interlaced bit for sdvo dtd conversion Daniel Vetter
2012-05-13  1:52 ` Peter Ross
2012-05-13 13:24   ` Daniel Vetter [this message]
2012-05-21 18:38 ` Paulo Zanoni
2012-05-22  7:24   ` 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=20120513132433.GB4720@phenom.ffwll.local \
    --to=daniel@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