author | Kenneth Graunke <kenneth@whitecape.org> | |
Thu, 12 Jul 2012 20:41:11 +0000 (13:41 -0700) | ||
committer | Kenneth Graunke <kenneth@whitecape.org> | |
Thu, 12 Jul 2012 20:44:21 +0000 (13:44 -0700) | ||
commit | 992e2afd59539d169689bf21d78fac8b5cea4e3c | |
tree | 8ace1f959ab6292a52293e5ac0b149a13771ee3c | tree | snapshot (tar.xz tar.gz zip) |
parent | 881e69f185d2450ca35964caf254b04e7e8838c1 | commit | 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>
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>
intel/intel_bufmgr_gem.c | diff | blob | history |