Re: [Mesa-dev] [RFC 1/1] glx: port dri2GetBuffers/dri2GetBuffersWithFormat to XCB

2017-04-26 Thread Michel Dänzer
On 26/04/17 07:11 PM, Gregory Hainaut wrote: > On 4/26/17, Michel Dänzer wrote: >> On 26/04/17 05:07 PM, Gregory Hainaut wrote: >>> >>> Note: those dri2* functions are typically called by gallium/mesa state >>> tracker to handle new backbuffer allocation. When the old

Re: [Mesa-dev] [RFC 1/1] glx: port dri2GetBuffers/dri2GetBuffersWithFormat to XCB

2017-04-26 Thread Gregory Hainaut
On 4/26/17, Michel Dänzer wrote: > On 26/04/17 05:07 PM, Gregory Hainaut wrote: >> >> Note: those dri2* functions are typically called by gallium/mesa state >> tracker to handle new backbuffer allocation. When the old backbuffer was >> previously invalidated due to vsync. > >

Re: [Mesa-dev] [RFC 1/1] glx: port dri2GetBuffers/dri2GetBuffersWithFormat to XCB

2017-04-26 Thread Michel Dänzer
On 26/04/17 05:07 PM, Gregory Hainaut wrote: > > Note: those dri2* functions are typically called by gallium/mesa state > tracker to handle new backbuffer allocation. When the old backbuffer was > previously invalidated due to vsync. FWIW, DRI2 buffer invalidation isn't directly related to

[Mesa-dev] [RFC 1/1] glx: port dri2GetBuffers/dri2GetBuffersWithFormat to XCB

2017-04-26 Thread Gregory Hainaut
By default Xlib isn't thread safe so we better avoid it when gl thread is enabled. It will help applications that use XCB. But it will still crash if applications are still relying on Xlib (without XInitThread). Note: those dri2* functions are typically called by gallium/mesa state tracker to