The intention with this session is to provide guidelines for developing a Trusted Applicationbased on the Global Platform TEE Specifications, and for running it based on the OP-TEE implementation of the TEE.
The Dalvik virtual machine is the crucial part of Android responsible for executing platform independent code in Android apps.The upcoming L release of Android replaces "Dalvik" with a new implementation of the Dalvik virtual machine called the "Android RunTime" (ART). In this session you can learn about ART, Dalvik compatibility, and our experiences assisting with the 64bit porting efforts on AOSP.
This session is an introductory course on Linux kernel upstreaming fundamentals. The course covers the definition the Linux mainline kernel tree as well as the maintainer hierarchy and processes used to contribute software into the mainline kernel. Special focus is given to understanding what documentation will help understand the process and mechanics in more detail while breaking the workflow into the various steps of upstreaming software patches. The target audience is both software engineers and engineering managers preparing to upstream software into the kernel. The topic requires a solid background in software configuration management terminology and the git SCM tool as well as a good technical understanding of the Linux kernel itself.
Making NEON shine simply requires following a few tips. In this presentation, I'll first introduce NEON and do a comparison between ARMv8 and ARMv7 NEON before we explore the key factors to a successful use of NEON. I'll present work I've done on the Skia graphics library (used in Chromium, Firefox, Android) and share a number of tips.
QEMU ARMv8-A system emulation was completed shortly after LCA14 and has been fully upstreamed in QEMU. During this session we will briefly cover the level of support and functionality, and we will introduce developers to using QEMU for running 64-bit ARM kernels and distributions using QEMU. We also developed a small set of patches on top of upstream QEMU which allows us to run a 64-bit Android build. We will explain the status and efforts coordinated between Google and Linaro, demo the working system, and show how developers can start playing with this.
Task scheduling on big.Little targets is a known challenge in the community. A commercial grade solution exists with ARM's Global Task Scheduler and there is a second solution being developed by ARM to solve this problem in a more generic, upstream-friendly way. The HMP scheduler extensions developed at Qualcomm Innovation Center (QuIC) were created to achieve many of the same benefits being sought in the power-aware scheduler in current development upstream, along with perhaps some additional ones. This presentation will cover the features, design and status of QuIC's HMP scheduler extensions.
Some areas of interest from ARM-Linaro perspective:
- Some intro to their target arch/platform.
- Architecture of their software solution (sched, load tracking algorithm, power- management from the scheduler, energy model description and use, DT etc).
- Pain points from an upstream integration PoV.
- Results, if any.
Coresight is the name given to a set of IP blocks providing hardware assisted tracing for ARM based SoCs. This presentation will give an introduction to the technology, how it works and offer a glimpse of the capabilities it offers. More specifically we will go over the components that are part of the architecture and how they are used. Next will be presented the framework Linaro is working on in an effort to provide consolidation and standardization of interfaces to the coresight subsystem. We will conclude with a status of our current upstreaming efforts and how we see the coming months unfolding.
OP-TEE (Open Portable Trusted Execution Environment) is the source code for the TEE in Linux using the ARM Trustzone technology. This component meets the Global Platform TEE System Architecture specification. Most of the code is generic. However, a number of platform specific characteristics are addressed, such as memory layout or board specific hardware IP. In this session, you can learn the steps to follow to port OP-TEE for your armv7 platform, as the ones that have been defined when porting OP-TEE to A80 (SWG-77). OP-TEE to the Allwinner A80 platform