On 10/29/2012 11:41 AM, Marek Olšák wrote:
On Mon, Oct 29, 2012 at 6:29 PM, Ian Romanick wrote:
On 10/28/2012 09:55 AM, Marek Olšák wrote:
How does Gallium handle GL_WRITE_ONLY mappings of busy buffers? In the
past, this would cause drivers to allocate a temporary buffer (of some sort)
and re
On Mon, Oct 29, 2012 at 6:29 PM, Ian Romanick wrote:
> On 10/28/2012 09:55 AM, Marek Olšák wrote:
>
> How does Gallium handle GL_WRITE_ONLY mappings of busy buffers? In the
> past, this would cause drivers to allocate a temporary buffer (of some sort)
> and return that to the application. In at
On 10/28/2012 09:55 AM, Marek Olšák wrote:
How does Gallium handle GL_WRITE_ONLY mappings of busy buffers? In the
past, this would cause drivers to allocate a temporary buffer (of some
sort) and return that to the application. In at least some cases, that
temporary buffer came from malloc...
On 10/28/2012 10:55 AM, Marek Olšák wrote:
---
docs/GL3.txt |2 +-
src/gallium/drivers/i915/i915_screen.c |1 +
src/gallium/drivers/llvmpipe/lp_screen.c |1 +
src/gallium/drivers/nv30/nv30_screen.c |1 +
src/gallium/drivers/nv5
---
docs/GL3.txt |2 +-
src/gallium/drivers/i915/i915_screen.c |1 +
src/gallium/drivers/llvmpipe/lp_screen.c |1 +
src/gallium/drivers/nv30/nv30_screen.c |1 +
src/gallium/drivers/nv50/nv50_screen.c |1 +
src/gallium/driver
