linaro-dev

linaro-dev@lists.linaro.org

4332 discussions

[NOTES] Toolchain WG Weekly Status report 2011-06-17

by Mounir Bsaibes

Enclosed you'll find the links to the meetings minutes and Weekly Status report for the Toolchain working group for the week ending 2011-06-17. == Meetings minutes == https://wiki.linaro.org/WorkingGroups/Toolchain/Meetings/2011-06-13<https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2011-06-13> https://wiki.linaro.org/WorkingGroups/Toolchain/Meetings/2011-06-16<https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2011-06-16> == Weekly Status Report == https://wiki.linaro.org/WorkingGroups/ToolChain/Status/2011-06-16 == Summary == * Released Linaro GCC 4.6 and 4.5 2011.06 * Adds new optimisations * Adds vectoriser improvements. * Released Linaro QEMU 2011.06 * Restores graphics on OMAP devices * Adds USB keyboard and mouse support to Beagle * 64 bit atomics are prototyped. * Vectoriser * Fixes for over widening of multiplies fix regressions introduced by strided load/store * Working on the loop peeling heuristics * EEMBC and DENBench source is now pushed up to Launchpad Regards, Mounir

13 years, 11 months

LAVA Dashboard user forum

by Zygmunt Krynicki

Hello everyone. Since a few people started asking me questions about lava dashboard, reports and other things I though I we could benefit from sharing this knowledge. I created user forum for the dashboard at: http://fracture.suxx.pl/projects/lava-dashboard/boards Please go there and post questions you may have. You will need an account which you can quickly create here: http://fracture.suxx.pl/account/register I hope that will make the communication smoother. Thanks ZK

13 years, 11 months

Bug escalation procedure

by Fathi Boudra

Hi, This is an update to the bug management process. The wiki page is: https://wiki.linaro.org/Cycles/BugManagement Cheers, Fathi -- Bug escalation procedure ------------------------ It's important that bugs which affect the LEB's and other images are caught early and fixed as soon as possible. To help the Linaro Release Team in identifying and tracking the release blocker bugs, any individual could propose a bug as a blocker and follow the bug escalation procedure. Prerequisite ------------ * All bugs in a 'New' state should be sufficiently triaged to determine their importance. * All bugs in a 'High' or 'Critical' state should be highlighted to the Linaro Release Team: Please, add it to the wiki page 'Bugs' section for the next release meeting. The release meeting calendar can be found on the wiki. Meetings are held on Thursday. If possible, attend the meeting. Procedure --------- 1. Subscribe Linaro Release Team ('linaro-release') to the proposed bug. 2. Linaro Release Team evaluates the proposed bug. 2a. Linaro Release Team accepts the bug as a release blocker: * notify by a comment on the bug. * set the milestone to the next release. * assign to the appropriate team. 2b. Linaro Release Team rejects the bug as a release blocker: * unsubscribe Linaro Release Team from the poposed bug.

13 years, 11 months

[PATCH v4 00/12] mmc: use nonblock mmc requests to minimize latency

by Per Forlin

