The Kernel Consolidation 2.0 lead project aims to identify and work on reducing areas where vendors need to ship out of tree modifications and additions to kernel frameworks in order to deliver key functionality. In this session we will discuss how we are going to organize and coordinate this work in conjunction with other efforts in the community.
Linaro is using OpenEmbedded as part of its engineering builds. We propose to discuss how Linaro is using OpenEmbedded for its use cases and how we can improve our contribution to YOCTO project. The goal of the discussion is to identify areas in which Linaro can help.
ARM FDPIC toolset and kernel patches makes it possible to boot a mmu-less Linux kernel and support userland applications which rely on dynamic loading. No source change are needed to compiler the application (compared to the BFLAT model). The presentation will focus on the toolset structure and characteristics and give some insights on the FDPIC ABI.
In this session, Tim Bird will discuss the mainline status of several ARM SoCs used in mobile products. The average phone uses kernel software that is 3 years old, 20 versions behind mainline, and has 1 to 3 million lines of code out-of-tree. Tim will describe the “Device Mainlining” project of the Linux Foundation CE Workgroup, which seeks to address this problem. Some of the activities of this project are:
* publishing tools for mainline analysis
* finding big areas where multiple vendors have code out of tree
* identifying institutional barriers to corporate developer mainlining, and addressing them through education, training, and collaboration
* working with upstream to address deficient sub-systems or needed maintainer assistance
It is hoped that discussion will ensue about ways to continue enhancing this work, to get more SoC code mainlined.
Android doesn’t give application access to hardware over bus interfacing APIs like I2C, SPI, GPIO, UART, etc. This is going to change in future as Android apps needs to work with multiple different devices like sensors, controllers, etc directly to meet the efficiency and speed required. In this presentation we will introduce the APIs, architecture design and a working demo.
It's not easy, perhaps not possible, to establish a common boot architecture meeting the security needs of OS vendors, SoC vendors, BIOS vendors and OEMs across all market segments. This informal session evaluates the current boot architecture(s) and immediate security needs of the ARMv8-A ecosystem. This is an opportunity for all interested attendees to meet and set the agenda for more specific discussions during the week.
This session is a continuation of the Advanced Toolchain Usage series started at LCU14. These sessions will cover a variety of topics, such as: symbol-versioning how-to, what the compiler can’t know, search paths (LD_LIBRARY_PATH, RPATH, RUNPATH), versioning structures, ELF sections on ARM/Aarch64, addressing models and performance considerations (PIC, short branches, long branches, relative addressing, trampolines, relaxation, etc), data alignment performance considerations on ARM/Aarch64, Timers, Timestamps and the VDSO, branch prediction extensions vs hardware auto branch prediction. Out-of-order execution vs in-order execution performance considerations, and others.