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!
Viciouss has quit [Ping timeout: 265 seconds]
Viciouss has joined #lima
kaspter has joined #lima
psydread has quit [Excess Flood]
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #lima
kaspter has quit [Excess Flood]
kaspter has joined #lima
buzzmarshall has quit [Remote host closed the connection]
kaspter has quit [Ping timeout: 260 seconds]
kaspter has joined #lima
camus1 has joined #lima
kaspter has quit [Ping timeout: 264 seconds]
camus1 is now known as kaspter
psydread has joined #lima
monstr has joined #lima
cwabbott has quit [Read error: Connection reset by peer]
narmstrong has quit [Read error: Connection reset by peer]
narmstrong has joined #lima
cwabbott has joined #lima
lvrp16 has quit [Ping timeout: 240 seconds]
lvrp16 has joined #lima
kaspter has quit [Ping timeout: 258 seconds]
kaspter has joined #lima
kaspter has quit [Quit: kaspter]
jbrown has joined #lima
monstr has quit [Remote host closed the connection]
jbrown has quit [Ping timeout: 272 seconds]
dddddd has quit [Remote host closed the connection]
dddddd has joined #lima
<anarsoul> enunes: hey
<anarsoul> sounds like we should do the same as vc4?
<enunes> anarsoul: can be, I didnt fully investigate that path, just noticed that vc4_resource_transfer_map allocates a bo while lima_transfer_map doesnt as its probably done somewhere else
<anarsoul> yeah, we create bo in lima_resource_create
<anarsoul> hm, I don't see where vc4 creates a BO in transfer_map()
<anarsoul> oh, found it
<anarsoul> so it does it for PIPE_TRANSFER_DISCARD_WHOLE_RESOURCE
<enunes> that flag is indeed set
Ntemis has joined #lima
<anarsoul> yeah, vc4, v3d and panfrost all allocate new BO if this flag is set
<anarsoul> panfrost also has some heuristics to check whether BO is currently in use
<anarsoul> we should do the same for sure
<enunes> fair enough, going to prototype a solution with that
<anarsoul> I was talking about bo allocation, not heuristics
<anarsoul> I don't think we need to make it complex, just allocating BO is fine
<enunes> yes thats my understanding too
lvrp16 has quit [Ping timeout: 244 seconds]
lvrp16 has joined #lima
Ntemis has quit [Read error: Connection reset by peer]