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/
megi has joined #lima
megi1 has joined #lima
megi has quit [Ping timeout: 480 seconds]
camus has joined #lima
camus1 has quit [Ping timeout: 480 seconds]
mvnetbiz[m] has joined #lima
Daanct12 has joined #lima
Danct12 has quit [Ping timeout: 480 seconds]
Daanct12 has quit [Read error: Connection reset by peer]
Danct12 has joined #lima
Daanct12 has joined #lima
Daaanct12 has joined #lima
Danct12 has quit [Ping timeout: 480 seconds]
Danct12 has joined #lima
Daanct12 has quit [Ping timeout: 480 seconds]
Daaanct12 has quit [Ping timeout: 480 seconds]
Daanct12 has joined #lima
Danct12 has quit [Ping timeout: 480 seconds]
Daanct12 has quit [Remote host closed the connection]
erlehmann has quit []
chewitt has joined #lima
Danct12 has joined #lima
drod has joined #lima
jernej_ is now known as jernej
camus1 has joined #lima
camus has quit [Ping timeout: 480 seconds]
Wizzup has joined #lima
dllud_ has joined #lima
dllud has quit [Remote host closed the connection]
dllud has joined #lima
dllud_ has quit [Read error: Connection reset by peer]
<enunes> anarsoul rellla any time to review https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14894 soon ?
<enunes> also I wonder if there are any opinions on proposing any of that to stable or 22.0
<anarsoul> I guess it's OK for 22.0, and probably too much changes to stable
<enunes> by the way regarding CI I started http://lists.infradead.org/pipermail/linux-amlogic/2022-February/011662.html , some people confirm it is a bug but not much other feedback so far
<anarsoul> enunes: see my comment, you can't just drop lima_job_get(ctx) call
<anarsoul> you'll get a crash somewhere later. It won't be triggered by deqp, you need some reproducer that does a lot of draws without flush
<enunes> lima_job_get gets called in the following line
<enunes> should I just remove the assignment to job then if we want to keep another call expicit there?
<enunes> that doesnt make a lot of sense though, its not a static var or a parameter or anything
<anarsoul> I guess you can drop assignment
<enunes> first thing in lima_update_job_wb is another call of that, maybe thats why it has no functional change
<anarsoul> oh, right
<anarsoul> likely it's some leftover, let me do some git archeology...
<anarsoul> ugh, I don't like this implicit job allocation
<anarsoul> it's fragile, if we ever drop lima_job_get() from somewhere it may break
<anarsoul> I think it's OK to drop it here
<rellla> enunes: sorry, i'm very busy with $work$, so there's not much time for lima atm. but anarsoul did it already. thanks guys for keep on working on lima ;)
Viciouss5 has quit [Ping timeout: 480 seconds]
Viciouss5 has joined #lima
Viciouss5 has quit []
Viciouss has joined #lima
xdarklight has quit [Server closed connection]
oftc has joined #lima
oftc is now known as Guest135
drod has quit [Remote host closed the connection]
dllud_ has joined #lima
dllud has quit [Remote host closed the connection]