summaryrefslogtreecommitdiffstats
path: root/src/gallium/drivers/r600/r600_llvm.c
diff options
context:
space:
mode:
authorKenneth Graunke <[email protected]>2013-01-17 09:38:02 -0800
committerKenneth Graunke <[email protected]>2013-01-18 11:31:27 -0800
commit1ee2880e865135df451a3dc21ccc8f3631bdba02 (patch)
tree06d33d1f703fe3cc3ed396e8e53b6ca8b211e7cc /src/gallium/drivers/r600/r600_llvm.c
parentf0dbd9255b5813d1567e1f09266f80e35dcbeb70 (diff)
mesa: Only mark textures as mipmap incomplete on MAX_LEVEL issues.
According to the OpenGL 3.2 Core Profile specification, section 3.8.12: "For one-, two-, and three-dimensional and one-and two-dimensional array textures, a texture is mipmap complete if all of the following conditions hold true: - [...] - levelbase <= levelmax [...] Using the preceding definitions, a texture is complete unless any of the following conditions hold true: - [...] - The minification filter requires a mipmap (is neither NEAREST nor LINEAR), and the texture is not mipmap complete." (This text also appears in all GL >= 3.2 specs and the ES 3.0 spec.) From this, we see that levelbase <= levelmax should only affect mipmap completeness, not base-level completeness. Prior versions of GL did not have the notion of mipmap completeness, simply calling the texture incomplete in this case. But I don't think we really care. Fixes es3conform's sgis_texture_lod_basic_completeness test. Signed-off-by: Kenneth Graunke <[email protected]> Reviewed-by: Ian Romanick <[email protected]>
Diffstat (limited to 'src/gallium/drivers/r600/r600_llvm.c')
0 files changed, 0 insertions, 0 deletions