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>
Subject: Re: [PATCH 0/4] [CFT] interlaced support
Date: Fri, 27 Jan 2012 11:22:21 +0100 [thread overview]
Message-ID: <20120127102221.GA3901@phenom.ffwll.local> (raw)
In-Reply-To: <CA+gsUGRGfCN4zLC+0mqMLVkZh4QMjQm2AjpBmVE0nLqy2bc+5A@mail.gmail.com>
On Fri, Jan 27, 2012 at 12:56:23AM -0200, Paulo Zanoni wrote:
> Hi
>
> 2012/1/26 Daniel Vetter <daniel.vetter@ffwll.ch>:
> > Hi all,
> >
> > http://cgit.freedesktop.org/~danvet/drm/log/?h=interlaced
> >
>
> I just tested your patch set and it didn't work: my monitor reported
> 1920x539@50Hz. We're missing something from patch "fixup interlace
> vertical timings confusion". The reg dump is attached.
>
> By the way, VTOTAL_B was 1078. We need to remove those "-1" and also
> those "-2". Look at ironlake_crtc_mode_set: we already do the
> subtractions when we write to HSYNC, HTOTAL, etc. From the register
> descriptions, those -1 are independent of interlaced or
> non-interlaced. I believe there was some confusion with these
> registers because intel_reg_dumper already re-adds +1 when showing the
> register values.
Ok, so something is still botched up :( Btw I think VSYNCSHIFT is only
used by analog outputs to place the 2nd field lines exactly between the
lines of the 1st field. Can you also please attach a reg dump with Peter's
patch so I can compare?
Thanks, Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-01-27 10:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 21:01 [PATCH 0/4] [CFT] interlaced support Daniel Vetter
2012-01-26 21:01 ` [PATCH 1/4] drm/i915: fixup interlaced vertical timings confusion Daniel Vetter
2012-01-26 22:03 ` Chris Wilson
2012-01-26 22:11 ` Daniel Vetter
2012-01-27 19:08 ` Daniel Vetter
2012-01-26 21:01 ` [PATCH 2/4] drm/i915: fixup interlaced support on ilk+ Daniel Vetter
2012-01-26 21:01 ` [PATCH 3/4] drm/i915: allow interlaced mode output on the SDVO connector Daniel Vetter
2012-01-26 21:01 ` [PATCH 4/4] drm/i915: allow interlaced mode output on the HDMI connector Daniel Vetter
2012-01-26 21:38 ` [PATCH 0/4] [CFT] interlaced support Alfonso Fiore
2012-01-26 21:50 ` Daniel Vetter
2012-01-26 22:10 ` Alfonso Fiore
2012-01-26 22:22 ` Daniel Vetter
2012-01-26 23:34 ` Alfonso Fiore
2012-01-27 17:02 ` Daniel Vetter
2012-01-27 17:20 ` Alfonso Fiore
2012-01-26 21:45 ` Paul Menzel
2012-01-27 2:56 ` Paulo Zanoni
2012-01-27 10:22 ` Daniel Vetter [this message]
2012-01-27 16:25 ` Paulo Zanoni
2012-01-27 17:43 ` Daniel Vetter
2012-01-27 21:41 ` Daniel Vetter
2012-01-28 1:52 ` Alfonso Fiore
2012-01-28 11:13 ` Daniel Vetter
2012-01-28 10:21 ` Peter Ross
2012-01-28 10:46 ` Alfonso Fiore
2012-01-28 14:08 ` 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=20120127102221.GA3901@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--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