linaro-dev

linaro-dev@lists.linaro.org

4332 discussions

Should we include patches sent to devicetree-discuss in our stats?

by Guilherme Salgado

Hi folks, There is a significant number of patches sent to devicetree-discuss that were CCed to patches(a)linaro.org and thus will be counted when generating our patch stats. However, if this is just a mailing list for discussion and the patches are actually being sent to the lkml (or other ML like linux-arm-kernel) as well, they will end up being double counted, which is not what you want. I'd appreciate if somebody could clarify to me what's the purpose of the devicetree-discuss ML and whether or not we should be ignoring patches sent there. (Note that even if the right thing to do is to ignore patches sent there it's fine, for simplicity's sake, for you all to continue CCing patches sent there to patches(a)l.o -- we'll just ignore them when generating stats). Cheers, -- Guilherme Salgado <https://launchpad.net/~salgado>

15 years

[RFC] SMARTT - System Metrics gathering tool for Graphics and Multimedia

by Avik Sil

Hi, SMARTT (System Metrics - Annotation Recording and Tracing Tool) is a tool to capture and display system metrics data from the system. It's mainly targeted for system metrics that are interesting for Graphics and Multimedia WG for measuring and analyzing performance of their tools/applications. It has been designed and developed by Sudip Jain of Multimedia WG for the Linaro 11.05 cycle [1][2][3], and packaged by Kunal Goel of Developer Platform team [4]. A brief overview of the tool. It is a distributed application where the systems metrics are gathered by smartt-server running on the target system. At present, it gathers metrics from perf (smartt-perf), top (smartt-top) and a GStreamer based media player (smartt-player). A smartt-client app connects to smartt-server to receive and display all system metrics in real-time. It has been decided to continue to develop and maintain this tool for Linaro 11.11 cycle. So inputs are required from the intended users of this tool: * the feature they would like to have it included in the tool * the metrics data they would like to add * design of the tool etc. Please share your inputs and review comments on this tool. Regards, Avik [1] 11.05 BP: https://blueprints.launchpad.net/linaro-multimedia-wg/+spec/multimedia-lina… [2] Spec: https://wiki.linaro.org/WorkingGroups/Middleware/Multimedia/Specs/1105/Vali… [3] git repo: http://git.linaro.org/gitweb?p=people/sudip-jain/smartt.git;a=summary [4] Package: https://launchpad.net/~goelkunal/+archive/multimedia

15 years

[ACTIVITY] OCTO status - wk22.2011

by Ilias Biris

See https://wiki.linaro.org/OfficeofCTO/Status/2011-05-31 for relevant links. == Key Points for wider discussion == * Any tool related to tracking work progress during a development cycle should be sufficiently integrated to our requirements and issue management tool (Launchpad) - otherwise there will be need to handle more than 1 tool. * Debconf + Sprint: some contributors may be divided between the two events. We should clearly indicate who needs to be participating to the sprint to avoid confusion == Team Highlights == * Blueprints: in place, check OCTO 11.11 schedules * Public plans review: material prepared (check 11.11 public plans review wiki page), comments from TSC requested * Highlights o Working on server work planning; will be like a whitepaper, might turn into a wiki page; first draft expected next week o Work on kernel merge window; Device Tree work went in! o GPIO drivers moving from arch/arm/mach-*/ to drivers/gpio/ o PXE boot -- kexec based? Need to followup (OCTO-Grant Likely, Kernel WG - Deepak) on state of kexec to see whether we need a blueprint on this o Updated Java plan - read more about the Optimized Java Interpreter on the wiki link * Work items sequencing is ongoing - Ilias -- Ilias Biris, Aallonkohina 2D 19, 02320 Espoo, Finland Tel: +358 50 4839608 (mobile) Email: ilias dot biris at linaro dot org Skype: ilias_biris

15 years

ARM porting Jam - today

by Riku Voipio

Hi, Linaro Developer Platform team organises every week (Wednesday 14:00 - 18:00 UTC) an ARM porting Jam. The idea is to gather all developers together to fix userspace portability issues across the board. The list of bugs being worked on is at launchpad: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=arm-porting-queue&orderby… Interested in making the software in Ubuntu run better on ARM? Join us on the #linaro channel on irc.linaro.org today! Cheers, Riku

15 years

AUTO: Javed A Rahman is out of the office (returning 15/06/2011)

by Javed A Rahman

I am out of the office until 15/06/2011. I am on vacation and will not be reachable by mail or phone. Note: This is an automated response to your message "Does anyone care about LSB on arm?" sent on 31/5/11 21:52:39. This is the only notification you will receive while this person is away.

15 years

reorganzing the lava projects on launchpad

by Michael Hudson-Doyle

Hi there, Some of you know about this already as it was discussed a bit at LDS, but probably not very inclusively. We have a slightly strange arrangement of projects on Launchpad, with the main ones being "launch-control" and "lava". AIUI, Zygmunt really wanted to call "launch-control" "dashboard" from day 1, but that was clearly an overly generic name. Since then, we've come up with the "lava" name to cover our automated validation efforts, but currently the "lava" project just contains code to do with the validation farm in Cambridge, which is only part of the story. So. We have a plan to reorganize the projects like so (also documented on https://blueprints.launchpad.net/linaro-validation-misc/+spec/linaro-platfo…): - lava -- project group containing: - lava-server -- contains the django settings file and templates - this well mostly be extracted from what is lp:launch-control today - lava-scheduler -- django application for scheduling jobs - what exists for this is in lp:lava currently - lava-dispatcher -- tool that runs tests on hardware - this is also in lp:lava currently - lava-dashboard -- django application for showing test results - this is lp:launch-control currently - lava-tool -- command line entry point and framework - this actually exists already and has the right name! - lava-dashboard-tool - new name for launch-control-tool - lava-test-tool -- plugin for lava-tool that adds commands for running tests - new name and refactoring for abrek - lava-auth-tool -- plugin for lava-tool that adds commands for authenticating against validation.linaro.org - lava-scheduler-tool -- plugin for lava-tool that adds commands for interacting with the scheduler - these last two don't actually exist yet It's possible there are too many lava-tool plugins here, but we can see how that goes when it comes to implementing those bits. There will be a certain amount of churn and broken links during the reorganization, so this is mostly a heads up and apologies in advance. Bike shedding on the details of the rearrangement will probably be ignored :) I'll probably do this on Monday morning my time, which should be nice and quiet. Cheers, mwh

15 years

Re: [RFC] Kernel WG Slides for Public Plan Review, Draft 1

by Zach Pfeffer

On 27 May 2011 11:45, Deepak Saxena <dsaxena(a)linaro.org> wrote: > On 26 May 2011 20:17, Zach Pfeffer <zach.pfeffer(a)linaro.org> wrote: >> My only comment is on: >> >> What We're Not Doing >> >> Integrating graphics drivers >> ● Handled by vendor Landing Team >> >> I think aspects of this will need to be handled by the kernel team. >> Especially with the work Jesse and the MM summit are proposing. > > Hi Zach, > > Clarification on the above point is that we will not be handling integrating > binary blobs for the different SOCs. Any work that Jesse's team and > upstream developers do on consolidating towards a single buffer > management solution will certainly be integrated into the linaro-linux > tree as it starts stabilizing. We're going to need to chat about that. I'll need support for binary blob integration from all teams. Overall I'm asking for each team (Landing Teams included) to: (Thanks to Michael Hope for suggesting this list) 1. Build the working group output and Android combinations with each commit (CI) * Build last-known-good Android with latest working group output * Build latest Android with last-released working group output * Build latest Android with latest working group output 2. Smoke test (CI/test farm) * Load onto a board * Run a test script * Run 0xbench 3. Report any build or smoke test failures (CI) 4. Report any performance regressions (CI) 5. Document Linaro improvements in general and on Android, how to build the component and how to get it. 6. Add benchmarks to showcase Linaro improvements. 7. Add tests to test functionality. Some of this will be automated with Gerrit eventually. Until then it'll be a manual process. -Zach

15 years

[ACTIVITY] (Android Team) 2011-05-22 to 2011-05-28

by Zach Pfeffer

See https://wiki.linaro.org/Platform/Android/Status/2011-06-02 for all links == Key Points for wider discussion == * Need to replace the kernel in the Panda-LEB build with Linaro's kernel and support GFX * Need to compile the Panda-LEB build with Linaro's toolchain == Team Highlights == * Released generic Panda and Beagle xM builds and a Panda LEB with GFX [[https://launchpad.net/linaro-android/+milestone/11.05]] * Helped write and finalize job recs for Android * [[https://docs.google.com/a/linaro.org/leaf?id=0BzePOvQgrt3GN2Y3YTlhY2MtMzY5O… Platform Engineer]] * [[https://docs.google.com/a/linaro.org/leaf?id=0BzePOvQgrt3GY2Q1ODQ4M2UtMzMyY… Multimedia Platform Engineer]] * [[https://docs.google.com/a/linaro.org/document/d/1ZSqZ75lt2p-Hm9dYpS9r7Veirv… Integration Platform Engineer]] * Worked toward closing out Android LAVA issues [[https://bugs.launchpad.net/linaro-android/+bug/784836]] * Supported Computex demo * Ensured that Scott Bambrough and 0xlab had what they needed to successfully demo Linaro * Wrote a demo script that Michael Opdenacker filmed and posted on the Linaro blog [[http://www.linaro.org/linaro-blog/2011/05/31/linaro-android-build-service-v…: * [[http://free-electrons.com/tmp/webm/linaro-android-leb-panda-x450p.webm]] * [[http://free-electrons.com/tmp/webm/linaro-android-leb-panda.webm]] * Organized and expanded Blueprints for 11.11 and each sub-cycle. * [[https://blueprints.launchpad.net/linaro-android?searchtext=linaro-android-o]] * [[https://blueprints.launchpad.net/linaro-android?searchtext=linaro-android-t…]] * Attempted to disable Android PM to solve [[https://bugs.launchpad.net/linaro-android/+bug/789089]] * Worked on integrating the Pandroid community build into the Linaro build system == Risks / Issues == * Android LEBs for all boards listed at [[http://www.linaro.org/low-cost-development-boards]] == Miscellaneous == * Jeremy leaving 2011/5/31

15 years

Slides from Linaro@UDS-O plenary

by Christian Robottom Reis

Hi there, Here are the slides I presented on the May 9th plenary; I was supposed to send these earlier but surprise, surprise, I never found the time for it ;-) We'll see in a month's time how well it worked! -- Christian Robottom Reis | [+55] 16 9112 6430 | http://launchpad.net/~kiko Linaro Engineering VP | [ +1] 612 216 4935 | http://async.com.br/~kiko

15 years

Linaro Public Plan Review (Power Management)

by Amit Kucheria

Hi all, The public reviews for Linaro plans for this year start today with the first session talking about Power Management WG plans. Please participate if you're interested in hearing what we'll be working on. Feedback is very welcome. Slides and participation details are at https://wiki.linaro.org/Cycles/1111/PublicPlanReview See you there. Regards, Amit

15 years

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev