From: Brian Starkey <brian.starkey@arm.com>
To: Daniel Stone <daniel@fooishbar.org>
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
dri-devel <dri-devel@lists.freedesktop.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Sean Paul" <seanpaul@chromium.org>,
"Lionel Landwerlin" <lionel.g.landwerlin@intel.com>
Subject: Re: [PATCH v2] drm/color: Document CTM eqations
Date: Fri, 17 Feb 2017 13:54:52 +0000 [thread overview]
Message-ID: <20170217135451.GA18487@e106950-lin.cambridge.arm.com> (raw)
In-Reply-To: <CAPj87rPRD57-rkzTOm6jbcTaDp1dB-sSJPC=ewZRyVb5qoXGJg@mail.gmail.com>
What's the verdict? We've got [1] which is about to become another
(driver) implementation - better to change before that merges than
after I guess.
-Brian
[1] https://lkml.org/lkml/2017/2/13/304
On Wed, Feb 15, 2017 at 11:56:55AM +0000, Daniel Stone wrote:
>Hi,
>
>On 15 February 2017 at 11:39, Ville Syrjälä
><ville.syrjala@linux.intel.com> wrote:
>> On Tue, Jan 31, 2017 at 06:46:39PM +0100, Daniel Vetter wrote:
>>> On Tue, Jan 31, 2017 at 6:22 PM, Ville Syrjälä
>>> <ville.syrjala@linux.intel.com> wrote:
>>> > Hmm. Two's complement is what I was thinking it is. Which shows that
>>> > I never managed to read the code in any detail. Definitely needs to
>>> > be documented properly.
>>>
>>> That sounds supremely backwards. I guess we can't fix this anymore?
>>
>> I have no idea. Anyone else?
>
>I don't know of any implementation using this; maybe closed Intel
>Android stuff? Certainly GitHub showed no-one using it, and neither X
>nor Weston/Mutter are using it yet.
>
>Cheers,
>Daniel
next prev parent reply other threads:[~2017-02-17 13:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 10:48 Brian Starkey
2017-01-31 11:30 ` Jani Nikula
2017-01-31 12:02 ` Brian Starkey
2017-01-31 12:37 ` Jani Nikula
2017-01-31 15:18 ` Ville Syrjälä
2017-01-31 15:39 ` Brian Starkey
2017-01-31 17:22 ` Ville Syrjälä
2017-01-31 17:46 ` Daniel Vetter
2017-02-15 11:39 ` Ville Syrjälä
2017-02-15 11:56 ` Daniel Stone
2017-02-17 13:54 ` Brian Starkey [this message]
2017-02-17 14:42 ` Lionel Landwerlin
2017-02-17 14:56 ` Ville Syrjälä
2017-02-17 15:05 ` Lionel Landwerlin
2017-02-17 15:16 ` Ville Syrjälä
2017-02-17 15:15 ` Daniel Stone
2017-02-26 19:45 ` 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=20170217135451.GA18487@e106950-lin.cambridge.arm.com \
--to=brian.starkey@arm.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@fooishbar.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lionel.g.landwerlin@intel.com \
--cc=seanpaul@chromium.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
Powered by JetHome