ChanServ changed the topic of #lima to: Development channel for open source lima driver for ARM Mali4** GPUs - Kernel driver has landed in mainline, userspace driver is part of mesa - Logs at https://oftc.irclog.whitequark.org/lima/
dllud_ has joined #lima
dllud has quit [Read error: Connection reset by peer]
camus has joined #lima
camus1 has quit [Ping timeout: 480 seconds]
anarsoul has quit [Ping timeout: 480 seconds]
anarsoul has joined #lima
dmh has joined #lima
tanty has joined #lima
camus1 has joined #lima
camus has quit [Ping timeout: 480 seconds]
camus1 has quit [Ping timeout: 480 seconds]
camus has joined #lima
chewitt has quit [Read error: Connection reset by peer]
chewitt has joined #lima
chewitt has quit []
<enunes> anarsoul: about https://gitlab.freedesktop.org/mesa/mesa/-/issues/6036 , I was thinking if it would make sense that they might have the disk shader cache populated with bugged shaders
<enunes> would that make sense at all, or is the disk shader cache smart enough to rebuild it?
<enunes> couldn't find much information on it
<enunes> hmm might be unlikely, looks like we encode what I guess is the git version as part of the key
drod has joined #lima
<anarsoul> enunes: unlikely, shader cache won't match with different build hash id
tlwoerner_ has joined #lima
anarsoul|2 has joined #lima
tlwoerner has quit [Remote host closed the connection]
anarsoul has quit [Read error: Connection reset by peer]
anarsoul|2 has quit []
anarsoul has joined #lima
camus1 has joined #lima
camus has quit [Read error: Connection reset by peer]
tlwoerner_ has quit []
tlwoerner has joined #lima
robher has quit [Read error: Connection reset by peer]
daniels has quit [Read error: Connection reset by peer]
daniels has joined #lima
robher has joined #lima
drod has quit [Remote host closed the connection]
dllud has joined #lima
dllud_ has quit [Read error: Connection reset by peer]