From 0657fc00dd9e69f71d679d480b5d5f4c33cfae35 Mon Sep 17 00:00:00 2001 From: Zack Rusin Date: Wed, 26 Jan 2011 00:01:51 -0500 Subject: gallium: add an interface for query predicates as specified in the arb_occlusion_query2. just the interface. --- src/gallium/docs/source/context.rst | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'src/gallium/docs') diff --git a/src/gallium/docs/source/context.rst b/src/gallium/docs/source/context.rst index 6760e7be4b..f0d3b84783 100644 --- a/src/gallium/docs/source/context.rst +++ b/src/gallium/docs/source/context.rst @@ -233,6 +233,11 @@ The most common type of query is the occlusion query, are written to the framebuffer without being culled by :ref:`Depth, Stencil, & Alpha` testing or shader KILL instructions. The result is an unsigned 64-bit integer. +In cases where a boolean result of an occlusion query is enough, +``PIPE_QUERY_OCCLUSION_PREDICATE`` should be used. It is just like +``PIPE_QUERY_OCCLUSION_COUNTER`` except that the result is a boolean +value of FALSE for cases where COUNTER would result in 0 and TRUE +for all other cases. Another type of query, ``PIPE_QUERY_TIME_ELAPSED``, returns the amount of time, in nanoseconds, the context takes to perform operations. -- cgit v1.2.3