[OE-core] [PATCH 1/2] piglit: move to meta-oe

Alexander Kanavin alex.kanavin at gmail.com
Sat Feb 29 13:42:23 UTC 2020


On Sat 29. Feb 2020 at 14.14, Richard Purdie <
richard.purdie at linuxfoundation.org> wrote:

> On Sat, 2020-02-29 at 14:11 +0100, Alexander Kanavin wrote:
> > On Sat 29. Feb 2020 at 11.40, Richard Purdie <
> > richard.purdie at 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.


Right, I can put Piglit on top of virgl and see how well that works. It
would be good to enable virgl ‘out of the box’ at some point, I’ve been
proposing that for a while :)

Alex

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20200229/77e2dd8c/attachment.html>


More information about the Openembedded-core mailing list