From: Nicolas Dechesne <nicolas.dechesne@linaro.org>
To: Carlos Rafael Giani <dv@pseudoterminal.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] kmscube: add recipe
Date: Tue, 11 Apr 2017 18:19:43 +0200 [thread overview]
Message-ID: <CAP71WjzJ63peDwzhuLZ7D3GWnk7tc6BUS+XKk7C9ZcWY+knXPg@mail.gmail.com> (raw)
In-Reply-To: <77e0f2a1-520d-5a0d-b1c0-d231622cfe79@pseudoterminal.org>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On Tue, Apr 11, 2017 at 10:30 AM, Carlos Rafael Giani <dv@pseudoterminal.org
> wrote:
> On 2017-04-11 10:26, Alexander Kanavin wrote:
>
>> On 04/11/2017 10:54 AM, Carlos Rafael Giani wrote:
>>
>>> This is a useful tool to test KMS and GBM-based EGL & OpenGL ES drawing
>>>
>>
>> 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.
>>
>> Alex
>>
>>
> 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.
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.
nico
[-- Attachment #2: Type: text/html, Size: 1629 bytes --]
next prev parent reply other threads:[~2017-04-11 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 7:54 [PATCH] kmscube: add recipe Carlos Rafael Giani
2017-04-11 8:26 ` Alexander Kanavin
2017-04-11 8:30 ` Carlos Rafael Giani
2017-04-11 16:19 ` Nicolas Dechesne [this message]
2017-04-12 12:14 ` [PATCH v2] " Carlos Rafael Giani
2017-04-12 17:19 ` Alexander Kanavin
2017-05-10 16:06 ` Nicolas Dechesne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP71WjzJ63peDwzhuLZ7D3GWnk7tc6BUS+XKk7C9ZcWY+knXPg@mail.gmail.com \
--to=nicolas.dechesne@linaro.org \
--cc=dv@pseudoterminal.org \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.