<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Don't print: "Note: Buggy applications may crash, if they do please report to vendor"" href="https://bugs.freedesktop.org/show_bug.cgi?id=99715#c18">Comment # 18</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Don't print: "Note: Buggy applications may crash, if they do please report to vendor"" href="https://bugs.freedesktop.org/show_bug.cgi?id=99715">bug 99715</a> from <a class="email" href="mailto:jason@jlekstrand.net" title="Jason Ekstrand <jason@jlekstrand.net>"> Jason Ekstrand</a> <pre>(In reply to programmerjake from <a href="show_bug.cgi?id=99715#c16">comment #16</a>) > Created <a href="attachment.cgi?id=129733" name="attach_129733" title="removed dri2 checking">attachment 129733</a> <a href="attachment.cgi?id=129733&action=edit" title="removed dri2 checking">[details]</a> <a href='page.cgi?id=splinter.html&bug=99715&attachment=129733'>[review]</a> [review] > removed dri2 checking Have you tested the patch against both NVIDIA and AMD proprietary X drivers? (In reply to programmerjake from <a href="show_bug.cgi?id=99715#c14">comment #14</a>) > Mostly unrelated, I'd like to be the one to end up submitting the patch for > this bug as I'm trying to qualify for Google summer of code to implement > something like llvmpipe for Vulkan. I don't really care that much one way or the other. I have plenty of patches in mesa with my name on them. If you're willing to do the legwork to test it thoroughly, you're welcome to it. That said, if you really want open-source project cred for your GSOC application, my recommendation would be to run piglit or dEQP against llvmpipe and try and fix some rendering errors. That would both demonstrate a bit more applicable knowledge and get you some experience in llvmpipe which will give you a leg up on the project. Just a thought. :-)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>