platforms/drm: explicit modifiers
IN_FORMATS contains information about which buffer formats can be scanned out with a given drm plane. Using these plane-specific format+modifier combinations as well as explicit modifiers in general can yield bandwidth and performance improvements, especially in multi-gpu systems.
-
Developer
@zamundaaa - this commit causes my display port monitor to look like this.
Interestingly when I screenshot it looks perfectly normal.
Thoughts?
-
Author Developer
What happens if you set the environment variable
KWIN_DRM_NO_MODIFIERS
to 1 for KWin? -
Developer
I tried setting that and it makes no difference.
-
Author Developer
Hmm, then nothing should've changed with this commit. What's the output of
drm_info
?Also make sure you have d6de38c1 / the latest git master.
-
Developer
When i'm running latest master i suffer from the black screen bug that came about in commit 1be65e818c8759c12dfd7f731f142ef067b4c050
-
Developer
-
Author Developer
Hmm. The screenshot being normal means that the buffer on the Intel GPU is fine, something just goes wrong when copying it over.
drm_info
says we're usingXRGB8888
like usual though... And we're always using the same format on all GPUs atm.Is the
drm_info
output with this commit, or from an earlier revision? Having both would be good to compare them. -
Developer
My Bad from another revision. I'll make some for other revisions then :)
this revision - 26dff99f drm_info-26dff99f7827be3dc52f13b2eddaabcd82e0671a.txt
-
Developer
last working commit - 19cc2210 - drm_info-19cc22102c834aeadc9e1b68f32b7514aefaa769.txt
-
Author Developer
Aha -
XRGB2101010
is the actual format form the current revision. That explains everything... With !1348 (merged) everything should work again then :) -
Developer
1be65e81 - black external monitor bug - drm_info-1be65e818c8759c12dfd7f731f142ef067b4c050.txt