[Mesa-dev] [PATCH 1/2] RFC : Context aware user space Resource control
lionel.g.landwerlin at intel.com
Tue Jul 24 11:11:09 UTC 2018
On 23/07/18 10:20, Kedar J Karanje wrote:
> On Fri, Jul 20, 2018 at 10:59:03AM +0100, Lionel Landwerlin wrote:
>> On 20/07/18 09:32, aravindan.muthukumar at intel.com wrote:
>>> diff --git a/src/egl/generate/egl.xml b/src/egl/generate/egl.xml
>>> index 9250f93..52b0c9f 100644
>>> --- a/src/egl/generate/egl.xml
>>> +++ b/src/egl/generate/egl.xml
>>> @@ -460,6 +460,14 @@
>>> <unused start="0x3107" end="0x310F"/>
>>> + <enums namespace="EGL" start="0x31A0" end="0x31A3" vendor="IMG" comment="Reserved for context aware load type">
>>> + <enum value="0x31A0" name="EGL_CONTEXT_LOAD_TYPE"/>
>>> + <enum value="0x31A1" name="EGL_CONTEXT_LOAD_LOW"/>
>>> + <enum value="0x31A2" name="EGL_CONTEXT_LOAD_MEDIUM"/>
>>> + <enum value="0x31A3" name="EGL_CONTEXT_LOAD_HIGH"/>
>>> + <unused start="0x31A0" end="0x31A3"/>
>>> + </enums>
>>> <enums namespace="EGL" start="0x3110" end="0x311F" vendor="ATX" comment="Reserved for Tim Renouf, Antix (Khronos bug 4949)">
>>> <enum value="0x3110" name="EGL_BITMAP_PIXEL_SIZE_KHR"/>
>>> <unused start="0x3111" end="0x311F"/>
>> Are you defining a new extension here?
>> The chunk above seems to imply this is from IMG, but still commented as
>> As far as I understand enums need to be allocated through Khronos group
>> before you can make use of them.
>> Otherwise this will be unusable by applications as soon as another extension
>> reuses the same enums...
> Hello Lionel,
> Thank you for the comments, yes we used IMG extension as a template and were
> wondering how the xml is modified , when we found the procedure for proposing
> an extension : https://www.khronos.org/registry/OpenGL/docs/rules.html ,
> just wondering how does it work for RFC ,
> Do we need to get through the Khronos process first then send for RFC or
> is the other way round ok ? I shall dig into the mail archives for any
> existing extension and how it came into being.
I think usually there is some amount of discussion internally about
whether the feature makes sense.
Then it's published through Khronos and finally the implementation can land.
>> mesa-dev mailing list
>> mesa-dev at lists.freedesktop.org
More information about the mesa-dev