Define what levels of support to apply to boards and how they path that support levels can take Define how board support gets picked up (BOL) and phased out (End Of Life)

Give an overview of what is currently being done for Android toolchain benchmarking in Linaro. Discuss future enhancements we should look into. Agenda: * explain what I currently do each month * discuss some of the short-comings * discuss some of the future ideas we have and get other ideas on what we should do to improve this Goals: * decide what areas we should focus on related to android toolchain benchmarking going forward * get an idea of the effort required * does Andy have the time to do this on his own

Currently Linaro uses a PPA for the package Overlay, and unless the source package requires a -dbg package, no dbg symbol package is provided for it. Discuss about possible ways to make dbg packages available for the Ubuntu LEB own packages/changes, covering the currently solution for Ubuntu and if it can be also applied for our ppa/derived distro.

Linaro's platforms allow the engineers of tomorrow to work on today's cutting edge SoCs with the leaders in the opensource community. This session will discuss this and come up with some concrete goals to enable outreach programs. Goals: Create a set of milestones and plans to test-run educational programs Select candidate programs Discuss interns and projects that may be interesting Agenda: Establish Linaro's educational outreach goals Have Dave Pigott give an overview of the school that would like to work with Linaro Discuss a possible program for the school Discuss adding other schools Talk about logistics Zach to talk about getting a program at UT off the ground, sister school? Interns, we now have some, talk about projects Other

Afternoon engineering and hacking session for Android and Ubuntu Working Groups

Afternoon engineering and hacking session for Platform Working Group

Afternoon engineering and hacking session for Platform Working Group

This session will discsuss the current issues we're facing with the toolchain CI builds, looking for different solutions and discuss with the TWG how frequent the builds should be to be valid. This will also cover the validation plans for both native and cross Linaro GCC. More info at https://linaro-public.papyrs.com/public/4120/LINUX2011-TOOLCHAIN-CI

In this session we will talk about device tree on Android. Description ------------------ Linaro has a goal of creating a single runtime image that can run across SoC hardware. The Android team is supporting this effort by using a common Linaro Android tree as a base for all our trees and working to unify all the SoC trees into one. Once unification is done, device tree will allow us to re-factor basic support that was once compile time configurable into runtime configurable options. Having this support on Android early will help us towards this goal and ensure that our kernels can boot as device tree becomes more widespread. Linaro Kernel WG and OCTO have worked on getting Device Tree support accepted into the mainline kernel, and initial support for all recent member SoCs is available. Ubuntu images are already using Device Tree; the next logical step is to make Device Tree be used by default in Linaro's Android LEBs. This feature requires improvements to the Linaro Android builds to enable production of binary flattened device trees as part of the platform build. Also required is updating installation tools and u-boot to ensure that the FDT is used during the boot process as needed. Additional fixes in Android-specific kernel and driver code may be required. Acceptance Criteria ------------------------------- 1. LEB Android builds come with u-boot and kernel that have device tree support enabled 2. LEB Android builds include appropriate flattened device tree in the 'boot' artifact 3. Installing LEB images using linaro-android-media-create will yield an image with device tree being used by u-boot and kernel See https://linaro.papyrs.com/page/4112/ANDROID2011-FDT-LEB for the original description. Agenda ------------ TBD Goal of this Session ----------------------------- To brainstorm and generate concrete work items for landing device tree in all LEBs.

