On Wed, Sep 27, 2017 at 11:06 PM, Emil Velikov wrote:
> On 25 September 2017 at 08:25, Tomasz Figa wrote:
>
>> Gentle ping. :)
>>
>
> I forgot that you don't have commit access. Can you please apply for one?
Yep, I have it on my list, sorry for
On 25 September 2017 at 08:25, Tomasz Figa wrote:
> Gentle ping. :)
>
I forgot that you don't have commit access. Can you please apply for one?
Thanks
Emil
[1] https://www.freedesktop.org/wiki/AccountRequests/
[2] https://bugs.freedesktop.org/show_bug.cgi?id=99601
On Fri, Aug 11, 2017 at 1:31 PM, Tomasz Figa wrote:
> On Fri, Aug 11, 2017 at 2:29 AM, Emil Velikov
> wrote:
>> On 10 August 2017 at 14:59, Tomasz Figa wrote:
>>> dri2_fallback_swap_interval() currently used to stub out swap
On Fri, Aug 11, 2017 at 2:29 AM, Emil Velikov wrote:
> On 10 August 2017 at 14:59, Tomasz Figa wrote:
>> dri2_fallback_swap_interval() currently used to stub out swap interval
>> support in Android backend does nothing besides returning EGL_FALSE.
>>
Reviewed-by: Tapani Pälli
On 08/10/2017 04:59 PM, Tomasz Figa wrote:
dri2_fallback_swap_interval() currently used to stub out swap interval
support in Android backend does nothing besides returning EGL_FALSE.
This causes at least one known application (Android Snapchat)
On Thu 10 Aug 2017, Tomasz Figa wrote:
> dri2_fallback_swap_interval() currently used to stub out swap interval
> support in Android backend does nothing besides returning EGL_FALSE.
> This causes at least one known application (Android Snapchat) to fail
> due to an unexpected error and my loose
On 10 August 2017 at 14:59, Tomasz Figa wrote:
> dri2_fallback_swap_interval() currently used to stub out swap interval
> support in Android backend does nothing besides returning EGL_FALSE.
> This causes at least one known application (Android Snapchat) to fail
> due to an
dri2_fallback_swap_interval() currently used to stub out swap interval
support in Android backend does nothing besides returning EGL_FALSE.
This causes at least one known application (Android Snapchat) to fail
due to an unexpected error and my loose interpretation of the EGL 1.5
specification