[Mesa-dev] Mesa EGL extensions

Kristian Høgsberg krh at bitplanet.net
Fri Aug 27 05:26:40 PDT 2010

2010/8/27 Chia-I Wu <olvaffe at gmail.com>:
> 2010/8/27 Kristian Høgsberg <krh at bitplanet.net>:
>> On Thu, Aug 26, 2010 at 11:55 AM, nobled <nobled at dreamwidth.org> wrote:
>> I can't speak for EGL_MESA_screen_surface, but shipping unauthorized
>> tokens certainly is a problem.
> I am not aware of any user of EGL_MESA_screen_surface.  It was
> designed for Xegl which was dead for a while, IIRC.
> It is conceptually useful though.  It enables EGL on platforms without
> window systems.  The bulk of the extension is about mode setting.  But
> as the extension predates KMS, which is still getting new features
> itself, the extension does not receive much attention.
> With the new DRM display and image extensions, there is nothing in
> EGL_MESA_screen_surface that cannot be accomplished by the new
> extensions.  The complexity of mode setting, which is taken care of by
> EGL_MESA_screen_surface, can also be moved to an utility library.
> Personally, I would vote for killing the extension in the git history.

Yes, I think removing it would be the best route, but lets see what Brian says.

>>> Finally, a few things about the new EGL_MESA_drm_image extension:
>>> - Is it also using unallocated enums? They're in the 0x31D0
>>> "any_vendor_use" range in the eglenum.spec file, but I think that
>>> means 'these might belong to any vendor after Khronos allocates them;
>>> aka Reserved', based on the instructions after that seeming to be
>>> directed to Khronos employees who can edit the file.
>> It's using allocated tokens.
> Allocated for Mesa?

Yes, for this specific extension.


More information about the mesa-dev mailing list