[Mesa-dev] [Bug 109258] Weston drm-backend.so seems to fail with Mesa master and LIBGL_ALWAYS_SOFTWARE=1

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Jan 22 10:37:18 UTC 2019


https://bugs.freedesktop.org/show_bug.cgi?id=109258

Eric Engestrom <fdo-bugs at engestrom.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |NOTABUG

--- Comment #6 from Eric Engestrom <fdo-bugs at engestrom.ch> ---
(In reply to n3rdopolis from comment #5)
> Created attachment 143147 [details] [review]
> Reverse 47273d7312cb5b5b6b0b9faa814d574bbbce1c01
> 
> Weston and Gnome shell work with LIBGL_ALWAYS_SOFTWARE with this patch, but
> all I did was revert commit 47273d7312cb5b5b6b0b9faa814d574bbbce1c01 and
> then changed up the conflicts.

This revert makes Mesa ignore LIBGL_ALWAYS_SOFTWARE for the drm (and android)
platforms.
This is making it "work" by not doing what the user asked for, which is not
what we want.

DRM does not have a software path yet, hence the
    /* Not supported yet */
    if (disp->Options.ForceSoftware)
       return EGL_FALSE;
in dri2_initialize_drm()

If a software DRM path is needed, then patches to implement it are welcome :)
I have to admit for rendering I'm not sure what needs to be done there, but for
display if you don't have a DRM driver you can use VKMS.

I'm closing this as NOTABUG, as EGL is working as intended.

If a wayland compositor want to discard the user's instructions and use the
hardware when given LIBGL_ALWAYS_SOFTWARE, it needs to override the env var
(set to `0` or simply unset) before calling eglInitialize().

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20190122/656e6f46/attachment.html>


More information about the mesa-dev mailing list