12:27 <cwabbott> anarsoul: I was rebasing my series and trying to build it, seems building just lima is broken atm due to sharing the tiling stuff

12:43 <enunes> cwabbott: you mean to not build kmsro or panfrost? I build only lima and kmsro (no panfrost) and it works for me

12:44 <cwabbott> enunes: sorry for the noise, it was my offline compiler thing that was broken (I didn't look closely enough at the error message)

13:04 <bshah> Hi there, when running KDE Plasma with lima, we get : "gpir: if nir_cf_node not support" quite a lot. We're also seeing weird issue where windows which aren't supposed to be transperent are fully transperent.

13:05 <bshah> wondering, if people here have any idea what might be missing?

13:07 <enunes> bshah: it means that the vertex shader compiler still doesn't support control flow, it is a very large missing feature. for now it means that the driver still doesn't support what you want to run

13:07 <enunes> see https://gitlab.freedesktop.org/lima/web/wikis/home

13:10 <bshah> okay, and is windows being transperent seperate bug? or probably is same bug?

13:12 <enunes> no idea, but if you hit shader compilation errors like shaders requiring nir_cf_node, applications will surely misbehave

13:20 <bshah> the whole thing is quite weird... window with complex svg texture and everything seems to be working fine but window with plain colored rectangle is broken ... qt can work in mysterious way :/

13:25 <enunes> bshah: the driver is in quite early stage for this kind of application, it doesn't surprise me that qt applications don't work. we are not so many and are still working on making a complete shader compiler

13:27 <bshah> Aye, I am aware is early stage of development :D

13:27 <bshah> Thanks for work you're putting into this :)

16:03 <MoeIcenowy> bshah: are you sure you met problem of gpir cf?

16:04 <MoeIcenowy> I think 2D application should meet ppir if cf missing

16:04 <MoeIcenowy> which is what anarsoul trying to do

16:18 <enunes> MoeIcenowy: I have seen the failure with gpir cf too checking a qt application, so I believe it is indeed that

16:20 <anarsoul> I hope cwabbott redesigned gpir compiler considering future addition of cf support :)

16:21 <anarsoul> enunes: I hope Qt doesn't use too complex shaders

16:21 <anarsoul> vertex shader on mali4x0 can have only up to 512 instructions

16:22 <enunes> I captured some but don't have them available now, I think it's some blurring or moving effect or something

16:22 <anarsoul> blurring in vertex shader?

16:23 <enunes> yeah probably not that one, have to look again, but there was a big conditional in the vertex shader too

16:24 <anarsoul> I see

16:51 <bshah> MoeIcenowy: I am kinda not sure that is exact issue, but it is only thing I see in "broken" app log from lima

16:51 <bshah> There's also this warning from qt itself

16:51 <bshah> QSGContext::initialize: depth buffer support missing, expect rendering errors

16:51 <bshah> QSGContext::initialize: stencil buffer support missing, expect rendering errors

16:52 <bshah> Which we disabled by qt specific environment variable still, result was ultmately same.

16:53 <bshah> I was trying this very simple qml file, https://invent.kde.org/snippets/327 (in terms of QML is quite simple, not simple in terms of graphics driver ofcourse :D) which in theory should be red rectangle. but renders white only

16:54 <anarsoul> bshah: you may have better luck with Qt software renderer. I doubt that they care about GLES 2.0 GPUs nowadays

16:54 <bshah> qt software renderer is quite meh :/

16:54 <bshah> for wayland at least :/

16:55 <bshah> (performance wise that is, it provides quite shitty performance)

16:55 <bshah> While even while being "broken" rendering wise, lima performance is quite good actually ^^

16:57 <anarsoul> bshah: yeah, rendering nothing is fast

16:57 <anarsoul> :)

16:57 <bshah> :-P

16:58 <anarsoul> anyway, kde is pretty smooth for me with sw renderer

16:58 <anarsoul> much better than with llvmpipe

16:58 <bshah> on X11 right?

16:58 <anarsoul> yes

16:59 <bshah> in wayland unfortunately kwin compositor is quite meh :/

16:59 <bshah> (using software rendering that is)

16:59 <anarsoul> I don't care about wayland, it's still 2nd class citizen in kde world

16:59 <bshah> well, yes.. but for plasma mobile I care about it only :P

16:59 <anarsoul> yes, they add new features only to wayland compositor, but wayland session is just non-functional

17:08 <bshah> anarsoul: in fact wayland + qt/qml itself is kinda fine already. LuneOS people have got their stuff working with same devkit fine. So I'd assume something is wrong from kwin side or something we are doing extra then LuneOS people ..