linaro-dev March 2011

linaro-dev@lists.linaro.org

123 participants
172 discussions

Booting linux-linaro-2.6.37 on Beagle Board

by Avik Sil

Hi, I tried booting linux-linaro-2.6.37 kernel on my beagle board C4. I executed following: 1. Installed linaro on a 4 GB SD card using linaro-image-tools 0.4.1 with hwpack daily snapshot hwpack_linaro-omap3_20110125-0_armel_supported.tar.gz and linaro-natty-headless-tar-20101202-1.tar.gz. It was booting properly on my BB. 2. Cloned linux-linaro-2.6.37. Changed to source directory 3. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap2plus_defconfig 4. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- menuconfig (enabled EARLY_PRINTK) 5. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage 6. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules 7. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules_install INSTALL_MOD_PATH=/media/rootfs 8. cp arch/arm/boot/uImage /media/boot; sync Everything went on smoothly. Then I put the SD card on BB and powered it on. I got a kernel panic: http://paste.ubuntu.com/560562 Please help me figuring out the problem. Is it because I didn't create uInitrd? If so, then how to create it for ARM? Regards, Avik

13 years

gcc: Thumb interworking and weakly linked functions

by Aneesh V

Hi, I have an interesting observation that I thought might be interesting to the tool-chain team. I was trying to build u-boot in Thumb2 for OMAP4. Everything was fine until I added some patches recently. One of these patches introduced an API (let's say foo()) that has a weakly linked alias(let's say __foo()) and a strongly linked implementation(the real foo()) in an assembly file. Although I give -mthumb and -mthumb-interwork for all the files, apparently GCC generates ARM code for assembly files. In the final image foobar() calls foo() using a BL. Since foobar() is in Thumb and foo() in ARM, it ends up crashing. Looks like foobar() assumed foo() to be Thumb because __foo() is Thumb. Also I see that 'objdump -S' aborts when it tries to parse foo(). I could workaround this problem by having foo() also in a C file that in turn calls into the assembly file. I tried Linaro GCC 4.5.2 and Codesourcery Lite GCC 4.4.1. Both seem to have the issue. Isn't this an issue with GCC or am I missing something? -Aneesh

13 years, 11 months

Better reviews for the same cost in gcc-linaro

by Michael Hope

We currently use a feature branch / merge request / merge / test / push approach in gcc-linaro. This works fine for a reasonable cost but can mean that patches sit unreviewed and unmerged for up to a month. Ramana, Andrew, and I had a talk about this earlier in the week and I've written up the ideas here: https://wiki.linaro.org/MichaelHope/Sandbox/ReviewThoughts We're a bit unique as gcc-linaro started from a mature base, running the testsuite takes days, and the product is so big that bzr takes a long time to work on it. If you have experience in running a master branch or ideas on continious integration please have a read. -- Michael

14 years, 8 months

[PATCH 0/5] consolidate sdhci pltfm & OF drivers and get them self registered

by Shawn Guo

