summaryrefslogtreecommitdiff
path: root/Events/XDC2016/Program/reveman_arcpp.mdwn
diff options
context:
space:
mode:
authorMartin Peres <martin.peres@linux.intel.com>2016-09-21 15:39:56 +0300
committerMartin Peres <martin.peres@linux.intel.com>2016-09-21 15:39:56 +0300
commit3732844d9b5628cd19103c3faf647b0ee5e5bce1 (patch)
treec022187b2a7c23831d289ed566889a530120e564 /Events/XDC2016/Program/reveman_arcpp.mdwn
parent58a5f80bed78903a57cef5da95b9464c2c1a908c (diff)
add one more slide
Diffstat (limited to 'Events/XDC2016/Program/reveman_arcpp.mdwn')
-rw-r--r--Events/XDC2016/Program/reveman_arcpp.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/Events/XDC2016/Program/reveman_arcpp.mdwn b/Events/XDC2016/Program/reveman_arcpp.mdwn
index 0b677df0..806743d6 100644
--- a/Events/XDC2016/Program/reveman_arcpp.mdwn
+++ b/Events/XDC2016/Program/reveman_arcpp.mdwn
@@ -1,5 +1,7 @@
# David Reveman - ARC++
+[[Slides|Arcpp_Graphics.pdf]]
+
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.