Hi,
This is a mail sent to remind you the coming release dates:
* Toolchain WG components release for 11.09 is September 15th, 2011.
* Linaro 11.09 components release is September 22nd, 2011.
* Linaro 11.09 RC images is September 26th, 2011.
* Linaro 11.09 release is September 29th, 2011.
The following components are planned to be delivered this month:
* Graphics WG: compiz, compiz-plugins, glcompbench, glmark2, glproxy
* Kernel WG: u-boot-linaro, linux-linaro
* Landing Teams: linux-linaro-lt-freescale, linux-linaro-android-lt-ti,
linux-linaro-lt-samsung, linux-linaro-lt-st-ericsson, linux-linaro-lt-ti
* Multimedia WG: libjpeg-turbo (for Android)
* Platform Teams: lava-dashboard, lava-dispatcher, lava-qatracker,
lava-scheduler, lava-scheduler-tool, lava-test, linaro-image-tools, svammel
* Power Management WG: powerdebug
* Toolchain WG: gcc-linaro 4.5, gcc-linaro 4.6, gdb-linaro, qemu-linaro,
cortex-strings
Note: the Toolchain WG will use a new release scheme from now on. They will
release two weeks before Linaro release, giving Developer Platform and
Android Teams a fixed two weeks between the Toolchain and the Platform
release.
The release dates and deliveries information is available from the release
dashboard: http://wiki.linaro.org/Cycles/1109/Release/Dashboard
Cheers,
--
Fathi Boudra
Linaro Release Manager | Platform Project Manager
Linaro.org | Open source software for ARM SoCs
I started working on a results view in LAVA for the bootchart results since
they are now part of the daily runs. This is using a partial copy of the
data I have locally, so please don't concern yourself too much with the
actual data in it. A couple of things to point out:
1. legend is not placed well, that's something I'm not yet sure how to fix
as my javascript-fu is lacking here (zyga, any ideas on this?)
2. The set of results here is not very large. That's adjustable and when
it's using live data, should have a lot more data points to better see
trends
3. This is purposefully restricted to a single board. We are not running
benchmarks in a controlled enough manner as to make comparison of boards to
one another reasonable, nor is it encouraged due to the collaborative nature
of Linaro.
In particular I'm looking for opinions on how it would be most useful to
display this data. This view shows all 4 image types on a single chart. I
did a previous version that had them separate. Is there a preference? It
would also be easy to do both on the same page, but perhaps a bit redundant.
Thanks,
Paul Larson
Akinobu Mita reported that the boot option for mmc fault injection is never
compiled in due to a fauly "ifdef KERNEL" that is never set.
A correct ifdef would be "ifndef MODULE". This patch set adds a
module_param_cb() and thereby no ifndef MODULE is needed.
Using a module_param makes it possible to pass default fault attributes for
external modules too.
This patch set is for 3.2
Change log:
v2 - use module_param_cb() to set default fault attributes
- fix spelling of documentation in patch #3
Per Forlin (3):
fault-inject: export setup_fault_attr()
mmc: add module param to set fault injection attributes
fault-injection: update documentation with the mmc module param
Documentation/fault-injection/fault-injection.txt | 2 +-
drivers/mmc/core/debugfs.c | 38 +++++++++++----------
lib/fault-inject.c | 3 +-
3 files changed, 23 insertions(+), 20 deletions(-)
--
1.7.4.1
From: Per Forlin <per.forlin(a)linaro.org>
change log:
v2 - Resolve build issue in mmc core.c due to multiple init_module by
removing the fault inject module.
- Export fault injection functions to make them available for modules
- Update fault injection documentation on MMC IO
v3 - add function descriptions in core.c
- use export GPL for fault injection functions
v4 - make the fault_attr per host. This prepares for upcoming patch from
Akinobu that adds support for creating debugfs entries in
arbitrary directory.
v5 - Make use of fault_create_debugfs_attr() in Akinobu's
patch "fault-injection: add ability to export fault_attr in...".
v6 - Fix typo in commit message in patch "export fault injection functions"
v7 - Don't compile in boot param setup function if mmc-core is
built as module.
v8 - Update fault injection documentation.
Add fail_mmc_request to boot option section.
v9 - remove ifdef around include files and inline empty function,
comments from Linus Walleij.
Per Forlin (3):
fault-inject: export fault injection functions
mmc: core: add random fault injection
fault injection: add documentation on MMC IO fault injection
Documentation/fault-injection/fault-injection.txt | 8 ++++-
drivers/mmc/core/core.c | 41 +++++++++++++++++++++
drivers/mmc/core/debugfs.c | 25 +++++++++++++
include/linux/mmc/host.h | 5 +++
lib/Kconfig.debug | 11 ++++++
lib/fault-inject.c | 2 +
6 files changed, 91 insertions(+), 1 deletions(-)
Akinobu Mita reported that the boot option for mmc fault injection is never
compiled in due to a fauly "ifdef KERNEL" that is never set.
A correct ifdef would be "ifndef MODULE". Akinobu suggested to use
a module param instead.
This patch set is for 3.2
Per Forlin (3):
fault-inject: export setup_fault_attr()
mmc: add module param to set fault injection attributes
fault-injection: update documenation with the mmc module param
Documentation/fault-injection/fault-injection.txt | 2 +-
drivers/mmc/core/debugfs.c | 29 ++++++++-------------
lib/fault-inject.c | 3 +-
3 files changed, 14 insertions(+), 20 deletions(-)
--
1.7.4.1
----- Forwarded message from Roger Teague <Roger.Teague(a)arm.com> -----
Date: Wed, 7 Sep 2011 14:25:11 +0100
From: Roger Teague
Subject: Cortex Programmers Guide
Folks,
Are you aware of the following?
http://www.cadence.com/Community/blogs/sd/archive/2011/08/04/a-must-read-th…
a blog from Cadence but it does carry a link to the doc.
----- End forwarded message -----
Enjoy!
--
Christian Robottom Reis, Engineering VP
Brazil (GMT-3) | [+55] 16 9112 6430 | [+1] 612 216 4935
Linaro.org: Open Source Software for ARM SoCs