Overview

Linaro Evaluation Builds for Android target low cost development boards for Linaro Member SoCs and aim to feature a fully enabled Android experience. This document sets the scope of the BSP delivery required from Linaro members to enable Android Platform to produce such builds.

The deliverables documented on this page are designed to allow Linaro android platform to work on the following topics:

  • release fully enabled android images for low cost development boards to the public (LEB).
  • review, consolidate and upstream (consolidated) HALs required to achieve a full enablement of member SoCs

  • validate and benchmark fully enabled builds as part of Linaros Validation efforts (LAVA)
  • integrate and show Linaro Working Group output and performance optimizations into LEBs

Features + Deliverables

During Android effort Ramp Up, Linaro Android Platform relaxes the requirements from "full enablement" for the sake of ensuring that members can meet those requirements. Hence, for now the following features are expected to be delivered:

  • Boot Android to Launcher screen
  • Graphics (accelerated SurfaceFlinger support)

  • Audio (preferably ALSA)
  • Hardware Accelerated Video Playback solution supporting main codecs like MPEG-2, MPEG-4 and H.264
    • preferred: OMX component compatible with stagefright
    • or: open-source stagefright fork together with OMX components
    • or: open-source gstreamer based stagefright replacement with binary gstreamer codecs
  • USB + Ethernet network support in kernel
  • Serial console
  • HDMI
  • MMC/SD support (kernel + bootloader)

To qualify for adoption by the Android Platform Team, members are supposed to deliver:

  • a freely redistributable flash tool compatible with ubuntu maverick and above (if the target board requires)
  • kernel
  • open-source bootloader
  • android platform sources + userspace driver binaries (see below for details on this)

Binaries

While we aim for a full-open source android platform, Evaluation Builds can be supplemented with binaries to meet the enablement goals mentioned above using one of the following distribution options:

  • binaries can be hosted with a redistributable non-click-through license in git.linaro.org
  • binaries can be hosted outside of git.linaro.org such that dropping them into a build coming out of the git.linaro.org hosted tree will yield enablement without further modifications; in this case, git.linaro.org hosted parts must build and run in non-accelerated mode without the binaries being available. However, in order to qualify for a LEB the binaries must be distributed in such a way that non-humans can legally download and install them (e.g. for use in a open validation farm setup).

To ensure that android platform team is legally allowed to work on consolidating and upstreaming non-differentiating code differences across member goals, we require one of the following:

  • copyright assignment and patent indemnification for the code delivered by members
  • or copyright indemnification to enable the android platform team to develop and upstream consolidated solutions based on member BSP code
  • any other of legal arrangement that ensures that Linaro can upstream all or parts of the BSP code delivered to the google open-source project under the Corporate Contributor License Agreement.

Hardware

  • 4+ Boards with accessories must be supplied to the Linaro Android Platform Team
  • 4+ Boards with accessories must be supplied to the Linaro Validation Farm
  • more boards are typically required for the Landing Team; the number of additional hardware required for LTs to support the Android LEB is out of scope of this documents; for details contact Linaro VP of Member Services.

internal/archive/Platform/Android/EvaluationBuild/MemberDeliverables (last modified 2013-08-29 07:25:31)