[wpe-webkit] [EXT] Re: imx6 backend "no default display support on wayland"

Seuntjens, Jonas jonas.seuntjens at doverfs.com
Wed Jun 13 04:24:22 PDT 2018

Hi Carlos 

Thanks for the quick reply!
I am very sure that I am using wpebackend-rdk/imx6 backend.  I did a recent rebuild with this change.
Tried again by opening an SSH session and setting the WPE_INIT environment variables. Still the same result.
Following configuration is in my local.conf file:

IMAGE_INSTALL_append = " wpewebkit cog qtbase-examples qtmultimedia-examples"
CORE_IMAGE_EXTRA_INSTALL = "cryptodev-module"
PREFERRED_PROVIDER_virtual/wpebackend = "wpebackend-rdk"
DISTRO_FEATURES_append = " opengl wayland"
PACKAGECONFIG_pn-wpebackend-rdk = "imx6"
PACKAGECONFIG_append_pn-cairo=" glesv2"
PACKAGECONFIG_APPEND_pn-wpewebkit=" 2dcanvas"
IMAGE_INSTALL_append = " gstreamer1.0-plugins-imx gstreamer1.0-plugins-imx-meta"

Maybe something else which could have some effect: I am using Vivante driver version: 6.2.2

Kind regards

-----Original Message-----
From: webkit-wpe [mailto:webkit-wpe-bounces at lists.webkit.org] On Behalf Of Carlos Alberto Lopez Perez
Sent: Wednesday, 13 June 2018 12:22
To: webkit-wpe at lists.webkit.org
Subject: [EXT] Re: [wpe-webkit] imx6 backend "no default display support on wayland"

[External: Sender is outside the Organization]

On 13/06/18 11:07, Seuntjens, Jonas wrote:
> Hi
> I am trying to get webkit working on an i.mx6 Quad following the very clear guidelines on:
> https://github.com/Igalia/meta-webkit/wiki/WPE
> https://github.com/Igalia/meta-webkit/wiki/i.MX6
> I am able to do a complete build and have a working cog browser with wayland backend.
> However it seems that the performance is not completely what we expected. That is why we tried to build wpe-webkit with the i.mx6 backend which would render the full-screen directly to the framebuffers using the Vivante driver.

The usage of one backend over other may impact graphic performance, but it has no impact at all on other parts of the performance of a webapp (like JavaScript performance).

> This build completed but when I try to start the cog browser I get following error message:
> Initialization of linux input system succeeded.
> EGL: Warning: No default display support on wayland
> PlatformDisplayWPE: could not create the EGL display: EGL_SUCCESS
> ** (WPEWebProcess:1056): CRITITCAL **: 
> gst_gl_display_egl_new_with_egl_display" assertion 'display != NULL' 
> failed Cannot create EGL sharing context: invalid display (last error: 
> Build is using  Rocko Release 01 - 4.9.11.
> We also tried to run the cog browser directly from the command line (no wayland active) but we still have the same error.
> Do you have any idea what could be wrong here?

It looks a bit strange that it complains with a "no default display support on wayland" error when the wpebackend-rdk/imx6 backend doesn't use wayland at all.

I tested it on a Wandboard QP with Yocto rocko and it worked fine for me.

Can you double-check you are using wpebackend-rdk/imx6 backend ?
That one is selected by setting on local.conf:

PREFERRED_PROVIDER_virtual/wpebackend = "wpebackend-rdk"
PACKAGECONFIG_pn-wpebackend-rdk = "imx6"

And rebuilding the image.

Then when the image starts, weston has to be stopped and cog launched via a text terminal (or via SSH). To select the window size export the env variables before launching cog like:


More information about the webkit-wpe mailing list