On 15 May 2017 at 17:50, Rob Herring <r...@kernel.org> wrote: > On Mon, May 15, 2017 at 11:23 AM, Emil Velikov <emil.l.veli...@gmail.com> > wrote: >> On 11 May 2017 at 19:57, Emil Velikov <emil.l.veli...@gmail.com> wrote: >>> From: Emil Velikov <emil.veli...@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.veli...@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? The same.
> That will soon be very common when gralloc is > in its own process. > Smashing thanks for the confirmation. I'll preserve the original behaviour and only address the "fragile" parts. -Emil _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
