Planning to take glproxy from a proof of concept level to a library suitable for integration into a real-world application like glcompbench (for example).

Planning session for work needed to support UCM on Android for the Linaro development boards.

The session is driven by Linaro Release Team. The following topics will be discussed: * current release process - what's the current process? * release internals - how the release works? * the road to continuous integration - how the CI is going to transform the release?

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

Supporting large scale testing of kernel trees and defconfig in the LAVA lab is a high priority engineering effort across all Linaro engineering and Landing Teams for Q4.10. This organization wide effort imposes a growing list of requirements that LAVA team has started to work on during Q3 and will focus on driving forward during the Q4.2011. This effort involves improvements to the lava dashboard to ensure that the build and test results data can be efficiently consumed by kernel engineers improvements to the lava dashboard to make it easy to follow every step of a submitted job from the scheduler to the job submissions step. increase of capacity for all LEB board types deployed in the lava-lab to a level suitable to continuously track 20+ kernel branches with multiple defconfigs each. improvements to lava job submissions tools that make it easy for services like the kernel CI service to hook link from their build page to the scheduler job and the results. The goal of this session is to discuss user stories around LAVA components for driving continuous integration testing and results tracking through LAVA. Session Notes: Currently the kernel is cross built in ec2 by jenkins -- build results are submitted to the dashboard and if successful a test is run in LAVA. http://validation.linaro.org/lava-server/kernel-ci-views/index attempts to convey a summary of the results. Current process of getting your own tree is manual - talk to Deepti to get your tree included. Wishlist: Want to able to use the set up topic trees for temporary testing. Maybe need to make it easier for KWG devs to set up trees for themselves We might want to use per-user configs so that users can select the trees/configs they care about Per-user reports and a web form so they can submit git tree, branch and config for a one-time or regular testing of their tree per-tree specification of tests to run Determine which tests to run with the new kernel: ACTION: mwhudson to submit mp to change this ltp hw enablement tests PM functional tests Store the kernel version (uname) so that we can cross-reference this Build results notification (by email, RSS feed) Can just do this in Jenkins for now Want to do this in LAVA RSS ok for now Weekly build-status digest email for the community? Deepak to do this manually for now John's builds don't appear on the tree view Waterfall view perhaps not appropriate for one-time builds Should use tags for grouping results (now that tags exists) deepti to change jenkins jobs to use tags Add tagging support to dispatcher so the results get tagged similarly View for test/build combination Easy way to see last successful build for a test/build Waterfall-ish view of test suite vs test/build history Also improve bundle view Anti-wishlist: Builds of out of tree configs Basically, developer should commit the Kconfig changes to the tree ACTION: start tagging build and test results (with LAVA tags) Figure out how our read-only tags look like (since tags cannot be changed afterwards). Mouse-over git-describe: show the shortlog

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.

Linaro now has around 40 sub-domains, all of which are perceived as individual sites by search engines. Only 5 of these are linked to from the linaro.org home page and many will not be getting significant levels of traffic. We need to bring these together into a logical structure to not only help accessibility, but also to boost our ranking in search results. We want to discuss this structure and if there is a reason to keep any of our online services as sub-domains.

Discuss support for EMM4.5 specification Etherpad @ http://summit.linaro.org/uds-p/meeting/19259/linaro-kernel-emmc4.5/

Continue discussion of EMMC 4.5 and UFS

Alternative to sched_mc and hotplug

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

Discussion with David Brash of ARM

A training session guiding users through common use-case scenarios for BZR users.

Private

We want to provide Monthly Engineering Views on status.linaro.org. Alexander can provide information about this. Initial Requirements for Discussion are here: https://wiki.linaro.org/Platform/Infrastructure/Specs/MonthlyViews

Planning for a Linaro graphics working group project to do a webkit port that leverages prior work on the OpenGL ES 2.0 backend for cairo. Link to requirement: https://linaro-public.papyrs.com/public/4146/GWG2011-WEBKIT-CAIRO-GLES/#

Discussion of how we map upstream-oriented kernel development to the Linaro process Etherpad @ http://summit.linaro.org/uds-p/meeting/19264/linaro-general-upstream-process/ Problem definition, scenarios and proposals https://docs.google.com/a/linaro.org/document/d/1Inj3Esvk4Lbqe5PN7NHnK1WKRaM_5e9B6htKN6hDBqk/edit?hl=en_US

Feedback on the LT performance

RedHat — Matthew Garrett

Continuing cross-distribution meeting series, aimed at sharing ideas and problems that people may have related to ARM porting ARMv8 Standardization Multiarch Triplets

Continuing cross-distribution meeting series, aimed at sharing ideas and problems that people may have related to ARM porting ARMv8 Standardization Multiarch Triplets

We'd like to use Firefox as a toolchain testsuite and a benchmark. Discuss approach, existing testsuites, and the parts to benchmark. I would like to check if these workloads are the interesting ones? Load and rendering of a good set of web pages JavaScript Start up of browser Shutdown of browser Imaging - or are we covered by EEMBC DENBench, ConsumerBench Input data that can be redistributed? I would like to hear the views on this and understand how to proceed. Can Mozilla share the tp5 pages? Is it necessary that the content is redistributed, or can it be internal to the tcwg? How to proceed with cross-compiling? I would like to use a multistrap/xdeb approach, but it seems hard. Is it OK to create a chroot with everything installed, zip it up and reuse it for some months? Configuring the build for different flags and features Should we use .mozconfig, myRules.mk, and myConfig? If debian package is used for building, can myrules and myconfig still be used? Which benchmark(s) to choose for browsing? ARMBBench EEMBC BrowsingBench Talos with a set of pages Would it be possible to integrate ARMBBench or EEMBC BrowsingBench in the Talos framework? System level testing What are the plans for system level? Is there an overlap? Can we benfit, work together... When done, should the toolchain browsing benchmark tests be run in LAVA?

This will be a presentation talking about how to get involved and participate in the Linaro community. The primary audience is: * people who are transitioning from propriety to open source * community members interested in getting involved in Linaro Topics included:   * working in open source - differences from properietary   * working with Linaro   * leasons learned from a community member's success story