/!\ Historical information; the current topics are listed in Releases/1105/TechnicalTopics /!\

This page holds technical requirements as they looked previous to TSC input at the September TSC meeting.

Power Management

  • Gokul, Amit K. and Loïc M.
  • WG: Power Management
  • Commentary

Ref

Name

Description

Reference

PM1

PM frameworks

Improve behaviour of existing Linux PM frameworks on the ARM architecture

Details

PM2

Tools

Tools to make it easy for developers and users to track PM-offenders

Details

PM3

Multi-core

Enhance kernel support to minimise power consumption on multi-core platforms

Details

Memory Regions and Reserving Memory

  • Sree, Paul M. and Loic M.
  • WG: Kernel Consolidation, Multimedia
  • Commentary

Ref

Name

Description

Reference

MR1

Memory Regions

Memory regions support enabling use and evacuation of a given region of memory.

MR2

Contiguous Allocation

Hot-unplug desired region and allocate contiguous memory, while allowing other usage.

Samsung Use Case

MR3

Memory Power Control

Map main-memory power domains to regions, allowing a domain to be evacuated and powered down.

Android Strategy

  • Yves, Loïc, Scott B.
  • WGs: Kernel Consolidation, Toolchain, Power Management?
  • Commentary

Ref

Name

Description

Reference

A1

Early build

Bootstrap minimal infrastructure: setup mirrors, a daily build and add support for basic developer platforms

A2

Benchmark (tentative)

Capture information on boot time and size of binaries to measure improvements over time

A3

Toolchain

Provide pre-built Android toolchains and integrate the outputs of the Linaro Toolchain Working Group in the Android deliverables: build downloadable Linaro toolchain for Android, and bootstrap Android using this. Test, maintain and improve based on WG efforts.

A4

Kernel

Setup a base Linaro Android kernel tree: pursue development of missing kernel features/patches upstream, setup common Linaro Android kernel tree, (tentative) demonstrate Linaro Linux features in Android

Boot Interface and Device Trees

  • Gokul, Loïc and Grant Likely
  • WGs: Kernel Consolidation
  • Commentary

Ref

Name

Description

Reference

Your items here

kernel and boot stuff -- sorry

Ref

Name

Description

Reference

K1

(linux) reserved memory, memory hotplug, large continuous memory allocation etc.; makes our tree long-lived

K2

(linux) SMP + Thumb2 + highmem standard configuration: build all kernels SMP and runtime disable SMP on UP; SMP + highmem fixes; build all kernels T2 by default; (tentative) kexec across the board

K3

(linux) Consolidation: continue making code more common across mach-* and plat-* subtrees; reduce amount of duplicated code by x % across an agreed-upon subset of SoCs

K4

(linux) Android: help upstream kernel patches

K5

(linux) SD performance: write tools to measure the performance of the SD subsystem and of specific drivers, identify bottlenecks and try to improve performance

K6

(linux) kernel configuration policy and toolkit: tune our configs and harmonize across SoCs, have a linaro kernel config policy and documentation in using the toolkit for specific use cases, production, or tuning for specific use cases

K7

(linux + u-boot?) boot performance: track boot time up to userspace, parallelize, improve

K8

(u-boot) fastboot implementation: easier Android development but unlikely to be used in production

K9

(u-boot + linux) continue DeviceTree, finish u-boot implementaiton, support more SoCs and more devices in each SoC

Graphics Acceleration: Kernel to Userspace

  • Andrea G., Alexander S. and David R.
  • WGs: Middleware/Graphics
  • Commentary

Ref

Name

Description

Reference

G1

GL ES 2.0 toolkit support for distributions

make toolkit backends fit for shipment in binary distributions

draft for technical requirements

G2

toolkit rendering for ARM GPUs

optimize toolkit graphics rendering through GL ES 2.0 backends and use of co-processors (NEON, vfp)

draft for technical requirements

G3

compositors for GL ES 2.0

optimize graphics subsystems for major compositors

draft for technical requirements

G4

mesa software rendering for GL ES 2.0

add missing features to mesa GL 2.0 software rendering to allow application testing and development with software rendering

draft for technical requirements

G5

kernel support for ARM GPUs

prepare kernel frameworks for ARM GPUs

draft for technical requirements

G6

validation & test apps for GL ES 2.0

validation and performance applications for GL ES 2.0

draft for technical requirements

G7

consolidated dri framework for ARM GPUs

share a single DRI framework and make vendor specifics pluggable

Multimedia: Optimization and Consolidation

  • Andrea G., Alexander S. and David R.
  • WGs: Middleware/Multimedia
  • Commentary