Here are what the patch set does. * Remove .probe and .remove hooks from sdhci-pltfm.c and make it be a pure common helper function providers. * Add .probe and .remove hooks for sdhci pltfm drivers sdhci-cns3xxx, sdhci-dove, sdhci-tegra, and sdhci-esdhc-imx to make them self registered with calling helper functions created above. * Migrate the use of sdhci_of_host and sdhci_of_data to sdhci_pltfm_host and sdhci_pltfm_data, so that OF version host and data structure works can be saved, and pltfm version works for both cases. * Add OF common helper stuff into sdhci-pltfm.c, and make OF version sdhci drivers sdhci-of-esdhc and sdhci-of-hlwd become self registered as well, so that sdhci-of-core.c and sdhci-of.h can be removed. * Consolidate the OF and pltfm esdhc drivers into one with sharing the same pair of .probe and .remove hooks. As a result, sdhci-esdhc-imx.c and sdhci-of-esdhc.c go away, while sdhci-esdhc.c comes in and works for both MPCxxx and i.MX. * Eliminate include/linux/mmc/sdhci-pltfm.h with moving stuff into drivers/mmc/host/sdhci-pltfm.h. And the benefits we gain from the changes are: * Get the sdhci device driver follow the Linux trend that driver makes the registration by its own. * sdhci-pltfm.c becomes simple and clean as it only has common helper stuff there now. * All sdhci device specific things are going back its own driver. * The dt and non-dt drivers are consolidated to use the same pair of .probe and .remove hooks. * SDHCI driver for Freescale eSDHC controller found on both MPCxxx and i.MX platforms is consolidated to use the same one .probe function. The patch set works against the tree below, and was only tested on i.mx51 babbage board, all other targets were build tested. git://git.secretlab.ca/git/linux-2.6.git devicetree/test Comments are welcomed and appreciated. Regards, Shawn PS: The first patch is a squashing of the patch set below, which was posted for review a few days back. [PATCH 0/5] make sdhci device drivers self registered Some patches in this series are relatively large, involving more changes than expected, I chose to not split considering they are logically integral, and doing so can reduce the patch quantity much, and make bisect much easier. But sorry for that it makes reviewers' life harder. Shawn Guo (5): mmc: sdhci: make sdhci-pltfm device drivers self registered mmc: sdhci: eliminate sdhci_of_host and sdhci_of_data mmc: sdhci: make sdhci-of device drivers self registered mmc: sdhci: consolidate sdhci-of-esdhc and sdhci-esdhc-imx mmc: sdhci: merge two sdhci-pltfm.h into one drivers/mmc/host/Kconfig | 71 ++++--- drivers/mmc/host/Makefile | 17 +- drivers/mmc/host/sdhci-cns3xxx.c | 68 ++++++- drivers/mmc/host/sdhci-dove.c | 69 ++++++- drivers/mmc/host/sdhci-esdhc-imx.c | 149 ------------- drivers/mmc/host/sdhci-esdhc.c | 412 ++++++++++++++++++++++++++++++++++++ drivers/mmc/host/sdhci-of-core.c | 247 --------------------- drivers/mmc/host/sdhci-of-esdhc.c | 89 -------- drivers/mmc/host/sdhci-of-hlwd.c | 89 +++++++- drivers/mmc/host/sdhci-of.h | 42 ---- drivers/mmc/host/sdhci-pltfm.c | 251 +++++++++------------- drivers/mmc/host/sdhci-pltfm.h | 36 +++- drivers/mmc/host/sdhci-tegra.c | 187 ++++++++++------- include/linux/mmc/sdhci-pltfm.h | 35 --- 14 files changed, 912 insertions(+), 850 deletions(-)

14 years, 9 months

[PATCH 0/2] SMDKV310 Board support

by Chander Kashyap

Hi, This patchset adds support for a new board SMDKV310, based on S5PV310 SOC. This SOC is very similar to S5PC210 SOC, hence we are re-using this SOC code. Chander Kashyap (2): ARMV7: Adding support for Samsung SMDKV310 Board ARMV7: MMC SPL Boot support for SMDKV310 board Makefile | 11 +- board/samsung/smdkv310/Makefile | 46 ++ board/samsung/smdkv310/config.mk | 1 + board/samsung/smdkv310/lowlevel_init.S | 549 ++++++++++++++++++++ board/samsung/smdkv310/mem_setup.S | 632 +++++++++++++++++++++++ board/samsung/smdkv310/smdkv310.c | 138 +++++ boards.cfg | 1 + include/configs/smdkv310.h | 199 +++++++ spl/board/samsung/smdkv310/Makefile | 104 ++++ spl/board/samsung/smdkv310/mmc_boot.c | 82 +++ spl/board/samsung/smdkv310/tools/mkv310_image.c | 103 ++++ spl/board/samsung/smdkv310/u-boot.lds | 86 +++ 12 files changed, 1951 insertions(+), 1 deletions(-) create mode 100644 board/samsung/smdkv310/Makefile create mode 100644 board/samsung/smdkv310/config.mk create mode 100644 board/samsung/smdkv310/lowlevel_init.S create mode 100644 board/samsung/smdkv310/mem_setup.S create mode 100644 board/samsung/smdkv310/smdkv310.c create mode 100644 include/configs/smdkv310.h create mode 100644 spl/board/samsung/smdkv310/Makefile create mode 100644 spl/board/samsung/smdkv310/mmc_boot.c create mode 100644 spl/board/samsung/smdkv310/tools/mkv310_image.c create mode 100644 spl/board/samsung/smdkv310/u-boot.lds

14 years, 10 months

UTRACE/UPROBE support on ARM

by Frederic Turgis

Hi all, In the scope of my work on systemtap, I would like to have a look to its user-space instrumentation capabilities. Systemtap relies on uprobes+utrace for that purpose so has anyone some feedback/global view on these with regards to ARM ? utrace did not make it into the mainline and would need more to convince Linux. I have also seen that a utraceless uprobe is emerging. There is also a PPA with a utrace enabled kernel but this is not covering ARM. I am in parallel seeking info on utrace-devel mailing list. thanks for any help Regards Fred

14 years, 10 months

Libraries with NEON backends

by Michael Hope

Hi there. I'm looking for areas where the toolchain could generate faster code, and a good way of doing that is seeing how compiled code does against the best hand-written code. I know of skia, ffmpeg, pixman, Orc, and efl - what others are out there? Thanks for any input, -- Michael

14 years, 10 months

OMAP4 MPU DVFS patches

by Vishwanath Sripathy

