<div>On Sat 29. Feb 2020 at 11.40, Richard Purdie <<a href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>> wrote:<br></div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sat, 2020-02-29 at 11:14 +0100, Alexander Kanavin wrote:<br>
> This recipe is build-heavy, yet is not part of any images and isn't<br>
> runtime tesed as<br>
> part of oe-core. There's no evidence of anyone using it, as all<br>
> commits are revision updates. It also pulls in NumPy, which is also<br>
> a significant support item, and wouldn't otherwise be part of core.<br>
<br>
I'm not sure about this. The intent was to use piglit as a way of<br>
improving our graphics testing, particularly allowing it to be<br>
automated.<br>
<br>
Whilst we've had to focus on getting the basics right, I'm not sure<br>
that objective isn't still a worthy goal over time?</blockquote><div dir="auto"><br></div><div dir="auto">Piglit is meant for testing and validating OpenGL drivers for real hardware. While we can put it on top of software Mesa driver or virgl, I am not sure there is much value in that? Software rendering might even be too slow to run in practice.</div><div dir="auto"><br></div><div dir="auto">Alex</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></blockquote></div></div>