Hello, The mesa/main support for ARB_gs5 is nearly ready, and I have the various mesa/st patches all sent out. The last bit is the dynamic sampler support which I think will Just Work in mesa/st once glsl lets it through.
Most extensions are enabled on the basis of a PIPE_CAP_*, either it being enabled, or being > some limit. However ARB_gs5 is an extension composed of like 10 sub-features. I could go through and add caps for each of them, but that seems really excessive. In a future universe, we might rely on PIPE_CAP_GLSL_FEATURE_LEVEL >= 400, but since fp64/tess support aren't there yet (and may not be implemented by all drivers simultaneously when they are), I feel a little weird about using that as the "defining" metric. But it's not so bad -- fp64 could require some sort of DOUBLE shader cap, and tess could check for max instructions with the relevant PIPE_SHADER_*. What's the preferred way of doing this? Cheers, -ilia _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
