Software rendering with Mesa and Wayland 1.0

[Sannu K]

On Thu, Oct 25, 2012 at 5:57 PM, nerdopolis
<bluescreen_avenger at verizon.net> wrote:
> Hi.
>
>
>
> I am trying to get the fallback software rendering working for Weston
>
>
>
> It seems now I am getting this output when I export, EGL_LOG_LEVEL=debug
>
>
>
> libEGL debug: Native platform type: wayland (autodetected)
>
> libEGL debug: EGL search path is /opt/lib/i386-linux-gnu/egl
>
> libEGL debug: added /opt/lib/i386-linux-gnu/egl/egl_gallium.so to module
> array
>
> libEGL debug: added egl_dri2 to module array
>
> libEGL debug: added egl_glx to module array
>
> libEGL debug: dlopen(/opt/lib/i386-linux-gnu/egl/egl_gallium.so)
>
> libEGL info: use wayland for display 0x9b084f8
>
> libEGL debug: EGL user error 0x3001 (EGL_NOT_INITIALIZED) in
> eglInitialize(failed to initialize screen)
>
>
>
> libEGL info: use wayland for display 0x9b084f8
>
> libEGL info: use software fallback
>
> libEGL debug: EGL user error 0x3001 (EGL_NOT_INITIALIZED) in
> eglInitialize(failed to initialize screen)
>
>
>
> libEGL debug: EGL user error 0x3001 (EGL_NOT_INITIALIZED) in eglInitialize
>
>
>
> failed to initialize display
>
> failed to create display: No such file or directory
>
>
>
>
>
>
>
> I used to use an older commit, in order to get qtbase to build, as it used
> to fail with the "the opengles 2 test failed' or something of that nature,
> so I tried to use that older commit, and attempt to separate and apply the 3
> Wayland 1.0 patches against it. The patches applied, mesa built, however I
> got the same EGL errors as above.
>
>
>
> Now if I can also recall, by using master, I don't think qtbase was failing
> with opengles 2 test failed anymore.
>
>
>
> I think that something about the new Wayland patches in Mesa are preventing
> it from allowing software fallback with weston.
>
>
>
> Thanks.
>
>
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/wayland-devel
>


I guess there is some problem with mesa 9.0 and wayland 1.0. Is it
related to that? I am not a wayland developer and I am not much aware
of technical things in wayland so this may not be correct. Just a
guess.

Regards,
Sannu K