[wpe-webkit] EGL_NOT_INITIALIZED on Cog with fdo/swrast/fbdev
Karl Krach
ml at krach.email
Wed Jun 26 08:18:37 PDT 2019
Hello,
I was wrong with my analysis of the initializeEGLDisplay() failure:
>
> 2) Second it's called from
> wpewebkit-2.24.2/Source/WebCore/platform/graphics/PlatformDisplay.cpp
> in initializeEGLDisplay(), uses the EGL_DEFAULT_DISPLAY and fails in
> dri2_initialize_wayland_swrast() with rt=-1 wl_shm=0:
>
The reason is the missing support for the 'EGL_WL_bind_wayland_display'
extension (see Instance::initialize() in ws.cpp) when not using drm
(dri2_initialize_wayland_drm() in platform_wayland.c) but swrast
(dri2_initialize_wayland_swrast) instead. This reason is already
documented in
* "Segmentation fault on Buildroot -branch next / RPi3B+" -
https://github.com/Igalia/cog/issues/90 and
* "WaylandCompositor misusing eglGetProcAddress" -
https://bugs.webkit.org/show_bug.cgi?id=182490#c0
Since I rely on the udlfb kernel module, I cannot use drm.
* Do I have any alternative?
* Is there a webkit version which works without the
'EGL_WL_bind_wayland_display' extension?
* Is there a mesa3d version, which supports
'EGL_WL_bind_wayland_display' for swrast? (e.g. the DRI swrast driver)
BR, Karl
PS: I found an article about an DRM driver for DisplayLink
(https://wiki.archlinux.org/index.php/DisplayLink#USB_2.0_DL-1x5,_DL-1x0_Devices)
- but I don't know if it fulfills our needs... at least it's not working
out of the box ('weston --backend=drm-backend.so --tty=4' fails with 'no
drm device found')
More information about the webkit-wpe
mailing list