dddddd has quit [Read error: Connection reset by peer]
chewitt has quit [Read error: Connection reset by peer]
buzzmarshall has quit [Quit: Leaving]
megi has quit [Ping timeout: 265 seconds]
Barada has joined #lima
Barada has quit [Client Quit]
Barada has joined #lima
Barada has quit [Quit: Barada]
<anarsoul>
MoeIcenowy: you should probably use single reload field and turn it into flags
<anarsoul>
(similar to .resolve)
<anarsoul>
beside that I'm not sure why it regresses, you'll need to debug it
<anarsoul>
MoeIcenowy: oh, I think that "resolve" should also affect "reload" field, since we may skip writing depth/stencil if upper layer calls invalidate_resource() for it
<anarsoul>
so basically we can't reload depth/stencil if it was invalidated
<anarsoul>
same is true for cbuf
megi has joined #lima
_whitelogger has joined #lima
Barada has joined #lima
Barada has quit [Client Quit]
buzzmarshall has joined #lima
warpme_ has joined #lima
buzzmarshall has quit [Quit: Leaving]
buzzmarshall has joined #lima
<anarsoul|c>
MoeIcenowy: likely you need different format for depth16 for reload
warpme_ has quit [Quit: Connection closed for inactivity]
<Viciouss>
hey, currently trying to get lima running on my galaxy note 10.1 tablet. I have a mainline kernel 5.4.17, activated DRM with exynos and lima support then I packaged the kernel into a buildroot image with libdrm (only build with exynos, there is nothing for lima?) and mesa. after starting kmscube the mesa loader tries to use exynos then swrast but not lima, what am I missing?
<anarsoul>
lima is render-only driver, so you need to enable kmsro in mesa which will bind it with your display driver (exynos in your case)
<Viciouss>
that was an easy fix, thank you!
<anarsoul>
np
<anarsoul>
I'd also suggest upgrading to 5.5 and using mesa-20.0-rc1 (or git master)