From: Gary Thomas <gary@mlbassoc.com>
To: meta-freescale@yoctoproject.org
Subject: Re: [meta-fsl-arm] chrome with Vivante GPU on i.MX6
Date: Mon, 31 Mar 2014 16:18:50 -0600 [thread overview]
Message-ID: <5339E9CA.2090606@mlbassoc.com> (raw)
In-Reply-To: <5334074E.5050304@mlbassoc.com>
On 2014-03-27 05:11, Gary Thomas wrote:
> I now have X11 running with the Vivante GPU on my i.MX6solo.
> Or so I thought - now I'm not so sure :-(
>
> The X11 server happy reports that it is using the Vivante libraries,
> but I think there are problems. In particular, I see this message
> in the log (complete log attached):
> [ 53044.383] (EE) AIGLX error: vivante exports no extensions (/usr/lib/dri/vivante_dri.so: undefined symbol: __driDriverExtensions)
> [ 53044.383] (EE) AIGLX: reverting to software rendering
>
> Then there are these messages which don't make much sense:
> [ 53044.493] (II) GLX: Initialized DRISWRAST GL provider for screen 0
> [ 53044.495] (II) VIVANTE(0): Setting screen physical size to 211 x 127
> (my physical screen is 800x480)
>
> Finally, when I run Google chrome, I get a slew of EGL related errors:
> [2136:2136:0327/105115:ERROR:gl_surface_glx.cc(742)] glXChooseFBConfig failed.
> [2136:2136:0327/105115:ERROR:gpu_info_collector.cc(27)] gfx::GLContext::CreateOffscreenGLSurface failed
> [2113:2131:0327/105117:ERROR:browser_process_resource_provider.cc(52)] Not implemented reached in task_manager::BrowserProcessResource::BrowserProcessResource()
> [ 1] libGAL: Performing a software resolve!
> [2136:2136:0327/105117:ERROR:buffer_manager.cc(313)] [.Compositor-0x3b7c34f8]GL ERROR :GL_INVALID_ENUM : glBufferData: <- error from previous GL command
> [2203:2203:0327/105117:ERROR:gl_surface_glx.cc(742)] glXChooseFBConfig failed.
> [2203:2203:0327/105117:ERROR:gpu_info_collector.cc(27)] gfx::GLContext::CreateOffscreenGLSurface failed
> [ 1] libGAL: Performing a software resolve!
> [2203:2203:0327/105117:ERROR:buffer_manager.cc(313)] [.Compositor-0x39e5a998]GL ERROR :GL_INVALID_ENUM : glBufferData: <- error from previous GL command
> [2214:2214:0327/105117:ERROR:gl_surface_glx.cc(742)] glXChooseFBConfig failed.
> [2214:2214:0327/105117:ERROR:gpu_info_collector.cc(27)] gfx::GLContext::CreateOffscreenGLSurface failed
> [ 1] libGAL: Performing a software resolve!
> [2214:2214:0327/105118:ERROR:buffer_manager.cc(313)] [.Compositor-0x3b835a30]GL ERROR :GL_INVALID_ENUM : glBufferData: <- error from previous GL command
>
> and the chrome://gpu/ page indicates that hardware acceleration
> is *not* available.
>
> None of these errors are particular to my i.MX6solo platform.
> I get the same indications when I run on my i.MX6Q SabreLite
> using the "out of the box" build for Nitrogen6x.
>
> What am I missing? How can I tell if the Vivante GPU is being
> used? If not, what need I do to get it going?
>
> Thanks for any ideas/pointers
What about this? IMO, it's truly broken.
Where do I file a bug report for meta-fsl-arm??
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-03-31 22:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 11:11 [meta-fsl-arm] chrome with Vivante GPU on i.MX6 Gary Thomas
2014-03-31 22:18 ` Gary Thomas [this message]
2014-03-31 22:25 ` Otavio Salvador
2014-03-31 23:27 ` Gary Thomas
2014-03-31 23:49 ` Otavio Salvador
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=5339E9CA.2090606@mlbassoc.com \
--to=gary@mlbassoc.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.