Ref

Name

Description

Reference

MM1

optimize software codecs

optimize existing gstreamer and ffmpeg software codecs using NEON (prioritize codecs that usually have no hw acceleration)

MM2

common omax core

work on a common omax core framework shared across vendors (e.g. bellagio, gstreamer-omax)

MM3

multimedia validation suite

improve existing or create freesoftware multimedia validation suite for functional & performance testing of full gstreamer stack (video/audio playback, recording, etc.)

MM4

low power audio

low power compressed and uncompressed audio playback

Virtualization

  • Paul M. and your name here
  • WGs: Kernel Consolidation
  • Commentary

Ref

Name

Description

Reference

V2

Paravirtualization

Run cooperating OSes using software virtualization.

V3

Full Virtualization

Full hardware virtualization (requires virtualizable hardware, Eagle etc.).

V4

Full Virtualization qemu

Full hardware virtualization based on emulation of hardware virtualization.

Developer Platform

  • Steve L., Roger T., Amit K.
  • Platform: Foundations
  • Commentary

Ref

Name

Description

Reference

DP1

Host developer tools

Provide a Linaro image that includes a full suite of tools for Linux development on ARM hardware

DP2

Build developer tools

Improve integration of desktop-based development tools for embedded development in Ubuntu

DP3

Android build environment

Streamline the setup of environments that can be used for building both Android apps and Android itself

Toolchain

Ref

Name

Description

Reference

T1

Performance

Improve the performance of typical code on current and near-term ARM Cortex-A architectures

T1.1

Continue to improve the time-based performance of GCC 4.5 on the Cortex-A9 with NEON

T1.2

Widen and continue to improve the string routines (memcpy, strcpy, etc) in GLIBC, Bionic, and newlib on the Cortex-A9 with NEON

T2

Dev tools correctness

Fix gross errors in the core toolchain

T2.1

Continue fixing GDB for Cortex-A9 with NEON and SMP on Linux

T2.1

Complete and verify Valgrind support for Cortex-A9 with NEON

T3

Dev tools expansion

Extend the development tools to match the state of the art

T3.1

Investigate the state of the art in developer tools and recommend future areas

T3.2

Enusure oprofile supports Cortex-A9 with NEON and SMP

T3.3

Extend and tidy up the OpenOCD support for Cortex-A8 and Cortex-A9 with NEON

T4

Validation

Validate the performance and correctness of any outputs

T4.1

Define platforms (phone, tablet, ...) and workloads (video decode, web browsing, ...) to optimise against

T4.2

Implement an open, sharable set of benchmarks that represent the workloads

T4.3

Provide regular benchmarks results showing any improvements

T4.4

Use the toolchain in real, large projects such as Ubuntu, Meego, and Android and fix any reported issues

T5

Consumption

Be available in native and cross forms on the most common GNU/Linux-based systems

T5.1

Maintain a Linaro GCC 4.5 branch that gives timely access to any improvements

T5.2

Track GCC 4.6 such that a Linaro GCC 4.6 is available shortly after the FSF 4.6 release

T5.3

Make Linaro GCC 4.5 available in major operating systems such as Ubuntu N

T5.4

Make a preview of Linaro GCC 4.6 available in major operating systems such as Ubuntu N+1

T5.5

Provide cross-compilers in major operating systems such as Ubuntu N

T6

Emulation

Ensure support for usable Cortex-A8 and Cortex-A9 platforms in QEMU

T6.1

Improve the emulation performance

T6.2

Add complementry support for the other toolchain outputs such that most features can be demonstrated or trialed under emulation

Infrastructure

  • Scott B., Steve L.
  • Platform: Infrastructure
  • Commentary

Ref

Name

Description

Reference

I1

Continuous integration

Setup and maintain a continuous integration infrastructure. Automated builds and tests of individual projects on a continuous basis.

WG, LT

I2

Patch Management

Investigate & deploy patch management system allowing us to get metrics about patches and track state of patches.

WG, LT, Foundations

I3

Derived Archives

Complete work and tools postponed from last cycle.

WG, User Platform

I4

Image Building

Customization of LexBuilder for Linaro image building needs. Integration with automated QA.

User Platform, LT

I5

Quality Assurance

Testing of images. Design and implementation of automated tests. Design of test plans.

User Platform, LT, Foundations

I6

Project Management

Investigate, implement change in LP for improved project management and reporting.

WG, Foundations, User Platform, Release Mgmt

Cycles/1105/TechnicalTopics/PreTSC (last modified 2011-03-25 18:15:31)