[Mesa-dev] Properly exposing limits with gallium
imirkin at alum.mit.edu
Thu Jul 30 13:21:35 PDT 2015
So I'm trying to get these things to line up, especially for nvc0.
Here are the limits exposed by the blob drivers:
and they reflect what the hardware is capable. More specifically, I need
GL_MAX_VERTEX_OUTPUT_COMPONENTS = 128
GL_MAX_VARYING_FLOATS_ARB = 124
GL_MAX_FRAGMENT_INPUT_COMPONENTS = 128
GL_MAX_GEOMETRY_INPUT_COMPONENTS = 128
GL_MAX_GEOMETRY_OUTPUT_COMPONENTS = 128
What would the proper way to expose this be? Should we always just say
MAX_VARYING_FLOATS = MAX_VERTEX_OUTPUT_COMPONENTS - 4? Or a separate
PIPE_SHADER_CAP for the maxvaryingfloats?
More information about the mesa-dev