Lines Matching refs:protected
57 This extension introduces the concept of protected contexts and protected
59 creation time whether a context, surface or EGLImage is protected or not.
61 A protected context is required to allow the GPU to operate on protected
62 resources, including protected surfaces and protected EGLImages.
67 to handle protected content is by using a protected virtual to physical
69 read or write faults when a non-protected source tries to access a protected
72 actually allowing a transfer of data from a protected surface to a
73 non-protected surface.
95 is said to be protected. A protected context is required to allow the
96 GPU to operate on protected resources, including protected surfaces and
97 protected EGLImages.
100 defined to be protected or not protected. Each stage defines
101 restrictions on whether it can read or write protected and unprotected
104 When a GPU stage is protected, it:
105 - Can read from protected resources
107 - Can write to protected resources
110 When a GPU stage is not protected, it:
111 - Can NOT read from protected resources
113 - Can NOT write to protected resources
119 This extension does not specify which pipeline stages of a protected
120 context are protected or not. This is left to a client API extension to
121 define. All stages in a regular (not protected) context are not
122 protected. However, if EGL_EXT_protected_surface is also supported, a
123 regular (not protected) context will execute stages where one or more
124 protected resources is accessed as if it were a protected context.
128 made about whether the stage will be protected or not protected.
130 are the intersection of the allowed operations for protected and not
131 protected stages, i.e it:
133 - Can NOT read from protected resources
135 - Can NOT write to protected resources
163 "EGL_PROTECTED_CONTENT_EXT specifies the protected state of the new
165 protected. If its value is EGL_FALSE, then the context is not
166 protected. See section 2.7 (Protected Content) for more information
167 about protected contexts.
184 "EGL_PROTECTED_CONTENT_EXT specifies the protected state of the
186 is said to be protected. If its value is EGL_FALSE, then the surface
187 content is not protected. See section 2.7 (Protected Content) for
188 more information about protected and non-protected surfaces.
190 Client APIs will not allow contents of protected surfaces to be
191 accessed by non-protected contexts in the system (including
195 Calling eglSwapBuffers on such a protected surface will succeed, but
198 protected content. Any disallowed operation will fail and result in
223 and the EGLImage sources can be guaranteed to be protected, then the
224 EGLImage is said to be protected. See section 2.7 (Protected Content)
225 for more information about protected resources including EGLImages.
229 - If EGLImage sources are not protected, the EGLImage is said to be
230 not protected. See section 2.7 (Protected Content) for more
231 information about non-protected resources including EGLImages.
232 - If EGLImage sources are protected then the EGLImage content will
234 context is protected or not. Trying to access such an EGLImage's
241 regarding the protected state of the EGLImage source, the error
245 1) Can a protected context be shared with a non-protected context?
247 RESOLVED - Yes. The rule that protected surfaces can only be used by
248 protected contexts still applies. An example use case is where
250 context and then share it with a protected context to be used as a texture.
252 2) Should all surfaces within a protected context be protected by default?
254 RESOLVED - No, several implementations have limited amounts of protected
255 memory, so the API will require opting into protected memory.
257 3) Can these protected surfaces be used by stages other than fragment
268 of inferring the protected status from EGLImage sources -
273 For these use cases a protected attribute is useful, so we want to
276 need to be completed before a protected EGL image can be accessed.
277 This attribute along with a corresponding protected buffer will act
281 be aware of the fact that the resource is protected or may be unable
283 protected buffer through an EGLImage will be predicated on the
284 buffer being protected, having a protected context and the intent of
302 10 04/08/16 rsmith - Added general section on protected content.
304 refer to the general protected content principles.
306 protected, including allowing for the protected
310 - Removed references to the GPU protected mode,