tk has quit [Quit: Well, this is unexpected.]
tk has joined #maemo-leste
villagechap has joined #maemo-leste
villagechap has quit [Ping timeout: 256 seconds]
xes has quit [Quit: WeeChat 3.3]
villagechap has joined #maemo-leste
villagechap has quit [Ping timeout: 240 seconds]
inky has quit [Ping timeout: 240 seconds]
xes has joined #maemo-leste
Pali has quit [Ping timeout: 240 seconds]
joerg has quit [Ping timeout: 240 seconds]
joerg has joined #maemo-leste
TonyStone has quit [Remote host closed the connection]
<tmlind> freemangordon: nice yeah it's smoother now :) the tearing issue is still there and the ants are still there though, maybe they are both related
<tmlind> hmm is the tearing issue even more visible now?
<tmlind> freemangordon: yeah ok not looping waiting for blits to complete makes sense :)
macros_ has quit [Ping timeout: 240 seconds]
macros__ has joined #maemo-leste
<tmlind> freemangordon: maybe also test what happens if you revert "drm/omap: Fix drm_handle_vblank() handling for command mode panels"? without that wl does not get updated, but it may not be needed for xorg at all
<tmlind> actually, maybe in omap_crtc_framedone_irq() try moving the if (omap_state->manually_updated) { } part to the end after wake_up(&omap_crtc->pending_wait)?
<tmlind> seems like the vblank interrupt should be generated only after framedone has completed, then the simulated vblank interrupt triggers the redraw of the command mode display
villagechap has joined #maemo-leste
villagechap has quit [Ping timeout: 256 seconds]
<tmlind> here's a patch to try, untested so far: http://muru.com/linux/d4/vblank-after-framedone.patch
villagechap has joined #maemo-leste
joerg has quit [Read error: Connection reset by peer]
<tmlind> not seeing a difference with my testcase, might be worth testing with xorg though
<tmlind> looks like .cpu_cache_flags = OMAP_BO_UNCACHED makes no difference for me
villagechap has quit [Remote host closed the connection]
joerg has joined #maemo-leste
<freemangordon> tmlind: ok
<freemangordon> goign tot try
<tmlind> yeah worth trying to try to narrow the remaining issues down
<freemangordon> I think tearing is the only one remaining in omapdrm
<freemangordon> it looks to me the only way we have tearing is to start frame upload while another one is in progress
<freemangordon> not sure how to verify though
<tmlind> well if the command modem vblank simulation forces refresh the wrong time it could cause tearing
<freemangordon> yes, that's what I mean
<tmlind> so maybe test first with the vblank-after-framedone.patch applied, then without that and the revert to get rid of the vblank patch
<freemangordon> yep, rebooting with the new kernel
<tmlind> ok
<tmlind> i mean second test without vblank-after-framedone.patch and the vblank patch reverted
<freemangordon> mhm
<tmlind> ok
<freemangordon> vblank patch is not upstream, right?
<tmlind> nope
<freemangordon> still tears, lemme try with that reverted
<tmlind> ok
<freemangordon> hmm
<freemangordon> still tears
<freemangordon> but that patch is not needed :)
<tmlind> any issues with terminal not updating?
<freemangordon> in h-d?
<tmlind> in h-d droid4 lcd with no hdmi cable connected
<freemangordon> or without compositing manager?
<tmlind> well not sure..
<freemangordon> ok, xterm is fulscreen
<freemangordon> and updates fine
<freemangordon> hmm, rotation transition is way faster now
<tmlind> ok might as well revert that one too for m-l, seems this is is only needed for wl
<freemangordon> mhm
<freemangordon> hmm, maybe I shall do page fliip instead of 'dirty fb"
<freemangordon> it could be that "dirty fb" requests immediate redraw
<freemangordon> glmark2 Score: 84
<freemangordon> I think this revert affected the performance
<tmlind> nice
<freemangordon> but I am not sure reverting it is the right thing to do
<tmlind> yeah sounds like some variant is still needed
<freemangordon> anyway, have to stop for few hours, will continue later on
<freemangordon> ttyl
<tmlind> ttyl
peetah has quit [Ping timeout: 256 seconds]
Pali has joined #maemo-leste
peetah has joined #maemo-leste
pere has quit [Ping timeout: 240 seconds]
Twig has joined #maemo-leste
_inky has quit [Ping timeout: 256 seconds]
inky has joined #maemo-leste
_inky has joined #maemo-leste
pere has joined #maemo-leste
inky has quit [Ping timeout: 240 seconds]
inky has joined #maemo-leste
pere has quit [Ping timeout: 256 seconds]
joerg has quit [Excess Flood]
joerg has joined #maemo-leste
pere has joined #maemo-leste
xmn has quit [Ping timeout: 256 seconds]
xmn has joined #maemo-leste
sunshavi has quit [Remote host closed the connection]
pere has quit [Ping timeout: 256 seconds]
sunshavi has joined #maemo-leste
inky has quit [Ping timeout: 245 seconds]
inky_ has joined #maemo-leste
_inky has quit [Ping timeout: 268 seconds]
uvos has joined #maemo-leste
<uvos> new sphone incomming:
<uvos> supports typing + on keypad via longpress
<uvos> all the ui bits are now modules so you can unload the dialer, the call ui, the sms ui etc speratly and replace them with something else if you like
<uvos> sphone now allows you to choose at runtime between using a glib mainloop and needing only gtk/glib or using a glib/qt mainloop that allows qt and gtk windows at the same time
<uvos> so replacing the ui modules one at a time with qt ones is an option if someone is so inclined
<uvos> + various fixes
_inky has joined #maemo-leste
pere has joined #maemo-leste
<freemangordon> sounds good
pere has quit [Ping timeout: 260 seconds]
pere has joined #maemo-leste
<Wizzup> ok, I have SDWire
<Wizzup> and some dc-dc power module
Twig has quit [Ping timeout: 240 seconds]
<uvos> dpkg: warning: downgrading mce-dev:armhf from 1.9.10 to 1.9.8
<uvos> uhh
<uvos> oh
<uvos> nvm user error
TonyStone has joined #maemo-leste
<uvos> so new mce version now turns off cpu1 on mapphones while the display is off
<uvos> as a hopfully temporary hack to reduce the ipis
<uvos> note that this is bad if your compiling stuff on it
<uvos> see the above to turn it off
<uvos> or unload the quriks-mapphone to disable all the other pm hacks as well
<Wizzup> did that actually help with pm for you btw?
<Wizzup> I think for my it actually made it use more power somehow
<Wizzup> but maybe I set it wrong
<Wizzup> (when I did it manually I mean)