Use flag settings for a non-scanout buffer in all cases for exynos drm.
Using the correct settings for the dumb buffer create flags causes
problems for chromebook so we use the non-scanout setting in both
cases. This is okay for mainline drm which effectively always creates
scanout buffers anyway.
Change-Id: Icaee2a519b83c089c6aa939569d75796af230849
diff --git a/src/drmmode_exynos/drmmode_exynos.c b/src/drmmode_exynos/drmmode_exynos.c
index f1fa033..17b8ec4 100644
--- a/src/drmmode_exynos/drmmode_exynos.c
+++ b/src/drmmode_exynos/drmmode_exynos.c
@@ -52,7 +52,13 @@
#define DRM_IOCTL_EXYNOS_PLANE_SET_ZPOS DRM_IOWR(DRM_COMMAND_BASE + \
DRM_EXYNOS_PLANE_SET_ZPOS, struct drm_exynos_plane_set_zpos)
-#define EXYNOS_SCANOUT_FLAGS 0x00000000
+/* TODO MIDEGL-1845: EXYNOS_SCANOUT_FLAGS should be defined as 0x00000000 but
+ * this causes problems for chromebook. Leaving it at 0x00000001 here doesn't
+ * adversely affect mainline exynos DRM as it effectively always uses
+ * contiguous memory. See kernel file drivers/gpu/drm/exynos/exynos_drm_buf.c
+ * function lowlevel_buffer_allocate().
+ */
+#define EXYNOS_SCANOUT_FLAGS 0x00000001
#define EXYNOS_NON_SCANOUT_FLAGS 0x00000001
static int init_plane_for_cursor(int drm_fd, uint32_t plane_id)