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

[Rob Herring]

On Mon, May 15, 2017 at 11:23 AM, Emil Velikov <emil.l.velikov at gmail.com> wrote:
> 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?

What exactly does without EGL mean? A process only using GBM and no
EGL context or screen? That will soon be very common when gralloc is
in its own process.

Rob