[Mesa-dev] [PATCH 13/13] gbm: don't manage our set of DRI extensions

[Emil Velikov]

On 11 May 2017 at 19:57, Emil Velikov <emil.l.velikov at gmail.com> wrote:
> From: Emil Velikov <emil.velikov at collabora.com>
>
> Don't fetch/manage our set of extensions apart from __DRI_CORE,
> __DRI_DRI2 and __DRI_SWRAST. We require these to setup a screen and
> context (in case of bo map/unmap).
>
> The rest are fetched and kept in sync with the rest of EGL, via the
> egl/drm code.
>
> Signed-off-by: Emil Velikov <emil.velikov at collabora.com>
> ---
>
> Strictly speaking this might break if one uses GBM without EGL. If that
> is a valid usecase we can keep the required extensions - flush/image
> within GBM itself.

Rob what do you think wrt the above question?

A bit of a background:
ATM we fetch "all" the extensions required by EGL within GBM and copy
the extension pointers over.
It tends to be rather fragile since we forget to keep to update GBM
alongside EGL.

Thanks
Emil