#asahi-gpu · 2026-03-08 10:55
chadmedyeah#asahi-gpu · 2026-03-08 10:54
jannaufor the partially occluded case, to keep the user-space code simpler. you can't really argue against valid API use regardlessly of how stupid it looks#asahi-gpu · 2026-03-08 10:51
chadmedkwin does the former when it hides the cursor #asahi-gpu · 2026-03-08 10:50
chadmedwould you then not just drop the fb object/make the plane invisible? why would you drop it to a lower plane and keep rendering it underneath#asahi-gpu · 2026-03-08 10:49
jannauwhy would the cursor be on top most plane?. hiding the cursor over video is common #asahi-gpu · 2026-03-08 10:48
jannaukwin can do what it likes. I meant dcp can reorder the planes/surfaces as it likes if they don't overlap#asahi-gpu · 2026-03-08 10:45
chadmedlike if its picking up an overlay for use with the cursor it should know to keep it at the highest z in most circumstances, but it just doesnt#asahi-gpu · 2026-03-08 10:44
chadmedi am reasonably sure that some of this is kwin being pathological wrt overlays given that it is very new code and still WIP#asahi-gpu · 2026-03-08 10:44
chadmedthis is the problem#asahi-gpu · 2026-03-08 10:43
chadmedtell that to kwin :P #asahi-gpu · 2026-03-08 10:43
jannauif the cursor is not occluded it can be rendered above the overlay#asahi-gpu · 2026-03-08 10:42
jannauwe need explicit tests with igt or my overlay sample app before I'm happy to enable overlays#asahi-gpu · 2026-03-08 10:42
chadmedyes and this also causes issues when the cursor is not occluded#asahi-gpu · 2026-03-08 10:41
jannauif the overlay is opaque we could just not render the cursor when it is hidden but we probably run into the same issues as with display edges if it is partially occluded#asahi-gpu · 2026-03-08 10:38
jannaudcp could reject the commit in atomic_check but if user space intends to render the cursor below the overlay dcp can not revert the order#asahi-gpu · 2026-03-08 10:38
chadmedbecause overlays are supposed to be fungible? #asahi-gpu · 2026-03-08 10:36
jannauif that's a dcp requirement it's incompatible with KMS planes#asahi-gpu · 2026-03-08 10:36
chadmedno i know _this_ is not an x11 issue, the x11 issue was dcp crashing immediately with a plane set to cursor#asahi-gpu · 2026-03-08 10:35
jannauthis is not an x11 issue but doing so would make dcp a broken KMS driver#asahi-gpu · 2026-03-08 10:35
chadmedkwin kept trying to put window surfaces at z=3 and move the cursor down to z=2 for some reason for example#asahi-gpu · 2026-03-08 10:34
chadmedthat seems to be what was breaking a lot of stuff, seems like one of the rules is "the smallest rectangle goes on top" or some variant of that#asahi-gpu · 2026-03-08 10:33
chadmedif we want this to work eventually, we dont have a choice unless we teach every single compositor to never ever ever try to put anything on top of the plane which has the cursor on it#asahi-gpu · 2026-03-08 10:33
jannauare you thinking of adding a cursor plane? I don't think we should do that#asahi-gpu · 2026-03-08 10:32
chadmedwhen i added the cursor plane the first time, xorg would cause dcp to crash immediately#asahi-gpu · 2026-03-08 10:32
jannauthat said I do not see what in dcp could break X11#asahi-gpu · 2026-03-08 10:31
chadmedthis would also break other wayland compositors that dont do sw cursor fallback anyway#asahi-gpu · 2026-03-08 10:31
chadmedyeah#asahi-gpu · 2026-03-08 10:31
jannauI care enough not to break it. "X11 is not supported" was always meant as we do not care about improving the the experience on X11 or catering to requierements only X11 has#asahi-gpu · 2026-03-08 10:26
chaos_princesswe should care enough to not deprecate and remove it in a single cycle#asahi-gpu · 2026-03-08 10:09
chadmeddo we still care somewhat about x11 compat?#asahi-gpu · 2026-03-08 10:07
chadmedhm okay, surface 0 as primary, surface 1 as overlay and surface 3 as _cursor_ works #asahi-gpu · 2026-03-08 09:58
chadmedmight be a leftover from 12.x#asahi-gpu · 2026-03-08 09:58
chadmedyeah ik about the comments/commit message, but ive never actually noticed it being a problem #asahi-gpu · 2026-03-08 09:58
jannauchadmed: not me but marcan, see 312dc146eb0c6cdc9 but that doesn't appear to be an issue anymore#asahi-gpu · 2026-03-08 09:54
chadmedmacos uses it for the desktop/fullscreen stuff#asahi-gpu · 2026-03-08 09:54
chadmedwhat issues did you see with surface 0? i havent noticed anything#asahi-gpu · 2026-03-08 09:52
jannauyes, there some limitations on what surfaces can do. I thought so far that surface 0 was special and had only limted support. We weren't using it because it caused issues w.r.t. to color space handling#asahi-gpu · 2026-03-08 09:46
chadmedswaps with three surfaces in them also seem to work fine like this too #asahi-gpu · 2026-03-08 09:44
chadmedthere must be rules for it or something#asahi-gpu · 2026-03-08 09:44
chadmedso how does macos use surface 2#asahi-gpu · 2026-03-08 09:44
chadmedthen just expose three planes #asahi-gpu · 2026-03-08 09:44
chadmednormalized_zpos == 2 ? normalized_zpos + 1 : normalized_zpos#asahi-gpu · 2026-03-08 09:44
chadmedsurface 2 is just... broken?#asahi-gpu · 2026-03-08 09:44
chadmedhahahah oh my god i "fixed" it#asahi-gpu · 2026-03-08 09:25
jannaudcp could still ignore it because as far as I see it wouldn;t use that value anyway#asahi-gpu · 2026-03-08 09:24
jannauit's currently not wrong but I think we want to align the stride to tile width * blocksize in the modifier documentation. Same for the height#asahi-gpu · 2026-03-08 09:15
oliverjannau: is this fine for you: https://files.narf.zone/60ab0d2640361b88/mesa.patch#asahi-gpu · 2026-03-08 09:07
oliveryes, confirmed, works as expected.#asahi-gpu · 2026-03-08 09:00
oliverjannau: I imagine that your commit would help, yes. #asahi-gpu · 2026-03-08 08:59
chadmedreproducing the behaviour in traces still doesnt work