How significant is the cache maintenance over head? It depends, the eMMC are much faster now compared to a few years ago and cache maintenance cost more due to multiple cache levels and speculative cache pre-fetch. In relation the cost for handling the caches have increased and is now a bottle neck dealing with fast eMMC together with DMA. The intention for introducing none blocking mmc requests is to minimize the time between a mmc request ends and another mmc request starts. In the current implementation the MMC controller is idle when dma_map_sg and dma_unmap_sg is processing. Introducing none blocking mmc request makes it possible to prepare the caches for next job parallel with an active mmc request. This is done by making the issue_rw_rq() none blocking. The increase in throughput is proportional to the time it takes to prepare (major part of preparations is dma_map_sg and dma_unmap_sg) a request and how fast the memory is. The faster the MMC/SD is the more significant the prepare request time becomes. Measurements on U5500 and Panda on eMMC and SD shows significant performance gain for large reads when running DMA mode. In the PIO case the performance is unchanged. There are two optional hooks pre_req() and post_req() that the host driver may implement in order to move work to before and after the actual mmc_request function is called. In the DMA case pre_req() may do dma_map_sg() and prepare the dma descriptor and post_req runs the dma_unmap_sg. Details on measurements from IOZone and mmc_test: https://wiki.linaro.org/WorkingGroups/Kernel/Specs/StoragePerfMMC-async-req Changes since v3: * Based on 2.6.39-rc7 * Add error check for testlist in mmc_test.c * Resolve in mmc-queue-thread that caused the mmc-thread to miss a wakeup. * Move parallel request handling to core.c. This simplifies the interface from 4 public functions to 1. This also gives access for SDIO to use the same functionallity, even though the function is not tuned for the SDIO execution flow yet. Per Forlin (12): mmc: add none blocking mmc request function omap_hsmmc: use original sg_len for dma_unmap_sg omap_hsmmc: add support for pre_req and post_req mmci: implement pre_req() and post_req() mmc: mmc_test: add debugfs file to list all tests mmc: mmc_test: add test for none blocking transfers mmc: add member in mmc queue struct to hold request data mmc: add a block request prepare function mmc: move error code in mmc_block_issue_rw_rq to a separate function. mmc: add a second mmc queue request member mmc: test: add random fault injection in core.c mmc: add handling for two parallel block requests in issue_rw_rq drivers/mmc/card/block.c | 452 +++++++++++++++++++++++++---------------- drivers/mmc/card/mmc_test.c | 361 ++++++++++++++++++++++++++++++++- drivers/mmc/card/queue.c | 184 +++++++++++------ drivers/mmc/card/queue.h | 32 +++- drivers/mmc/core/core.c | 165 ++++++++++++++- drivers/mmc/core/debugfs.c | 5 + drivers/mmc/host/mmci.c | 146 ++++++++++++-- drivers/mmc/host/mmci.h | 8 + drivers/mmc/host/omap_hsmmc.c | 90 ++++++++- include/linux/mmc/core.h | 6 +- include/linux/mmc/host.h | 19 ++ lib/Kconfig.debug | 11 + 12 files changed, 1187 insertions(+), 292 deletions(-) -- 1.7.4.1

13 years, 11 months

Generating ancillary sections with gas

by Dave Martin

Hi Michael, This thread about how to generate ancillary sections using gas has resurfaced again. Do you know who might be available from the toolchain group to take a look at this? It appears that this issue can best be solved by a change to gas (or, possibly, to gcc). Cheers ---Dave References: Dynamic patching in discarded sections <http://thread.gmane.org/gmane.linux.kernel/1152142> Generating ancilliary sections with gas <http://thread.gmane.org/gmane.linux.linaro.toolchain/686>

13 years, 11 months

Draft daily (hmm) cloud builds of Android toolchain from bzr

by Paul Sokolovsky

Hello, Alexander, I've set up builds of Android toolchain from bzr: https://android-build.linaro.org/builds/~pfalcon/linaro-toolchain-4.5-bzr/ https://android-build.linaro.org/builds/~pfalcon/linaro-toolchain-4.6-bzr/ Jim, I had to revamp bzr build in linaro-build.sh: http://git.linaro.org/gitweb?p=people/pfalcon/android/toolchain/build.git;a… Note that it now expects bzr branch with explicit version, e.g. lp:gcc-linaro/4.5 or lp:gcc-linaro/4.6 . Well, now the issue: the builds above are not quite ready to be daily. That's because bzr checkout is slow, and is also quite big. Normal bzr clone takes 1.1Gb and cloud build takes 1hr instead of 30min with a tarball. I tried to play with bzr checkout --lightweight, but ctrl+c'ed it when it showed that it dealt with 1.3Gb of stuff (surprisingly, after break, I saw almost empty local empty structure, so I wonder if that wasn't d/l counter, but even then it's awfully slow). So, where do we go from here? Unless there's tip export feature directly out of remote repo for bzr (bzr export seem to requite local working copy), we'd need to play mirror, this time bzr, again %). -- Best Regards, Paul

13 years, 11 months

[NOTES] Dev Platforms Status Meeting Notes and Actions 6/16

by Tom Gall

Enclosed you'll find a link to the agenda, notes and actions from the Linaro Developer Platforms Weekly Status meeting held on June 16th in #linaro-meeting on irc.freenode.net at 14:00 UTC. https://wiki.linaro.org/Platform/DevPlatform/Meetings/2011-06-16 New and Carried Over Actions: * rsalveti to create a RT so wookey can have access to people.linaro and git.linaro * aviksil to sync with npitre about http://lists.infradead.org/pipermail/linux-arm-kernel/2011-March/045283.html * rsalveti to discuss with gwg to see if they should host the smartt wiki and such * rename the team from foundations to devplatform and work with james_w to fix status.linaro.org once the team gets renamed * suihkulokki to see if he can merge his kernel wiki into the linaro HowTo section * rsalveti to propose a call for smartt to identify next steps * rsalveti to make sure all bps from the dev platform team are showing at status.linaro.org Regards, Tom Developer Platforms Team "We want great men who, when fortune frowns will not be discouraged." - Colonel Henry Knox w) tom.gall att linaro.org w) tom_gall att vnet.ibm.com h) tom_gall att mac.com IRC) Dr_Who, tgall_foo