In this session we will talk about the Linaro Android QA process. Description ------------------ The Android QA process tests high-level functionality, characterizes failures and files bugs against likely subsystems. The current set of tests are listed here: ADB ADB over USB ADB over Ethernet All ADB commands Boot and Basics u-boot serial support android console output over serial android console shell over serial android boots to console shell android boots to UI Audio HDMI audio Audio output on jacks Audio input on jacks Video Out - HDMI All resolutions work Monitor recognized Best resolution automatically chosen Monitor hot-plug Video Out - DVI All resolutions work Monitor recognized Best resolution automatically chosen Monitor hot-plug Graphics Not-Accellerated Accellerated 2D Accellerated 3D Ethernet Ethernet configurable from command line Ethernet auto-configured at boot Ethernet integrated into Android connection manager Wireless Onboard wireless configurable from the command line Onboard wireless auto-configured at boot Onboard wireless integrated into Android connection manager Bluetooth Bluetooth available from command line Bluetooth integrated into Android Bluetooth framework Scanning devices in UI works Pairing with headset in UI works Modem USB modem works for the command line USB modem works with the connection manager SD SD-card mounted through fstab SD-card can be accessed through gallery Camera Capture works Save works Gallery display Video Playback Software Playback Hardware accellerated playback Playback all supported formats Powermanagement Suspend and resume Wakelock works clock tree in debugfs P-states (cpufreq driver) C-states (cpuidle driver) powertop App Support Can install apps Browser Calculator Calendar Camera Clock Contacts Email Gallery Messaging Phone USB Host USB Keyboard USB Mouse USB Device Gadget driver loaded Mass storage function (sdcard export) Ethernet function (tethering) Agenda ------------ 1. Introduce the current QA process 2. Brainstorm Goal of this Session ----------------------------- To share the current QA practice and get input on how to make it better.

Topics: - How to go beyond ubuntu core and linaro nano even more - Bootstrap x multstrap - How to replace the basic core package set

Live meeting of the Infrastructure Stakeholders.

Afternoon engineering and hacking session for Platform Working Group

Topics: - Discuss what would be interesting to support at u-boot - Extend PXE support? - USB booting? - Splash/display support? - What might help the Ubuntu server team?

Afternoon engineering and hacking session for Platform Working Group

We've had useful discussions about refactoring flash-kernel in the past, but they've not not (yet) come to fruition. Where are we up to, and when can we get things done? Other packages and image builds should be depending on this work, but cannot yet.

Afternoon engineering and hacking session for Platform Working Group

In this session we will talk about plans to more effectively parameterize Android builds across kernels, toolchains, compiler flags, etc.

In this session we will talk about automated Android testing. Description ------------------ Before each change is accepted it undergoes premerge testing. The tester, LAVA, runs a set of tests on a test build that contains the change. To get the most out of the test loop, we would like to identify areas of improvement so that faults found in this loop can be efficiently analysed and fixed. Agenda ------------ 1. Introduce what we have and what's happened recently with reviewing, building and testing. 2. Open a discussion on improvements/new features  * What improvements can we make in LAVA  * What improvements can we make in Gerrit  * Speed ups/efficiencies. Goals -------- 1. Discuss new tests 2. Plan for keeping a unit alive in a failed state 3. Plan for bootloader testing (JTAG) 4. Discuss the best way to capture and present test results for developers

In this session we'll talk about the future of Linaro Android and brainstorm ways we can make things better for the platform. Agenda: ICS Android's Pandaboard Build Community unification Phone builds/components RT Linux Android LTS (long-term-support) Single Android image Getting to 48 hour monkey Goals: Have a lively discussion about Linaro's future Android plans Generate ideas for future topics

Agenda of "Android Porting" session at Connect. ============================== This will be a "How-To" session on "Porting Android on New Platforms", including but not limited to following sub-topics:    * Android Software Stack overview    * AOSP Code structure    * Vendor/Device specific settings and HAL implementations/hooks.    * AOSP Build process.    * Android Boot process. * Android Debugging

Afternoon engineering and hacking session for Platform Working Group

Afternoon engineering and hacking session for Platform Working Group

Afternoon engineering and hacking session for Platform Working Group

Multiarch cross-dependency satisfaction (as currently implented in apt) needs -dev packages as well as plain lib packages to be make multiarch-ready and thus co-installable. This process is not yet well-specified like the library conversions, and it needs to be for package maintainers to be able to do this work. A related issue is changing whether the default of apt-get build-dep -a is to install for HOST or BUILD arch. The latter requires making library and -dev packages Multi-arch: same, the former requires marking all other build-deps Multi-arch: foreign. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646288 for discussion, along with the table at the bottom of: https://wiki.ubuntu.com/MultiarchCross Things to cover: Change apt build-dep -a behaviour? Guidelines for -dev conversion:  header moving  binaries (foo-config)  what else?