Hi Nicolas, Attached patch set has support for MPU DVFS (cpufreq) on OMAP4 and these are rebased against latest .38 linaro kernel. omap cpufreq driver changes are already posted to lo (https://patchwork.kernel.org/patch/589081/) and OMAP4 DVFS layer changes will be upstreamed once Basic DVFS framework is accepted. Kindly let me know if you can merge these patches for .38 linaro kernel. Regards Vishwa

14 years, 10 months

[PATCH android/toolchain/build] Add --enable-graphite option to build script

by Jim Huang

GCC 4.5 and up supports graphite optimization, and cloog and ppl are required. This change attempts to support some combinations of ppl and cloog/cloog-ppl libraries. Since cloog and ppl are written in C++, it implies we might suffer from C++ ABI breakage problems when host environment changes, that is a well-known issue in GNU/Linux distributions. Thus, we have to drop runtime libstdc++ dependency by statically linking libstdc++. Code Review: https://review.source.android.com//#change,22033 PS: The attachment contains the patch against HEAD in Linaro's android/toolchain/build.git, but please make yours comments via gerrit since this change is generic in upstream.

14 years, 10 months

[PATCH] toolchain/build: Integrate Linaro-GDB in Android toolchain build system

by Luse Cheng

Integrate Linaro-GDB in Android toolchain build system --- linaro-build.sh | 126 ++++++++++++++++++++++++++++++++++-------------------- 1 files changed, 79 insertions(+), 47 deletions(-) diff --git a/linaro-build.sh b/linaro-build.sh index 18d4c84..388ee7a 100755 --- a/linaro-build.sh +++ b/linaro-build.sh @@ -20,6 +20,7 @@ ARG_WGET_LINARO_GCC_SRC= ARG_BZR_LINARO_GCC_SRC= ARG_WITH_GCC= +ARG_WITH_GDB= ARG_WITH_SYSROOT= ARG_APPLY_PATCH=no @@ -54,72 +55,91 @@ usage() { echo " --prefix=<path> Specify installation path [/tmp/android-toolchain-eabi]" echo " --toolchain-src=<path> Toolchain source directory [`dirname $PWD`]" echo " --with-gcc=<path> Specify GCC source (support: directory, bzr, url)" + echo " --with-gdb=<path> Specify gdb source (support: directory, bzr, url)" echo " --with-sysroot=<path> Specify SYSROOT directory" echo " --apply-gcc-patch=<yes|no> Apply Linaro's extra gcc-patches [no]" echo " --help Print this 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} fails." +# $1 - package name (gcc, gdb, etc) +# $2 - value of ARG_WITH_package (lp:*, http://*) +downloadFromBZR() { + local package=$1 + local MY_LP_LINARO_PKG=$2 + local src_dir=${MY_LP_LINARO_PKG#*:} + + local PACKAGE_NAME=`echo $package | tr "[:lower:]" "[:upper:]"` + eval "ARG_LINARO_${PACKAGE_NAME}_SRC_DIR=${src_dir}" + + [ ! -d ${ARG_TOOLCHAIN_SRC_DIR}/$package ] && mkdir -p "${ARG_TOOLCHAIN_SRC_DIR}/$package" + if [ ! -d "${ARG_TOOLCHAIN_SRC_DIR}/$package/${src_dir}" ]; then + info "Use bzr to clone ${MY_LP_LINARO_PKG}" + RUN=`bzr clone ${MY_LP_LINARO_PKG} ${ARG_TOOLCHAIN_SRC_DIR}/$package/${src_dir}` + [ $? -ne 0 ] && error "bzr ${MY_LP_LINARO_PKG} fails." else - info "${ARG_TOOLCHAIN_SRC_DIR}/gcc/${ARG_LINARO_GCC_SRC_DIR} already exists, skip bzr clone" + info "${ARG_TOOLCHAIN_SRC_DIR}/$package/${src_dir} already exists, 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 +# $1 - package name (gcc, gdb, etc) +# $2 - arg (lp:*, http://*) +downloadFromHTTP() { + local package=$1 + local url=$2 + local file=`basename $url` + + local PACKAGE_NAME=`echo $package | tr "[:lower:]" "[:upper:]"` + + info "Use wget to get $file" + if [ -f "${ARG_TOOLCHAIN_SRC_DIR}/${file}" ] || [ -f "${ARG_TOOLCHAIN_SRC_DIR}/$package/${file}" ]; then #TODO: Add md5 check - info "${MY_LINARO_GCC_FILE} is already exist, skip download" + info "${file} is already exist, skip download" else - RUN=`wget $1` - [ $? -ne 0 ] && error "wget $1 error" + wget "$url" || error "wget $1 error" + mv "$file" "${ARG_TOOLCHAIN_SRC_DIR}/$package" || error "fail to move $file" #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 + local src_dir=$(basename $file) + src_dir=$(echo $src_dir | sed "s/$\.tar\.bz2\|\.tar\.gz\|\.tgz\|\.tbz$//") + eval "ARG_LINARO_${PACKAGE_NAME}_SRC_DIR=${src_dir}" } -getGCCFrom() { - # set empty to detect error - ARG_LINARO_GCC_SRC_DIR= - ARG_LINARO_GCC_VER= +# $1 - value of ARG_WITH_package +getPackage() { + local package=$(basename $1) + local version=${package#*-} + version=$(echo $version | sed "s/$\.tar\.bz2\|\.tar\.gz\|\.tgz\|\.tbz$//") + package=${package%%-*} + + local PACKAGE_NAME=`echo $package | tr "[:lower:]" "[:upper:]"` case $1 in lp:*) # bzr clone lp:gcc-linaro - downloadFormBZR $1 + downloadFromBZR $package $1 ;; http://*) # snapshot URL: http://launchpad.net/gcc-linaro/4.5/4.5-2011.03-0/+download/gcc-linaro-4.5-… - downloadFormHTTP $1 + downloadFromHTTP $package $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 + [ ! -d "${ARG_TOOLCHAIN_SRC_DIR}/$package/$1" ] && error "$ARG_TOOLCHAIN_SRC_DIR/$package/$1 not exist" + eval "ARG_LINARO_${PACKAGE_NAME}_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 + # verify version + case $package in + gcc) + # make sure version is greater than 4.5 + ver=`echo $version | grep -o "^4\.$[5-9]\|[1-9][0-9]$"` + if [ x"$version" = x"" ]; then + warn "Cannot detect version for $package-$version, 4.5 is used" + version="4.5" + fi + ;; + esac + + eval "ARG_LINARO_${PACKAGE_NAME}_VER=$version" } while [ $# -gt 0 ]; do @@ -136,6 +156,9 @@ while [ $# -gt 0 ]; do --with-gcc=*) ARG_WITH_GCC="${ARG#*=}" ;; + --with-gdb=*) + ARG_WITH_GDB="${ARG#*=}" + ;; --with-sysroot=*) ARG_WITH_SYSROOT="${ARG#*=}" ;; @@ -160,7 +183,7 @@ if [ "${ARG_TOOLCHAIN_SRC_DIR}" = "" ] || [ ! -f "${ARG_TOOLCHAIN_SRC_DIR}/build error "--toolchain-src-dir is not set or ${ARG_TOOLCHAIN_SRC_DIR} is not ANDROID_TOOLCHAIN_ROOT" fi -if [ "${ARG_WITH_GCC}" = "" ]; then +if [ x"${ARG_WITH_GCC}" = x"" ]; then error "Must specify --with-gcc to build toolchain" fi @@ -171,7 +194,11 @@ if [ ! -z "${ARG_WITH_SYSROOT}" ]; then BUILD_SYSROOT="--with-sysroot=${ARG_WITH_SYSROOT}" fi -getGCCFrom $ARG_WITH_GCC +for package in ${!ARG_WITH*}; do + if [ x"${!package}" != "x" ]; then + getPackage ${!package} + fi +done if [ "x${ARG_APPLY_PATCH}" = "xyes" ]; then note "Will apply patches in toolchain/gcc-patches/${ARG_LINARO_GCC_VER}" @@ -186,8 +213,13 @@ if [ "x${ARG_APPLY_PATCH}" = "xyes" ]; then fi -GCC_VARIANT=`basename ${ARG_LINARO_GCC_SRC_DIR}` -GCC_VARIANT=${GCC_VARIANT#gcc-*} +if [ x"${ARG_WITH_GCC}" != x"" ]; then + BUILD_WITH_GCC="--with-gcc-version=${ARG_LINARO_GCC_VER}" +fi + +if [ x"${ARG_WITH_GDB}" != x"" ]; then + BUILD_WITH_GDB="--with-gdb-version=${ARG_LINARO_GDB_VER}" +fi if echo "$BUILD_ARCH" | grep -q '64' ; then info "Use 64-bit Build Enviorment" @@ -204,11 +236,11 @@ ${ARG_TOOLCHAIN_SRC_DIR}/build/configure \ --disable-docs --disable-nls \ --host=${BUILD_HOST} --build=${BUILD_HOST} \ ${BUILD_SYSROOT} \ - --with-gcc-version=${GCC_VARIANT} \ + ${BUILD_WITH_GCC} \ + ${BUILD_WITH_GDB} \ --with-binutils-version=2.20.1 \ --with-gmp-version=4.2.4 \ - --with-mpfr-version=2.4.1 \ - --with-gdb-version=7.1.x + --with-mpfr-version=2.4.1 make make install -- 1.7.0.4

14 years, 10 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev March 2011