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
camus1 has quit [Ping timeout: 480 seconds]
camus1 has joined #lima
camus has quit [Remote host closed the connection]
mripard_ has joined #lima
mripard has quit [Ping timeout: 480 seconds]
tlwoerner has joined #lima
jernej_ has joined #lima
jernej has quit [Read error: Connection reset by peer]
camus has joined #lima
camus1 has quit [Read error: Connection reset by peer]
camus has quit []
camus has joined #lima
camus has quit [Ping timeout: 480 seconds]
camus has joined #lima
camus1 has joined #lima
camus has quit [Ping timeout: 480 seconds]
camus has joined #lima
camus1 has quit [Ping timeout: 480 seconds]
drod has joined #lima
dllud has joined #lima
dllud_ has quit [Read error: Connection reset by peer]
dllud_ has joined #lima
dllud has quit [Read error: Connection reset by peer]
dllud has joined #lima
dllud_ has quit [Remote host closed the connection]
camus1 has joined #lima
camus has quit [Ping timeout: 480 seconds]
camus has joined #lima
camus1 has quit [Ping timeout: 480 seconds]
Danct12 has quit [Remote host closed the connection]
Net147 has quit [Remote host closed the connection]
Net147 has joined #lima
camus1 has joined #lima
camus has quit [Remote host closed the connection]
camus has joined #lima
camus1 has quit [Ping timeout: 480 seconds]
Wizzup has joined #lima
camus1 has joined #lima
camus has quit [Ping timeout: 480 seconds]
<Wizzup> Things have much improved since I updated mesa, which is great, but compositing seems buggy somehow
<Wizzup> (the device is the 'pinephone')
<Wizzup> I have a few (relatively) simple cases when I can reproduce bugs where the screen is not correctly redrawn, and in other cases some textures from windows below the current window seem to show in the current window
<Wizzup> It doesn't seem to be a bug in modesetting or X, since it works on other devices with other drivers, and also with llvmpipe on the pinephone
<Wizzup> if I disable compositing for a window and then put something on top of it, the problem disappears
<Wizzup> the window manager in this case is hildon-desktop (from maemo)
<Wizzup> so I guess my question is, what can I do to file a useful bug report?
<enunes> Wizzup: well, if you can put some effort into it ideally you could provide an apitrace of the application (in this case the compositor?) reproducing the issue
<Wizzup> ok, I can do that
<Wizzup> enunes: hm... this is particualrly weird, but it looks like I cannot reproduce the problem when running under apitrace
<enunes> Wizzup: is it the same environment that the compositor runs otherwise other than apitrace?
<Wizzup> I believe it is the same, yes
<Wizzup> I suppose that could point to some timing issues, but it does look like one of the issues I am seeing remains
<enunes> like if you run the compositor manually it reproduces, but then also manually with apitrace it doesnt?
<enunes> just to make sure you are not comparing manually vs run by a login manager or something
<Wizzup> enunes: yes, that is right, both spawned from the same login shell over ssh
<enunes> well if you can confirm at least one of the issues does reproduce, thats a start
<Wizzup> yeah - I'll come back tomorrow with some (hopefully) useful traces
<enunes> timing issues havent been much of a thing so I am a bit skeptical of that
<Wizzup> I see a lot of glitching (old pixmaps/data being rendered when it shouldn't), also in firefox, but now when I run hildon-desktop with apitrace, it's fine. (slow, but fine)
<Wizzup> I'll also try to make a video in addition to the traces tomorrow (it's getting late here)
camus has joined #lima
camus1 has quit [Ping timeout: 480 seconds]