On Thu, Mar 2, 2017 at 6:37 PM, Samuel Pitoiset
wrote:
> Replying here.
>
> Yes, it makes sense, but looks like Roy still has some rendering issues with
> Pidgin even with that patch. Maybe something else is also broken in
> nvc0_validate_suf()?
Could be. Could also be an unrelated issue. Either
Replying here.
Yes, it makes sense, but looks like Roy still has some rendering issues
with Pidgin even with that patch. Maybe something else is also broken in
nvc0_validate_suf()?
Either way:
Acked-by: Samuel Pitoiset
On 03/01/2017 05:09 PM, Ilia Mirkin wrote:
When binding as textures, t
On Wed, Mar 1, 2017 at 11:54 AM, Roland Scheidegger wrote:
> Am 01.03.2017 um 17:09 schrieb Ilia Mirkin:
>> When binding as textures, the alignment can be 16. However when binding
>> as an image, the address has to be aligned to 256. (Also when binding as
>> an RT, but that can't happen with GL or
Am 01.03.2017 um 17:09 schrieb Ilia Mirkin:
> When binding as textures, the alignment can be 16. However when binding
> as an image, the address has to be aligned to 256. (Also when binding as
> an RT, but that can't happen with GL or current gallium APIs.)
FWIW binding buffers as rt is fully suppo
When binding as textures, the alignment can be 16. However when binding
as an image, the address has to be aligned to 256. (Also when binding as
an RT, but that can't happen with GL or current gallium APIs.)
Reported-by: Roy Spliet
Signed-off-by: Ilia Mirkin
---
src/gallium/drivers/nouveau/nvc0
