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/
drod has quit [Remote host closed the connection]
camus has joined #lima
camus has quit [Ping timeout: 480 seconds]
camus has joined #lima
Daanct12 has joined #lima
Danct12 has quit [Ping timeout: 480 seconds]
Daaanct12 has joined #lima
Daanct12 has quit [Ping timeout: 480 seconds]
Daaanct12 has quit [Ping timeout: 480 seconds]
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #lima
Leopold_ has quit [Remote host closed the connection]
<marex>
enunes: anarsoul: hi, do I read the mesa driver right in that lima does support MRT ?
uis_ has joined #lima
uis has quit [Ping timeout: 480 seconds]
<enunes>
marex: I think it is not supported right now, there was a way to write to specify the output register other than r0 in the command buffer that anarsoul found and I think there could be more, but I think it was never implemented to actually write to multiple outputs
<marex>
enunes: ahh, but at least the hardware might support it then, thanks !
<anarsoul>
marex: no
<anarsoul>
and there's no proper hardware support for MRT
<anarsoul>
from what alyssa said, Utgard MRT support is similar to early Midgard and it's literally unusuable. Essentially you cannot attach arbitrary RT, they all have the same base address, and are separated by specified stride
<marex>
urgh
<marex>
anarsoul: thanks for this input
<anarsoul>
MRT they have in hw is for writing out unresolved MSAA