Linaro Android Google Collaboration
This blueprint calls out ways to improve collaboration with Google. After an initial ELC meeting and UDS brainstorming session its time to follow up with the ideas that were presented at ELC.
Blueprint information
- Status:
- Not started
- Approver:
- Zach Pfeffer
- Priority:
- Undefined
- Drafter:
- Zach Pfeffer
- Direction:
- Needs approval
- Assignee:
- Zach Pfeffer
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Roughly in P1.2, Android Toolchain packages, High, Provide Linaro Toolchain and Platform code ready for consumption by android product builders, Android
from
https:/
We may need another TR.
See the "Meeting with Google at ELC / Android Builders 2011 San Francisco" email for the original context.
From
> [1] Redistribution of binaries, per SoC grid
As a Android engineer I would like a per-SoC grid detailing what binaries are available.
linaro-
From
> [2] Development environment, non-Linux based development
As an Android engineer I would like to use the Linaro build environment for non-linaro builds to support Mac and Windows Android development of the platform and the kernel.
We have a topic for this in
https:/
From
> [3] Divergence from the open source, clean patch-set
As an Android engineer I would like a clean patch set on top of a tip kernel for supporting Android builds with full multimedia and graphics support.
linaro-
From
> [4] Memory Management
Jesse's taking care of this.
From
> [5] Platform independence, unify platform code, platform camp
As an Android engineer I would like better platform independence so that I can use the same platform across SoCs.
linaro-
As an Android engineer I would like to have a platform camp where I could go and get support for bringing up Android on an new platform.
linaro-
