Home	Sort by: relevance | last modified time | path

Full Search in project(s): src xsrc Definition Symbol File Path History   | | Help

    Searched refs:In (Results 1 - 25 of 46) sorted by relevancy

1 2

/xsrc/external/mit/libepoxy/dist/registry/
README.md	3 In order to update the registry XML files and retain the history you cannot
/xsrc/external/mit/MesaLib/dist/docs/_extra/specs/
MESA_window_pos.spec	31 In order to set the current raster position to a specific window 35 rely on a subtle side-effect of the Bitmap command in order to circumvent
MESA_ycbcr_texture.spec	34 This extension supports texture images stored in the YCbCr format. 42 The first component is luminance (Y). For pixels in even-numbered 43 image columns, the second component is Cb. For pixels in odd-numbered 78 In section 3.6.4, Rasterization of Pixel Rectangles, on page 101, 88 In section 3.6.4, Rasterization of Pixel Rectangles, on page 102, 106 In section 3.6.4, Rasterization of Pixel Rectangles, on page 104, 115 In section 3.8.1, Texture Image Specification, on page 125, add 120 indicate that the image data is in YCbCr format. type must 122 as seen in tables 3.8 and 3.10. Table 3.12 describes the mapping 132 In section 3.8.1, Texture Image Specification, on page 126, ad     [all...]
MESA_pixmap_colormap.spec	15 Shipping since Mesa 1.2.8 in May, 1996. 34 in order to compute pixel values during rendering. 64 pixmaps of any visual class, not just TrueColor or DirectColor. In order
MESA_query_renderer.spec	37 In many situations, applications want to detect characteristics of a 41 In addition, versions of supported APIs and implementation API 44 methods only available in a compatibility profile, but another 45 implementation may only support the desired version in a core profile. 56 the available renderers for a particular display and screen. In 74 Accepted as an <attribute> in glXQueryRendererIntegerMESA and 89 Accepted as an <attribute> in glXQueryRendererStringMESA and 109 can be used. The value for <attribute> will be returned in one or more 111 of each renderer attribute are listed in the table below. 156 In the table, boolean attributes will have either the value 0 or 1     [all...]
MESA_multithread_makecurrent.spec	34 objects in parallel, and leaves synchronization for write access 38 ensuring that the glFlush happens in one thread before another 46 a feature not specified in WGL. 67 In addition, a rendering context can be current for only one 70 In addition, an indirect rendering context can be current for 106 (1) What happens if the app binds a context/drawable in multiple 107 threads, then binds a different context/thread in one of them? 113 (2) What happens if the app binds a context/drawable in multiple 114 threads, then binds None/None in one of them? 119 (3) What happens if the app binds a context/drawable in 7 threads     [all...]
MESA_swap_control.spec	15 Deployed in DRI drivers post-XFree86 4.3. 35 of color buffer swaps, measured in video frame periods. 87 full frame of video data. In the case of an interlaced monitor,
WL_bind_wayland_display.spec	38 more interfaces in the Wayland protocol to allow clients to create 45 needed for buffer sharing in an EGL wayland platform. 65 Accepted as <target> in eglCreateImageKHR 69 Accepted in the <attrib_list> parameter of eglCreateImageKHR: 80 Accepted in the <attribute> parameter of eglQueryWaylandBufferWL: 104 A wl_buffer can have several planes, typically in case of planar 105 YUV formats. Depending on the exact YUV format in use, the 112 return EGL_FALSE. In that case the wl_buffer can not be used with 121 in the shader. The naming conventions separates planes by _ and 124 sampler. X indicates that the corresponding component in the rgb     [all...]
WL_create_wayland_buffer_from_image.spec	41 its contents with a given EGLImage. The expected use case for this is in a 45 intermediate buffer. The compositing can then be done in the parent 74 updates to the image will also be updated in the wl_buffer. Typically the 75 EGLImage will be generated in a nested Wayland compositor using a buffer 78 If there was an error then the function will return NULL. In particular it 82 format or tiling mode or that the buffer is in memory that is inaccessible
MESA_swap_frame_usage.spec	15 Deployed in DRI drivers post-XFree86 4.3. 51 completion of the two swaps. If the value is in the range [0,1], the 53 constant frame rate. If the value is in the range (1,max], a constant 58 WGL_I3D_swap_frame_usage. In WGL_I3D_swap_frame_usage, the measurement 113 between two buffer-swap operations being committed. In unextended GLX the 121 glXSwapBuffersMscOML. The frame usage in this case is less than 1.0 if 130 glXGetFrameUsageMESA returns a floating-point value in <usage> 140 If a swap is missed based in the rate control specified by the 162 last missed frame is returned in the location pointed to by
/xsrc/external/mit/MesaLib.old/dist/docs/specs/
MESA_window_pos.spec	31 In order to set the current raster position to a specific window 35 rely on a subtle side-effect of the Bitmap command in order to circumvent
MESA_ycbcr_texture.spec	34 This extension supports texture images stored in the YCbCr format. 42 The first component is luminance (Y). For pixels in even-numbered 43 image columns, the second component is Cb. For pixels in odd-numbered 78 In section 3.6.4, Rasterization of Pixel Rectangles, on page 101, 88 In section 3.6.4, Rasterization of Pixel Rectangles, on page 102, 106 In section 3.6.4, Rasterization of Pixel Rectangles, on page 104, 115 In section 3.8.1, Texture Image Specification, on page 125, add 120 indicate that the image data is in YCbCr format. type must 122 as seen in tables 3.8 and 3.10. Table 3.12 describes the mapping 132 In section 3.8.1, Texture Image Specification, on page 126, ad     [all...]
MESA_pixmap_colormap.spec	15 Shipping since Mesa 1.2.8 in May, 1996. 34 in order to compute pixel values during rendering. 64 pixmaps of any visual class, not just TrueColor or DirectColor. In order
MESA_query_renderer.spec	37 In many situations, applications want to detect characteristics of a 41 In addition, versions of supported APIs and implementation API 44 methods only available in a compatibility profile, but another 45 implementation may only support the desired version in a core profile. 56 the available renderers for a particular display and screen. In 74 Accepted as an <attribute> in glXQueryRendererIntegerMESA and 89 Accepted as an <attribute> in glXQueryRendererStringMESA and 109 can be used. The value for <attribute> will be returned in one or more 111 of each renderer attribute are listed in the table below. 156 In the table, boolean attributes will have either the value 0 or 1     [all...]
MESA_multithread_makecurrent.spec	34 objects in parallel, and leaves synchronization for write access 38 ensuring that the glFlush happens in one thread before another 46 a feature not specified in WGL. 67 In addition, a rendering context can be current for only one 70 In addition, an indirect rendering context can be current for 106 (1) What happens if the app binds a context/drawable in multiple 107 threads, then binds a different context/thread in one of them? 113 (2) What happens if the app binds a context/drawable in multiple 114 threads, then binds None/None in one of them? 119 (3) What happens if the app binds a context/drawable in 7 threads     [all...]
MESA_swap_control.spec	15 Deployed in DRI drivers post-XFree86 4.3. 35 of color buffer swaps, measured in video frame periods. 87 full frame of video data. In the case of an interlaced monitor,
WL_bind_wayland_display.spec	38 more interfaces in the Wayland protocol to allow clients to create 45 needed for buffer sharing in an EGL wayland platform. 65 Accepted as <target> in eglCreateImageKHR 69 Accepted in the <attrib_list> parameter of eglCreateImageKHR: 80 Accepted in the <attribute> parameter of eglQueryWaylandBufferWL: 104 A wl_buffer can have several planes, typically in case of planar 105 YUV formats. Depending on the exact YUV format in use, the 112 return EGL_FALSE. In that case the wl_buffer can not be used with 121 in the shader. The naming conventions separates planes by _ and 124 sampler. X indicates that the corresponding component in the rgb     [all...]
WL_create_wayland_buffer_from_image.spec	41 its contents with a given EGLImage. The expected use case for this is in a 45 intermediate buffer. The compositing can then be done in the parent 74 updates to the image will also be updated in the wl_buffer. Typically the 75 EGLImage will be generated in a nested Wayland compositor using a buffer 78 If there was an error then the function will return NULL. In particular it 82 format or tiling mode or that the buffer is in memory that is inaccessible
MESA_swap_frame_usage.spec	15 Deployed in DRI drivers post-XFree86 4.3. 51 completion of the two swaps. If the value is in the range [0,1], the 53 constant frame rate. If the value is in the range (1,max], a constant 58 WGL_I3D_swap_frame_usage. In WGL_I3D_swap_frame_usage, the measurement 113 between two buffer-swap operations being committed. In unextended GLX the 121 glXSwapBuffersMscOML. The frame usage in this case is less than 1.0 if 130 glXGetFrameUsageMESA returns a floating-point value in <usage> 140 If a swap is missed based in the rate control specified by the 162 last missed frame is returned in the location pointed to by
/xsrc/external/mit/MesaLib/dist/docs/_extra/specs/OLD/
MESA_resize_buffers.spec	33 cannot properly respond to window system events. In particular, 38 since most applications call glViewport in response to window size 41 In some situations, however, the application may not call glViewport
MESA_trace.spec	43 and linkage issues. In the driver dispatch table a simple 49 The extension spec is in the public domain. The current implementation 50 in Mesa is covered by Mesa's XFree86-style copyright by the authors above. 62 would result in symbol collisions. 72 trace into frames, in whatever way considered adequate. 84 will be traced as requested by Enable/DisableTraceMESA, in the order 103 data in the context. There is no need to have the ability mark names 173 using C syntax. The primary intention of tracing is to aid in program 181 attribute groups. The state values included in those attribute groups 185 that <traceName> will be interpreted as a filename in most implementations     [all...]
/xsrc/external/mit/MesaLib.old/dist/docs/specs/OLD/
MESA_resize_buffers.spec	33 cannot properly respond to window system events. In particular, 38 since most applications call glViewport in response to window size 41 In some situations, however, the application may not call glViewport
MESA_trace.spec	43 and linkage issues. In the driver dispatch table a simple 49 The extension spec is in the public domain. The current implementation 50 in Mesa is covered by Mesa's XFree86-style copyright by the authors above. 62 would result in symbol collisions. 72 trace into frames, in whatever way considered adequate. 84 will be traced as requested by Enable/DisableTraceMESA, in the order 103 data in the context. There is no need to have the ability mark names 173 using C syntax. The primary intention of tracing is to aid in program 181 attribute groups. The state values included in those attribute groups 185 that <traceName> will be interpreted as a filename in most implementations     [all...]
/xsrc/external/mit/MesaLib.old/dist/src/mesa/program/
Android.mk	5 # to deal in the Software without restriction, including without limitation 11 # in all copies or substantial portions of the Software. 15 # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL 17 # LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING 18 # FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER 19 # DEALINGS IN THE SOFTWARE. 52 # TODO(chadv): In Makefile.sources, move these vars to a different list so we can
/xsrc/external/mit/imake/dist/
mergelib.cpp	7 XCOMM that the above copyright notice appear in all copies and that both that 8 XCOMM copyright notice and this permission notice appear in supporting 11 XCOMM The above copyright notice and this permission notice shall be included in 16 XCOMM FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 17 XCOMM OPEN GROUP BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN 18 XCOMM AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN 19 XCOMM CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. 21 XCOMM Except as contained in this notice, the name of The Open Group shall not be 22 XCOMM used in advertising or otherwise to promote the sale, use or other dealings 23 XCOMM in this Software without prior written authorization from The Open Group     [all...]

Completed in 11 milliseconds

1 2

Indexes created Mon Apr 13 00:22:24 UTC 2026