96Boards is most obviously a hardware specification and website providing support and access to software downloads. The software is, to a certain extent, taken for granted, but it is the software that differentiates 96Boards from many other development boards. This session will start with a brief introduction to the 96Boards Software Reference Platform and then invite discussion about how to improve the platform and what should and shouldn’t be a part of the platform across the range of boards.
This session will go through the problems caused by decisions made in the early days of UEFI on ARM, how they are still hurting us - in expanding our validation as well as by providing poor examples for porters to new platforms. But also about projects underway to resolve this legacy once and for all. We will also cover changes to Linaro’s platform infrastructure, as well as our increasing involvement with EDK2 maintainership.
An introductory session of a system-level overview at Power State Coordination
* Focus on ARMv8
* Goes top-down from ACPI
* A demo based on the current code in qemu (and/or 96Boards)
* The specifications are very dynamic - what’s onging for ACPI and PSCI
This presentation will focus on beginner’s benchmarking best practices covering the three Rs: repeatability, reproducibility, and reporting. An experiment is repeatable if one team can repeatedly run the same experiment over short periods of time and get the same results. An experiment is reproducible if external teams can run the same experiment over large periods of time and get comparable results. Clear, concise reporting allows others to utilise benchmark results.
We get lots of questions from members during initial HW design, SW implementation and tuning of PM on their platforms. This session will address some of those questions and make general recommendations for new platforms.