glamor: Enable dmabuf_capable by default on Intel hardware
With the potential modeset vs. modifiers issue covered by
commit 899c87af1f
("modesetting: unflip before any setcrtc() calls")
we can safely enable modifiers by default, at least on Intel
hardware where we know that things work properly.
I suppose the one open question is whether everything will work
correctly with wonky multi-GPU setups? I don't have one to test
myself.
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
This commit is contained in:
parent
62fec48a6b
commit
2bf0f9e113
|
@ -1206,6 +1206,8 @@ glamor_egl_init(ScrnInfoPtr scrn, int fd)
|
||||||
if (xf86Info.debug != NULL)
|
if (xf86Info.debug != NULL)
|
||||||
glamor_egl->dmabuf_capable = !!strstr(xf86Info.debug,
|
glamor_egl->dmabuf_capable = !!strstr(xf86Info.debug,
|
||||||
"dmabuf_capable");
|
"dmabuf_capable");
|
||||||
|
else if (strstr((const char *)renderer, "Intel"))
|
||||||
|
glamor_egl->dmabuf_capable = TRUE;
|
||||||
else
|
else
|
||||||
glamor_egl->dmabuf_capable = FALSE;
|
glamor_egl->dmabuf_capable = FALSE;
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue