[Intel-gfx] [PATCH i-g-t] tests/kms_cursor_legacy: Use gem_mmap__gtt() rather than gem_mmap__wc()
Ville Syrjala
ville.syrjala at linux.intel.com
Wed Sep 20 16:35:05 UTC 2017
From: Ville Syrjälä <ville.syrjala at linux.intel.com>
WC mmaps aren't universally supported, so let's not depend on them when
any kind of mmap will do.
Signed-off-by: Ville Syrjälä <ville.syrjala at linux.intel.com>
---
tests/kms_cursor_legacy.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/kms_cursor_legacy.c b/tests/kms_cursor_legacy.c
index 1aa4518c361c..9c63fb1944d2 100644
--- a/tests/kms_cursor_legacy.c
+++ b/tests/kms_cursor_legacy.c
@@ -506,7 +506,7 @@ static uint32_t *make_busy(int fd, uint32_t target)
memset(obj, 0, sizeof(obj));
obj[0].handle = target;
obj[1].handle = gem_create(fd, 4096);
- batch = gem_mmap__wc(fd, obj[1].handle, 0, 4096, PROT_WRITE);
+ batch = gem_mmap__gtt(fd, obj[1].handle, 4096, PROT_WRITE);
gem_set_domain(fd, obj[1].handle,
I915_GEM_DOMAIN_GTT, I915_GEM_DOMAIN_GTT);
--
2.13.5
More information about the Intel-gfx
mailing list