[Bug 98330] [dEQP, EGL, HSW] dEQP-EGL.functional.buffer_age.no_preserve fails

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Dec 9 22:06:59 UTC 2016


https://bugs.freedesktop.org/show_bug.cgi?id=98330

Mark Janes <mark.a.janes at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NOTOURBUG                   |---

--- Comment #7 from Mark Janes <mark.a.janes at intel.com> ---
>From the dEQP test engineers:

 From: Mika Isojarvi <misojarvi at google.com>
 Subject: Re: dEQP-EGL.functional.buffer_age.no_preserve bug
 To: Mark Janes <mark.a.janes at intel.com>
 Cc: deqp-external-requests <deqp-external-requests at google.com>
 Date: Fri, 09 Dec 2016 13:52:15 -0800

 [ multipart/alternative ]
 [ text/plain ]
 Hi Mark,

 The preserve bit is not relevant for the EGL buffer age extensions. Setting
 the preserve bit means that the color buffer must be preserved over the
 eglSwapBuffers() call. So the color buffer content at the end of the frame
 and at the beginning of the next frame must be exactly same. The EGL buffer
 age extension allows querying the age of the color buffers contents at the
 beginning of the frame e.g. if the driver returns  2 then the color buffers
 contents must match the content two frames ago(or it can return 0 if the
 color buffer contents don't match any previous frame). This guarantee does
 not require that the color buffer preserved bit is set.

 The test case is using preserve bit to check that if the preserve bit is
 set then buffer age is always 1. Meaning that the color buffer contents are
 the same as at the end of the previous frame.

 Regards,
 Mika

-- 
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/20161209/4c68f486/attachment.html>


More information about the intel-3d-bugs mailing list