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!
machinehum has quit [Ping timeout: 265 seconds]
machinehum has joined #lima
yuq825 has joined #lima
kaspter has joined #lima
cwabbott has quit [Quit: cwabbott]
cwabbott has joined #lima
_whitelogger has joined #lima
_whitelogger has joined #lima
Barada has joined #lima
<rellla> anarsoul: i guess i have sth wrong in my last commit. so no urgent need for you to look into it. but if you don't know what to do, you can give me some hints though. :)
psydread has left #lima [#lima]
<rellla> as a benchmarking tool i think i can use https://gitlab.freedesktop.org/anholt/gpu-trace-perf/-/tree/master together with apitrace and making the changes runtime configurable. i can't build aptitrace locally though due to a OOM issue i think. so i have to find out, how to get it compiled still
psydread has joined #lima
psydread has left #lima [#lima]
dddddd has quit [Remote host closed the connection]
psydread has joined #lima
machinehum has quit [Ping timeout: 265 seconds]
psydread has left #lima [#lima]
psydread has joined #lima
psydread has left #lima [#lima]
psydread has joined #lima
camus1 has joined #lima
kaspter has quit [Ping timeout: 260 seconds]
camus1 is now known as kaspter
dllud_ has joined #lima
dllud has quit [Ping timeout: 265 seconds]
dllud_ is now known as dllud
<rellla> ok, so i have installed. what do i need to set to replay a trace? i get "error: unable to open display"
<rellla> creating a trace is possible
<rellla> *installed apitrace
<rellla> do i need gui?
adjtm_ has quit [Quit: Leaving]
yuq825 has quit [Remote host closed the connection]
adjtm has joined #lima
adjtm has quit [Remote host closed the connection]
adjtm has joined #lima
Ntemis has joined #lima
dddddd has joined #lima
monstr has joined #lima
chewitt has joined #lima
<rellla> WAFFLE_PLATFORM=gbm did the trick :)
xexaxo1 has quit [Ping timeout: 272 seconds]
kaspter has quit [Quit: kaspter]
xexaxo1 has joined #lima
yann has quit [Ping timeout: 258 seconds]
yuq825 has joined #lima
yann has joined #lima
buzzmarshall has joined #lima
Barada has quit [Quit: Barada]
Ntemis has quit [Remote host closed the connection]
enunes has joined #lima
enunes has quit [Quit: ZNC - https://znc.in]
danqo has quit [Remote host closed the connection]
enunes has joined #lima
enunes has quit [Client Quit]
enunes has joined #lima
yuq825 has quit [Quit: Leaving.]
<warpme_> guys: do we have plans to support sync-vblank (iirc via GLX_EXT_swap_control)? Without this I have quite unpleasant tearing on video playback....
enunes has quit [Quit: ZNC - https://znc.in]
enunes has joined #lima
<anarsoul> warpme_: that's something related to display driver so I'm not familiar with it
<warpme_> hmm - not sure about this. Isn't that GL has dedicated EXT for this (GLX_EXT_swap_control)?
<anarsoul> warpme_: lima is render-only driver, it knows nothing about displays
adjtm_ has joined #lima
<anarsoul> so whereever it's handled it's not lima
adjtm has quit [Ping timeout: 250 seconds]
<warpme_> anarsoul: i don't want to pretend like specialist here but...even if we are talking on render-only component - for tear-less rendering sort of synch is needed between presentation component and rendering component. It might be fifo+sem or interrupt or callback or... Just Q: is lima responsible to implement of GLX_EXT_swap_control or rather underlying mesa infra?
<anarsoul> warpme_: lima provides a fence for waiting job to complete in lima_pipe_flush()
<anarsoul> I'm not sure how it integrates with vsync though
<warpme_> indeed. it will be good to have somebody good in this area to see where issue is before 20.1 release....
monstr has quit [Remote host closed the connection]
cwabbott has quit [Ping timeout: 272 seconds]
machinehum has joined #lima
cwabbott has joined #lima
<anarsoul> rellla: you also need some vertex-heavy workload
machinehum has quit [Ping timeout: 264 seconds]
machinehum has joined #lima
Viciouss has quit [Ping timeout: 256 seconds]
Viciouss has joined #lima
danqo has joined #lima
dddddd has quit [Ping timeout: 260 seconds]
Viciouss has quit [Ping timeout: 256 seconds]
Viciouss has joined #lima
machinehum has quit [Read error: Connection reset by peer]
machinehum has joined #lima
Viciouss has quit [Ping timeout: 265 seconds]
Viciouss has joined #lima
machinehum has quit [Read error: Connection reset by peer]
machinehum has joined #lima
champagneg has joined #lima
buzzmarshall has quit [Remote host closed the connection]
<anarsoul> enunes: can you actually create MRs so we can comment on changes?