[15:04] <kdub> good morning, got swapinterval 0 (display) to work on nex4, galaxy nexus's driver is more difficult though
[15:36] <tvoss> kdub, \o/
[16:07] <alf__> status: first lttng probes up for review (after a valiant fight with clang and cross-compilation rpaths), removing unneeded mir_connection_drm_auth_magic() call and all related code
[16:08] <alf__> all: Have a great weekend!
[16:08] <kdub> you too alf__
[16:09] <greyback> kdub: I was setting swapinterval 0 on galaxy nexus, but no luck. Will be interested to see what you do
[16:10] <kdub> greyback, i'll let you know when swapinterval 0 is exected to work for the shell usecase :)
[16:10] <greyback> kdub: thanks. I'm more curious /how/ you do it :)
[17:37] <racarr> the swapinterval(0)
[17:37] <racarr> just reminds me of when we had an FPS counter in beryl
[17:37] <racarr> then once we enabled vsync
[17:37] <racarr> everyone posted on the forum about their FPS dropping from 4000 to 60
[17:47] <kdub> racarr, yeah... trying to avoid that
[17:49] <racarr> XD.
[18:48] <racarr> trying to track down how we accidentally implemented sticky keys :p
[19:02] <racarr> I guess we are mapping on the wrong side of
[19:02] <racarr> key repeat
[19:02] <racarr>  / not ignoring repeated events
[19:02] <racarr> well, not mapping, but updating the key state
[19:02] <racarr> so xkb common is interpreting repeated shift key down as
[19:03] <racarr> ...um...I don't even know what to call it
[19:03] <racarr> shift levels , additional shifts
[19:03] <racarr> haha