A head's up for people submitting fastmodel jobs to LAVA. We've recently
decided on a different naming scheme for the device/device-types in the
lab. Previously it was:
device-type: fastmodel
device: fastmodel01, fastmodel02
We are changing this to be:
device-type: rtsm_ve-a15x4-a7x4
device: rtsm_ve-a15x4-a7x4_01, rtsm_ve-a15x4-a7x4_02
and I'll also be creating a new device/type:
device-type: rtsm_ve-a15x1-a7x1
device: rtsm_ve-a15x1-a7x1_01, rtsm_ve-a15x1-a7x1_02
How does this affect me? You'll need to change your job you submit to
LAVA to match this new device type.
-andy
Postmortem and lessons learned for Linaro's release 2012.08
https://wiki.linaro.org/Cycles/1208/Release/Review
Highlights and Key Successes
============================
Linaro also held its first Virtual Connect event on 13 - 17 August,
2012. This online event used Google+ Hangouts on Air and was streamed
and recorded via YouTube. Members of the various Linaro Teams provided
informative, educational and exciting sessions that allowed for public
viewing and participation.
http://plus.google.com/u/0/b/112814496864921562564/116754366033915823792/po…
The Android team created stable Jelly Bean builds from AOSP and an
Android benchmarking platform to automate many of the tests in the
AOSP codebase.
The Developer Platform Team announced USB Host enablement is now
available in LAVA and that all packaged linux-linaro kernels are now
cross-compiled and boot tested via LAVA before they are uploaded to
Linaro Overlay PPA. Additionally, U-Boot-Linaro is now based on the
latest upstream release--v2012.07.
Postmortem and Lessons Learned
==============================
This cycle was fairly low key: lots of people were out for vacations
and many others were attending external conferences such as Linux
Plumbers.
One issue of concern was the deployment of an infrastructure project
on the last week before release.
A the new django application was deployed on snapshots.linaro.org that
disrupted several builds on the Friday before the release. The issues
took one week to resolve.
The issues are:
- The deployment was not communicated and broadcast properly
- Build maintainers were not given proper warning
- deploying new functional software on a Friday with no one
available on the weekend for emergency
- deploying during a release week
A big "thank you" is in order for Georgy Redkozubov (gesha) for his
help and availability in troubleshooting and getting it fixed.
An incident report has been filed here:
https://wiki.linaro.org/Internal/Process/DealingWithCrisis/IncidentReports/…
Blueprints
=========
The number of high or essential priority blueprints that missed the cycle:
Android 3 out of 13
Developer Platform 0 out of 3
Infrastructure 1 out of 6
Lava 2 out of 4
Total 6 out of 26
23% of high or essential priority blueprints scheduled for this cycle
were not delivered.
Total blueprints: 14 out of 49 missed the cycle.
High priority missed blueprints recap:
12.05: 19 out of 48, 39%
12.06: 13 out of 31, 42%
12.07: 14 out of 31, 45%
12.08: 6 out of 26, 23%
* Not included is data from working groups and landing teams
Source: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AjEaTwrvj1bidGhNZ…
--
David Zinman
Linaro Release Manager | Project Manager
Linaro.org | Open source software for ARM SoCs
Hi,
I am trying to boot kernel on panda board. I got the source from:
http://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git;a=shortlog;…
Following is my branch HEAD:
commit 7f39bb7ab9591c6254e5930a00d762e4b37f08b2
Merge: 1d10459 8b29cd5
Author: Andrey Konovalov <andrey.konovalov(a)linaro.org>
Date: Mon Sep 3 17:10:24 2012 +0400
Merge branch 'tracking-ll-last-minute-fixes' into merge-linux-linaro
I am using following for compilation: omap2plus_defconfig, omap4-panda.dts
When i try to boot, kernel hangs after uncompressing linux...
If i just remove the 0x815f0000 from bootm command.. i.e. boot without dtb...
it boots fine.
Earlier i have flashed my card using linaro-media-create. Got, H/w package and
devel rootfs from 12.08 release. Replaced uImage and board.dtb in /dev/mmcblk0p1
viresh
This patchset updates devfreq core to add support for devices
which can idle. When device idleness is detected perhaps
through runtime-pm, need some mechanism to suspend devfreq
load monitoring and resume when device is back online.
patch 1 introduce core design changes - per device work, decouple
delayed work from core and event based interaction.
patch 2 add devfreq suspend and resume apis.
patch 3 current frequency bug fix and add new sysfs attribute for
governor predicted next target frequency.
The existing devfreq apis are kept intact. Two new apis
devfreq_suspend_device() and devfreq_resume_device() are
added to support suspend/resume of device devfreq.
--
Rajagopal Venkat (3):
devfreq: core updates to support devices which can idle
devfreq: Add suspend and resume apis
devfreq: Add current freq callback in device profile
Documentation/ABI/testing/sysfs-class-devfreq | 7 +
drivers/devfreq/devfreq.c | 412 +++++++++++---------------
drivers/devfreq/governor.h | 11 +
drivers/devfreq/governor_performance.c | 16 +-
drivers/devfreq/governor_powersave.c | 16 +-
drivers/devfreq/governor_simpleondemand.c | 42 +++
drivers/devfreq/governor_userspace.c | 23 +-
include/linux/devfreq.h | 46 ++-
8 files changed, 291 insertions(+), 282 deletions(-)
--
1.7.11.3
Hi Guys,
I have flashed my SD card with linaro-media-create with precise-devel
and latest h/w pack (12.08)
Now i have two requirements:
- Always use my copy of devel instead of the new devel everytime from
the latest release
As i do install a lot of stuff on it. Will apt-get update would be
enough to get the latest things
from linaro?
- Update kernel image, with my kernel, from mainline or linaro I have
tried a lot of
combinations... but always some issues
I went through this too: https://wiki.linaro.org/Resources/HowTo/KernelDeploy
I want to know what's the best practice of updating image that is
followed by most of the Linaro developers?
viresh
NOTE: I raised this query here too:
http://ask.linaro.org/questions/1625/how-do-you-update-kernel-image-on-pand…