[Mesa-dev] [PATCH 11/17] gallium: add PIPE_CAP_MAX_TEXTURE_BUFFER_SIZE for GL

Brian Paul brianp at vmware.com
Thu May 2 07:23:00 PDT 2013


On 05/01/2013 09:43 PM, Marek Olšák wrote:
> ---
>   src/gallium/docs/source/screen.rst           |    2 ++
>   src/gallium/drivers/llvmpipe/lp_screen.c     |    2 ++
>   src/gallium/drivers/nv30/nv30_screen.c       |    1 +
>   src/gallium/drivers/nv50/nv50_screen.c       |    2 ++
>   src/gallium/drivers/nvc0/nvc0_screen.c       |    2 ++
>   src/gallium/drivers/r300/r300_screen.c       |    1 +
>   src/gallium/drivers/r600/r600_pipe.c         |    3 +++
>   src/gallium/drivers/radeonsi/radeonsi_pipe.c |    1 +
>   src/gallium/drivers/softpipe/sp_screen.c     |    2 ++
>   src/gallium/drivers/svga/svga_screen.c       |    1 +
>   src/gallium/include/pipe/p_defines.h         |    3 ++-
>   src/mesa/state_tracker/st_extensions.c       |    5 ++++-
>   12 files changed, 23 insertions(+), 2 deletions(-)
>
> diff --git a/src/gallium/docs/source/screen.rst b/src/gallium/docs/source/screen.rst
> index 3ab7e9e..2630491 100644
> --- a/src/gallium/docs/source/screen.rst
> +++ b/src/gallium/docs/source/screen.rst
> @@ -162,6 +162,8 @@ The integer capabilities:
>     state should be swizzled manually according to the swizzle in the sampler
>     view it is intended to be used with, or herein undefined results may occur
>     for permutational swizzles.
> +* ``PIPE_CAP_MAX_TEXTURE_BUFFER_SIZE``: The maximum accessible size with
> +  a buffer sampler view, in bytes.
>
>
>   .. _pipe_capf:
> diff --git a/src/gallium/drivers/llvmpipe/lp_screen.c b/src/gallium/drivers/llvmpipe/lp_screen.c
> index 667ade1..d518b33 100644
> --- a/src/gallium/drivers/llvmpipe/lp_screen.c
> +++ b/src/gallium/drivers/llvmpipe/lp_screen.c
> @@ -224,6 +224,8 @@ llvmpipe_get_param(struct pipe_screen *screen, enum pipe_cap param)
>         return 0;
>      case PIPE_CAP_TEXTURE_BUFFER_OBJECTS:
>         return 1;
> +   case PIPE_CAP_MAX_TEXTURE_BUFFER_SIZE:
> +      return 65535;

Dumb question: why isn't this 65536?

-Brian


More information about the mesa-dev mailing list