In this session we will talk about adding standard Linux developer tools to Android. Description ------------------ To improve the tools available for embedded developers that care about the core platform, kernel and user space code, the Linaro Android Platform team considers it important to provide tools commonly used by low level GNU/Linux developers. We continuously monitor and identify areas where porting and integrating those tools with Android will benefit the overall Android community. Discussion and reviews lead us to believe that focusing on the binary debugging front would be the most useful next step. The first part of this effort will be a research project that reviews debugging tools commonly used by embedded Linux developers, checking for applicability of those use cases to Android. We will also identify equivalent tools or gaps in the offering of the stock AOSP NDK and SDK. Potential candidates taken from pre-discussion that this research project will pay special attention to are: oprofile perf valgrind powerdebug Based on the findings from the effort above, a priority ordered list of tools will be defined and the engineering plan expanded accordingly. Acceptance Criteria ------------------------------- 1. Results of the research project with a significant list of tools for porting are published 2. Debugging tools identified are integrated and available in Linaro Android Images or the NDK See https://linaro.papyrs.com/page/4115/ANDROID2011-DEVTOOLS-1/# for the original description. Agenda ------------ Give a quick overview of what is already there (and what theoretically should be there) Discuss what other tools we need (and what tools are realistic to port) Best way to get there [see rsalveti comment on the BP whiteboard] Goal of this Session ----------------------------- To identify the tools Android needs and brainstorm and generate concrete work items to integrate those tools into Linaro's LEBs.

Currently, installing images on Versatile Express is a weird procedure with many manual steps. This impairs testability and makes life difficult for users. Kernel package upgrading also does not work smoothly. The aim of this session is to explore options for a less weird, more convenient and more robust deployment mechanism. Topics include: * Getting closer to full SD-based boot * Firmware-based image reflashing

Topics: - Describe what is currently supported at the cross-buildd - Go over the issues, discuss about how to improve it, and what kind of features do we want to improve/develop More info at: https://wiki.linaro.org/Platform/DevPlatform/CrossBuildd

Session jointly led remotely by Vincent Guittot and locally arbitrated by Tony Mansson. In this session we will talk about how Android can exploit the benefits of full Idle Support.

Topics: - Go over the issues we had during the Oneiric cycle - 1 month x 6 months cycle - Feature planning (present how Linaro plans the engineering work) - How to manage SRU and FFe - Package upload (should we create a Linaro upload group for Linaro packages?)

Afternoon engineering and hacking session for Platform Working Group

Afternoon engineering and hacking session for Platform Working Group

Topics:  - What is necessary to have a working multitouch demo with Ubuntu LEB?  - What kind of demo do we want/need?  - What hardware should be used, and which board should we try to support? More details at https://linaro-public.papyrs.com/public/4121/LINUX2011-MULTITOUCH-DEMO

Afternoon engineering and hacking session for Platform Working Group

Topics: - How to improve the relationship - Work on simliar features every cycle - Hardware support and LT - Ubuntu with Android image?

Currently for every kernel flavour we need the following packages: - kernel-headers-abi - kernel-headers-abi-flavour - kernel-image-abi-flavour - kernel-image-abi-flavour-dbgsym - linux-tools-abi-flavour - linux-tools-common Until we have one single kernel that could support different flavours, we need to support having different packages at our overlay. Common issues we have with the current solution: - DKMS depends on linux-headers/image-generic - How to depend on a common and single headers package - same dependency issue with the debug package This session is about discussin possible ways to fix this long standing issues at the Ubuntu LEB, and future planing on how to properly add new flavors in the future.

In this session we will consider Android Build System performance during last 6 months, what was good, what bad, what was done from LDS11.05 plans, what was not, how recent Android team workflow affects older plans. Then, we'll consider improvements to Android Build. This may include: tabbed build organization, commandline build launching, easier parameterization, test-result co-location, etc. Goals: Create a set of plans and milestones to improve how android-build looks and runs.

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.

We would like to package metadata with the Linaro (Ubuntu and Android) images. The purpose is to pass information about the image to linaro-(android-)media-create such as information related to live builds or capabilities to be matched with hwpacks.

Topics: - Go over the current test cases and show what is currently tested - How to hook Offspring builds into LAVA as soon they are completed? - Supporting different test bundles across images and platforms - Extending test support: - Hardware support, such as wifi, bluetooth, sound - Regression/smoke test for LEB images

Afternoon engineering and hacking session for Platform Working Group

Afternoon engineering and hacking session for Platform Working Group