From: Adam Jackson <ajax@redhat.com>
To: Dave Airlie <airlied@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] drm/modes: do not enforce an odd vtotal for interlaced modes
Date: Mon, 06 Feb 2012 13:22:25 -0500 [thread overview]
Message-ID: <4F301A61.7030905@redhat.com> (raw)
In-Reply-To: <CAPM=9twm9jk19Rj6Dy1Eog7X1S3zZEAWNHW_bUSgT_K3DngEGA@mail.gmail.com>
On 2/3/12 4:37 AM, Dave Airlie wrote:
> On Fri, Jan 27, 2012 at 9:40 PM, Daniel Vetter<daniel.vetter@ffwll.ch> wrote:
>> CEA actually specifies an interlaced mode with even vtotal and
>> supplies a diagram showing how this is supposed to work.
>>
>> Note that interlaced modes with an even vtotal seem to be a fairly
>> recent invention. All modelines lore I could dig up with googling says
>> that vtotal for interlaced modes _needs_ to be odd. But the even
>> modelines in CEA are not a spec-bug, there's a figure in CEA-861-E
>> called "Figure 5 Special Interlaced Video Format Timing (Even Vtotal)"
>> that explains how it's supposed to work. Furthermore intel Bspec
>> explicitly mentions that both odd and even interlaced vtotal are
>> supported (VTOTAL register in the south display engine of PCH split
>> chips).
>>
>> Cc: Adam Jackson<ajax@redhat.com>
>> Signed-Off-by: Daniel Vetter<daniel.vetter@ffwll.ch>
>> ---
>
> Ajax? I'd like your ack/review on this.
That |= 1 logic was just slavishy copied from the server's RANDR code,
which afaict slavishly copied it from xfree86 4, and I think even that
was copypasta from xfree86 3. I don't know what it was ever meant to do.
- ajax
prev parent reply other threads:[~2012-02-06 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 21:40 [PATCH] drm/modes: do not enforce an odd vtotal for interlaced modes Daniel Vetter
2012-02-03 9:37 ` Dave Airlie
2012-02-06 18:22 ` Adam Jackson [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=4F301A61.7030905@redhat.com \
--to=ajax@redhat.com \
--cc=airlied@gmail.com \
--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.