From: Lyude Paul <lyude@redhat.com>
To: Daniel Vetter <daniel@ffwll.ch>, Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
"Chris Wilson" <chris@chris-wilson.co.uk>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Daniel Vetter" <daniel.vetter@intel.com>,
"David Airlie" <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915/dp: Stop enabling limited color ranges for everything
Date: Thu, 05 Jan 2017 09:49:51 -0500 [thread overview]
Message-ID: <1483627791.14256.0.camel@redhat.com> (raw)
In-Reply-To: <20170105085258.uq6ltsivjewguirf@phenom.ffwll.local>
On Thu, 2017-01-05 at 09:52 +0100, Daniel Vetter wrote:
> On Thu, Jan 05, 2017 at 10:41:07AM +0200, Jani Nikula wrote:
> > No matter what we do here, the question remains what to do with
> > Chamelium. Changing the color range is really a workaround for
> > Chamelium, not a fix. Using CEA range is perfectly fine per DP
> > spec.
>
Of course, I had just figured this was actually a bug, but I guess not
:). I'll just make sure RGB Broadcast is set in the igt tests then
> Can we just set a non-CEA mode/edid for chamelium, problem solved? We
> want
> to do that anyway for HDMI, where you really have to do the limited
> range
> dance to make stuff display correctly.
> -Daniel
prev parent reply other threads:[~2017-01-05 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 1:11 [PATCH] drm/i915/dp: Stop enabling limited color ranges for everything Lyude
2017-01-05 8:41 ` Jani Nikula
2017-01-05 8:52 ` Daniel Vetter
2017-01-05 10:04 ` Daniel Stone
2017-01-05 14:49 ` Lyude Paul [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=1483627791.14256.0.camel@redhat.com \
--to=lyude@redhat.com \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ville.syrjala@linux.intel.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