ozone: Allocate scanout buffer according to KMS modifiers

ui/ozone/platform/drm/gpu/drm_device.cc

Index: ui/ozone/platform/drm/gpu/drm_device.cc
diff --git a/ui/ozone/platform/drm/gpu/drm_device.cc b/ui/ozone/platform/drm/gpu/drm_device.cc
index 03ac08417b654c485fa12c3dcd8168074ce09862..82b937bcf70a23a3e70f53699e9e43ccbb8d63d4 100644
--- a/ui/ozone/platform/drm/gpu/drm_device.cc
+++ b/ui/ozone/platform/drm/gpu/drm_device.cc
@@ -476,12 +476,14 @@ bool DrmDevice::AddFramebuffer2(uint32_t width,
                                 uint32_t handles[4],
                                 uint32_t strides[4],
                                 uint32_t offsets[4],
+                                uint64_t modifiers[4],
                                 uint32_t* framebuffer,
                                 uint32_t flags) {
   DCHECK(file_.IsValid());
   TRACE_EVENT1("drm", "DrmDevice::AddFramebuffer", "handle", handles[0]);
-  return !drmModeAddFB2(file_.GetPlatformFile(), width, height, format, handles,
-                        strides, offsets, framebuffer, flags);
+  return !drmModeAddFB2WithModifiers(file_.GetPlatformFile(), width, height,

[Daniele Castagna, 2016/12/20 18:03:28]

How does this compile on the trybot where we use an old precise sysroot and this
is not even defined?

crrev.com/2594483002 might turn out to be useful for this too.

[hoegsberg1, 2016/12/22 23:05:20]

I've been using cros sdk with the chromiumos buildroot where I have the right
libdrm version. Thanks for getting the sysroots updated.

+                                     format, handles, strides, offsets,
+                                     modifiers, framebuffer, flags);
 }
 
 bool DrmDevice::RemoveFramebuffer(uint32_t framebuffer) {