summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel van Vugt <vanvugt@gmail.com>2016-02-11 09:44:03 (GMT)
committerDaniel van Vugt <vanvugt@gmail.com>2016-02-11 09:44:03 (GMT)
commit3f1e0ab7e5a8af5578cd10492c1f93e9bf97e252 (patch)
treef526b79b52379235f87557145060abcc92e29083
parent3cb094e9db002945c229894782f0dc062b3ef319 (diff)
Enable full performance mode! (LP: #1502738)
There's always some risk, but finally it seems the blocking bugs are fixed: LP: #1391261, LP: #1497828 So you now require Mir 0.16+ and if you're using Unity8, also a newish version of QtMir from Jan 2016 or later. Otherwise this change could cause freezes.
-rw-r--r--hw/xmir/xmir.c13
1 files changed, 8 insertions, 5 deletions
diff --git a/hw/xmir/xmir.c b/hw/xmir/xmir.c
index 613f1b5..aac24a5 100644
--- a/hw/xmir/xmir.c
+++ b/hw/xmir/xmir.c
@@ -773,13 +773,16 @@ xmir_realize_window(WindowPtr window)
xmir_screen->flatten_top = xmir_window;
mir_surface_set_event_handler(xmir_window->surface, xmir_surface_handle_event, xmir_window);
-#if 0
- /* Until recently (LP: #1391261) Mir's Android platform was still too buggy
- * to deal with this. But we're also still blocked by Unity8 bugs:
- * TODO: Fix bug LP: #1497828 to enable this in Unity8 (including ARM)
+ /*
+ * Traditional X apps actually get zero throttling, so an interval of
+ * zero is most appropriate, and of course avoids lag and provides
+ * maximum frame rates.
+ * This does however overclock DRI2 GLX clients who want an interval of
+ * one, but they are a tiny minority and much less important than
+ * minimizing lag right now. We'll fix that later. (LP: #1211186)
*/
mir_surface_set_swapinterval(xmir_window->surface, 0);
-#endif
+
xmir_window_enable_damage_tracking(xmir_window);
if (xmir_screen->glamor)