-- Current state of ACPI on ARM -- Support/backing for a longer term organization (i.e., mailing lists, web sites, further meetings...) -- Use of _DSD device properties -- Follow-up on others items from the last meeting (mostly promised documents) All of this sort of stuff is on [email protected], so folks can go sort thru the archive for more details, if they'd like.

Read more

Previous introductory tutorials on LAVA have focussed on virtual platforms. This is an end-to-end tutorial as a basis to evaluate LAVA with one or more embedded targets using U-Boot. It integrates both a physical bootloader device with a stand-alone installation of LAVA, along with a simple PDU for target power control which is based on off-the-shelf Arduino components and fully integrated with pdudaemon. It covers device requirements, device configuration for 32- and 64-bit platforms, use of lavatool, tftp, pduclient and logging via the LAVA web interface and /var.

Read more

The RP Enterprise Kernel is the combination of Reference Platform topic branches. The goal is that, members of Linaro will in combination contribute to a kernel branch that incorporates the activities and development of all members. The topics will be targeted towards tip, and rebased once the kernel has moved from rc to stable. As in, if the current RC is for 4.4, then all topics will be based on that kernel. Once the 4.4 kernel is released, all patches that were not accepted into the kernel release, will be rebased to the next developement kernel. In the case of this example, rebase from 4.4 to 4.5.

Read more

ATOS is an Auto Tuning Optimization System that is able to find automatically the best performance/size tradeoff from a build system and a training application. The input of ATOS tools are a build command and a run command. From the build command, ATOS will infer an internal build configuration that it will run with different sets of compiler options. These build configurations are executed with the run command from which code size and performance will be extracted. From the set of build configurations that ATOS explores, one can extract the preferred trade-off between code size and performance. The extracted build configuration can be archived and replayed later in order to generate the optimized executable without any modification into the initial build system. The nice property of ATOS is that NO modification of the sources or the makefiles are needed. ATOS can work on any large/deep project, as soon as the compiler used is gcc or LLVM under Linux.

Read more

Last year, to provide at least a stop-gap solution to the problem of getting platform support upstreamed into EDK2, I created a separate repository called OpenPlatformPkg as a way to start keeping and organising opensource platform support. This presentation goes through how to use and contribute to this repository, as well as providing a bit of an update about what is going on with getting platform code with EDK2 solved upstream.

Read more

The concept of Enterprise Firmware is a fairly new one for ARM, and pretty much started in LEG, while ARM Ltd. was still focusing on mobile platforms. Also, in parallel, several partners did their own work internally without sharing, resulting in multiple implementations of what should be a standard platform. To make our partners successful, we need to help them - by leading through example - to get more done. This talk covers both the commercial importance of aligning the ecosystem and some of the technical challenges to overcome, and what ARM and Linaro are planning to do about it.

Read more

An overview of collaborative effort done by Builds and Baselines, LMG, 96boards and HiKey landing team in getting HiKey integrated into AOSP. Covers work on the AOSP common.git branches, cross kernel/bootloader feature work that provides more form-factor like integration not commonly found on devboards, lessons learned, etc.

Read more

- What we mean by EAS core and how it's distinct from the other components - also why it's so difficult to get it merged. (This is driven by key partner concerns). - An update on misc work that's underway to resolve the upstreaming. - Misc load balance pathway enhancements - Wakeup pathway mods (cleanups, basic big.LITTLE capacity awareness etc) - Periodic load balancer mods. - Energy model expression (why this is important, partner perspectives/experience and bottlenecks) - Proposals to get an expression into the mainline - Optional boot-time auto-detection of capacity over-ridable by sysfs - Leveraging the merged power coefficient bindings - Leveraging the OPP bindings .. to effectively get to EAS' struct sched_group_energy. - How we are structuring things to ease upstream acceptance. What's helping, what's not, where partners can help.

Read more

ILP32 is a programming model that may be useful on AArch64 systems for performance and also for legacy code with 32-bit data size assumptions. We combined ILP32 support from upstream projects with the LEAP distribution to enable experimentation with this model. This talk discusses the relative benchmark performance of the LP64 and ILP32 programming models under AArch64.

Read more

An overview of the infrastructure the Linaro LMG team is using for the ART development, describing some of the interaction between Gerrit, Jenkins and Lava, the differences between target and host tests as well as a high level overview of most of the Linaro ART Jenkins tests. The presentation is aimed at providing a better understanding of our infrastructure to any ART new starter as well as to anyone that is interesting in putting together a similar infrastructure for any other software project.

Read more
Page 5 of 10« First...34567...10...Last »