From: John Weber <rjohnweber@gmail.com>
To: meta-freescale@yoctoproject.org
Subject: Re: glmark2 errors
Date: Tue, 29 Apr 2014 08:41:58 -0500 [thread overview]
Message-ID: <535FAC26.9030209@gmail.com> (raw)
In-Reply-To: <535F4D18.9060007@pseudoterminal.org>
Hi Carlos and Diego -
On 4/29/14, 1:56 AM, Carlos Rafael Giani wrote:
> On 2014-04-29 08:51, Diego wrote:
>> John Weber wrote:
>>> The GL benchmark glmark2 throws the following warnings reapeatedly:
>>>
>>> ** GLX does not support GLX_EXT_swap_control or GLX_MESA_swap_control!
>>> ** Failed to set swap interval. Results may be bounded above by refresh
>>> rate.
>>>
>>> It will eventually segfault during the 'shadow' benchmark.
>> Hi John,
>>
>> as I previously reported plain OpenGL is not officially supported by Vivante
>> drivers. While hardware supports OpenGL, binary drivers support it only
>> unofficially, but there are no headers or explicitly documented support; and I
>> think situation will continue to be that way.
>>
>> See also:
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=5098
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=6083#c1
>>
>> Bests,
>> Diego
>>
>
> That makes sense. Regular OpenGL just isn't very well suited for embedded
> GPUs. Thats why OpenGL ES exists.
> Also, IIRC the Vivante libGL binaries just emulate it by using OpenGL ES calls
> internally.
>
> Carlos
No problem, and thanks for the information. Glmark2 was fully functional (no
warnings) in older versions of the FSL BSP. I run this benchmark as a way of
checking the health of a given image build, so when I see warnings like this I
wonder if there has been a regression.
prev parent reply other threads:[~2014-04-29 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 18:40 glmark2 errors John Weber
2014-04-28 18:42 ` John Weber
2014-04-29 13:41 ` Prabhu S
2014-04-29 6:51 ` Diego
2014-04-29 6:56 ` Carlos Rafael Giani
2014-04-29 13:41 ` John Weber [this message]
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=535FAC26.9030209@gmail.com \
--to=rjohnweber@gmail.com \
--cc=meta-freescale@yoctoproject.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.