All:
A new version of Shamrock implementing the OpenCL v1.2 spec, based
on LLVM/clang v3.6, is now available at:
https://git.linaro.org/gpgpu/shamrock.git , tag 'shamrock_v1.2'.
This has been validated on both ARMv7 (Chromebook 2) and ARMv8
(HiKey board) using Khronos conformance and piglit testing.
This is based on the clover OpenCL project:
http://people.freedesktop.org/~steckdenis/clover
and on the contributions from Texas Instruments for the Keystone II
Platform: (TI provides full OpenCL DSP Device support separately)
git.ti.com/opencl
and adding contributions from Linaro for ARM CPU Device support.
See the README for details.
Many thanks to the contributors who have assisted in the port to ARM
and to LLVM/MCJIT:
Tom Gall
Show Liu
Jia Jia
Renato Golin
Best Regards,
- Gil
== Progress ==
* BB-29 "ENG: Linux linaro baseline maintenance" (80%):
- added the updated Android topic back into linux-linaro-core-tracking tree, updated llct and ll to v4.2-rc3,
tagged the 15.07 linux-linaro kernel release
- fixed vexpress64 linux-linaro CI builds by removing the step to build the boot wrapper (it no longer needed)
- after the linux-linaro CI armv7 builds have been switched from utopic to vivid, the boards stopped booting
(/etc/machine-id is missing, and /etc is mounted ro). Added few kernel config option which are required by
systemd to distribution.conf fragment. This haven't made the "/etc/machine-id" error to disappear, but at least
the booting continued to the boot prompt, and the LAVA tests were executed.
- noticed that enabling CONFIG_LOCALVERSION_AUTO in the config fragment doesn't result in git commit id being
added to the kernel version in the builds. The (two) reasons have been identified, the solution is TBD.
* PTO (20%):
- July 24th - day off
== Plans ==
* BB-29 "ENG: Linux linaro baseline maintenance" (80%):
- create separate Jira issues ("stories") for the "/etc/machine-id" error, and the "LOCALVERSION_AUTO" issues.
- update linux-linaro kernel trees to v4.2-rc4.
* PTO (20%):
- July 31st - day off
== Issues ==
* none
Hello,
All Linaro Gerrit services (4 of them) currently run Gerrit 2.8.6.1,
the latest of 2.8 branch, which is now 1 year old, and 3 major releases
behind the latest, 2.11.
We (Systems) regularly get requests regarding features available in
newer Gerrit versions, and regularly face issues, which are not even
reportable upstream, as we run a pretty old version.
With all the improvements we did to Gerrit management across different
installs lately, we're now ready to raise the question of the version
upgrade. Here're basic facts about recent Gerrit versions:
1. Major change in 2.9 is introduction of new change summary screen.
It's pretty different by both looks and feel and it's fair to say taht
one needs to relearn Gerrit a bit with its introduction. It's still
possible to use old screen, until it's removed in further versions.
2. 2.11 does remove support for old change summary screen.
3. 2.10 and 2.11 are actively supported and maintained (e.g. 2.10.6
released Jun 29, 2.11.2 - Jul, 14).
Based on this, we would like to propose upgrade to 2.10, to let people
some leeway to learn the new change screen, and be able to switch back
to the old screen in the meantime.
As usual, we'd like to select single server for pilot upgrade first,
and among 4 we have, Linaro Android Gerrit,
https://android-review.linaro.org seems like a good candidate, as it's
used just by subset of Linaro teams, and at the same time, used
regularly to call it "tested" after the pilot period.
Things you can do/help with in the meantime:
1. Provide feedback on the general idea of the upgrade.
2. Let us know if you'd like a server you regularly use to be upgraded
sooner rather than later. We in particular would like to know whether
Android Team (and other stakeholders) agree to pilot new version on
https://android-review.linaro.org
3. Get feedback from any stakeholders which may be affected, first of
all, from Builds&Baselines, who run CI with Gerrit integration.
4. Get acquainted with new change screen "extramurally", by reviewing
documentation with extensive screenshots:
https://gerrit-documentation.storage.googleapis.com/Documentation/2.9/user-…
Thanks,
Paul
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
Hello All.
When I use the meta-linaro layer to build perf. I meet following fetch error:
ERROR: Fetcher failure: Fetch command failed with exit code 8, output:
ftp://ftp.debian.org/debian/pool/main/l/linux-tools/linux-tools_3.18.5.orig…:
2015-07-23 13:29:29 ERROR 404: Not Found.
ERROR: Function failed: Fetcher failure for URL: 'ftp://ftp.debian.org/debian/pool/main/l/linux-tools/linux-tools_3.18.5.orig…'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/b40527/ls2-yocto/fsl-qoriq-sdk/build_ls2085ardb_release/tmp/work/ls2085ardb-fsl-linux/perf/3.18.5-r9/temp/log.do_fetch.24496
ERROR: Task 4 (/home/b40527/ls2-yocto/fsl-qoriq-sdk/poky/meta/recipes-kernel/perf/perf.bb, do_fetch) failed with exit code '1'
I have checked the mirror: 'ftp://ftp.debian.org/debian/pool/main/l/linux-tools/ . linux-tools_3.18.5.orig.tar.xz has been removed.
So can you help to update the SRC_URI?
Thanks
Best Regards
Zongchun
== Progress ==
* Deploy new layout for releases.l.o (10%)
* Start meta-luv (60%)
* Dragonboard support for meta-96boards (20%)
* OE maintenance (10%)
== Plans ==
* Find mind bleach to erase any recollection luv-yocto contents and quality.
--
Koen Kooi
Builds and Baselines | Release Manager
Linaro.org | Open source software for ARM SoCs