<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 11, 2017 at 10:30 AM, Carlos Rafael Giani <span dir="ltr"><<a href="mailto:dv@pseudoterminal.org" target="_blank">dv@pseudoterminal.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 2017-04-11 10:26, Alexander Kanavin wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 04/11/2017 10:54 AM, Carlos Rafael Giani wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This is a useful tool to test KMS and GBM-based EGL & OpenGL ES drawing<br>
</blockquote>
<br>
Sorry, but the bar for adding recipes to oe-core is higher than a single all-purpose word 'useful'. Useful to whom? What does the tool do? Is it essential for making an embedded system? You really should write a (much) longer commit message, for a start.<br>
<br>
Alex<br>
<br>
</blockquote>
<br></span>
Well it is sort of an equivalent of glxgears for checking whether or not GBM-based rendering actually works. We have piglit for testing, eglinfo for getting information about the EGL & GLES support, and kmscube also adds a visual output to see that rendering actually behaves nicely.</blockquote></div><br>I am also using kmscube to test/debug mesa on our boards. i am also in favor of having the recipe in oe-core, for the reason stated above.</div><div class="gmail_extra">nico</div><div class="gmail_extra"><br></div></div>