Skip to content
This repository has been archived by the owner on Nov 1, 2021. It is now read-only.

backend/drm: fix GBM format mismatch #1509

Merged
merged 1 commit into from
Jan 29, 2019

Conversation

emersion
Copy link
Member

We create the EGL config with GBM_FORMAT_ARGB8888, but then initialize GBM BOs
with GBM_FORMAT_XRGB8888. This mismatch confuses Mesa.

Instead, we can always use GBM_FORMAT_ARGB8888, and use DRM_FORMAT_XRGB8888
when calling drmModeAddFB2.

Fixes #1438

We create the EGL config with GBM_FORMAT_ARGB8888, but then initialize GBM BOs
with GBM_FORMAT_XRGB8888. This mismatch confuses Mesa.

Instead, we can always use GBM_FORMAT_ARGB8888, and use DRM_FORMAT_XRGB8888
when calling drmModeAddFB2.

Fixes swaywm#1438
Copy link
Member

@ascent12 ascent12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'll see if this actually fixes anything for people before merging this.

@ddevault ddevault merged commit feb1b9b into swaywm:master Jan 29, 2019
@ddevault
Copy link
Contributor

Thanks! Looks like it did fix the issue for that dude.

@emersion emersion deleted the gbm-fmt-mismatch branch January 29, 2019 15:42
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants