It's actually a nice optimization opportunity. Some hardware might stop rendering immediately after the first sample passes the depth test and all following draw operations can then be safely ignored, provided there are no writes to any buffer. Particularly software rasterizers might benefit from this.<br>
<br>The R300 TODO is just a wishlist of things the hardware/driver could do.<br><br>Marek<br><br><div class="gmail_quote">On Sat, Sep 11, 2010 at 10:48 PM, Dave Airlie <span dir="ltr"><<a href="mailto:airlied@gmail.com">airlied@gmail.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;">Just noticed this on a list of things for r300 todo, seems kinda<br>
pointless but what do I know.<br>
<br>
I wonder if there is hw that can do OQ2 and can't do OQ, for which it<br>
might make sense.<br>
<font color="#888888"><br>
Dave.<br>
</font><br>_______________________________________________<br>
mesa-dev mailing list<br>
<a href="mailto:mesa-dev@lists.freedesktop.org">mesa-dev@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/mesa-dev" target="_blank">http://lists.freedesktop.org/mailman/listinfo/mesa-dev</a><br>
<br></blockquote></div><br>