Linaro_BW.jpg

Linaro Technical Requirements (May 2011)

Document Number:

Preliminary

Status:

[Preliminary (Pre LDS) | Mature (Post LDS) | Final (Feature Freeze)].

Last Edit

25th August 2010

Abstract This document describes the technical requirements for work that will be undertaken by Linaro during the November 2010 to May 2011 development cycle. This is a live document – visit http://wiki.linaro.org/TSC/RequirementsSpecifications/May2011/Specification for greater detail and latest status

Keywords VFP, ARMv7A, SMP, SIMD, Neon, UEFI, Device Tree, SFI, uboot, Thumb 2, ITM, STM, OCD, gcc, gas, gld, gdb


Contents


About this Document

Edit History and Expected Changes

This document is a live document being worked on by the Linaro Technical Steering Committee (see http://wiki.linaro.org/TSC) and the Linaro technical leads (see http://wiki.linaro.org/EngineeringTeam). Linaro executes on a six monthly cycle; the start of the cycle being a developer summit co-located with the Ubuntu Developer Summit (the next one is October 25th - 26th 2010). The technical requirements for the next cycle need to complete in time for that summit to start the engineering work needed to turn requirements into code.

TSC meetings and purpose

The following upcoming TSC meetings will discuss, agree and refine the May 2011 cycle technical requirements:

Date

Venue

Description

4-Aug-2010

Teleconference

Agree dateline. Agree / review combined requirements

18-Aug-2010

Teleconference

2-Sep-2010

Teleconference

15-16-Sep-2010

Face to face

Agree breakout and ownership of WGs and blueprints for October UDS

29-Sep-2010

Teleconference

13-Oct-2010

Teleconference

25-29-Oct-2010

UDS

Tasks

  • 4-Aug-2010
    • Integrate member requirements [DONE]
    • Fold in deferred requirements from Cycle 1 (November 2010) [DONE, revisited 24th August 2010]
  • Check for requirements already owned by a current working group
    • Power management
    • Kernel consolidation
    • Toolchain
  • Organise into
    • New requirements for existing work groups
    • Requirements for new working groups and special interest groups
    • Requirements needing more research

Terms and Abbreviations

Term

Meaning

ARMv7A

ARM Architecture V7, A profile

Device Tree

Data structure describing system device topology. Passed at boot time from the boot firmware to the kernel.

ITM

Instrumentation Trace Macrocell

LP

Launchpad.

LDS

Linaro Developer Summit – the place where plans for a release are formalised

Neon

ARM floating point vector processing engine

PPA

Personal Package Archive.

SIMD

Single Instruction, multiple data

SMP

Symetric multiprocessing

Thumb 2

ARM Thumb 2 instruction set

TSC

Linaro Technical Steering Committee

VFP

Vector Floating Point


High Level Objectives

The overarching objective for Linaro is to provide a foundation of work that downstream distributions can leverage to deliver their unique user experience on a broad selection of hardware platforms. In doing so, Linaro is aiming to cut the time and risk associated with OEM and ODM companies producing innovative devices seeking to leverage both innovative Linux distributions and cutting edge ARM architecture silicon. To achieve this, Linaro will:

  • Consolidate a wide variety of ARM hardware-related patches into a unified source tree.
  • Integrate and optimize the Linux development toolchain for ARM, including compiler, linker, debugging and profiling tools.
  • Ensure relevant graphics rendering pipelines are optimized for OpenGLES/2.0, and that drivers are integrated.
  • Provide tools that allow developers to customize and validate the reference OS components to their needs, possibly including proprietary extensions.


Development Process

Linaro engineering follows a date driven engineering process to ensure the various parallel development projects occurring within the working groups are brought together in a cohesive system level validation, applied across qualified hardware platforms.

To become a qualified hardware platform, a vendors hardware must have achieved the relevant requirements for inclusion in the official mainline as set by Linaro engineering on a release by release basis. Linaro uses a function called “landing teams” to manage this process on a vendor specific basis.

ldc.jpg

The diagram above outlines the approximate time lines associated with a generic Linaro development process from initial requirements and planning which occurs during the N-1 release cycle, and concluding with delivery on a specific day.



Cycles/1105/SpecificationCover (last modified 2011-03-25 18:15:55)