[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPj87rPoGykYsgbDb7DKfj-HHXY7vTBxoAZGUHqxEEyArJFtsw@mail.gmail.com>
Date: Fri, 17 Feb 2017 15:15:44 +0000
From: Daniel Stone <daniel@...ishbar.org>
To: Ville Syrjälä <ville.syrjala@...ux.intel.com>
Cc: Lionel Landwerlin <lionel.g.landwerlin@...el.com>,
Brian Starkey <brian.starkey@....com>,
Daniel Vetter <daniel.vetter@...ll.ch>,
dri-devel <dri-devel@...ts.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jani Nikula <jani.nikula@...ux.intel.com>,
Sean Paul <seanpaul@...omium.org>
Subject: Re: [PATCH v2] drm/color: Document CTM eqations
Hi,
On 17 February 2017 at 14:56, Ville Syrjälä
<ville.syrjala@...ux.intel.com> wrote:
> On Fri, Feb 17, 2017 at 02:42:26PM +0000, Lionel Landwerlin wrote:
>> If we're talking fixed point reprsentation, ChromeOS is using this :
>>
>> https://cs.chromium.org/chromium/src/ui/ozone/platform/drm/gpu/drm_device.cc?q=DrmDevice&l=209
>
> So it's already using the sign+magnitude stuff. Which presumably
> means we can't change it to two's complement anymore :( Maybe we add a
> CTM2 property ;)
I wouldn't be so sure; AFAIK it only ships on platforms where the
kernel is also built from the same tree, and generally where the
support is backported anyway. So it would be possible to atomically
land a change to CrOS such that the kernels and Chrome move together
to a changed representation.
Cheers,
Daniel
Powered by blists - more mailing lists