I only know about AMD_pinned_memory, which is for buffers only. I
don't know about an API for creating textures from user pointers. Yes,
there are pixel buffer objects, but they are a lot more difficult to
implement and they are defined such that a zero-copy approach to get a
texture is not possibl
What is this patch good for?
Nothing in particular, I just wanted to test how much overhead creating
a new BO each time we do transfer_inline_write actually makes.
BTW: Implementing transfer_inline_write using userptrs was just a prove
of concept. It turned out to actually be way slower than j
What is this patch good for?
Marek
On Tue, Aug 5, 2014 at 7:31 PM, Christian König wrote:
> From: Christian König
>
> Signed-off-by: Christian König
> ---
> src/gallium/drivers/radeon/r600_pipe_common.c | 9 ++
> src/gallium/drivers/radeon/r600_pipe_common.h | 11 +++
> src/gallium/d
From: Christian König
Signed-off-by: Christian König
---
src/gallium/drivers/radeon/r600_pipe_common.c | 9 ++
src/gallium/drivers/radeon/r600_pipe_common.h | 11 +++
src/gallium/drivers/radeon/r600_texture.c | 41 +--
3 files changed, 59 insertions(+), 2 de
