[Bug 98249] dEQP-GLES31.functional.debug.negative_coverage.get_error.buffer.copy_image_sub_data failed on SKL
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Oct 13 02:46:11 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=98249
Kenneth Graunke <kenneth at whitecape.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Kenneth Graunke <kenneth at whitecape.org> ---
Oh, I fixed this back in June and forgot to close the bug report. Fixed by:
commit 40f842ab5711672a5aec7ae973998ee3a07a91d8
Author: Kenneth Graunke <kenneth at whitecape.org>
Date: Thu Feb 23 15:04:52 2017 -0800
mesa: Require mipmap completeness for glCopyImageSubData() at times.
This patch makes glCopyImageSubData require mipmap completeness when the
texture object's built-in sampler object has a mipmapping MinFilter.
This is apparently the de facto behavior and mandated by Android's CTS.
One exception is that we ignore format based completeness rules
(specifically integer formats with linear filtering), as this is
also the de facto behavior that until recently was mandated by the
OpenGL 4.5 CTS.
This was discussed with both the OpenGL and OpenGL ES working groups,
and while everyone agrees this behavior is unfortunate and complicated,
it is what it is at this point. There was little appetite for relaxing
restrictions given that all conformant Android drivers followed the
mipmapping rule, and all conformant GL 4.5 implementations ignored the
integer/linear rule.
Fixes (on i965):
dEQP-GLES31.functional.debug.negative_coverage.*.buffer.copy_image_sub_data
Bugzilla: https://cvs.khronos.org/bugzilla/show_bug.cgi?id=16224
Reviewed-by: Roland Scheidegger <sroland at vmware.com>
--
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20171013/63707337/attachment.html>
More information about the intel-3d-bugs
mailing list