summaryrefslogtreecommitdiffstats
path: root/src/loader
diff options
context:
space:
mode:
authorNeil Roberts <[email protected]>2015-02-26 12:53:50 +0000
committerEmil Velikov <[email protected]>2015-03-11 18:11:40 +0000
commit614e7ebdad0ea1e0f14773db195cfcb75f74558d (patch)
treebfa64071bd39f9c43261ce6edf6b3c426a7728cd /src/loader
parent7f32fa0dcb7dcdc9cb28521c26ec93e48c198bfa (diff)
meta: Allow GL_UN/PACK_IMAGE_HEIGHT in _mesa_meta_pbo_Get/TexSubImage
Now that a layered source PBO is interpreted as a single tall 2D image it's quite easy to accept the image height packing option by just creating an image that is tall enough to include the image padding. I'm not sure whether the image height property should affect 1D_ARRAY textures. My intuition and interpretation of the GL spec (which is a bit vague) would be that it shouldn't. However the software fallback path in Mesa uses the property for packing but not for unpacking. The binary NVidia driver uses it for both. This patch doesn't use it for either case so it is different from the software fallback. There is some discussion about this here: http://lists.freedesktop.org/archives/mesa-dev/2015-February/077925.html This is tested by the texsubimage Piglit test with the array and pbo arguments. Previously this test was skipping this code path because it always sets the image height. I've also tested it by modifying the getteximage-targets test. It wasn't using this code path before because it was using the default texture object so this code couldn't successfully create a frame buffer. I also modified it to add some image padding with the image height in the PBO. Reviewed-by: Jason Ekstrand <[email protected]> Cc: "10.5" <[email protected]> (cherry picked from commit a08bff1e98b8e630f8bdf341af1491cd99e7d104)
Diffstat (limited to 'src/loader')
0 files changed, 0 insertions, 0 deletions