On 13/06/16 16:50, srol...@vmware.com wrote:
From: Roland Scheidegger
The gallium contract would be that bind flags must indicate all possible
bindings a resource might get used, but fact is the mesa state tracker does
not set bind flags correctly, and this is more or less
From: Roland Scheidegger
The gallium contract would be that bind flags must indicate all possible
bindings a resource might get used, but fact is the mesa state tracker does
not set bind flags correctly, and this is more or less unfixable due to GL.
This caused a bug with
On 13/06/16 09:56, Roland Scheidegger wrote:
Am 11.06.2016 um 18:41 schrieb Jose Fonseca:
On 11/06/16 00:19, srol...@vmware.com wrote:
From: Roland Scheidegger
The gallium contract would be that bind flags must indicate all possible
bindings a resource might get used, but
Am 11.06.2016 um 18:41 schrieb Jose Fonseca:
> On 11/06/16 00:19, srol...@vmware.com wrote:
>> From: Roland Scheidegger
>>
>> The gallium contract would be that bind flags must indicate all possible
>> bindings a resource might get used, but fact is the mesa state tracker
>>
On 11/06/16 00:19, srol...@vmware.com wrote:
From: Roland Scheidegger
The gallium contract would be that bind flags must indicate all possible
bindings a resource might get used, but fact is the mesa state tracker does
not set bind flags correctly, and this is more or less
From: Roland Scheidegger
The gallium contract would be that bind flags must indicate all possible
bindings a resource might get used, but fact is the mesa state tracker does
not set bind flags correctly, and this is more or less unfixable due to GL.
This caused a bug with