On Thu, Dec 1, 2016 at 5:09 PM, Ben Widawsky <benjamin.widaw...@intel.com> wrote: > When Kristian's interface is ready, kmscube can be modified to make use of it. > > Rob: are you interested in a PR for kmscube?
sure, from a quick look seems like it should be backwards compatible.. probably we should set up a git tree on fd.o for kmscube It does make me realize that I do need to figure out what to do w/ the atomic/fences branches.. maybe I should just make a legacy branch which sticks with the legacy APIs for hw that doesn't support atomic and old kernels. Otherwise I guess kmscube maybe needs to get split into more than one file to keep it from being too much of a mess ;-) btw, interesting that you went the route of an extra plane for "metadata".. I have something similar w/ a5xx, and was assuming I'd just have to go single-plane with well known formula for calculating offset of color data from aux data, to avoid confusing dri2/dri3 too badly. BR, -R _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
