On Sat, 2020-02-29 at 14:11 +0100, Alexander Kanavin wrote: > On Sat 29. Feb 2020 at 11.40, Richard Purdie < > richard.pur...@linuxfoundation.org> wrote: > > On Sat, 2020-02-29 at 11:14 +0100, Alexander Kanavin wrote: > > > This recipe is build-heavy, yet is not part of any images and > > isn't > > > runtime tesed as > > > part of oe-core. There's no evidence of anyone using it, as all > > > commits are revision updates. It also pulls in NumPy, which is > > also > > > a significant support item, and wouldn't otherwise be part of > > core. > > > > I'm not sure about this. The intent was to use piglit as a way of > > improving our graphics testing, particularly allowing it to be > > automated. > > > > Whilst we've had to focus on getting the basics right, I'm not sure > > that objective isn't still a worthy goal over time? > > 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.
OE-Core is meant to be usable for validating BSPs amongst other things though. Testing virgl does prove the graphics stack is working too from a software perspective so does have some value. Cheers, Richard -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
