Both the Android and Ubuntu have QA tests which expect to be able to
validate device-tree booting by looking in /proc/device-tree, so we
should enable this for all Linaro builds.
At the same time we can remove this option from ubuntu.conf as it's not
an Ubuntu specific requirement.
Signed-off-by: Jon Medhurst <tixy(a)linaro.org>
---
I'll push this out to the configs branch soon, but mailing this patch
out for visibility and to give some time for any comments...
linaro/configs/linaro-base.conf | 1 +
linaro/configs/ubuntu.conf | 1 -
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/linaro/configs/linaro-base.conf
b/linaro/configs/linaro-base.conf
index eaf0196..23638c3 100644
--- a/linaro/configs/linaro-base.conf
+++ b/linaro/configs/linaro-base.conf
@@ -87,3 +87,4 @@ CONFIG_CRC7=y
CONFIG_HW_PERF_EVENTS=y
CONFIG_FUNCTION_TRACER=y
CONFIG_ENABLE_DEFAULT_TRACERS=y
+CONFIG_PROC_DEVICETREE=y
diff --git a/linaro/configs/ubuntu.conf b/linaro/configs/ubuntu.conf
index fafabe1..b65be64 100644
--- a/linaro/configs/ubuntu.conf
+++ b/linaro/configs/ubuntu.conf
@@ -721,7 +721,6 @@ CONFIG_MTD_LPDDR=m
CONFIG_MTD_QINFO_PROBE=m
CONFIG_DTC=y
CONFIG_OF=y
-CONFIG_PROC_DEVICETREE=y
CONFIG_OF_FLATTREE=y
CONFIG_OF_EARLY_FLATTREE=y
CONFIG_OF_ADDRESS=y
--
1.7.10.4
Calendar Week 49: Here is test result summary for Linaro ubuntu image on
following boards:
1) ARM Versatile Express A9;
2) Samsung Origen;
3) TI Panda 4430;
4) TI Panda 4460;
5) Open Embedded SDK;
6) Open Embedded LAMP;
7) Open Embedded Minimum;
Synopsis: All ubuntu images have been upgraded to command based Linux
Linaro Quantal images; All UI related test cases have been ignored; Open
Embedded remains the exactly same status as last week.
1. ARM Versatile Express A9 + Linux Linaro Quantal (Column C):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdFNmV…
Data streaming failed in DS-5, Gator daemon doesn't exist in image. Device
Tree is still unavailable, and "Halt" test failed either. All other
features work well,
2. Samsung Origen + Linux Linaro Quantal (Column C):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEowN…
Data streaming failed in DS-5, lava-test is not pre-installed in image, and
this cause test "pwrmgmt" blocked. Also, "powertop" test will cause
segmentation fault and kernel panic. No Internet connection on this image,
neither Ethernet nor WiFi works. Both "reboot" & "halt" test failed.
3. TI Panda 4430 + Linux Linaro Quantal (Column C):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ…
Data streaming failed in DS-5, the directory of device tree is empty,
although the boot log shows it had been enabled during boot process.
lava-test doesn't exist in image. All other feature work well.
4. TI Panda 4460 + Linux Linaro Quantal (Column C):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ…
Exactly same as TI Panda 4430 above.
5. Open Embedded SDK in Fast Model (Column D):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AgB-fT5LL31CdDhwR…
All test passed.
6. Open Embedded LAMP in Fast Model (Column D):
Same issue as previous week, kernel exception message occurred if show any
PHP web page. All other test passed.
7. Open Embedded Minimum in Fast Model (Column D):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AgB-fT5LL31CdDhwR…
All test cases passed.
For the previous week (Calendar week 48) summary, please refer to
attachment.
Thank you.
Best Regards
Botao Sun
Postmortem and lessons learned for Linaro's release 2012.11
https://wiki.linaro.org/Cycles/1211/Release/Review
Highlights and Key Successes
============================
http://www.linaro.org/downloads/1211http://wiki.linaro.org/Cycles/1211/Release#Release_Information
Linaro continues with our monthly release cadence. This month
highlights the creation of the Linaro Enterprise Groups roadmap.
Roadmap cards are currently in the drafting stages and many
discussions are occurring around development and production. Also this
month features versions 11 and 12 of the big.LITTLE MP tree which
integrate a number of patches for the benefit of our members.
This was a conventional release cycle that did not see any major
issues happen. The TC2 board that was stuck in custom in India has
finally been released. We continue to refine our shipping procedures
to accommodate our widely distributed business model.
Blueprints
=========
The number of high or essential priority blueprints that missed the cycle:
Android Not Available
Developer Platform 3 out of 8
Infrastructure 0 out of 3
Lava 4 out of 8
QA Not Available
Total 7 out of 18
37% of high or essential priority blueprints scheduled for this cycle
were not delivered.**
Total blueprints: 24 out of 47 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%
12.09: 9 out of 28, 32%
12.10: 15 out of 38, 39%
12.11: 7 out of 18, 37%**
* Not included is data from working groups and landing teams
** Android metrics not available this month
Source:
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AjEaTwrvj1bidGR1T…
--
David Zinman, Project Manager
Linaro.org | Open source software for ARM SoCs
I am not subscribed to linaro-dev, so please Cc me in case you drop flashbench-results
mailinglist from receivers.
Hi Arnd, hi everyone!
For now quick and short.
A simple script to automate common steps on reporting flash medium test
results. It goes as far as read tests for erase block size and then suggests
some open au tests together with a warning that these write to the device.
I checked other flashbench-results posts as to what info would be
interesting.
Find it at:
git://gitorious.org/flashbench/flashbench.git
Example output is at:
[Flashbench] Samsung Plus MB-SPAGFFP Class 10 SDHC 16GB
Sat Dec 1 16:02:18 UTC 2012
http://lists.linaro.org/pipermail/flashbench-results/2012-December/000346.h…
Sorry that I occupied flashbench upstream name for project. I can look
into renaming it to "flashbench-martin" or something like that.
The script is in branch "flashreport".
In branch "defaultblocksize" you find a currently untested patch for
changing default block size to 1024.
I can try to send patches as mails via git, but I´d have to look it up first,
since I do this quite rarely.
Up to then please use the repo urls :)
Nice weekend,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
Hello Team,
big.LITTLE MP test execution summary is:
High Lights:
* sched_tests test suite has been executed on mphackbox with latest Android
Image.
On Android:
-----------------
Total Tests = 22
Tests Passed = 16
Tests Failed = 6
Bugs have been created for failed test cases.
Pre-built images are downloaded from
https://android-build.linaro.org/builds/~linaro-android/vexpress-jb-gcc47-a…
Summary of the results can be found in attachments.
Best regards
Naresh Kamboju
Hello
Now at Linaro we have two layers for our OpenEmbedded work:
- meta-aarch64
- meta-linaro
First one contains everything we need to get AArch64 booted in
fastmodels: toolchain, kernel and few recipes which needed changes to
build for AArch64. I am working on merging those changes into main
OpenEmbedded layers.
Second one is gcc-linaro from Toolchain WG and some recipes and changes
from Platform team.
Those who do OE builds with our toolchain have some components changed
due to our metadata (like Busybox with dpkg-deb) and I decided to fix it.
Today I pushed "new-layout" branch of meta-linaro repository. It
contains all Linaro layers:
- meta-aarch64
- meta-linaro
- meta-linaro-toolchain
First one was merged from meta-aarch64 repository and moved to own
directory. Third one contains only toolchain bits. Second one has all
that left.
I have to do some test builds with this layout and once they will
confirm that it works I will change all CI builds. This will also
deprecate meta-aarch64 repository - it will not have any updates and
will be dropped in ~month.
Opinions?
Hello everyone,
the Infrastructure team is going to perform a small update of Android
Build frontend today at 12UTC. The deployment shouldn't take more than
10 minutes.
Only the frontend will be affected.
If the downtime will cause you significant problems, please get in
touch with us.
Thanks.
--
Milo Casagrande
Infrastructure Engineer
Linaro.org <www.linaro.org> │ Open source software for ARM SoCs