On 02/07/2016 05:56 AM, Ilia Mirkin wrote:
On Sat, Feb 6, 2016 at 6:13 PM, Ilia Mirkin wrote:
On Sat, Feb 6, 2016 at 5:38 PM, Samuel Pitoiset
wrote:
When indirect compute is used, the size of the grid (in blocks) is
stored as three integers inside a buffer. This requires a macro to
set up G
On 02/07/2016 12:13 AM, Ilia Mirkin wrote:
On Sat, Feb 6, 2016 at 5:38 PM, Samuel Pitoiset
wrote:
When indirect compute is used, the size of the grid (in blocks) is
stored as three integers inside a buffer. This requires a macro to
set up GRIDDIM_YX and GRIDDIM_Z.
Signed-off-by: Samuel Pitoi
On Sat, Feb 6, 2016 at 6:13 PM, Ilia Mirkin wrote:
> On Sat, Feb 6, 2016 at 5:38 PM, Samuel Pitoiset
> wrote:
>> When indirect compute is used, the size of the grid (in blocks) is
>> stored as three integers inside a buffer. This requires a macro to
>> set up GRIDDIM_YX and GRIDDIM_Z.
>>
>> Signe
On Sat, Feb 6, 2016 at 5:38 PM, Samuel Pitoiset
wrote:
> When indirect compute is used, the size of the grid (in blocks) is
> stored as three integers inside a buffer. This requires a macro to
> set up GRIDDIM_YX and GRIDDIM_Z.
>
> Signed-off-by: Samuel Pitoiset
> ---
> src/gallium/drivers/nouve
When indirect compute is used, the size of the grid (in blocks) is
stored as three integers inside a buffer. This requires a macro to
set up GRIDDIM_YX and GRIDDIM_Z.
Signed-off-by: Samuel Pitoiset
---
src/gallium/drivers/nouveau/nvc0/mme/Makefile | 2 +-
src/gallium/drivers/nouveau/nvc0/m
