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!
_whitelogger has joined #lima
kaspter has joined #lima
_whitelogger has joined #lima
dddddd has quit [Remote host closed the connection]
kaspter has quit [Ping timeout: 265 seconds]
kaspter has joined #lima
megi has quit [Ping timeout: 240 seconds]
Barada has joined #lima
yann|work has quit [Ping timeout: 276 seconds]
yann|work has joined #lima
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #lima
Barada has quit [Quit: Barada]
Barada has joined #lima
kaspter has quit [Ping timeout: 245 seconds]
megi has joined #lima
Barada has quit [Quit: Barada]
kaspter has joined #lima
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #lima
warpme_ has joined #lima
yann|work has quit [Ping timeout: 246 seconds]
yann|work has joined #lima
maccraft123 has joined #lima
yuq825 has quit [Quit: Leaving.]
camus has joined #lima
kaspter has quit [Ping timeout: 276 seconds]
camus is now known as kaspter
monstr has joined #lima
monstr has quit [Remote host closed the connection]
<warpme_> guys: i'm developing mythtv appliance for mali450 hw. Currently mythtv can use mesa for rendering video with: OpenGL & yv12 renderers + GLSL based shader deinterlacers (OneFileld. LinearBlend & Kernel). From those possible 6 combinations - only one working ok at this moment: yv12 renderer+LinearBlend DI. Should I report bug + provide apitrace for rest 5 failing cases or rather now it is not yest good time for this (as
<warpme_> lima is WiP)?
<anarsoul> please open a bug and provide apitrace
<plaes> btw.. do bugs go under mesa or the old lima project?
<anarsoul> mesa
<anarsoul> btw, note that fragment shader in mali450 can do only fp16
<anarsoul> do I'm not really sure whether deinterlacer would work well
<anarsoul> since you can't accurately sample textures larger than 1024x1024 if you do any calculcations on coordinates
<anarsoul> that's why deinterlacer may fail at larger resolutions
<anarsoul> warpme_: ^^
dddddd has joined #lima
yann|work has quit [Ping timeout: 265 seconds]
maccraft123 has quit [Quit: WeeChat 2.6]
maccraft123 has joined #lima
maccraft123 has quit [Client Quit]
maccraft123 has joined #lima
yann|work has joined #lima
<warpme_> anarsoul: pls find bug report with attached apitraces: https://gitlab.freedesktop.org/mesa/mesa/issues/2126
<anarsoul> how exactly does it fail?
<warpme_> anarsoul: playback has wrong content (parts of UI before playback etc). pls look in "middle" of trace during trace playback and compare this with working ok apitrace I attached. In working apitrace You should see TV programm picture while in problematic apitraces You will see garbage or parts of UI etc.
<anarsoul> they're huge
<warpme_> yeah: it is from launched app where I first walking on UI to get recording to playback and then stating playback of this recording...
<anarsoul> can you trim the traces? :)
<warpme_> i don't have apitrace GUI utility to play with apitrace files and trim them - as i'm working on appliance sw. with minimal software just to run mythtv. If there is way to reduce size of apitraces - pls advice!
<anarsoul> see qapitrace
<anarsoul> it'll work with desktop qapitrace as well
<warpme_> but I don't desktop with apitrace (i'm on mac with macOS)
<anarsoul> I think you can build it on macOS as well
<warpme_> iirc I was trying to use macOS apitrace - but I fails with msg like "unsupported api called" or something like this
<warpme_> probably macOS has different level of GL available api - just suspect....
<anarsoul> :(
<warpme_> what else I can do?
<anarsoul> I guess someone will have to look into your traces
<warpme_> anarsoul: just launched ubuntu18.04 on vm, installed qapitrace and receiving "Unsupported API" :-(. It is because Ubuntu has older mesa (without APIs used by mesa at apitrace gathering)?
<anarsoul> I guess old apitrace
<warpme_> well - most current from ubuntu repo.....
<anarsoul> yeah, they're known to ship outdated software
<warpme_> indeed: my appliance apitrace is 8.0 while ubuntu is 7.1. Hate ubuntu so time to go with lovely ArchLinux
Elpaulo has quit [Ping timeout: 276 seconds]
<warpme_> ough: kicking archlinux; done full update (apitrace is 8.0.1). Launching qapitrace, loaded .trace file and asking for playback and .... getting "process crashed" at qapitrace status bar. well - what next?
<anarsoul> likely your videodriver crashed? :)
<anarsoul> try with software rendering?
<anarsoul> i.e. LIBGL_ALWAYS_SOFTWARE=1
<warpme_> hmm: opened terminal; type export LIBGL_ALWAYS_SOFTWARE=1; type qapitrace; load trace; ask for playback and the same "Process crashed"
<warpme_> well - i think qapitrace is broken in archlinux: call to any function in menu gives "Process crashed". omg....
jernej_ has joined #lima
<anarsoul> warpme_: it works for me
<anarsoul> likely your gpu driver is broken
<anarsoul> (if you have one installed)
jernej_ has quit [Remote host closed the connection]
jernej_ has joined #lima
<warpme_> hmm - this is vm under parallels hypervisor with parallels GL driver for guest. looks like this might be issue....
jernej has quit [Ping timeout: 276 seconds]
jernej_ is now known as jernej
dllud has quit [Quit: ZNC 1.7.4 - https://znc.in]
maccraft123 has quit [Ping timeout: 252 seconds]
dllud has joined #lima
camus has joined #lima
kaspter has quit [Ping timeout: 240 seconds]
camus is now known as kaspter
dllud has quit [Read error: Connection reset by peer]
dllud has joined #lima
dllud has quit [Quit: ZNC 1.7.4 - https://znc.in]