I don't feel strongly about it anyway. Can always change it later.
Jose
- Original Message -
> On 04.04.2013 21:53, Christoph Bumiller wrote:
> > On 04.04.2013 21:44, Jose Fonseca wrote:
> >> I think that PIPE_BIND_INDIRECT_BUFFER would be more self-descriptive.
>
> Marek suggested PIPE_
On 04.04.2013 21:53, Christoph Bumiller wrote:
> On 04.04.2013 21:44, Jose Fonseca wrote:
>> I think that PIPE_BIND_INDIRECT_BUFFER would be more self-descriptive.
Marek suggested PIPE_BIND_DRAW_INDIRECT_BUFFER, but I think that's too
specific because there's also a DISPATCH_INDIRECT buffer for co
On 04.04.2013 21:44, Jose Fonseca wrote:
> I think that PIPE_BIND_INDIRECT_BUFFER would be more self-descriptive.
>
> Or do you envision other uses of such buffer?
It's possible that at some point we add a mechanism to let the driver
store arbitrary commands into a buffer created by the st, or hav
I think that PIPE_BIND_INDIRECT_BUFFER would be more self-descriptive.
Or do you envision other uses of such buffer?
Jose
- Original Message -
> Intended for use with GL_ARB_draw_indirect's DRAW_INDIRECT_BUFFER
> target or for D3D11_RESOURCE_MISC_DRAWINDIRECT_ARGS.
> ---
> src/gallium/d
Intended for use with GL_ARB_draw_indirect's DRAW_INDIRECT_BUFFER
target or for D3D11_RESOURCE_MISC_DRAWINDIRECT_ARGS.
---
src/gallium/docs/source/screen.rst |2 ++
src/gallium/include/pipe/p_defines.h |1 +
2 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/src/gallium/docs/
