Lines Matching refs:surfaces

43     This extension allows VDPAU video and output surfaces to be used
49     Alternatively, the GL may modify VDPAU surfaces in-place, and VDPAU
50     may then process and/or display those surfaces itself.
95                              const vdpauSurfaceNV *surfaces);
98                                const vdpauSurfaceNV *surfaces);
137     directly from the framebuffer, in the form of VDPAU surfaces.
139     VDPAU surfaces are logically ascribed an interop state. States
168     This operation will succeed even if surfaces exist in the mapped
169     or registered states; such surfaces will internally be unmapped and
233     In all cases, textures defined by VDPAU surfaces will be y-
249     state; such surfaces will internally be unmapped before being
298                                  vdpauSurfaceNV *surfaces);
300     moves a set of VDPAU surfaces from the registered state into the
306                                    vdpauSurfaceNV* surfaces);
308     moves a set of VDPAU surfaces from the mapped state into the
319     Texture image data for VDPAU surfaces in the mapped state is
402     surfaces with power-of-two size may be used with target TEXTURE_2D.
462     entry within the <surfaces> parameter of VDPAUMapSurfacesNV is
465     INVALID_OPERATION is generated if the state of any of the surfaces 
466     named by entries within the <surfaces> parameter of
483     1. Should YUV surfaces be exposed as a frame Y and frame UV
486        RESOLVED: YUV surfaces will be exposed as separate fields
516          * In NVIDIA's implementation, VDPAU surfaces are stored as
587          state transitions, legal access to surfaces by various APIs
613         - Fixed typo in table 3.8.3.1; the heights of luma surfaces