Re: [Mesa-dev] [PATCH 1/4] mesa: only lock framebuffer in compat profile

2017-04-25 Thread Fredrik Höglund
On Tuesday 25 April 2017, Timothy Arceri wrote: > On 24/04/17 22:51, Fredrik Höglund wrote: > > On Monday 24 April 2017, Timothy Arceri wrote: > >> From the EXT_framebuffer_object spec: > >> > >> "Framebuffer objects created with the commands defined > >> by the GL_EXT_framebuffer_object

Re: [Mesa-dev] [PATCH 1/4] mesa: only lock framebuffer in compat profile

2017-04-24 Thread Timothy Arceri
On 24/04/17 22:51, Fredrik Höglund wrote: On Monday 24 April 2017, Timothy Arceri wrote: From the EXT_framebuffer_object spec: "Framebuffer objects created with the commands defined by the GL_EXT_framebuffer_object extension are defined to be shared, while FBOs created with

Re: [Mesa-dev] [PATCH 1/4] mesa: only lock framebuffer in compat profile

2017-04-24 Thread Fredrik Höglund
On Monday 24 April 2017, Timothy Arceri wrote: > From the EXT_framebuffer_object spec: > >"Framebuffer objects created with the commands defined >by the GL_EXT_framebuffer_object extension are defined >to be shared, while FBOs created with commands defined >by the OpenGL core or

Re: [Mesa-dev] [PATCH 1/4] mesa: only lock framebuffer in compat profile

2017-04-24 Thread Emil Velikov
On 24 April 2017 at 11:49, Timothy Arceri wrote: > On 24/04/17 20:27, Emil Velikov wrote: >> >> Hi Tim, >> >> On 24 April 2017 at 06:28, Timothy Arceri wrote: >> >>> So in theory we could have a flag that is set by the bind >>> functions to decide if

Re: [Mesa-dev] [PATCH 1/4] mesa: only lock framebuffer in compat profile

2017-04-24 Thread Timothy Arceri
On 24/04/17 20:27, Emil Velikov wrote: Hi Tim, On 24 April 2017 at 06:28, Timothy Arceri wrote: So in theory we could have a flag that is set by the bind functions to decide if to lock or not. However we only expose GL_EXT_framebuffer_object in compat profile so this

Re: [Mesa-dev] [PATCH 1/4] mesa: only lock framebuffer in compat profile

2017-04-24 Thread Timothy Arceri
On 24/04/17 20:06, Nicolai Hähnle wrote: On 24.04.2017 07:28, Timothy Arceri wrote: From the EXT_framebuffer_object spec: "Framebuffer objects created with the commands defined by the GL_EXT_framebuffer_object extension are defined to be shared, while FBOs created with commands

Re: [Mesa-dev] [PATCH 1/4] mesa: only lock framebuffer in compat profile

2017-04-24 Thread Emil Velikov
Hi Tim, On 24 April 2017 at 06:28, Timothy Arceri wrote: > So in theory we could have a flag that is set by the bind > functions to decide if to lock or not. However we only > expose GL_EXT_framebuffer_object in compat profile so this > change just uses that to decide if

Re: [Mesa-dev] [PATCH 1/4] mesa: only lock framebuffer in compat profile

2017-04-24 Thread Nicolai Hähnle
On 24.04.2017 07:28, Timothy Arceri wrote: From the EXT_framebuffer_object spec: "Framebuffer objects created with the commands defined by the GL_EXT_framebuffer_object extension are defined to be shared, while FBOs created with commands defined by the OpenGL core or

[Mesa-dev] [PATCH 1/4] mesa: only lock framebuffer in compat profile

2017-04-23 Thread Timothy Arceri
From the EXT_framebuffer_object spec: "Framebuffer objects created with the commands defined by the GL_EXT_framebuffer_object extension are defined to be shared, while FBOs created with commands defined by the OpenGL core or GL_ARB_framebuffer_object extension are defined *not* to