linaro-dev March 2011

linaro-dev@lists.linaro.org

123 participants
172 discussions

by Per Forlin

Hi, If I mess up the u-boot in my efikamx smart book how can I install a new one? I tried booting with an SD-card image from http://www.powerdeveloper.org/asset/by-id/116. I guess this only works if I have a working u-boot in place. I don't have the serial/JTAG connector. Is this what I need in order to recover? Thanks, Per

14 years, 1 month

Display support for Pandaboard

by Anand Gadiyar

Hi all, Per Nicolas' request, I've compiled a list of all patchsets needed to get functional display on the Pandaboard. There are 35 patches in all, over 6 series, plus one patch for the board file to enable the DVI support. I've set up two branches (against v2.6.38-rc4, and against the head of linux-linaro-2.6.37 as of today) to make it easy for people to extract and test these. They are available in my git tree here: git://dev.omapzoom.org/pub/scm/anand/linux-omap-usb.git in the display-patches-for-v2.6.38-rc4 and display-patches-for-linaro-37 branches respectively. I've updated the bug report for this issue (Bug #707038) with links to the component series, as well as the link to my tree above. (I'll make sure these two branches stick around - at least as a reference - until the patches make it upstream). @Nicolas, None of these have been queued up by the respective maintainers yet, so they aren't in linux-next as of today. However I believe there are no outstanding review comments for these. I can send a pull request for these if it's okay with you. Let me know if you need them based off any particular tag/commit/branch. - Anand

14 years, 1 month

[NOTES] Minutes & Actions: Toolchain Working Group meetings of Mar 07 & Mar 09, 2011

by Mounir Bsaibes

Enclosed you'll find a link to the agenda, minutes and actions from the Linaro toolchain working group weekly meetings of March 07 & March 09, 2011. https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2011-03-07 https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2011-03-09 == Summary == * Did the 2011.03 releases of Linaro GCC 4.5, 4.6, Linaro GDB 7.2, and Linaro QEMU * Linaro QEMU now contains Versatile Express support. * First couple of optimised string routines are now in Ubuntu * Continuing with benchmarks. * Re-run against FSF trunk to see the areas we can improve on * Continuing progress on SMS optimisation, GDB correctness, and libffi Regards, Mounir

14 years, 1 month

[NOTES] Minutes & Actions: Kernel Working Group meetings of March 7, 2011

by Mounir Bsaibes

Enclosed you'll find a link to the agenda, minutes, actions and IRC logs from the Linaro kernel working group weekly meetings of March 07, 2011. https://wiki.linaro.org/WorkingGroups/KernelConsolidation/Meetings/2011-03-… == Summary == * Bug reviews * Google Summer of code * Patches submission reminder * Trying to get first pass at the kconfig fragments work in such a state that can be sent for initial review * Sending out the V2 patch for MX51 dt support * Will merge the MX53 loco board support patchset soon. * Sent out v13 of the clk-common patches, tweaked them for !CONFIG_USE_COMMON_STRUCT_CLK compatibility, and sent out v14 * A backlog of patches being reviewed to comment on and/or pick up into devicetree/arm, expect updates later this week Regards, Mounir

14 years, 1 month

Linaro 11.05 weekly testing 2011-03-10

by Jamie Bennett

Hi, This is a message sent out once per week to call on our community to help test the Linaro evaluation builds we produce. If you have supported hardware, as found on: http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/ please help our initiative by testing: Ubuntu Desktop: http://snapshots.linaro.org/11.05-daily/linaro-ubuntu-desktop/ Nano: http://snapshots.linaro.org/11.05-daily/linaro-nano/ ALIP: http://snapshots.linaro.org/11.05-daily/linaro-alip/ Developer Tools: http://snapshots.linaro.org/11.05-daily/linaro-developer/ Make your way to: http://wiki.linaro.org/Releases/DailyBuilds 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 Regards, Jamie. -- Linaro Release Manager

14 years, 1 month

Cross toolchain source packages status

by Marcin Juszkiewicz

Ubuntu/natty got some cross toolchain updates recently so it is installable again. This gave me some free time to work on improvements. And this mail is an attempt to summary it and to provide some ideas/questions. = Introduction = During Emdebian sprint it was decided that my source packages will be used in Debian to provide cross toolchains for users in archive itself (as now Emdebian team autobuilds them into separate archive). We created crosstoolchain project [1] at Alioth and plan to keep Debian branches in git.debian.org repository [2]. = Existing branches = Speaking of branches - there are several ones in my git repository [3] and some of them are also present as Bazaar branches on Launchpad. This list follows: debian/experimental/armel-cross-toolchain-base debian/experimental/gcc-4.5-armel-cross debian/experimental/gcc-4.6-armel-cross debian/unstable/gcc-4.4-armel-cross Those ones can be used to provide cross toolchain for Debian. First one is really ugly as for now it contains a copy of eglibc and linux-2.6 packaging. I have to report few patches [4][5][6] for both components to get this situation sorted. GCC ones do not have any such problems. ubuntu/natty/armel-cross-toolchain-base ubuntu/natty/gcc-4.4-armel-cross ubuntu/natty/gcc-4.5-armel-cross Those ones will be soon sent for review/merge/upload into Ubuntu. ubuntu/not-used/gdb-armel-cross Superseeded by gdb-multiarch package - gdb 7.2-1ubuntu8 or newer required. ubuntu/ppa-backport/armel-cross-toolchain-base ubuntu/ppa-backport/gcc-4.5-armel-cross ubuntu/ppa-backport/patches Those branches are used to generate packages in Linaro toolchain backport PPA [7]. "/patches" branch keeps all patches which I use to alter components. = Status = During sprint I merged 3 branches of armel-cross-toolchain-base into one set of rules so today there are not differences between Ubuntu ones and Debian one contains extra debian/packaging directory with copies of eglibc/debian and linux-2.6/debian dirs. Generation of debian/control file is now inside of debian/rules so differences in build dependencies are handled. Switch between Ubuntu and Debian is sorted by using "lsb_release" (idea taken from gcc-4.5) and PPA build can be enabled by "touch debian/ppa". = Ideas = There was idea to generate just one source package from this (so it would be debian/experimental/armel-cross-toolchain-base branch) and generate all versions from it. I think that this will work but first we need to get Debian version into state which will be acceptable for inclusion into archive. = Problems = Main problem is debian/packaging/ directory in Debian version. I need review of [4] patch and then will report a bug against eglibc. = Multiarch versions (future) = When cross build dependencies will be working then we will get rid of armel-cross-toolchain-base package and replace it with binutils-armel-cross (or extend binutils-multiarch to contain "as" and rest of missing binaries). 1. http://alioth.debian.org/projects/crosstoolchain/ 2. http://git.debian.org/?p=collab-maint/cross-toolchain.git;a=summary 3. http://git.linaro.org/gitweb?p=people/hrw/cross-toolchain-packaging.git;a=s… 4. http://42.pl/u/2zj4 5. http://42.pl/u/2zj5 6. http://bugs.debian.org/611382 (merged into http://bugs.debian.org/550776 one) 7. https://launchpad.net/~linaro-maintainers/+archive/toolchain

14 years, 1 month

problem with linaro-media-create

by Aneesh V

Hi, I am trying to prepare an MMC card to boot up Panda with Linaro daily build image. I downloaded linaro-image-tools from: https://launchpad.net/linaro-image-tools I installed all dependencies mentioned in the README and tried to run linaro-media-create like below: sudo ./linaro-media-create --rootfs ext3 --mmc /dev/sdb1 --binary /home/a0393566local/linaro/headless/linaro-natty-headless- tar-20110206-0.tar.gz --hwpack /home/a0393566local/linaro/hwpack /hwpack_linaro-panda_20110206-0_armel_supported.tar.gz --dev panda However, it crashes immediately with the following dump: http://pastebin.com/SV78dP8L Any idea what could be going wrong? Thanks, Aneesh

14 years, 1 month

[PATCH] toolchain/build: Support linaro android toolchain

by Meng-Hsuan Cheng

Add linaro-build.sh to support linaro android toolchain. --prefix= Specify where to install (default: /tmp/android-toolchain-eabi) --toolchain-src= Specify Android toolchain source dir (default: <toolchain/build>/../) --with-gcc= Specify GCC source (support: directory, bzr, url) --apply-gcc-patch=(yes|no) Apply gcc-patches (default: no) --help Print help message Change-Id: I15478ba3b3dd4f49be3767724028e4e4dcade1ca --- linaro-build.sh | 195 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 195 insertions(+), 0 deletions(-) create mode 100755 linaro-build.sh diff --git a/linaro-build.sh b/linaro-build.sh new file mode 100755 index 0000000..57266dd --- /dev/null +++ b/linaro-build.sh @@ -0,0 +1,195 @@ +#!/bin/bash + +# Copyright (C) 2011 Linaro +# +# This file is free software; you can redistribute it and/or modify it +# under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, but +# WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU +# General Public License for more details. + +ARG_PREFIX_DIR=/tmp/android-toolchain-eabi +ARG_TOOLCHAIN_SRC_DIR=${PWD%/build} + +ARG_LINARO_GCC_SRC_DIR= +ARG_WGET_LINARO_GCC_SRC= +ARG_BZR_LINARO_GCC_SRC= + +ARG_WITH_GCC= + +ARG_APPLY_PATCH=no + +abort() { + echo $@ + exec false +} + +error() { + abort "[ERROR] $@" +} + +warn() { + echo "[WARNING] $@" +} + +info() { + echo "[INFO] $@" +} + +note() { + echo "[NOTE] $@" +} + +usage() { + echo "--------------------------------------------------------------------" + echo "--prefix= Specify where to install (default: /tmp/android-toolchain-eabi)" + echo "--toolchain-src= Specify Android toolchain source dir (default: <toolchain/build>/../)" + echo "--with-gcc= Specify GCC source (support: directory, bzr, url)" + echo "--apply-gcc-patch=(yes|no) Apply gcc-patches (default: no)" + echo "--help Print help message" + echo "--------------------------------------------------------------------" +} + +ARG_LINARO_GCC_SRC_DIR= + + +downloadFormBZR() { + local MY_LP_LINARO_GCC=$1 + ARG_LINARO_GCC_SRC_DIR=${MY_LP_LINARO_GCC#*:} + + [ ! -d ${ARG_TOOLCHAIN_SRC_DIR}/gcc ] && mkdir -p "${ARG_TOOLCHAIN_SRC_DIR}/gcc" + if [ ! -d "${ARG_TOOLCHAIN_SRC_DIR}/gcc/${ARG_LINARO_GCC_SRC_DIR}" ]; then + info "Use bzr to clone ${MY_LP_LINARO_GCC}" + RUN=`bzr clone ${MY_LP_LINARO_GCC} ${ARG_TOOLCHAIN_SRC_DIR}/gcc/${ARG_LINARO_GCC_SRC_DIR}` + [ $? -ne 0 ] && error "bzr ${MY_LP_LINARO_GCC} error" + else + info "${ARG_TOOLCHAIN_SRC_DIR}/gcc/${ARG_LINARO_GCC_SRC_DIR} is already exist, skip bzr clone" + fi +} + +downloadFormHTTP() { + info "Use wget to get $1" + local MY_LINARO_GCC_FILE=`basename $1` + if [ -f "${MY_LINARO_GCC_FILE}" ]; then + #TODO: Add md5 check + info "${MY_LINARO_GCC_FILE} is already exist, skip download" + else + RUN=`wget $1` + [ $? -ne 0 ] && error "wget $1 error" + #TODO: Add md5 check + fi + + ARG_LINARO_GCC_SRC_DIR=`basename ${MY_LINARO_GCC_FILE} .tar.bz2` + [ ! -d ${ARG_TOOLCHAIN_SRC_DIR}/gcc ] && mkdir -p "${ARG_TOOLCHAIN_SRC_DIR}/gcc" + if [ ! -d "${ARG_TOOLCHAIN_SRC_DIR}/gcc/${ARG_LINARO_GCC_SRC_DIR}" ]; then + info "untar ${MY_LINARO_GCC_FILE} to ${ARG_TOOLCHAIN_SRC_DIR}/gcc" + tar jxf ${MY_LINARO_GCC_FILE} -C ${ARG_TOOLCHAIN_SRC_DIR}/gcc + else + info "${ARG_TOOLCHAIN_SRC_DIR}/gcc/${ARG_LINARO_GCC_SRC_DIR} is already exist, skip untar" + fi +} + +getGCCFrom() { + # set empty to detect error + ARG_LINARO_GCC_SRC_DIR= + ARG_LINARO_GCC_VER= + + case $1 in + lp:*) # bzr clone lp:gcc-linaro + downloadFormBZR $1 + ;; + http://*) # snapshot url http://launchpad.net/gcc-linaro/4.5/4.5-2011.02-0/+download/gcc-linaro-4.5-… + downloadFormHTTP $1 + ;; + *) # local directory + [ ! -d "${ARG_TOOLCHAIN_SRC_DIR}/gcc/$1" ] && error "$ARG_TOOLCHAIN_SRC_DIR/gcc/$ARG_LINARO_GCC_SRC_DIR not exist" + ARG_LINARO_GCC_SRC_DIR=$1 + esac + + ARG_LINARO_GCC_VER=`echo ${ARG_LINARO_GCC_SRC_DIR} | grep -o "4\.[5-9]"` + if [ ${ARG_LINARO_GCC_VER} = "" ]; then + warn "Cannot detect version for ${ARG_LINARO_GCC_VER}, 4.5 is used" + ARG_LINARO_GCC_VER=4.5 + fi +} + +while [ $# -gt 0 ]; do + ARG=$1 + ARG_PARMS="$ARG_PARMS '$ARG'" + shift + case "$ARG" in + --prefix=*) + ARG_PREFIX_DIR="${ARG#*=}" + ;; + --toolchain-src=*) + ARG_TOOLCHAIN_SRC_DIR="${ARG#*=}" + ;; + --with-gcc=*) + ARG_WITH_GCC="${ARG#*=}" + ;; + --apply-gcc-patch=yes | --apply-gcc-patch=no) + ARG_APPLY_PATCH="${ARG#*=}" + ;; + --help) + usage && abort + ;; + *) + error "Unrecognized parameter $ARG" + ;; + esac +done + +BUILD_ARCH=`uname -m` +BUILD_WITH_LOCAL= +BUILD_HOST= + +if [ "${ARG_TOOLCHAIN_SRC_DIR}" = "" ] || [ ! -f "${ARG_TOOLCHAIN_SRC_DIR}/build/configure" ] ; then + error "--toolchain-src-dir is not set or ${ARG_TOOLCHAIN_SRC_DIR} is not ANDROID_TOOLCHAIN_ROOT" +fi + +if [ "${ARG_WITH_GCC}" = "" ]; then + error "Must specify --with-gcc to build toolchain" +fi + +getGCCFrom $ARG_WITH_GCC + +if [ "x${ARG_APPLY_PATCH}" = "xyes" ]; then + note "Will apply patches in toolchain/gcc-patches/${ARG_LINARO_GCC_VER}" + cd ${ARG_TOOLCHAIN_SRC_DIR}/gcc/${ARG_LINARO_GCC_SRC_DIR} + for FILE in `ls ${ARG_TOOLCHAIN_SRC_DIR}/gcc-patches/${ARG_LINARO_GCC_VER}` ; do + if [ ! -f ${FILE}-patch.log ]; then + note "Applying patch ${FILE}" + git apply ${ARG_TOOLCHAIN_SRC_DIR}/gcc-patches/${ARG_LINARO_GCC_VER}/${FILE} 2>&1 | tee "${FILE}-patch.log" + fi + done + cd - +fi + +ARG_LINARO_GCC_SRC_DIR=${ARG_LINARO_GCC_SRC_DIR#gcc-*} + +if echo "$BUILD_ARCH" | grep -q '64' ; then + info "Use 64-bit Build Enviorment" + BUILD_HOST=x86_64-linux-gnu + CC="gcc -m32" + CXX="g++ -m32" +else + info "Use 32-bit Build Enviorment" + BUILD_HOST=i686-unknown-linux-gnu +fi + +${ARG_TOOLCHAIN_SRC_DIR}/build/configure \ + --prefix=${ARG_PREFIX_DIR} --target=arm-eabi \ + --disable-docs --disable-nls \ + --host=${BUILD_HOST} --build=${BUILD_HOST} \ + --with-gcc-version=${ARG_LINARO_GCC_SRC_DIR} \ + --with-binutils-version=2.20.1 \ + --with-gmp-version=4.2.4 \ + --with-mpfr-version=2.4.1 \ + --with-gdb-version=7.1.x + +make +make install -- 1.7.0.4

14 years, 1 month

Fw: [PATCH][RFC] CC_OPTIMIZE_FOR_SIZE should default to N

by Paul E. McKenney

Thoughts? Thanx, Paul ----- Forwarded message from Jesper Juhl <jj(a)chaosbits.net> ----- Date: Sun, 6 Mar 2011 00:49:58 +0100 (CET) From: Jesper Juhl <jj(a)chaosbits.net> To: linux-kernel(a)vger.kernel.org cc: Andrew Morton <akpm(a)linux-foundation.org>, "Paul E. McKenney" <paulmck(a)linux.vnet.ibm.com>, Ingo Molnar <mingo(a)elte.hu>, Daniel Lezcano <daniel.lezcano(a)free.fr>, Eric Paris <eparis(a)redhat.com>, Roman Zippel <zippel(a)linux-m68k.org> Subject: [PATCH][RFC] CC_OPTIMIZE_FOR_SIZE should default to N I believe that the majority of systems we are built on want a -O2 compiled kernel. Optimizing for size (-Os) is mainly benneficial for embedded systems and systems with very small CPU caches (correct me if I'm wrong). So it seems wrong to me that CC_OPTIMIZE_FOR_SIZE defaults to 'y' and recommends saying 'Y' if unsure. I believe it should default to 'n' and recommend that if unsure. People who bennefit from -Os know who they are and can enable the option if needed/wanted - the majority shouldn't select this. Right? Signed-off-by: Jesper Juhl <jj(a)chaosbits.net> --- Kconfig | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/init/Kconfig b/init/Kconfig index be788c0..7e16268 100644 --- a/init/Kconfig +++ b/init/Kconfig @@ -886,12 +886,12 @@ endif config CC_OPTIMIZE_FOR_SIZE bool "Optimize for size" - default y + default n help Enabling this option will pass "-Os" instead of "-O2" to gcc resulting in a smaller kernel. - If unsure, say Y. + If unsure, say N. config SYSCTL bool -- Jesper Juhl <jj(a)chaosbits.net> http://www.chaosbits.net/ Plain text mails only, please. Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html ----- End forwarded message -----

14 years, 1 month

The android build service is now feature complete!

by Michael Hudson-Doyle

tl;dr version: see https://android-build.linaro.org/mockup/index, click around. Don't expect to be able to do much unless you're in ~linaro-android-builders Hi all, The frontend to the build service that I've been working on for the last couple of weeks is -- to my understanding <wink> -- now feature complete. You can see it at: https://android-build.linaro.org/mockup/index It works better in chrome than firefox currently, although I hope to be through the worst of that soon. You can log in using your Launchpad ID, but access to the interesting functionality (being able to trigger, edit and set up builds) is restricted to members of the ~linaro-android-builders team (I've made Loic, Alexander and Patryk admins of this team as well as myself). There is another team, ~linaro-android-official-builders, whose members can make "official" builds. I've tried pretty hard to make things self explanatory so I don't want to explain too much here. One thing that probably needs explaining is that a "configuration" is a snippet of shell that sets various environment variables that are interpreted by the build scripts, such as MANIFEST_REPO, MANIFEST_BRANCH and the various TARGET_* variables understood by the android build tools. If there's something missing from this or some aspect that seems really badly designed, *please* tell me! Otherwise I'll assume you all love it. I hear a rumour that Alexander wants simpler browsing of build artefacts. I also know it's not especially pretty and the error handling & reporting is a bit inconsistent. If you're curious as to how it works, the web interface is a frontend to jenkins, which is serving at https://android-build.linaro.org/jenkins. Each configuration corresponds to a job in jenkins, with the configuration data stored as the default value for a parameter. There's a lot of javascript (using YUI 3) going on, and in particular most pages get the data they display by making ajax requests directly to jenkins' remote access API. The rest of it is a Django web application, which handles generating the html (though this are only very very lightly templated) and handling the 'write' operations that need server side access control. The code is in lp:~mwhudson/linaro-android/frontend on Launchpad and is pretty messy, although still fairly small (around 1500 lines of code). I plan to spend some time over the next week making the code much more maintainable, but I don't have any other plans for this code myself. Now get criticizing! Cheers, mwh

14 years, 1 month

← Newer
1
...
10
11
12
13
14
15
16
17
18
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev March 2011