[06:24] <duflu> RAOF: Is it right that our probing expects DRM in order to declare Mesa supported?
[06:24] <duflu> Aren't there non-DRM Mesa platforms?
[06:38] <RAOF> duflu: Not really.
[06:39] <RAOF> Also, our mesa platform *is* a DRM platform.
[06:40] <RAOF> The display buffer code is all about the raw drm KMS usage.
[07:06] <RAOF> Wooot!
[07:06] <RAOF> I've fixed precompiled headers!
[08:59] <duflu> anpok: I finally received "new" old Microsoft Intellimouse Explorer 3.0's. And am happy now. Not sure what new mice are just as good, but do know that the Microsoft Comfort mouse is rubbish
[09:00] <duflu> I'm not sure if Microsoft makes any good mice now
[09:26] <duflu> anpok: Can I hand this over to you? ... https://bugs.launchpad.net/mir/+bug/1528135
[09:37] <anpok> duflu: aye
[12:59] <sturmflut> Just out of interest: What's the target use case for "Mir-on-X"?
[13:01] <davmor2> sturmflut: I would imagine being able to run click and snap apps in a secure manner which you can't do on x alone
[13:02] <sturmflut> davmor2: So there is a plan to have devices that still run X, and then run click/snap packages on top of Mir on top of X?
[13:04] <davmor2> sturmflut: Unity7 and deb based distro will still be alive so having the ability to run snaps and clicks there will be of benefit. I assume that is the target for now if this is still a thing
[13:04] <sturmflut> Oh
[13:18] <kdub> sturmflut, my understanding is that its to help shell developers who are still transitioning out of an X environment (or testing)
[13:54]  * mcphail_ thinks Mir-on-X is likely to be useful for developing Mir clients
[14:11] <tvoss> sturmflut, what kdub said
[14:12] <tvoss> it's meant to ease development
[14:50]  * kdub looses connectivity to launchpad/etc anyone else?
[14:52] <kdub> ah, just a fun consequence of the VPN... rebooting
[14:53] <anpok> not really
[14:53] <anpok> k