On Wed, 13 Feb 2019 at 09:32, Luigi Santivetti
wrote:
>
> Hello Emil,
>
> thanks for your feedback, I agree, dri2_make_current() looks complex.
> I'll comment inline.
>
> Emil Velikov writes:
>
> > Hi all,
> >
> > Haven't looked it this has landed or not.
> >
> > On Tue, 5 Feb 2019 at 16:41,
Hello Emil,
thanks for your feedback, I agree, dri2_make_current() looks complex.
I'll comment inline.
Emil Velikov writes:
> Hi all,
>
> Haven't looked it this has landed or not.
>
> On Tue, 5 Feb 2019 at 16:41, Eric Engestrom wrote:
>>
>> On Friday, 2019-02-01 13:36:27 +, Luigi
Hi all,
Haven't looked it this has landed or not.
On Tue, 5 Feb 2019 at 16:41, Eric Engestrom wrote:
>
> On Friday, 2019-02-01 13:36:27 +, Luigi Santivetti wrote:
> > Before this change, if bindContext() failed then dri2_make_current() would
> > rebind the old EGL context and surfaces and
On Friday, 2019-02-01 13:36:27 +, Luigi Santivetti wrote:
> Before this change, if bindContext() failed then dri2_make_current() would
> rebind the old EGL context and surfaces and return EGL_BAD_MATCH. However,
> it wouldn't rebind the DRI context and surfaces, thus leaving it in an
>
Before this change, if bindContext() failed then dri2_make_current() would
rebind the old EGL context and surfaces and return EGL_BAD_MATCH. However,
it wouldn't rebind the DRI context and surfaces, thus leaving it in an
inconsistent and unrecoverable state.
After this change, dri2_make_current()
