akossh has quit [Quit: Leaving.]
nela has quit [Quit: bye]
nela has joined #maemo-leste
nela has quit [Quit: bye]
nela has joined #maemo-leste
enviosity has quit [Ping timeout: 240 seconds]
slep has quit [Quit: Gateway shutdown]
antranigv has quit [Quit: ZNC 1.8.2 - https://znc.in]
antranigv has joined #maemo-leste
k1r1t0 has quit [Quit: leaving]
joerg has quit [Ping timeout: 268 seconds]
joerg has joined #maemo-leste
wice has joined #maemo-leste
antranigv has quit [Quit: ZNC 1.8.2 - https://znc.in]
antranigv has joined #maemo-leste
vahag has quit [Read error: Connection reset by peer]
uvos has quit [Quit: Konversation terminated!]
fab_ has joined #maemo-leste
xmn has quit [Quit: ZZZzzz…]
<freemangordon> upstream glamor/ms is about 30% slower on d4 compared to omap ddx :(
<freemangordon> according to glmark that is
<freemangordon> and until it works, as [desktop] benchmark crashes GPU
dos has quit [Ping timeout: 268 seconds]
dos has joined #maemo-leste
<Wizzup> freemangordon: 30% is not TOO bad if all other trhings work, but yeah hangs aren't great :D
<freemangordon> WTYM not bad? it is supposed to be faster
<Wizzup> dri3 wise yeah I suppose
<freemangordon> mhm
akossh has joined #maemo-leste
<Wizzup> well iirc glamor was never faster
<Wizzup> it uses a lot of generic paths so it's unlikely to be more optimised
<Wizzup> but it would give us tearfree :D
<freemangordon> it will not
<Wizzup> latest modesetting+glamor has tearfree support regardless of driver AFAIK
<freemangordon> not until omapdrm driver is smart enough to properly support panels with TE (IIRC)
<freemangordon> the tearing you see now is because of omapdrm
<Wizzup> ok
sch has quit [Ping timeout: 256 seconds]
arno11 has joined #maemo-leste
fab_ has quit [Quit: fab_]
fab_ has joined #maemo-leste
pere has quit [Ping timeout: 256 seconds]
<tmlind> uvos: weird
<tmlind> uvos: does modprobe modprobe cpufreq-dt-platdev fix it for you?
<tmlind> well with just one modprobe :)
<Wizzup> it's funny, whatever random failures I tend to observe in the wifi plugin, whenever I actually try to debug them they almost mostly disappear.
sch has joined #maemo-leste
pere has joined #maemo-leste
<Wizzup> I might have asked this before, but on d4 I see this:
<Wizzup> [273515.024200] wlan0: authenticate with 64:70:02:e2:a2:55
<Wizzup> [273515.035369] wlan0: send auth to 64:70:02:e2:a2:55 (try 1/3)
<Wizzup> [273515.040222] wlan0: send auth to 64:70:02:e2:a2:55 (try 2/3)
<Wizzup> [273515.044586] wlan0: send auth to 64:70:02:e2:a2:55 (try 3/3)
<Wizzup> [273515.049713] wlan0: authentication with 64:70:02:e2:a2:55 timed out
<Wizzup> should the timeout really be that short?
xmn has joined #maemo-leste
<Wizzup> wpa_supplicant sets the authentication timeout to 10s per its logs
<Wizzup> ok, it looks to me like most of the random wifi failures that we have on the d4 are not a problem in my icd2 module
<Wizzup> sicelo: tmlind: do you guys see this as well on something other than m-l ?
<Wizzup> 250ms for total authentication timeout seems way too low given that wpa_supplicant set it to 10s, iiuc
<Wizzup> wlcore debug_level didn't show any errors to my eye
<freemangordon> Wizzup: do you debug "first connect always fails" issue?
<freemangordon> to me this is driver issue, never happens on n900
<Wizzup> freemangordon: I am seeing this more frequently, not just the first time
<Wizzup> the droid4 would sometimes randomly decide not to connect to wifi, in like an instant
<Wizzup> and I was trying to debug if this was a problem in my code
<Wizzup> and it seems it is not
<Wizzup> every time this happens, you will something like above in dmesg
<freemangordon> yes, does nto seem sto be icd issue
<Wizzup> or even wpa_supplicant, I think, but who knows
<Wizzup> I did make a few minor changes to the wifi module
<Wizzup> but nothing major
<Wizzup> I'll push that out in a bit and jump back to sphone
<Wizzup> freemangordon: shall I add like 100GB more music or something, to see if that will trigger any other problems?
<Wizzup> or is that pushing it
<Wizzup> :D
<freemangordon> why not
<Wizzup> ok
arno11 has left #maemo-leste [#maemo-leste]
<Wizzup> uvos: I get this sometimes:
<Wizzup> sphone: sphone-conf: Could not get config key ContactsEvolution/ContactsSource
<Wizzup> sphone: contacts-ui-abook: Can not create ebook:
<Wizzup> double free or corruption (out)
<Wizzup> in my branch at least
<Wizzup> so with the qt loop
<Wizzup> maybe it's my bad, mixing some versions
fremantle2 has joined #maemo-leste
fremantle2 is now known as wizzup_tp
wizzup_tp has quit [Client Quit]
fab_ has quit [Quit: fab_]
<Wizzup> freemangordon: uvos: ok, I can call my d4 over sip using my fremantle n900 - no sound yet
<Wizzup> SIP IM works over conversations
<Wizzup> (which we knew already)
<Wizzup> but the ringing with a sip call is kinda cool :)
<Wizzup> freemangordon: rtcom-accounts-ui is using a lot of cpu, let me see if I can get a good backtrace
<Wizzup> It says this over and over: (rtcom-accounts-ui:12672): Gtk-CRITICAL **: 00:17:09.164: IA__gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed\n"
<Wizzup> droid4 to n900 doesn't work yet, but could be a config or farstream issue