/third_party/skia/third_party/externals/swiftshader/tests/regres/testlists/vk-default/ |
D | subgroups.txt | 13 dEQP-VK.subgroups.builtin_var.framebuffer.subgroupsize_vertex 14 dEQP-VK.subgroups.builtin_var.framebuffer.subgroupsize_tess_eval 15 dEQP-VK.subgroups.builtin_var.framebuffer.subgroupsize_tess_control 16 dEQP-VK.subgroups.builtin_var.framebuffer.subgroupsize_geometry 17 dEQP-VK.subgroups.builtin_var.framebuffer.subgroupinvocationid_vertex 18 dEQP-VK.subgroups.builtin_var.framebuffer.subgroupinvocationid_tess_eval 19 dEQP-VK.subgroups.builtin_var.framebuffer.subgroupinvocationid_tess_control 20 dEQP-VK.subgroups.builtin_var.framebuffer.subgroupinvocationid_geometry 36 dEQP-VK.subgroups.builtin_mask_var.framebuffer.subgroupeqmask_vertex 37 dEQP-VK.subgroups.builtin_mask_var.framebuffer.subgroupeqmask_tess_eval [all …]
|
/third_party/skia/third_party/externals/opengl-registry/extensions/ARB/ |
D | ARB_framebuffer_no_attachments.txt | 51 Each framebuffer object may have depth, stencil and zero or more color 52 attachments that can be written to by the GL. The size of the framebuffer 54 of that framebuffer. In unextended OpenGL 4.2, it is not legal to render 55 into a framebuffer object that has no attachments. Such a framebuffer 65 need to write color or depth values to a conventional framebuffer. 66 However, a framebuffer with no attachments will be considered incomplete 69 unnecessary "dummy" texture and attach it to the framebuffer (possibly 75 framebuffer with no attachments. Applications can specify default width, 76 height, layer count, and sample count parameters for a framebuffer object. 77 When a framebuffer with no attachments is bound, it will be considered [all …]
|
D | ARB_framebuffer_object.txt | 141 known collectively as "framebuffer-attachable images". This 142 extension provides a mechanism for attaching framebuffer-attachable 143 images to the GL framebuffer as one of the standard GL logical 145 framebuffer-attachable image to the accum logical buffer is left for 146 a future extension to define). When a framebuffer-attachable image 147 is attached to the framebuffer, it is used as the source and 150 By allowing the use of a framebuffer-attachable image as a rendering 153 of a texture to be used as framebuffer-attachable images. A 155 framebuffer-attachable image by specifying the mipmap level, cube 159 the framebuffer, followed immediately by a call to CopyTexSubImage. [all …]
|
/third_party/openGLES/extensions/ARB/ |
D | ARB_framebuffer_no_attachments.txt | 61 Each framebuffer object may have depth, stencil and zero or more color 62 attachments that can be written to by the GL. The size of the framebuffer 64 of that framebuffer. In unextended OpenGL 4.2, it is not legal to render 65 into a framebuffer object that has no attachments. Such a framebuffer 75 need to write color or depth values to a conventional framebuffer. 76 However, a framebuffer with no attachments will be considered incomplete 79 unnecessary "dummy" texture and attach it to the framebuffer (possibly 85 framebuffer with no attachments. Applications can specify default width, 86 height, layer count, and sample count parameters for a framebuffer object. 87 When a framebuffer with no attachments is bound, it will be considered [all …]
|
D | ARB_framebuffer_object.txt | 151 known collectively as "framebuffer-attachable images". This 152 extension provides a mechanism for attaching framebuffer-attachable 153 images to the GL framebuffer as one of the standard GL logical 155 framebuffer-attachable image to the accum logical buffer is left for 156 a future extension to define). When a framebuffer-attachable image 157 is attached to the framebuffer, it is used as the source and 160 By allowing the use of a framebuffer-attachable image as a rendering 163 of a texture to be used as framebuffer-attachable images. A 165 framebuffer-attachable image by specifying the mipmap level, cube 169 the framebuffer, followed immediately by a call to CopyTexSubImage. [all …]
|
/third_party/skia/third_party/externals/opengl-registry/extensions/APPLE/ |
D | APPLE_framebuffer_multisample.txt | 43 This extension extends the framebuffer object framework to 53 All of the framebuffer-attachable images attached to a framebuffer 54 object must have the same number of SAMPLES or else the framebuffer 55 object is not "framebuffer complete". If a framebuffer object with 56 multisample attachments is "framebuffer complete", then the 57 framebuffer object behaves as if SAMPLE_BUFFERS is one. 61 application-created framebuffer object and the destination is a 62 single-sample framebuffer object. Separate read and draw framebuffer 67 framebuffer. 126 framebuffer is the destination for rendering operations, and the [all …]
|
/third_party/openGLES/extensions/APPLE/ |
D | APPLE_framebuffer_multisample.txt | 43 This extension extends the framebuffer object framework to 53 All of the framebuffer-attachable images attached to a framebuffer 54 object must have the same number of SAMPLES or else the framebuffer 55 object is not "framebuffer complete". If a framebuffer object with 56 multisample attachments is "framebuffer complete", then the 57 framebuffer object behaves as if SAMPLE_BUFFERS is one. 61 application-created framebuffer object and the destination is a 62 single-sample framebuffer object. Separate read and draw framebuffer 67 framebuffer. 126 framebuffer is the destination for rendering operations, and the [all …]
|
/third_party/skia/third_party/externals/opengl-registry/extensions/OES/ |
D | OES_surfaceless_context.txt | 50 Applications that only want to render to framebuffer objects should 77 framebuffer are ultimately controlled by the window-system that 78 allocates framebuffer resources ... 81 by the state of the windowsystem-provided framebuffer" 87 system-provided framebuffer at any time, referred to as the default 88 framebuffer. Application-created framebuffers, referred to as 89 framebuffer objects, may be created as desired. These two types of 90 framebuffer are distinguished primarily by the interface for 92 The effects of GL commands on the default framebuffer are 94 framebuffer resources, determines which portions of the default [all …]
|
/third_party/openGLES/extensions/OES/ |
D | OES_surfaceless_context.txt | 60 Applications that only want to render to framebuffer objects should 87 framebuffer are ultimately controlled by the window-system that 88 allocates framebuffer resources ... 91 by the state of the windowsystem-provided framebuffer" 97 system-provided framebuffer at any time, referred to as the default 98 framebuffer. Application-created framebuffers, referred to as 99 framebuffer objects, may be created as desired. These two types of 100 framebuffer are distinguished primarily by the interface for 102 The effects of GL commands on the default framebuffer are 104 framebuffer resources, determines which portions of the default [all …]
|
/third_party/uboot/u-boot-2020.01/doc/device-tree-bindings/video/ |
D | simple-framebuffer.txt | 8 - compatible: "simple-framebuffer" 9 - reg: Should contain the location and size of the framebuffer memory. 10 - width: The width of the framebuffer in pixels. 11 - height: The height of the framebuffer in pixels. 12 - stride: The number of bytes in each line of the framebuffer. 13 - format: The format of the framebuffer surface. Valid values are: 18 framebuffer { 19 compatible = "simple-framebuffer";
|
/third_party/flutter/skia/third_party/externals/angle2/extensions/ |
D | ANGLE_framebuffer_blit.txt | 44 This extension modifies framebuffer objects by splitting the 45 framebuffer object binding point into separate DRAW and READ 46 bindings. This allows copying directly from one framebuffer to 86 to READ_FRAMEBUFFER_BINDING_ANGLE is not "framebuffer complete" 97 framebuffer is the destination for rendering operations, and the 98 read framebuffer is the source for readback operations. The same 99 framebuffer may be used for both drawing and reading. Section 100 4.4.1 describes the mechanism for controlling framebuffer usage." 104 "While an application-created framebuffer object is bound to 111 the object bound to READ_FRAMEBUFFER_BINDING_ANGLE is not "framebuffer [all …]
|
D | ANGLE_framebuffer_multisample.txt | 46 This extension extends the framebuffer object framework to 56 All of the framebuffer-attachable images attached to a framebuffer 57 object must have the same number of SAMPLES or else the framebuffer 58 object is not "framebuffer complete". If a framebuffer object with 59 multisample attachments is "framebuffer complete", then the 60 framebuffer object behaves as if SAMPLE_BUFFERS is one. 65 framebuffer object and the destination is a single-sample 66 framebuffer object (either application-created or window-system 104 READ_FRAMEBUFFER_BINDING_ANGLE is "framebuffer complete" and the value 114 (section 4.4) is non-zero, the read framebuffer is framebuffer [all …]
|
/third_party/skia/third_party/externals/opengl-registry/extensions/ANGLE/ |
D | ANGLE_framebuffer_blit.txt | 44 This extension modifies framebuffer objects by splitting the 45 framebuffer object binding point into separate DRAW and READ 46 bindings. This allows copying directly from one framebuffer to 86 to READ_FRAMEBUFFER_BINDING_ANGLE is not "framebuffer complete" 97 framebuffer is the destination for rendering operations, and the 98 read framebuffer is the source for readback operations. The same 99 framebuffer may be used for both drawing and reading. Section 100 4.4.1 describes the mechanism for controlling framebuffer usage." 104 "While an application-created framebuffer object is bound to 111 the object bound to READ_FRAMEBUFFER_BINDING_ANGLE is not "framebuffer [all …]
|
/third_party/openGLES/extensions/ANGLE/ |
D | ANGLE_framebuffer_blit.txt | 44 This extension modifies framebuffer objects by splitting the 45 framebuffer object binding point into separate DRAW and READ 46 bindings. This allows copying directly from one framebuffer to 86 to READ_FRAMEBUFFER_BINDING_ANGLE is not "framebuffer complete" 97 framebuffer is the destination for rendering operations, and the 98 read framebuffer is the source for readback operations. The same 99 framebuffer may be used for both drawing and reading. Section 100 4.4.1 describes the mechanism for controlling framebuffer usage." 104 "While an application-created framebuffer object is bound to 111 the object bound to READ_FRAMEBUFFER_BINDING_ANGLE is not "framebuffer [all …]
|
D | ANGLE_framebuffer_multisample.txt | 46 This extension extends the framebuffer object framework to 56 All of the framebuffer-attachable images attached to a framebuffer 57 object must have the same number of SAMPLES or else the framebuffer 58 object is not "framebuffer complete". If a framebuffer object with 59 multisample attachments is "framebuffer complete", then the 60 framebuffer object behaves as if SAMPLE_BUFFERS is one. 65 framebuffer object and the destination is a single-sample 66 framebuffer object (either application-created or window-system 104 READ_FRAMEBUFFER_BINDING_ANGLE is "framebuffer complete" and the value 114 (section 4.4) is non-zero, the read framebuffer is framebuffer [all …]
|
/third_party/skia/third_party/externals/angle2/extensions/ |
D | ANGLE_framebuffer_blit.txt | 44 This extension modifies framebuffer objects by splitting the 45 framebuffer object binding point into separate DRAW and READ 46 bindings. This allows copying directly from one framebuffer to 86 to READ_FRAMEBUFFER_BINDING_ANGLE is not "framebuffer complete" 97 framebuffer is the destination for rendering operations, and the 98 read framebuffer is the source for readback operations. The same 99 framebuffer may be used for both drawing and reading. Section 100 4.4.1 describes the mechanism for controlling framebuffer usage." 104 "While an application-created framebuffer object is bound to 111 the object bound to READ_FRAMEBUFFER_BINDING_ANGLE is not "framebuffer [all …]
|
D | ANGLE_framebuffer_multisample.txt | 46 This extension extends the framebuffer object framework to 56 All of the framebuffer-attachable images attached to a framebuffer 57 object must have the same number of SAMPLES or else the framebuffer 58 object is not "framebuffer complete". If a framebuffer object with 59 multisample attachments is "framebuffer complete", then the 60 framebuffer object behaves as if SAMPLE_BUFFERS is one. 65 framebuffer object and the destination is a single-sample 66 framebuffer object (either application-created or window-system 104 READ_FRAMEBUFFER_BINDING_ANGLE is "framebuffer complete" and the value 114 (section 4.4) is non-zero, the read framebuffer is framebuffer [all …]
|
/third_party/openGLES/extensions/EXT/ |
D | EXT_framebuffer_blit.txt | 54 framebuffer object binding point into separate DRAW and READ 55 bindings. This allows copying directly from one framebuffer to 92 "framebuffer complete" (section 4.4.4.2)." 101 READ_FRAMEBUFFER_BINDING_EXT is not "framebuffer complete" 109 bound to READ_FRAMEBUFFER_BINDING_EXT is not "framebuffer 117 DRAW_FRAMEBUFFER_BINDING_EXT is not "framebuffer complete" 125 DRAW_FRAMEBUFFER_BINDING_EXT is not "framebuffer complete" 133 to READ_FRAMEBUFFER_BINDING_EXT is not "framebuffer complete" 144 framebuffer is the destination for rendering operations, and the 145 read framebuffer is the source for readback operations. The same [all …]
|
D | EXT_framebuffer_object.txt | 104 known collectively as "framebuffer-attachable images". This 105 extension provides a mechanism for attaching framebuffer-attachable 106 images to the GL framebuffer as one of the standard GL logical 108 framebuffer-attachable image to the accum logical buffer is left for 109 a future extension to define). When a framebuffer-attachable image 110 is attached to the framebuffer, it is used as the source and 113 By allowing the use of a framebuffer-attachable image as a rendering 116 of a texture to be used as framebuffer-attachable images. A 118 framebuffer-attachable image by specifying the mipmap level, cube 122 the framebuffer, followed immediately by a call to CopyTexSubImage. [all …]
|
/third_party/skia/third_party/externals/opengl-registry/extensions/EXT/ |
D | EXT_framebuffer_blit.txt | 54 framebuffer object binding point into separate DRAW and READ 55 bindings. This allows copying directly from one framebuffer to 92 "framebuffer complete" (section 4.4.4.2)." 101 READ_FRAMEBUFFER_BINDING_EXT is not "framebuffer complete" 109 bound to READ_FRAMEBUFFER_BINDING_EXT is not "framebuffer 117 DRAW_FRAMEBUFFER_BINDING_EXT is not "framebuffer complete" 125 DRAW_FRAMEBUFFER_BINDING_EXT is not "framebuffer complete" 133 to READ_FRAMEBUFFER_BINDING_EXT is not "framebuffer complete" 144 framebuffer is the destination for rendering operations, and the 145 read framebuffer is the source for readback operations. The same [all …]
|
D | EXT_framebuffer_object.txt | 104 known collectively as "framebuffer-attachable images". This 105 extension provides a mechanism for attaching framebuffer-attachable 106 images to the GL framebuffer as one of the standard GL logical 108 framebuffer-attachable image to the accum logical buffer is left for 109 a future extension to define). When a framebuffer-attachable image 110 is attached to the framebuffer, it is used as the source and 113 By allowing the use of a framebuffer-attachable image as a rendering 116 of a texture to be used as framebuffer-attachable images. A 118 framebuffer-attachable image by specifying the mipmap level, cube 122 the framebuffer, followed immediately by a call to CopyTexSubImage. [all …]
|
/third_party/skia/third_party/externals/opengl-registry/extensions/NV/ |
D | NV_framebuffer_blit.txt | 58 framebuffer object binding point into separate DRAW and READ 59 bindings. This allows copying directly from one framebuffer to 92 READ_FRAMEBUFFER_BINDING_NV is not framebuffer complete 103 "The GL has two active framebuffers; the draw framebuffer is the 104 destination for rendering operations, and the read framebuffer is 105 the source for readback operations. The same framebuffer may be used 107 for controlling framebuffer usage. 109 The default framebuffer is initially used as the draw and read 110 framebuffer and the initial state of all provided bitplanes is 116 "While an application-created framebuffer object is bound to [all …]
|
D | NV_framebuffer_multisample.txt | 51 This extension extends the framebuffer object framework to 61 All of the framebuffer-attachable images attached to a framebuffer 62 object must have the same number of SAMPLES or else the framebuffer 63 object is not "framebuffer complete". If a framebuffer object with 64 multisample attachments is "framebuffer complete", then the 65 framebuffer object behaves as if SAMPLE_BUFFERS is one. 69 extension) where the source is a multisample framebuffer object 70 and the destination is a single-sample framebuffer object. 71 Source and destination framebuffer may be either application-created 104 is "framebuffer complete" and the value of SAMPLE_BUFFERS is greater [all …]
|
/third_party/openGLES/extensions/NV/ |
D | NV_framebuffer_blit.txt | 58 framebuffer object binding point into separate DRAW and READ 59 bindings. This allows copying directly from one framebuffer to 92 READ_FRAMEBUFFER_BINDING_NV is not framebuffer complete 103 "The GL has two active framebuffers; the draw framebuffer is the 104 destination for rendering operations, and the read framebuffer is 105 the source for readback operations. The same framebuffer may be used 107 for controlling framebuffer usage. 109 The default framebuffer is initially used as the draw and read 110 framebuffer and the initial state of all provided bitplanes is 116 "While an application-created framebuffer object is bound to [all …]
|
D | NV_framebuffer_multisample.txt | 51 This extension extends the framebuffer object framework to 61 All of the framebuffer-attachable images attached to a framebuffer 62 object must have the same number of SAMPLES or else the framebuffer 63 object is not "framebuffer complete". If a framebuffer object with 64 multisample attachments is "framebuffer complete", then the 65 framebuffer object behaves as if SAMPLE_BUFFERS is one. 69 extension) where the source is a multisample framebuffer object 70 and the destination is a single-sample framebuffer object. 71 Source and destination framebuffer may be either application-created 104 is "framebuffer complete" and the value of SAMPLE_BUFFERS is greater [all …]
|