ChanServ changed the topic of #lima to: Development channel for open source lima driver for ARM Mali4** GPUs - Kernel has landed in mainline, userspace driver is part of mesa - Logs at https://people.freedesktop.org/~cbrill/dri-log/index.php?channel=lima and https://freenode.irclog.whitequark.org/lima - Contact ARM for binary driver support!
machinehum has quit [Ping timeout: 256 seconds]
yuq825 has joined #lima
machinehum has joined #lima
wiewo has joined #lima
chewitt has quit [Read error: Connection reset by peer]
chewitt has joined #lima
chewitt has quit [Read error: Connection reset by peer]
chewitt has joined #lima
buzzmarshall has quit [Remote host closed the connection]
Elpaulo has joined #lima
ornxka_ has joined #lima
ornxka has quit [*.net *.split]
smaeul has quit [*.net *.split]
abordado has quit [*.net *.split]
Wizzup has quit [*.net *.split]
smaeul has joined #lima
Barada has joined #lima
kaspter has quit [Quit: kaspter]
kaspter has joined #lima
kaspter has quit [Ping timeout: 258 seconds]
kaspter has joined #lima
kaspter has quit [Ping timeout: 264 seconds]
kaspter has joined #lima
dddddd has quit [Ping timeout: 256 seconds]
camus1 has joined #lima
kaspter has quit [Ping timeout: 265 seconds]
camus1 is now known as kaspter
cwabbott has joined #lima
psydread has left #lima [#lima]
psydread has joined #lima
cwabbott has quit [Quit: cwabbott]
cwabbott has joined #lima
psydread has left #lima [#lima]
psydread has joined #lima
psydread has left #lima [#lima]
psydread has joined #lima
z3ntu_ has quit [Quit: killed]
danqo has quit [Quit: killed]
mariogrip has quit [Quit: killed]
paulk-leonov has quit [Ping timeout: 250 seconds]
mariogrip has joined #lima
paulk-leonov has joined #lima
paulk-leonov has quit [Ping timeout: 240 seconds]
paulk-leonov has joined #lima
z3ntu_ has joined #lima
kittehuwu has joined #lima
<kittehuwu> anyone know why pinephone has no FBO support using lima?
cwabbott has quit [Quit: cwabbott]
cwabbott has joined #lima
ornxka_ is now known as ornxka
dddddd has joined #lima
buzzmarshall has joined #lima
tbueno has joined #lima
cwabbott has quit [Quit: cwabbott]
cwabbott has joined #lima
cwabbott has quit [Remote host closed the connection]
cwabbott has joined #lima
Barada has quit [Quit: Barada]
yuq825 has quit [Quit: Leaving.]
<anarsoul> kittehuwu: it supports FBO, probably it doesn't support some format you're using
Wizzup has joined #lima
cwabbott has quit [Quit: cwabbott]
cwabbott has joined #lima
<Putti> So I tried to enable all the regulators, maxed out bus clocks and I still get glitches. Here is a video of the glitches: <http://git.putti.eu/video.AVI>
<Putti> I'm also debugging this with one person on #linux-exynos
<anarsoul> and do you get this pp mmu error in dmesg when glitch happens?
<Putti> no
<Putti> I thin that might have been only after suspend mode
<Putti> but before suspend there is no error messages
<Putti> and that video was taken before suspend mode
<anarsoul> Putti: well, then you need to come up with minimal reproducer of this issue in order for us to take a look. Unfortunately android doesn't have apitrace
<Putti> anarsoul, but this is most likely not lima driver issue?
<anarsoul> Putti: it could be driver issue
<Putti> the glitches looks pretty similar to what I got with software rendering when I had PM_DEVFREQ enabled
<anarsoul> oh, OK
<Putti> https://gitlab.freedesktop.org/drm-hwcomposer/drm-hwcomposer/issues/24 that is the issue we had earlier similar to this
<Putti> then we used llvmpipe
<Putti> and exynos display controller with HW overlay planes
<Putti> here the difference is that the display is not "scanning" when the error happens
<Putti> earlier the image slowly went upwards or downwards direction
<Putti> there is a video in the gitlabl issue too
<anarsoul> looks different to me
<Putti> yes, it is a bit different
<anarsoul> Putti: anyway, if it's a driver issue I'll need minimal reproducer
machinehum has quit [Ping timeout: 265 seconds]
<Putti> anarsoul, I could use some other distro, which one has apitrace?
<anarsoul> sure, any linux distro would do
<Putti> ok, is there any instructions to do this?
<Putti> apitracing I mean
<Putti> ah, okay thanks! I thought it was something specific to lima
cwabbott has quit [Ping timeout: 246 seconds]
cwabbott has joined #lima
machinehum has joined #lima
cwabbott has quit [Quit: cwabbott]
<Putti> does gnome3 run on lima? Trying to decide what would be the best DE to test with and try to get similar glitches
<anarsoul> it does
<anarsoul> Putti: wayland session runs smoother for me than X11
<anarsoul> but both work fine
<Putti> ok
<anarsoul> make sure you're using mesa from git master
<Putti> yeah, it will take me a while to figure out how to install that to debian 10
<anarsoul> build new package?
<Putti> I'm using debootstrap to create rootfs
<Putti> and so then I will have to somehow copy&paste the mesa binaries to that
<Putti> maybe it is just as easy as defining the --prefix in meson
<anarsoul> well, good luck with that
<anarsoul> I use archlinux and I usually build a package if I need to install new mesa system-wide
<Putti> that sounds easy
<anarsoul> because it is :)
<anarsoul> I have PKGBUILD ready, it's just a matter of 'makepkg; pacman -U mesa-xxxx.tar.xz'
<Putti> I just stumbled upon an issue having too old qemu so I cannot create debian 10 rootfs with gnome3 packages before I update my host system to debian 10..
machinehum has quit [Ping timeout: 256 seconds]
cwabbott has joined #lima
machinehum has joined #lima
<Putti> I could also use some pre-made armhf rootfs image with latest mesa master compiled with lima if I can find one
<Putti> Updating my build server seems to take a while.
buzzmarshall has quit [Remote host closed the connection]
<anarsoul> Putti: use archlinuxarm?
<anarsoul> here's PKGBUILD for mesa-git: https://gist.github.com/9f0d82d0e81e8a340db5fb120cbc38c3
<Putti> Thanks! I don't really know how arch linux works, but I might check it out if debian 10 doesn't pan out. I just got the debian 10 rootfs built so will try it first.
buzzmarshall has joined #lima
<Viciouss> if I put my device to sleep and wake it back up, then kmscube won't work anymore, I get those three messages in the kernel log: mmu command 2 timeout, gp error irq state=1800 status=4d, gp task error int_state=0 status=4c. I'm using 5.5 kernel and mesa 20.0.2
<Putti> Viciouss, according to your message on linux-sunxy we have both 4412 soc, My error messages are similar to you after waking up from suspend: http://paste.debian.net/plain/1140444
<Putti> Viciouss, I also get graphics corruption on 4412 (but only in one android application (lineageos setup wizard))
<Viciouss> Putti: I had AOSP Android 10 running a couple of days ago and didn't notice any issues but it was rather slow and I couldn't test a lot of stuff because there is drivers missing that I need to get up and running before exploring any further
machinehum has quit [Ping timeout: 260 seconds]
<anarsoul> Viciouss: IIRC it should be fixed by https://gitlab.freedesktop.org/lima/linux/-/issues/30
<anarsoul> if you test it and it works please comment on your issue and add your Tested-by