New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mesa-kms fails to initialise on Cosmic #435
Comments
Oh, ho! It seems the problem is that Mesa now supports |
So what we probably should do here is what Weston does - rather than ask for a EGLConfig with some bits set and hope that it'll match our GBM format, do a more thorough config selection and explicitly match the GBM format with the visual_id, guaranteeing we get either no matching config or a config that actually matches the GBM format we're using… |
…format. eglChooseConfig() will select the EGLConfig with *greatest* EGL_{RED,GREEN,BLUE}_SIZE greater than or equal to the size we request. Since Mesa now supports rendering to XRGB2101010, this will now pick a 10-bit format - obviously incompatible with the XRGB8888 gbm_bo we've allocated, resulting in a EGL_BAD_MATCH error. Instead, iterate over *all* configs which match our requirements and then choose the first one which has a GBM_FORMAT_XRGB8888 pixel format - this information is available from the EGL_NATIVE_VISUAL_ID field. Fixes #435.
462: Mir release 0.32.1 r=AlanGriffiths a=Saviq ### Enhancements: - [libmiral] Launcher for internal Wayland clients. (#410) - [miral-shell] Reinstate the "spinner" when starting miral-shell (re-implementing it in Wayland) ### Bugs fixed: - [mesa-kms] Select EGLConfig matching our GBM format. (#435) - [Wayland] Don't send output events that are not supported in the agreed protocol version. (#389) - [Wayland] Ensure resize configuration events are not superseded. (#449) Co-authored-by: Alan Griffiths <alan@octopull.co.uk>
The mesa-kms platform fails to initialise on 18.10 for me. The relevant error is:
The text was updated successfully, but these errors were encountered: