[06:06] <duflu> anpok, RAOF: OK, I've got the old PentiumD updated and waiting for a new mesa to test (i915) :)
[06:07] <duflu> In the mean time it serves as a noise and heat machine. Handy
[06:14] <RAOF> :)
[07:19] <alf_> duflu: Hi! @ bug 1372276, is it Ctrl-C for the nested or host server?
[07:19] <duflu> alf: Good question. Not sure :) Will paste script
[07:20] <duflu> alf_: Done
[17:26] <racarr> Hmm trying to test my cmake qtmir on x86 (desktop session) but can't even get desktop session going without my hacked up qtmir
[17:34] <racarr> :( of course you have to unplug external monitor
[17:34] <racarr> would like to submit a 15 minute fix but the whole process of testing it woudl take hours and hours
[17:34] <racarr> so doesnt seem possible
[17:39] <greyback_> racarr: yeah multi-monitor & qtmir not friends atm
[17:43] <racarr> It would be easy to for example have
[17:43] <racarr> qtmir reconfigure multiple outputs to clone
[17:43] <racarr> rather than crash...
[17:43] <racarr> but I dont have time today to test all the various configurations, etc...for another branch
[17:44] <greyback_> problem is to get Qt happy with that
[17:44] <racarr> really? I mean just present one output
[17:44] <racarr> to qt
[17:44] <greyback_> but what renders to each display then?
[17:45] <greyback_> to close, do you render for one display, then copy the front buffer to the other display?
[17:45] <greyback_> s/close/clone/
[17:45] <greyback_> or just to GL for each display.
[17:47] <racarr> hmm maybe we do render for each display
[17:47] <racarr> for some reason I was thinking
[17:47] <racarr> they were the same front buffer
[17:47] <racarr> im not sure thats truet hough
[17:48] <racarr> lalala
[17:48] <racarr> greyback_: On a happier note tested qtmir-cmake ondesktop and emulator
[17:48] <racarr> (and phone)
[17:48] <racarr> all good
[17:51] <greyback_> racarr: cool, thanks
[17:52] <racarr> greyback_: Adding the tests to ctest now then will submit another mp that should pass jenkins and do some self review
[17:52] <racarr> then you can do as you wish with it :D
[17:52] <greyback_> racarr: magic!
[17:53] <greyback_> racarr: there's this old qtmir branch you made still in review, dandrader left some comments and it's not gone anywhere since: https://code.launchpad.net/~mir-team/qtmir/server-client-acceptance/+merge/230018
[17:53] <greyback_> mark it WIP or think you'll resume it or...?
[17:54] <racarr> greyback_: I was just noticing that too...
[17:55] <racarr> im reflecting on it lol will do something after lunch
[17:57] <greyback_> racarr: thanks :)
[20:56] <doneill> Hi all! I'm hopeful in building Touch on an SoC sporting Mali400 GPU, but I can't find any evidence that Mir works with acceleration on this GPU. Can anybody confirm or refute this?
[20:57] <racarr> doneill: I can't off the top of my head! If you have android drivers theres a good chance Mir can use them.
[20:59] <greyback_> doneill: you may find this guide helpful: http://unity.ubuntu.com/mir/android_new_device_bringup.html
[21:00] <doneill> Excellent, thank you so much!
[21:03] <greyback_> doneill: this is the best channel to find the mir developers, so feel free to ask for help