diff options
author | Kenneth Graunke <[email protected]> | 2013-04-06 00:08:37 -0700 |
---|---|---|
committer | Kenneth Graunke <[email protected]> | 2013-04-08 11:03:08 -0700 |
commit | 97e40a524ebee72dc06208f2c730c25c962dea2a (patch) | |
tree | a50eecbbdb4b12273bf672fa51f688abe29d3894 /src/mesa | |
parent | 394edb5af5161f664c0c3b4eaba9be4e30f3c138 (diff) |
intel: Remove check for kernel 2.6.29.
Now that we require 2.6.39, there's no need to also check for 2.6.29.
Calling drm_intel_bufmgr_gem_enable_fenced_relocs() without checking
should be safe, as it simply sets a flag.
This does remove the check for zero fences available, but that doesn't
seem worth checking.
Signed-off-by: Kenneth Graunke <[email protected]>
Reviewed-by: Daniel Vetter <[email protected]>
Reviewed-by: Eric Anholt <[email protected]>
Diffstat (limited to 'src/mesa')
-rw-r--r-- | src/mesa/drivers/dri/intel/intel_screen.c | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/src/mesa/drivers/dri/intel/intel_screen.c b/src/mesa/drivers/dri/intel/intel_screen.c index eb451ba546b..58496e232c9 100644 --- a/src/mesa/drivers/dri/intel/intel_screen.c +++ b/src/mesa/drivers/dri/intel/intel_screen.c @@ -989,7 +989,6 @@ static bool intel_init_bufmgr(struct intel_screen *intelScreen) { __DRIscreen *spriv = intelScreen->driScrnPriv; - int num_fences = 0; intelScreen->no_hw = getenv("INTEL_NO_HW") != NULL; @@ -1000,12 +999,6 @@ intel_init_bufmgr(struct intel_screen *intelScreen) return false; } - if (!intel_get_param(spriv, I915_PARAM_NUM_FENCES_AVAIL, &num_fences) || - num_fences == 0) { - fprintf(stderr, "[%s: %u] Kernel 2.6.29 required.\n", __func__, __LINE__); - return false; - } - drm_intel_bufmgr_gem_enable_fenced_relocs(intelScreen->bufmgr); if (!intel_get_boolean(spriv, I915_PARAM_HAS_RELAXED_DELTA)) { |