Looks good, though the OUT_OF_MEMORY check should probably stay in my opinion, as it's a valid GL error that can be expected in this case, isn't it? Texture allocations may still fail in DRM and if that happens, NULL is returned in pipe_screen::resource_create (r300g).<br>
<br>Marek<br><br><div class="gmail_quote">On Wed, Nov 24, 2010 at 7:55 PM, Brian Paul <span dir="ltr"><<a href="mailto:brianp@vmware.com">brianp@vmware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Here's a patch for the new tex3d-maxsize test. The test now uses a proxy texture to find the largest working texture size and uses that to render something.<br>
<br>
Before if we couldn't create a 3D texture of GL_MAX_3D_TEXTURE_SIZE ^ 3 we just gave up.<br><font color="#888888">
<br>
-Brian<br>
<br>
<br>
</font><br>_______________________________________________<br>
Piglit mailing list<br>
<a href="mailto:Piglit@lists.freedesktop.org">Piglit@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/piglit" target="_blank">http://lists.freedesktop.org/mailman/listinfo/piglit</a><br>
<br></blockquote></div><br>