diff options
author | Kenneth Graunke <[email protected]> | 2018-01-31 07:03:17 -0800 |
---|---|---|
committer | Emil Velikov <[email protected]> | 2018-02-05 19:06:02 +0000 |
commit | d6a8939225710b01db846e612738d2eb05f7fa0a (patch) | |
tree | 7e8a15985bec411059a01d24d61aefbcb893b83b | |
parent | a445cba84d982a2f8b6eed24cf9e83fe47fee682 (diff) |
i965: Bump official kernel requirement to Linux v3.9.
In commit 3f353342a6b6744773c26ed66b12afed42bd57af (present in 17.3.0)
we started unconditionally using I915_EXEC_NO_RELOC, which was
introduced in Linux v3.9. ChromeOS kernel 3.8 has backported this,
so it should work too.
Running on older kernels would likely result in every single batch
being rejected by the kernel, which is pretty catastrophic. Yet, it
appears that nobody noticed. So, let's just bump the official
requirement and move forward ever so slowly.
Fixes: 3f353342a6b ("i965: Use I915_EXEC_NO_RELOC")
Reviewed-by: Chris Wilson <[email protected]>
Acked-by: Emil Velikov <[email protected]>
(cherry picked from commit c3cd2aac279908a2de755d9454f293761d7b8d5a)
-rw-r--r-- | src/mesa/drivers/dri/i965/intel_screen.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/mesa/drivers/dri/i965/intel_screen.c b/src/mesa/drivers/dri/i965/intel_screen.c index a4e34e9f2cf..675606e7137 100644 --- a/src/mesa/drivers/dri/i965/intel_screen.c +++ b/src/mesa/drivers/dri/i965/intel_screen.c @@ -1776,8 +1776,8 @@ intel_init_bufmgr(struct intel_screen *screen) return false; } - if (!intel_get_boolean(screen, I915_PARAM_HAS_WAIT_TIMEOUT)) { - fprintf(stderr, "[%s: %u] Kernel 3.6 required.\n", __func__, __LINE__); + if (!intel_get_boolean(screen, I915_PARAM_HAS_EXEC_NO_RELOC)) { + fprintf(stderr, "[%s: %u] Kernel 3.9 required.\n", __func__, __LINE__); return false; } |