- Period: (20110217-20110223)
Past reports : https://wiki.linaro.org/Platform/Android/Status
Burndown information : http://status.linaro.org
Key Points for wider discussion
Currently the way Linaro releases Android evaluation builds is being discussed at https://wiki.linaro.org/Platform/Android/ReleaseCycle
The Linaro toolchain in Android and the NDK (Native Developer Kit) is being discussed at https://wiki.linaro.org/Platform/Android/Toolchain
- The need for a 'Headless' Android build is being explored
- Deploying whole Linaro test images onto real hardware is not currently easy, some mechanism to do this needs investigating
Lots of work ongoing to define the Linaro Android efforts. Both the release cycle (https://wiki.linaro.org/Platform/Android/ReleaseCycle) and the toolchain (https://wiki.linaro.org/Platform/Android/Toolchain) have seen major discussions and these should be finalised soon.
- Patches have started to hit the mailing list with the virtual battery driver in review and hopefully pushed upstream for 2.6.39. Power management interfaces, USB composite driver API and hardware memory mapping all saw some attention.
Builds of Android continue to be produced at https://android-build.linaro.org/ and the team committed to more testing of these over the coming week.
- Framebuffer support to jstultz' git.linaro.org tree
- Beagle defconfig to jstultz' git.linaro.org tree
Risks / Issues
Kenjie Watanabe states that his company committed him to work in Linaro but he currently has no time for this. Noritsuna will discuss the problem with the president of his company next week (1 week). HIGH IMPACT as we have one less engineer for the team despite that resource being allocated to Linaro.
Currently the Linaro Android efforts are based on 2.6.37 but with Linaro moving to 2.6.38 and the upstream Android 2.6.38 kernel being available some rebasing efforts will be needed. John Stultz, Patrik Ryd and others need to discuss how this can be done in the smoothest way (1 week). Level of impact of the rebase is set to HIGH IMPACT as some amount of effort will be needed but that effort is unclear at this point. Will lower level after initial investigations if necessary.
The weekly engineering reports are a little light on information which is to be expected as this is the first week they were produced. Some coaching will be needed until the required standard is met (1 week). MEDIUM IMPACT as we need to convey the Engineering work that is being done but with a little coaching this should go away.
https://android-build.linaro.org/ is reporting an untrusted certificate when accessed, this needs investigating (1 week). Not a big deal and LOW IMPACT for now as visibility of builds is limited.
Platform/Android/Status/2011-02-24 (last modified 2011-02-23 15:12:11)