summaryrefslogtreecommitdiff
path: root/Events/XDC2016
diff options
context:
space:
mode:
authormperes <mperes@web>2016-08-19 14:59:47 +0000
committerxorg <iki-xorg@freedesktop.org>2016-08-19 14:59:47 +0000
commit58c2445e6106ff62c44aa7267af25ae26fc5e9ea (patch)
tree4e603cf8ac5d67b8276a1e5e3e34d9aad498490a /Events/XDC2016
parent41311d6de5d1ba6ddfa9c509f5a0152f238d907f (diff)
Diffstat (limited to 'Events/XDC2016')
-rw-r--r--Events/XDC2016/Program/reveman_arcpp.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/Events/XDC2016/Program/reveman_arcpp.mdwn b/Events/XDC2016/Program/reveman_arcpp.mdwn
new file mode 100644
index 00000000..0b677df0
--- /dev/null
+++ b/Events/XDC2016/Program/reveman_arcpp.mdwn
@@ -0,0 +1,5 @@
+# David Reveman - ARC++
+
+ARC++ provides existing and future Chromebooks with the ability to run applications from the Google Play Store. The performance and seamless integration into ChromeOS achieved by ARC++ is in large part a result of a carefully designed graphics stack. Rendering, compositing and window management has been designed to fit together in a way that makes no compromise on performance or resource usage.
+
+This talk will give an overview of the pieces that make up the ARC++ graphics stack, describe how Wayland is used as a compositor protocol and explain how we achieve the goal of running Android applications on ChromeOS with native graphics performance and window management capabilities expected from an application running on a Chromebook. It will also provide some basic pointers for running Wayland clients on ChromeOS, and future direction.