linaro-dev

linaro-dev@lists.linaro.org

4332 discussions

by David Rusling

All, for those of you that are here, welcome (especially any newbies), hope you have a good week! For those of you not here, you can join in as all of the sessions are streamed. You can also ask questions via IRC. A good link to the Linaro sessions is here: http://summit.linaro.org/uds-o/ Dave -- David Rusling, CTO http://www.linaro.org Linaro Lockton House Clarendon Rd Cambridge CB2 8FH

14 years, 1 month

Issues with Android toolchain build

by Paul Sokolovsky

Hello Android team, I was working on making Android toolchain buildable using Android build service, and finally I was able to do successful and reproducible builds - of AOSP pristine bare-matal toolchain so far (https://android-build.linaro.org/builds/~pfalcon/aosp-toolchain/). There were few issues which needed to be investigated and resolved, and which I would like to discuss here: 1. make -jN breakage Android build service builds on EC2 XLARGE instances with 16 concurrent make jobs (-j16). This invariably leads to build failure sooner or later (exact location depends on other options and maybe non-deterministic at all). The failure is "error: Link tests are not allowed after GCC_NO_EXECUTABLES." which somehow sends issue-hunting the wrong trail (like sysroot issues, etc.) but after some experiments I reduced this to exactly -j >1 being used, with -j1 it went past usual failure points reliably. 2. Lack of DESTDIR support There's standard GNU autotools variable "DESTDIR" to install package into other directory besides $prefix. It is supported for gcc, binutils, etc., but not for Android's own toolchain/build project. The usual local-use trick is just to pass another prefix just for make install target, and that's what toolchain/build's README suggests. My only concern is "cleanroomness" of the results - suppose make install suddenly wants to rebuild something (libtool used to have such habit), then new prefix may be embedded into some executable, and then hit beyond the usual usage pattern (like, with non-English locale). Still, this is more a theoretical risk, which I as a build engineer should note, but not something to much worry about. 3. libstdc++v3 build toolchain/build's README says that the default is not to build libstdc++v3 and it must be enabled explicitly. But in the current master I found that not to be the case - it gets enabled by default. And its build requires sysroot, so I had to disable it explicitly for bare-metal build. 4. sysroot source So, to build full-fledged toolchain, we need to supply sysroot. What should be source of it? Android build service script I started from extracts it from an official Android SDK release. Is that good enough source? I guess we'd miss some non-released optimizations that way (byteswap ARMv6 optimizations come to mind). Otherwise, what should be used instead? Obvious choice is to build Android target images, then build toolchain on that tree. But that would be too long and expensive. Should we prepare and tar sysroot and provide it as extra build artifact for Android target builds? Also, can there be any machine-specificity, or it's for sure one generic sysroot for specific Android version (with arch-specific things handled via #ifdef's)? Of these 4, first 3 are upstream-related bugreports with known workarounds. I wanted to write them down, but I'm not sure if more can be done about them - if you think it would be useful to submit them as bugs at lp/linaro-android (or directly to upstream?), I can do it. Sysroot issue of course requires input/discussion - in mail or at some LDS session. Thanks, Paul mailto:pmiscml@gmail.com

14 years, 1 month

linaro-android track

by Zach Pfeffer

All, I apologize for the broad distribution. Alexander and I have been getting the Android track going. We have the following topics. Most of these have subscribers. Would everyone mind taking a look through this list and subscribing or suggesting people who should be involved? I'll be getting more details into each of these this week. Hosting and Distribution of Linaro Builds https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-buil… This topic will focus on building and distributing Linaro Android builds. Topics will include: binary and source distribution, source and binary overlays (proprietary components and blobs from TI, Samsung, etc), license click-through, build and distribution location or method (host images and/or support on-demand image builds) and release tagging and naming. Subscribe: https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-buil… Android Code Review https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-code… This discussion will focus on Android code review. Topics will include Gerrit, continuous integration, maintainers, reviewers and validation. We'll focus on integrating the Android development model with Linaro. Subscribe: https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-code… Android Continuous Integration and Building https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-cont… This discussion will focus on Linaro Android continuous integration and builds. Topics include: infrastructure and validation requirements, test subsets for merges and unit testing. Subscribe: https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-cont… Android LEB Validation and Test Suite https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-vali… This discussion will focus on LEB validation and test suites. Topics will include: Monkey, CTS, Monkeyrunner, unit-tests, continuous integration merge tests. Subscribe: https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-vali… 2011 ELC Follow Up and Planning https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-2011… Linaro had a good meeting at the 2011 Embedded Linux Conference. Many things were discussed. This session will talk about next steps and future planning. Subscribe: https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-2011… Android Hardfloat Experiment https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-hard… This session will discuss strategies to find hot-spots that could benefit from hardfloat without breaking overall binary compatibility with market apps. Subscribe: https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-hard… Android LEB Documentation https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-leb-… This session will focus on discussing what documentation we need for LEB use and bundled with releases. Subscribe: https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-leb-… Linaro Android Toolchain Distribution https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-tool… This session will discuss how to distribute the various components of the Linaro toolchain. We'll discuss NDK and platform distribution, support on Ubuntu, Fedora and Mac, what components do we need to publish and benchmarking toolchain improvements. Subscribe: https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-tool… LEB Board Review and Deliverable Requirements https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-leb-… This discussion will talk about defining new member deliverable for Android LEBs, reviewing what's been delivered and assessing if we can raise the bar, discuss other low-cost high-volume board that currently exist or are on the way (Nexus One, Nexus S, Snowball), talk about LEB candidates, discuss cost ceilings (is the Elba board too expensive, for instance). Subscribe: https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-leb-… Open Source Development for Non-Application Cores https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-non-… This session will explore how to open up development for the various DSP and video cores that exist on many SoCs that are running Android to allow open source development of multimedia acceleration. Subscribe: https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-non-… Upstream Android Build https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-upst… This topic will discuss which changes we can upstream. Subscribe: https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-upst… ADB Shell Improvements https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-adb-… The adb shell lacks many features we take for granted. There is a need for a little more functionality, this session will discuss this. Subscribe: https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-adb-… Android Beyond Phones and Advanced Topics https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-beyo… This session will discuss the future of Android. It'll be a brainstorming session to talk about topics like: dual lib (bionic/glibc) support in Android, bringing apt-get into Android, Android as a general computing platform, expanded enterprise networking, expanded packages, traditional Linux application support, security certification and headless Android. Subscribe: https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-beyo… JTAG for the World https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-jtag This session will talk about improving tools for Ubuntu hosted JTAG tools, open JTAG script development and available JTAG platforms. Subscribe: https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-jtag… -Zach

14 years, 1 month

[Michael Hudson-Doyle] Use cases for "Continuous Integration of Linaro Components in LAVA"

by Michael Hudson-Doyle

Not only did I send this later than I wanted to, I got the address wrong...

14 years, 2 months

[Config] Select ARM_ERRATA_753970 for Pandaboard

by Paolo Pisati

flag@omap:~$ dmesg | grep -A 1 L310 [ 0.219024] L310 cache controller enabled [ 0.219055] l2x0: 16 ways, CACHE_ID 0x410000c4, AUX_CTRL 0x7e470000, Cache size: 1048576 B ^^^^^^^^^^^^^^ according to [1], that means Panda has a r3p0 L310 L2 controller. [flag@newluxor linux-linaro-2.6.38]$ git show 885028e commit 885028e4ba4caf49d565c96481e1a05220ecb517 Author: Srinidhi Kasagar <srinidhi.kasagar(a)stericsson.com> Date: Thu Feb 17 07:03:51 2011 +0100 ARM: 6741/1: errata: pl310 cache sync operation may be faulty The effect of cache sync operation is to drain the store buffer and wait for all internal buffers to be empty. In normal conditions, store buffer is able to merge the normal memory writes within its 32-byte data buffers. Due to this erratum present in r3p0, the effect of cache sync operation on the store buffer still remains when the operation completes. This means that the store buffer is always asked to drain and this prevents it from merging any further writes. This can severely affect performance on the write traffic esp. on Normal memory NC one. The proposed workaround is to replace the normal offset of cache sync operation(0x730) by another offset targeting an unmapped PL310 register 0x740. Signed-off-by: srinidhi kasagar <srinidhi.kasagar(a)stericsson.com> Acked-by: Linus Walleij <linus.walleij(a)stericsson.com> Acked-by: Catalin Marinas <catalin.marinas(a)arm.com> Signed-off-by: Russell King <rmk+kernel(a)arm.linux.org.uk> [1]: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0246d/Beibhh… -- bye, p.

14 years, 2 months

Display setups on your work desks

by Marcin Juszkiewicz

Hi I would like to ask about your display setups on work desks because recent changes in pandaboard kernel moves me into 'lets buy another lcd' direction... Now I have two displays on my desk: - 24" 1920x1080 - DVI port is main display of my desktop - VGA port was used with some boards in past - HDMI port was never used - 20" 1680x1050 - DVI (with HDMI->DVI adapter) is main display of pandaboard - VGA is secondary display of desktop or primary display of other (rarely used) PC But Pandaboard has two video outputs: DVI and HDMI. For most of time I used HDMI output but it was with Ubuntu 11.04 kernel. Now I am testing Linaro WIP kernel and it has working DVI output rather then HDMI one... Switching ports on panda requires powering it off in order to not damage it. Guessing which port works is not a way. Connecting panda HDMI to 24" HDMI is also no solution cause this will leave me without display for my desktop. How you people solve that in other way then buying yet-another-lcd?

14 years, 2 months

kmemcheck on ARM

by Christian Robottom Reis

Last quasi-random question of the night: would reviving the kmemcheck ARM port (that IIRC was hacked up a while back) be something useful, or is it something that is too niche to be worth it? At the board's request, I was looking across platform gaps and this feature was one of the things that I found. Thanks, -- Christian Robottom Reis | [+55] 16 9112 6430 | http://launchpad.net/~kiko Linaro Engineering VP | [ +1] 612 216 4935 | http://async.com.br/~kiko

14 years, 2 months

oom-killer, vm.overcommit & swap

by AJ ONeal

I believe that some of these random application crashes claiming to be out-of-memory have to do with the fact that swap is off by default. Knowing that to be an issue from my experience with OpenEmbedded I preemptively set vm.overcommit_memory = 2 vm.overcommit_ratio = 100 in /etc/sysctl.conf However, this seems to have made the issue worse. Has the meaning of these values changed between 2.6.36 and .39? Or are the defaults used with Linaro / Ubuntu more appropriate for swapless systems and those values don't need to be set? I'd appreciate any advise on how to use the full memory of my system and not get out-of-memory errors when I have 50%+ available memory. AJ ONeal

14 years, 2 months

How to make a defconfig that is likely to work well

by AJ ONeal

Is there some sort of base kernel config that I can mixin to the omap2plus_defconfig that will be likely to give me a more successful boot with 2.6.39? Please explain to me the process for creating such a defconfig. Thanks, AJ ONeal

14 years, 2 months

STM at UDS-Budapest

by Deao, Douglas

I am hosting an introductory session on System Trace at the summit. TI's System Trace Module (STM) provides a common protocol for instrumentation messages across multiple cores and system level hardware profiling in complex SoCs. Attached is a whitepaper for background reading. Looking forward to meeting you at the summit. Regards, Doug Deao Texas Instruments

14 years, 2 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev