From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: don't clobber the special upscaling lvds timings
Date: Sat, 14 Apr 2012 18:05:24 +0100 [thread overview]
Message-ID: <1334423133_103@CP5-2952> (raw)
In-Reply-To: <20120414165446.GB4215@phenom.ffwll.local>
On Sat, 14 Apr 2012 18:54:46 +0200, Daniel Vetter <daniel@ffwll.ch> wrote:
> To contrast with the state before these two patches:
> - No longer splattered all over (some of it was deep down in the encoder
> code, e.g. sdvo).
> - No more stupid confusion about interlaced timings.
Good things for sure. My biggest concern is that we have conflicting
requirements upon the mode as setup in crtcinfo that are not being
detected. The task of mode-valid is to find a compromise mode that works
for all attached connectors, and more importantly make sure we reject
combinations of connectors that would result in no compatible modes
(above and beyond the combination of encoders that are illegal).
And most of that concern is due to the fact that the modesetting code
seems to have evolved ad-hoc with very few sanity checks and no
overarching design.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-04-14 17:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-14 16:17 [PATCH] drm/i915: don't clobber the special upscaling lvds timings Daniel Vetter
2012-04-14 16:43 ` Chris Wilson
2012-04-14 16:54 ` Daniel Vetter
2012-04-14 17:05 ` Chris Wilson [this message]
2012-04-15 15:07 ` Eugeni Dodonov
2012-04-15 15:19 ` Eugeni Dodonov
2012-04-15 17:24 ` Daniel Vetter
2012-04-15 17:38 ` Chris Wilson
2012-04-15 17:53 ` Daniel Vetter
2012-04-15 18:03 ` Chris Wilson
2012-04-16 7:34 ` 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=1334423133_103@CP5-2952 \
--to=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=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 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.