/srv/irclogs.ubuntu.com/2013/11/08/#ubuntu-mir.txt

=== chihchun_afk is now known as chihchun
kgunnracarr: lol...like all the code...?00:48
=== chihchun is now known as chihchun_afk
Mirvkgunn: ok, and yes still trying to get all apps green05:06
=== chihchun_afk is now known as chihchun
RAOFReally? EventHub uses inotify to watch /dev/input to do hotplug? :(06:43
tvossRAOF, we have a bug open to adjust that admittedly wrong behavior :)07:00
RAOFThe EventHub is a big ball of spaghetti, isn't it.08:51
tvossRAOF, it is, we need to split it up a little :) we haven't done so far to avoid too big of an investment09:09
tvossRAOF, however, as we prepare for the scenegraph changes, we will tackle the EventHub/InputReader, too09:11
tvossRAOF, if you want to see convoluted, special-cased code, look at InputDispatcher ;)09:11
tvossthat's real fun09:11
RAOFI'm less interested in that, because dispatching happens after libtouchpad :)09:11
RAOFWheras EventHub is all up in libtouchpad's business.09:13
tvosslibtouchpad?09:16
RAOFhttps://github.com/whot/libtouchpad09:17
RAOFAKA: make touchpads not horrible.09:17
tvossRAOF, hmmm, interesting, will have a look09:18
RAOFNot much there yet, but I plan to help Peter migrate the various bits of functionality from xf86-input-synaptics.09:19
RAOFBut 8:30 says “time to stop work” :)09:19
dufluRAOF: Yes there's a problem if I reach my EOD before you :)09:27
alan_ggreyback: would you check another tweak to unity-mir for me? https://code.launchpad.net/~alan-griffiths/unity-mir/make-portable-across-Mir-versions/+merge/19447910:14
alan_ggreyback: (repeat in case you missed it) would you check another tweak to unity-mir for me? https://code.launchpad.net/~alan-griffiths/unity-mir/make-portable-across-Mir-versions/+merge/19447910:44
greybackalan_g: I missed the first ping. Yes I'll look now10:45
alan_ggreyback: thanks10:45
greybackalan_g: approved, thanks11:13
alan_ggreyback: ta11:13
=== dandrader is now known as dandrader|afk
=== dandrader|afk is now known as dandrader
=== chihchun is now known as chihchun_afk
=== alan_g is now known as alan_g|lunch
=== alan_g|lunch is now known as alan_g
greybackalf__: question for you: when a display is connected or removed, how is a new CompositingFunctor created/destroyed? Is it that the MultiThreadedCompositor is stopped and then started?13:51
greybackAnd then a second more general question: how is vsync respected? I don't see what blocks after a frame is ready, until vsync is done13:51
alf__greyback: 1. Yes, the MultiThreadedCompositor is currently torn down and set up from scratch13:53
greybackok13:56
alf__greyback: 2. the blocking happens in DisplayBuffer::post_update(), which is currently called internally by the DisplayBufferCompositor since it needs to call the right overload (with or without bypass)13:56
greybackalf__: got it. Thanks!13:57
alf__greyback: yw13:59
kgunnrobotfuel: hey...i'm probably gonna miss the standup (have an external call)...did you happen to file a ci feature bug for adding our demo clients ?14:41
kgunni know we spoke a few days ago...just following up14:41
robotfuelkgunn: yes, I already have a test runner for it as well that will pass or fail a demo after running x number of seconds depending on return code or stderr14:42
kgunnrobotfuel: cool...is it strictly binary for running or not ? or does it look at the performance as its pass/fail ?14:43
kgunnrobotfuel: just thinking if we could look at the fps # it would help prevent things like this...https://bugs.launchpad.net/mir/+bug/124921014:44
ubot5Ubuntu bug 1249210 in Mir "Mir client frame rate regression in r1196" [Critical,Triaged]14:44
robotfuelkgunn: we will add performance eventually as it's printed on tests in standard out, but we need to get data, before we can pass fail based on it.14:44
kgunnrobotfuel: cool....glad to know you're on it14:45
kgunnappreciate it14:45
=== dandrader is now known as dandrader|lunch
=== alan_g is now known as alan_g|afk
kgunnkdub: so i thot i'd be clever and try to build mir on the device to test the integration tests15:58
kgunnsounds like a yo dawg meme15:58
kgunnkdub: so all was going ok until i got to cmake ..15:58
kgunnkdub: then it complains about the boost libs15:59
kgunnkdub: i was now going to try to install them...but just wondering why that's not taken care of through all the install steps (devscripts, build-essential etc)16:00
kdubkgunn, i think there is a tool in devscripts for that... i usually use pbuilder-satisfydepends though16:03
=== dandrader|lunch is now known as dandrader
=== alan_g|afk is now known as alan_g
kdubdpkg-genbuilddeps16:04
kgunnkdub: hmmm...i'm doing apt-get install libboost-dev-all16:04
kdubthat should work too16:05
kgunnyeah...more than 1 way to skin a cat16:05
kgunnkdub: just to make sure (while i wait on the world to download)...if i simply say "YES" in the rules file for integration test, they should run as part of the build correct?16:34
kdubi believe so, but its not something i've tried recently16:36
greybackHey, am I reading this wrong: http://bazaar.launchpad.net/~mir-team/mir/trusty/view/head:/include/platform/mir/graphics/display.h <- does create_gl_context() create a GL context which spans all physical displays?16:37
kdubgreyback, i think thats how it works16:37
greybackkdub: hmm , I was expecting a gl context per framebuffer16:38
kdubalf__, would object if i'm wrong though :)16:38
kgunngreyback: fwiw, i've actually seen both...context per & 1 for many16:39
greybackkgunn: ok. I know both do-able, but I thought i heard someone mention Mir did context per fb. Was just checking16:40
greybackthink 1 context per many makes my life easier16:40
kgunnstill a good question...maybe alf__ will enlighten us16:40
kgunni really really heart verizon and their damn wifi route today :-|16:42
alf__greyback: Each DisplayBuffer gets its own GL context. However, all contexts, including the ones returned by create_gl_context(), are created sharing a common base share context, so they can all access shared resources (like textures).17:14
greybackalf__: ah cool17:15
greybackI didn't know that could be done17:15
alf__greyback: for a caveat about multithreading with shared contexts see the comment in src/server/compositor/gl_renderer_factory.cpp17:21
greybackalf__: understood17:22
* greyback eod17:23
=== dandrader is now known as dandrader|afk
=== dandrader|afk is now known as dandrader
=== alan_g is now known as alan_g|EOW
=== dandrader is now known as dandrader|bbl
racarrHad a full system hang from mir_demo_server_shell :(19:25
=== dandrader|bbl is now known as dandrader
doneill_sam113101: we should've been talking Mir over here, hah!20:06
sam113101doneill_: yeah20:07
sam113101doneill_: do you work on mir?20:07
doneill_Anyway, I suspect you'll bump into Unity-isms in Mir when you start implementing. I'd suggest poking around the Unity8 code and borrow gfx/input initialization from there.20:07
doneill_No, I work on Ubuntu Touch apps, but at this stage it requires being at least moderately familiar with Mir and how it works.20:08
sam113101ok20:09
doneill_I'm not in a very different position than you, except instead of weighing the options I'm using both Mir and Wayland.20:09
robotfuelracarr: ping20:18
racarrrobotfuel: pong20:58
robotfuelracarr: I asked the question in #mir20:58
robotfuelracarr: :D20:59
racarrI see20:59
racarrI dontknow about the bug but I have seen it before(just haven't investigate yet)20:59
racarrI will check it out once I finish 124921020:59
racarrI basically understand what is happeningwith 1249210 and have the fix butI dont quite understand21:19
racarrwhy it results in halfFPS when bypassed21:19
racarrrobotfuel: Investigating now as soon as I get a clean build dir:)21:41
kgunnupdatin' to trusty....22:06

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!