From: Daniel Stone <daniel@fooishbar.org>
To: "Jani Nikula" <jani.nikula@intel.com>, Lyude <lyude@redhat.com>,
intel-gfx <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 <dri-devel@lists.freedesktop.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/i915/dp: Stop enabling limited color ranges for everything
Date: Thu, 5 Jan 2017 10:04:04 +0000 [thread overview]
Message-ID: <CAPj87rMFquh4XkrGDTDsSnCernyo2B4g0cO1uemmiqmiBSg6Qw@mail.gmail.com> (raw)
In-Reply-To: <20170105085258.uq6ltsivjewguirf@phenom.ffwll.local>
Hi,
On 5 January 2017 at 08:52, Daniel Vetter <daniel@ffwll.ch> 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.
>
> 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.
Or, if you set the 'Broadcast RGB' connector property to 'Full',
you'll never hit the color_range_auto branch in the first place ...
Cheers,
Daniel
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Stone <daniel@fooishbar.org>
To: "Jani Nikula" <jani.nikula@intel.com>, Lyude <lyude@redhat.com>,
intel-gfx <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 <dri-devel@lists.freedesktop.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/i915/dp: Stop enabling limited color ranges for everything
Date: Thu, 5 Jan 2017 10:04:04 +0000 [thread overview]
Message-ID: <CAPj87rMFquh4XkrGDTDsSnCernyo2B4g0cO1uemmiqmiBSg6Qw@mail.gmail.com> (raw)
In-Reply-To: <20170105085258.uq6ltsivjewguirf@phenom.ffwll.local>
Hi,
On 5 January 2017 at 08:52, Daniel Vetter <daniel@ffwll.ch> 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.
>
> 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.
Or, if you set the 'Broadcast RGB' connector property to 'Full',
you'll never hit the color_range_auto branch in the first place ...
Cheers,
Daniel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-01-05 10:04 UTC|newest]
Thread overview: 11+ 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 1:11 ` Lyude
2017-01-05 8:41 ` Jani Nikula
2017-01-05 8:41 ` Jani Nikula
2017-01-05 8:52 ` Daniel Vetter
2017-01-05 8:52 ` Daniel Vetter
2017-01-05 9:41 ` Peter Frühberger
2017-01-05 10:04 ` Daniel Stone [this message]
2017-01-05 10:04 ` Daniel Stone
2017-01-05 14:49 ` Lyude Paul
2017-01-05 14:49 ` Lyude Paul
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=CAPj87rMFquh4XkrGDTDsSnCernyo2B4g0cO1uemmiqmiBSg6Qw@mail.gmail.com \
--to=daniel@fooishbar.org \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--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 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.