On Fri, Feb 17, 2017 at 01:54:52PM +0000, Brian Starkey wrote: > 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. We could also just switch the internal representation to something more reasonable, and add glue code in the atomic core to remap between whatever the properties are and the internal representation. Same thing we essentially already do with the display mode. That would then also extend to CTM2 or whatever. For sure not really a good reason to stall a driver imo. -Daniel > > -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@xxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxx> 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 -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
