| /xsrc/external/mit/xf86-video-nv/dist/src/ |
| nv_setup.c | 308 CARD32 implementation = pNv->Chipset & 0x0ff0; local
323 if(implementation == 0x01a0) {
327 } else if(implementation == 0x01f0) {
336 if(implementation == 0x01a0) {
339 } else if(implementation == 0x01f0) {
352 if(pNv->twoHeads && (implementation != 0x0110))
369 CARD16 implementation = pNv->Chipset & 0x0ff0; local
439 (implementation != 0x0100) &&
440 (implementation != 0x0150) &&
441 (implementation != 0x01A0) &
[all...] |
| /xsrc/external/mit/MesaLib/dist/docs/_extra/specs/OLD/ |
| MESA_trace.spec | 42 Application-side implementation of these features raises namespace
49 The extension spec is in the public domain. The current implementation
87 indentation and formatting has been used, is up to the implementation.
95 RESOLVED: No. The implementation is not forced to use this information
346 New Implementation Dependent State
|
| /xsrc/external/mit/MesaLib.old/dist/docs/specs/OLD/ |
| MESA_trace.spec | 42 Application-side implementation of these features raises namespace
49 The extension spec is in the public domain. The current implementation
87 indentation and formatting has been used, is up to the implementation.
95 RESOLVED: No. The implementation is not forced to use this information
346 New Implementation Dependent State
|
| /xsrc/external/mit/xorgproto/dist/include/X11/extensions/ |
| lgewire.h | 70 CARD32 implementation; member in struct:__anon11610
|
| /xsrc/external/mit/MesaLib/dist/docs/_extra/specs/ |
| MESA_query_renderer.spec | 41 In addition, versions of supported APIs and implementation API
43 For example, one implementation may prefer vertex data be supplied using
45 implementation may only support the desired version in a core profile.
48 display. For example, there is typically a hardware implementation and
49 a software based implementation. There are cases where an application
51 software implementation supports more features than the hardware
52 implementation. Another situation is when a particular version of the
53 hardware implementation is blacklisted due to known bugs.
119 the renderer implementation
343 possible. For example, if the implementation is running on a non-PC
[all...] |
| WL_bind_wayland_display.spec | 37 wl_display means that the EGL implementation should provide one or
43 Adding an implementation specific wayland interface, allows the
44 EGL implementation to define specific wayland requests and events,
|
| WL_create_wayland_buffer_from_image.spec | 79 will generate EGL_BAD_MATCH if the implementation is not able to represent
81 implementation-dependant but may include problems such as an unsupported
91 which prevents the implementation from representing the image as a
|
| MESA_pixmap_colormap.spec | 63 The Mesa implementation of GLX allows RGB rendering into X windows and
|
| MESA_configless_context.spec | 114 NOT RESOLVED: There are a few options here. An implementation can
|
| MESA_shader_debug.spec | 206 implementation dependent double-quoted string, each of this
250 New Implementation Dependent State
|
| MESA_swap_control.spec | 93 the maximum implementation-dependent value supported before being
119 New Implementation Dependent State
|
| MESA_ycbcr_texture.spec | 129 texture sampling using an implementation dependent conversion.
|
| /xsrc/external/mit/MesaLib.old/dist/docs/specs/ |
| MESA_query_renderer.spec | 41 In addition, versions of supported APIs and implementation API
43 For example, one implementation may prefer vertex data be supplied using
45 implementation may only support the desired version in a core profile.
48 display. For example, there is typically a hardware implementation and
49 a software based implementation. There are cases where an application
51 software implementation supports more features than the hardware
52 implementation. Another situation is when a particular version of the
53 hardware implementation is blacklisted due to known bugs.
119 the renderer implementation
343 possible. For example, if the implementation is running on a non-PC
[all...] |
| WL_bind_wayland_display.spec | 37 wl_display means that the EGL implementation should provide one or
43 Adding an implementation specific wayland interface, allows the
44 EGL implementation to define specific wayland requests and events,
|
| WL_create_wayland_buffer_from_image.spec | 79 will generate EGL_BAD_MATCH if the implementation is not able to represent
81 implementation-dependant but may include problems such as an unsupported
91 which prevents the implementation from representing the image as a
|
| MESA_pixmap_colormap.spec | 63 The Mesa implementation of GLX allows RGB rendering into X windows and
|
| MESA_configless_context.spec | 114 NOT RESOLVED: There are a few options here. An implementation can
|
| MESA_shader_debug.spec | 206 implementation dependent double-quoted string, each of this
250 New Implementation Dependent State
|
| MESA_swap_control.spec | 93 the maximum implementation-dependent value supported before being
119 New Implementation Dependent State
|
| MESA_ycbcr_texture.spec | 129 texture sampling using an implementation dependent conversion.
|
| /xsrc/external/mit/pixman/dist/pixman/ |
| pixman-glyph.c | 416 pixman_implementation_t *implementation = NULL; local
476 &implementation, &func); local
490 func (implementation, &info);
511 pixman_implementation_t *implementation = NULL; local
585 &implementation, &func); local
610 func (implementation, &info);
|
| /xsrc/external/mit/xcb-proto/dist/ |
| py-compile | 131 import_test="hasattr(sys.implementation, 'cache_tag')"
|
| /xsrc/external/mit/xinit/dist/ |
| startx.cpp | 4 XCOMM This is just a sample implementation of a slightly less primitive
|
| /xsrc/external/mit/fonttosfnt/dist/ |
| util.c | 175 #error no mktime_gmt implementation on this platform
|
| /xsrc/external/mit/xorg-server/dist/hw/xquartz/ |
| X11Application.m | 163 @implementation X11Application
873 @implementation X11Application (Private)
|
