zink: fix shader buffer size caps to use 65536

using max(Uniform|Storage)BufferRange yields some insane values that aren't
consistent with reality

affects PIPE_CAP_MAX_SHADER_BUFFER_SIZE and PIPE_SHADER_CAP_MAX_CONST_BUFFER_SIZE

Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6981>
This commit is contained in:
Mike Blumenkrantz 2020-06-26 15:17:32 -04:00 committed by Marge Bot
parent 0e3e323224
commit 9a8539206f
1 changed files with 2 additions and 2 deletions

View File

@ -296,7 +296,7 @@ zink_get_param(struct pipe_screen *pscreen, enum pipe_cap param)
return screen->info.props.limits.maxDescriptorSetStorageBuffers;
case PIPE_CAP_MAX_SHADER_BUFFER_SIZE:
return screen->info.props.limits.maxStorageBufferRange; /* unsure */
return 65536;
case PIPE_CAP_TGSI_FS_COORD_ORIGIN_UPPER_LEFT:
case PIPE_CAP_TGSI_FS_COORD_PIXEL_CENTER_HALF_INTEGER:
@ -417,7 +417,7 @@ zink_get_shader_param(struct pipe_screen *pscreen,
}
case PIPE_SHADER_CAP_MAX_CONST_BUFFER_SIZE:
return MIN2(screen->info.props.limits.maxUniformBufferRange, INT_MAX);
return 65536;
case PIPE_SHADER_CAP_MAX_CONST_BUFFERS:
return screen->info.props.limits.maxPerStageDescriptorUniformBuffers;