On 02/11/16 04:43 PM, Chris Wilson wrote:
> On Wed, Nov 02, 2016 at 04:16:55PM +0900, Michel Dänzer wrote:
>> On 02/11/16 04:13 PM, Chris Wilson wrote:
>>> On Wed, Nov 02, 2016 at 10:09:26AM +0900, Michel Dänzer wrote:
On 22/10/16 07:00 PM, Chris Wilson wrote:
> This applies a synchronisat
On Wed, Nov 02, 2016 at 04:16:55PM +0900, Michel Dänzer wrote:
> On 02/11/16 04:13 PM, Chris Wilson wrote:
> > On Wed, Nov 02, 2016 at 10:09:26AM +0900, Michel Dänzer wrote:
> >> On 22/10/16 07:00 PM, Chris Wilson wrote:
> >>> This applies a synchronisation point to GetBuffers() such that binding a
On 02/11/16 04:13 PM, Chris Wilson wrote:
> On Wed, Nov 02, 2016 at 10:09:26AM +0900, Michel Dänzer wrote:
>> On 22/10/16 07:00 PM, Chris Wilson wrote:
>>> This applies a synchronisation point to GetBuffers() such that binding a
>>> texture-from-pixmap its rendering is serialised with X. This match
On Wed, Nov 02, 2016 at 10:09:26AM +0900, Michel Dänzer wrote:
> On 22/10/16 07:00 PM, Chris Wilson wrote:
> > This applies a synchronisation point to GetBuffers() such that binding a
> > texture-from-pixmap its rendering is serialised with X. This matches the
> > synchronisation point inside DRI2,
On 22/10/16 07:00 PM, Chris Wilson wrote:
> This applies a synchronisation point to GetBuffers() such that binding a
> texture-from-pixmap its rendering is serialised with X. This matches the
> synchronisation point inside DRI2, but it is also arguable that implied
> sync should be explicitly handl
This applies a synchronisation point to GetBuffers() such that binding a
texture-from-pixmap its rendering is serialised with X. This matches the
synchronisation point inside DRI2, but it is also arguable that implied
sync should be explicitly handled by the client by calling glXWaitX()
following t