13 years, 11 months

Power Management WG Weekly Status report 2011-06-17

by Mounir Bsaibes

== Meetings minutes == https://wiki.linaro.org/WorkingGroups/PowerManagement/Meetings/2011-06-15 == Weekly Status Report == https://wiki.linaro.org/WorkingGroups/PoweManagement/Status/2011-06-16<https://wiki.linaro.org/WorkingGroups/PowerManagement/Status/2011-06-16> == Summary == * finalize on cpu topology patch * preparing thermal framework for Arm on 2.6.39 * powedebug new and improved various areas of the code Regards, Mounir

13 years, 11 months

Kernel WG Weekly Status report 2011-06-17

by Mounir Bsaibes

== Meetings minutes == https://wiki.linaro.org/WorkingGroups/Kernel/Meetings/2011-06-13 == Weekly Status Report == https://wiki.linaro.org/WorkingGroups/Kernel/Status/2011-06-16 == Summary == * Linaro kernel will be freezed one week before the monthly release. * linaro-android tree is now available: http://git.linaro.org/gitweb?p=people/jstultz/android.git;a=shortlog;h=refs… * Was able to build 99% of randconfig on all our member's current platforms * Completed the power measurement with and without memory regions patches Regards, Mounir

13 years, 11 months

Linaro 11.05 weekly testing 2011-06-16

by Fathi Boudra

Hi, This is a message sent out once per week to call on our community to encourage all Linux/ARM enthusiasts to try out the latest preview images of our Linaro Evaluation Builds (LEBs) for Android Handset and Ubuntu Desktop/Netbook. These images showcase the current state of development on our LEBs images on their way to the next release: 11.06. * Android: http://snapshots.linaro.org/offspring/11.05-daily/linaro-android/leb-panda/… * Ubuntu: http://snapshots.linaro.org/offspring/11.05-daily/linaro-ubuntu-desktop/201… http://snapshots.linaro.org/offspring/11.05-daily/linaro-hwpacks/panda-x11-… On top of the official Linaro Evaluation Builds, the Platform Team hosts a set of functional images and board support packages that are typically released by Linaro engineers for developers that have different images requirements. These images are not officially supported release artifacts and are provided on a best-effort basis in the hope that they can be useful for the Linux/ARM enthusiasts community. The download locations for these so called "Developers and Community Builds" can be found below. Developer Images based on Android with vanilla AOSP experience using linux-linaro mainline kernel as well as linaro toolchain: * Android Mainline for BeagleBoardr-xM: http://snapshots.linaro.org/offspring/11.05-daily/linaro-android/beaglexm/2… * Android Mainline for PandaBoard: http://snapshots.linaro.org/offspring/11.05-daily/linaro-android/panda/2011… Developer Images based on Ubuntu: Note: Ubuntu images are distributed in two parts: 1. a SoC independent userspace rootfs (the image) 2. a Soc specific BSP (the hwpack) * Nano: http://snapshots.linaro.org/offspring/11.05-daily/linaro-nano/20110616/0/im… * ALIP: http://snapshots.linaro.org/offspring/11.05-daily/linaro-alip/20110616/0/im… * Developer: http://snapshots.linaro.org/offspring/11.05-daily/linaro-developer/20110616… Not officially supported community board support packages are also provided for either boards that don't meet our Linaro Evaluation Builds criterias. The idea is that you can combine them freely (e.g. combine an imx51 hwpack with Nano or Developer); though in practice UI images might not work. A list of all hardware packs hosted by Linaro Platform can be found below: http://snapshots.linaro.org/offspring/11.05-daily/linaro-hwpacks/ Make your way to the installation instructions: https://wiki.linaro.org/Platform/Android/ImageInstallation https://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation For an explanation on how to test and submit your results to the QA tracker at: http://qatracker.linaro.org For an explanation of how to use the qatracker please see: https://wiki.linaro.org/QA/QATracker Cheers, Fathi -- Linaro Release Manager | Platform Project Manager

13 years, 11 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev