summaryrefslogtreecommitdiff
path: root/intel
diff options
context:
space:
mode:
authorKenneth Graunke <kenneth@whitecape.org>2012-07-12 13:41:11 -0700
committerKenneth Graunke <kenneth@whitecape.org>2012-07-12 13:44:21 -0700
commit992e2afd59539d169689bf21d78fac8b5cea4e3c (patch)
tree8ace1f959ab6292a52293e5ac0b149a13771ee3c /intel
parent881e69f185d2450ca35964caf254b04e7e8838c1 (diff)
intel: Change context create failure message to from fprintf to DBG().
Since there is no getparam for hardware context support, Mesa always tries to obtain a context by calling drm_intel_gem_context_create and NULL-checking the result. On an older kernel without context support, this caused libdrm to print an unwanted message to stderr: DRM_IOCTL_I915_GEM_CONTEXT_CREATE failed: Invalid argument In fact, this caused every Piglit test to fail with a "warn" status due to the unrecognized error message. Change the message to use DBG() rather than fprintf(), so people can still get the debug message, but it won't spam normally. Reviewed-by: Ben Widawsky <ben@bwidawsk.net> Signed-off-by: Kenneth Graunke <kenneth@whitecape.org>
Diffstat (limited to 'intel')
-rw-r--r--intel/intel_bufmgr_gem.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/intel/intel_bufmgr_gem.c b/intel/intel_bufmgr_gem.c
index a957c285..12a31977 100644
--- a/intel/intel_bufmgr_gem.c
+++ b/intel/intel_bufmgr_gem.c
@@ -2851,8 +2851,8 @@ drm_intel_gem_context_create(drm_intel_bufmgr *bufmgr)
ret = drmIoctl(bufmgr_gem->fd, DRM_IOCTL_I915_GEM_CONTEXT_CREATE, &create);
if (ret != 0) {
- fprintf(stderr, "DRM_IOCTL_I915_GEM_CONTEXT_CREATE failed: %s\n",
- strerror(errno));
+ DBG("DRM_IOCTL_I915_GEM_CONTEXT_CREATE failed: %s\n",
+ strerror(errno));
return NULL;
}