(Android) LEB Acceleration with Proprietary Binary Overlays

Registered by Zach Pfeffer

In this sessions we will talk about how to integrate proprietary binary overlays onto LEBs.

Description
------------------
The Linaro Platform unit recognizes that at least some of the binary drivers and firmware needed to deliver an accelerated LEB experience will be provided under a restricted license.

To unblock full enablement while maintaining our open development approach (which makes available all open-source components as well as the build service), the Linaro Android LEB program needs to grow support to supplement LEB builds through an overlay mechanism, containing acceleration binaries. The situations targeted are:

Binaries available on a login protected vendor or third party site
Binaries provided for download behind a click through form
Binaries available for download freely, but requiring user to accept a click-through license upon install

This work will include tools and LAVA improvements that will allow users and the validation lab to deal with the new binary components. It will also deliver proof of concept refactoring of Android Platform code to build without the binaries to support our pure upstream builds.

Acceptance Criteria
-------------------------------
1. Linaro Android Overlay package format defined and published supporting shipping an overlay file tree alongside with a license text
2. Linaro Android Overlay packages support including binaries requiring user acceptance or acknowledgement of included license text
3. Tools supporting the installation of Linaro Android Overlay packages by humans is available
4. Tools supporting the automated installation of Linaro Android Overlay packages, for LAVA, is available
5. LAVA supports managing LEBs with Linaro Android Overlays: one or more LEBs with overlays are automatically tested in LAVA

See https://blueprints.launchpad.net/linaro-android/+spec/linaro-platform-android-device-tree for the original description.

Agenda
------------
Explain the present status of Proprietary binaries in our builds.
Discuss the Blocking issues in the present distribution of binaries with linaro android.
Discuss a solution for end users to access the proprietary binaries.
Discuss a solution for LAVA to have access to the proprietary binaries.

Goal of this Session
-----------------------------
To brainstorm and generate concrete work items for integrating proprietary binaries with Linaro LEBs.

Blueprint information

Status:
Complete
Approver:
Zach Pfeffer
Priority:
Essential
Drafter:
vishal
Direction:
Approved
Assignee:
vishal
Definition:
Approved
Series goal:
Accepted for 2011q4
Implementation:
Implemented
Milestone target:
milestone icon connect-q4.11
Started by
Zach Pfeffer
Completed by
Zach Pfeffer

Related branches

Sprints

Whiteboard

LEB Binary Overlay

Graphics/Wifi/BT
Packages into built images
Public key authentication
iMX53 binaries for Ubuntu
Binaries
Multimedia binaries
Can't do the work without the PoC
Unifying Ubuntu and Android kernel
Handle Ubuntu and Android
#include CONFIG_ANDROID
Config options
Protected through a click through license, SSH key
Solution
    l-a-m-c
    android app to install
Allow Linaro to ship binary
    SSH
    Single click-through
Only go to one place
    igloo doesn't have builds
Infrastructure asks
Register with igloo
Click through
Everyones going to be different
Similar solution for Ubuntu
Click through
How can we get to the same innovation to get a pre-download for Ubuntu?
We need a pre-click through PPA
Need a click through pre-license
No license agreement for iMX53
No license agreement for Samsung
Fork of Stagefright

(?)

Work Items