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!
dllud has quit [Read error: Connection reset by peer]
dllud has joined #lima
jernej has quit [Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net]
jernej has joined #lima
<anarsoul> Viciouss: compare your dts for android and mainline?
_whitelogger has joined #lima
buzzmarshall has quit [Remote host closed the connection]
_whitelogger has joined #lima
warpme_ has joined #lima
jernej has quit [Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net]
jernej has joined #lima
jernej has quit [Remote host closed the connection]
jernej has joined #lima
jernej has quit [Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net]
jernej has joined #lima
jernej has quit [Remote host closed the connection]
jernej has joined #lima
deesix_ has joined #lima
dddddd_ has joined #lima
deesix has quit [Ping timeout: 264 seconds]
dddddd has quit [Ping timeout: 264 seconds]
dddddd_ is now known as dddddd
deesix_ is now known as deesix
uis has quit [Quit: ZNC 1.7.4 - https://znc.in]
uis has joined #lima
buzzmarshall has joined #lima
<Viciouss> I copy pasted it, no changes
<Viciouss> If I revert the patch in the android kernel that I found as root cause, everything goes back to normal
<anarsoul> well, I have no experience with android development
<anarsoul> did you try loading lima module manually?
Viciouss has quit [Quit: ZNC 1.7.5+deb4 - https://znc.in]
Viciouss has joined #lima
<Viciouss> I booted into buildroot with the android common kernel, my problem is not related to the android OS in any way. lima is built into my kernel, so it should automatically load on boot if there is a dt entry if I'm not mistaken