kaspter has quit [Remote host closed the connection]
kaspter has joined #lima
adjtm has joined #lima
ric96 has quit [Ping timeout: 264 seconds]
ric96 has joined #lima
dddddd has quit [Remote host closed the connection]
maccraft123 has joined #lima
kaspter has quit [Remote host closed the connection]
kaspter has joined #lima
maccraft123 has quit [Quit: WeeChat 2.6]
maccraft123 has joined #lima
gcl has quit [Remote host closed the connection]
dddddd has joined #lima
maccraft123 has quit [Quit: WeeChat 2.6]
anarsoul has quit [Read error: Connection reset by peer]
anarsoul|2 has joined #lima
enty is now known as ente
<piggz>
argh, i built mesa with gcc 8.3 "on-device" and it still fails with the white screen!!!
hellsenberg is now known as hell__
maccraft123 has joined #lima
anarsoul|2 is now known as anarsoul
<anarsoul>
piggz: guess you need to debug it
<piggz>
anarsoul: :( well, last time a bisected, i got told it was unlikely to be a problem ... no idea how to debug further
<anarsoul>
piggz: compare it with working setup?
<anarsoul>
also check that BO that lima renders into is the same as display driver uses for scanout
<piggz>
what does that mean?
<anarsoul>
lima is render-only driver, it doesn't know anything about display
<anarsoul>
so you have to have some display driver, in your case it's sun4i
<anarsoul>
kmsro in mesa binds sun4i and lima together since that's what userspace expects
<piggz>
i think i debugged one time, rendering to a png, and the png was empty
<piggz>
remember, 19.1 works
<anarsoul>
piggz: well, bisecting showed nothing irrelevant, so I'd bet that memory layout changed and it somehow impacted you
<anarsoul>
the change that you found in bisecting is a change to shader compiler(s) and it's no-op for kmscube shaders since it has no integers
<anarsoul>
anyway, get yourself identical 64-bit userspace and compare what it does to what your 32-bit userspace does
maccraft123 has quit [Quit: WeeChat 2.6]
<piggz>
anarsoul: the the problem .... sailfish doesnt have a 64bit userspace...
<piggz>
nemo does though, and it is similar ... there is a nemo dev currently rebuilding the whole rootfs and mes to see if it works
maccraft123 has joined #lima
<anarsoul>
piggz: well, archlinuxarm doesn't support multiarch, so I literally have no environment to debug the issue for you
<anarsoul>
however enunes tried that on fedora and lima works fine there with 64-bit kernel and 32-bit userspace
<piggz>
anarsoul: hmmm
<piggz>
what kernel is needed?
<anarsoul>
lima driver hasn't really changed since 5.2, but I'd recommend at least 5.3
<anarsoul>
it contains a fix that's necessary for BO cache to work correctly
<piggz>
im on 5.3.0-rc4
<anarsoul>
piggz: try newest mesa, and run your kmscube with LIMA_DEBUG=all, then share output and lima.out (it now has decoder for cmd stream so it's easier to analyze)
<piggz>
mesa is current master
warpme_ has quit [Quit: Connection closed for inactivity]
maccraft123 has quit [Quit: WeeChat 2.6]
Net147 has quit [Quit: Quit]
Net147 has joined #lima
Net147 has quit [Client Quit]
Net147 has joined #lima
Net147 has quit [Quit: Quit]
Net147 has joined #lima
Net147 has quit [Client Quit]
Net147 has joined #lima
Net147 has quit [Quit: Quit]
Net147 has joined #lima
Net147 has quit [Remote host closed the connection]