<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [IVB/HSW] ogl-samples: gl-320-fbo-depth-multisample render error (broken line at "horizon")" href="https://bugs.freedesktop.org/show_bug.cgi?id=76396#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [IVB/HSW] ogl-samples: gl-320-fbo-depth-multisample render error (broken line at "horizon")" href="https://bugs.freedesktop.org/show_bug.cgi?id=76396">bug 76396</a> from <a class="email" href="mailto:apinheiro@igalia.com" title="Alejandro Piñeiro (freenode IRC: apinheiro) <apinheiro@igalia.com>"> Alejandro Piñeiro (freenode IRC: apinheiro)</a> <pre>Ok, so after some time checking this, this is what I found. I was been looking to the public PRM and the code, and I didn't find anything wrong. So then I moved to see what piglit was reporting on this case. Although all the hiz tests are properly passing on HSW, the test for this case (depth multisample) on tests/spec/arb_texture_multisample is failing. If someone are interested to run it: ./bin/arb_texture_multisample-sample-depth -auto -fbo Worth to note that is the only test of that spec failing on HSW. Taking a look to the commit message of that test: commit ecf0faa4d71c0e117569c6e0edfe57b2f8bbabf7 Author: Chris Forbes <<a href="mailto:chrisf@ijw.co.nz">chrisf@ijw.co.nz</a>> Date: Sat Feb 8 16:06:41 2014 +1300 arb_texture_multisample: add test for sampling from depth This demonstrates an i965 bug, where hiz resolves for MSAA surfaces don't work (on BLORP platforms). Signed-off-by: Chris Forbes <<a href="mailto:chrisf@ijw.co.nz">chrisf@ijw.co.nz</a>> Reviewed-by: Glenn Kennard <<a href="mailto:glenn.kennard@gmail.com">glenn.kennard@gmail.com</a>> The commit message seems to suggest that this is a hw limitation. In any case it is not 100% explicit (other option would be that it is mentioning a bug on the driver). Will try to ask on IRC about that.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>