Power distribution automation and serial console controller on an ARM platform. OpenTAC is a community project using open hardware and free software. The hardware combines a PDU and serial console server in a single box and removes the forest of cables common to any developer desk or rack. Custom design PCB with full isolation of power and serial, support for 5V DC power, RS232 or UART serial, gigabit ethernet and per-device power consumption measurement. Implemented as a beaglebone-black cape and available in two variants, supporting 4 or 8 device channels respectively, to fit into a 1U case. Can be supplied with or without case. There is space inside the 4 channel variant for a small ARM server (e.g. cubietruck) with a SATA drive, making it ideal as a desktop or demonstrator unit. http://wiki.vero-apparatus.com/OpenTAC
Hands on training and a Q&A involving the Lab and LAVA Teams on how to create, submit and interact with hacking sessions. Additionally, a look at some of the issues people can create when they submit or re-submit jobs with inappropriate meta-data or to particular bundle streams, particularly how that affects LAVA Image Reports.
Key stakeholders are Hacking session users QA, LAVA team and Lab
One of the important technical novelties introduced with the recent release of Android Lollipop is the replacement of Dalvik, the VM which was used to execute the bytecode produced from Java apps, with ART, a new Android Run-Time. One interesting aspect in this upgrade is that the use of Just-In-Time compilation was abandoned in favour of Ahead-Of-Time compilation. This delivers better performance , also leaving a good margin for future improvements. ART was designed to support multiple compilers. The compiler that shipped with Android Lollipop is called the "Quick Compiler". This is simple, fast, and is derived from Dalvik's JIT compiler.
In 2014 our team at ARM worked in collaboration with Google to extend ART and its Quick Compiler to add support for 64-bit and for the A64 instruction set. These efforts culminated with the recent release of the Nexus 9 tablet, the first 64-bit Android product to hit the market. Despite Google's intention of replacing the Quick Compiler with the so-called "Optimizing Compiler", the job for the the Quick Compiler is not yet over. Indeed, the Quick Compiler will remain the only usable compiler in Android Lollipop. Therefore, all competing parties in the Android ecosystem have a huge interest in investigating and improving this component, which will very likely be one of the battlegrounds in the Android benchmark wars of 2015.
This talk aims to give an unofficial overview of ART's Quick compiler. It will first focus on the internal organisation of the compiler, adopting the point of view of a developer who is interested in understanding its limitations and strengths. The talk will then move to exploring the output produced by the compiler, discussing possible strategies for improving the generated code, while keeping in mind that this component may have a limited life-span, and that any long-term work would be better directed towards the Optimizing Compiler.
 The ART runtime, B. Carlstrom, A. Ghuloum, and I. Rogers, Google I/O 2014, https://www.youtube.com/watch?v=EBlTzQsUoOw
What software is required to make a standard hardware development platform a success? This session will invite input from a panel of representatives of multiple distributions, the toolchain and broader community.
Explains the building blocks involved in Security including TrustZone, OP-TEE, Trusted Firmware etc. Goes into detail on how Secure Boot Works.. and Why. Explains how a simple secure Trusted Application interacts with OP-TEE and works. Brief overview on how to port OP-TEE to an ARM platform. Opens discussions for Potential Challenges and Hardware limitations and how they can be overcome.
The concept of 'time' in Linux is encoded in many different ways, but the
most common one is based on the 'time_t' type that counts the number of
seconds that have passed since Jan 1, 1970. This type is currently defined
as 'long', which on 32-bit systems is a signed 32-bit number that will
overflow on Jan 19 2038 and likely cause all systems existing today to
In our presentation, we give an introduction to range of problems that
we see across user space and kernel, and we talk about the work that
we are doing to address some of these issues.
An example of a key system from a Clear Key point of view. Linaro implemented a sample CDM plugin for Chromium capable to exercise the EME implementation of the browser. The presentation gives an insight to the EME/CDM implementation in Chromium and the guidelines to integrating various DRM systems. We will present call flows with example classes, experiences learned, and example of things to watch out for.
Opening Keynote – George Grey, Linaro CEO
Speaker: George Grey
Date: February 9, 2015
★ Session Summary ★
Keynote Topic: Welcome to Linaro Connect and an update on the latest Linaro developments
★ Resources ★
★ Event Details ★
Linaro Connect Hong Kong 2015 – #HKG15
February 9-13th, 2015
Regal Airport Hotel Hong Kong Airport
Comparison of OVS implemented via ODP & vendor SDKs. Contrasting ODP linux-generic with the native Intel DPDK SDK and ODP implemented using the DPDK SDK on X86. Additionally comparing ODP linux-generic with ODP implemented using the Texas Instruments SDK on A15 ARM