linaro-dev October 2013

linaro-dev@lists.linaro.org

43 participants
34 discussions

by Ciprian Barbu

Hello, Does anyone have some good instructions on how to run our kernel(s) on the Samsung Chromebook? I'm especially interested in the tools needed to prepare the kernel image and write it to the SD card. Thanks, /Cip

10 years, 10 months

Cross compiling gmp package on x86_64 for foundation model

by Anil Singhar

Hi, I am trying to cross compile gmp on linux machine, the configure and make steps seem to be going fine but when I do make check on the foundation model, I get errors. Here is what I am trying: *Step 1: On x86_64 Ubuntu Host (using :gcc-linaro-aarch64-linux-gnu-4.7-2013.04-20130415_linux)* --------------------------------------------------------------------------------------------------------------------------------- $export AARCH64_TOOLCHAIN=/home/anilss/Linaro/tools/gcc-linaro-aarch64-linux-gnu-4.7-2013.04-20130415_linux/bin $export PATH=$PATH:$AARCH64_TOOLCHAIN $export ARCH=aarch64 $export CROSS_COMPILE=aarch64-linux-gnu- $./configure --build=coreisbr-unknown-linux-gnu --host=aarch64-oe-linux --target=aarch64-oe-linux $make (Note: the above value for build triplet I got while trying to build gmp natively on x86_64 machine where it detected it as * coreisbr-unknown-linux-gnu* and the target/host name *aarch64-oe-linux* for Foundation model system was obtained likewise. However I am not sure if the host and target values are correct.) *Step 2: After this, on the Foundation model (running on another xterm), from the above path (mounted)* ---------------------------------------------------------------------------------------------------------------------------------------- root@genericarmv8:~/anilss/pkgs/gmp/cross_arm64/gmp-5.1.3# make check make check-recursive make[1]: Entering directory `/home/root/anilss/pkgs/gmp/cross_arm64/gmp-5.1.3' Making check in tests make[2]: Entering directory `/home/root/anilss/pkgs/gmp/cross_arm64/gmp-5.1.3/tests' Making check in . make[3]: Entering directory `/home/root/anilss/pkgs/gmp/cross_arm64/gmp-5.1.3/tests' make libtests.la t-bswap t-constants t-count_zeros t-gmpmax t-hightomask t-modlinv t-popc t-parity t-sub make[4]: Entering directory `/home/root/anilss/pkgs/gmp/cross_arm64/gmp-5.1.3/tests' /bin/bash ../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c -o memory.lo memory.c libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c memory.c -fPIC -DPIC -o .libs/memory.o libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c memory.c -o memory.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c -o misc.lo misc.c libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c misc.c -fPIC -DPIC -o .libs/misc.o libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c misc.c -o misc.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c -o refmpf.lo refmpf.c libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c refmpf.c -fPIC -DPIC -o .libs/refmpf.o libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c refmpf.c -o refmpf.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c -o refmpn.lo refmpn.c libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c refmpn.c -fPIC -DPIC -o .libs/refmpn.o libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c refmpn.c -o refmpn.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c -o refmpq.lo refmpq.c libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c refmpq.c -fPIC -DPIC -o .libs/refmpq.o libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c refmpq.c -o refmpq.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c -o refmpz.lo refmpz.c libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c refmpz.c -fPIC -DPIC -o .libs/refmpz.o libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c refmpz.c -o refmpz.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c -o spinner.lo spinner.c libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c spinner.c -fPIC -DPIC -o .libs/spinner.o libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c spinner.c -o spinner.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c -o trace.lo trace.c libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c trace.c -fPIC -DPIC -o .libs/trace.o libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c trace.c -o trace.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=link gcc -std=gnu99 -O2 -pedantic -o libtests.la memory.lo misc.lo refmpf.lo refmpn.lo refmpq.lo refmpz.lo spinner.lo trace.lo ../libgmp.la libtool: link: ar cq .libs/libtests.a .libs/memory.o .libs/misc.o .libs/refmpf.o .libs/refmpn.o .libs/refmpq.o .libs/refmpz.o .libs/spinner.o .libs/trace.o libtool: link: ranlib .libs/libtests.a libtool: link: ( cd ".libs" && rm -f "libtests.la" && ln -s "../libtests.la" "libtests.la" ) gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -pedantic -c t-bswap.c /bin/bash ../libtool --tag=CC --mode=link gcc -std=gnu99 -O2 -pedantic -o t-bswap t-bswap.o libtests.la ../libgmp.la libtool: link: gcc -std=gnu99 -O2 -pedantic -o .libs/t-bswap t-bswap.o ./.libs/libtests.a /home/root/anilss/pkgs/gmp/cross_arm64/gmp-5.1.3/.libs/libgmp.so ../.libs/libgmp.so /home/root/anilss/pkgs/gmp/cross_arm64/gmp-5.1.3/.libs/libgmp.so: could not read symbols: *File in wrong format* * <------* ??? collect2: error: ld returned 1 exit status make[4]: *** [t-bswap] Error 1 make[4]: Leaving directory `/home/root/anilss/pkgs/gmp/cross_arm64/gmp-5.1.3/tests' make[3]: *** [check-am] Error 2 make[3]: Leaving directory `/home/root/anilss/pkgs/gmp/cross_arm64/gmp-5.1.3/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/home/root/anilss/pkgs/gmp/cross_arm64/gmp-5.1.3/tests' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/home/root/anilss/pkgs/gmp/cross_arm64/gmp-5.1.3' make: *** [check] Error 2 root@genericarmv8:~/anilss/pkgs/gmp/cross_arm64/gmp-5.1.3# Will appreciate any help. Thanks, Anil

10 years, 10 months

[PATCH 0/5] libhugetlbfs - Aarch64 support and some fixes

by Steve Capper

Hello, This series adds Aarch64 support and makes some minor tweaks. The first two patches of this series add Aarch64 support to libhugetlbfs. (Starting from 3.11-rc1, the Linux Kernel supports HugeTLB and THP for ARM64). Some general changes are also made: PROT_NONE is added to the mprotect unit test, and the linkhuge_rw test is enabled for 64 bit where there aren't any custom ldscripts. The final patch clears up the superfluous ARM ld.hugetlbfs HTLB_LINK logic. Any comments would be appreciated. Cheers, -- Steve Steve Capper (5): Aarch64 support. Aarch64 unit test fixes. Add PROT_NONE to the mprotect test. Add linkhuge_rw test to 64 bit && !CUSTOM_LDSCIPTS Cleanup ARM ld.hugetlbfs HTLB_LINK logic Makefile | 7 +++++++ ld.hugetlbfs | 7 +------ sys-aarch64elf.S | 34 ++++++++++++++++++++++++++++++++++ tests/Makefile | 2 +- tests/icache-hygiene.c | 7 ++++--- tests/mprotect.c | 6 ++++++ tests/mremap-expand-slice-collision.c | 2 +- 7 files changed, 54 insertions(+), 11 deletions(-) create mode 100644 sys-aarch64elf.S -- 1.8.1.4

10 years, 10 months

Linaro on Zynq

by Patrick Doyle

Is anybody working on (or has already worked on) using Linaro tools & builds on the Zynq SoC from Xilinx? More specifically, is anybody working on using the tools & builds on the microZed board? If so, may I collaborate with you? If not, would folks on this list mind giving me some "getting started" pointers... What toolchain would you recommend? Does it matter that the processor is a Cortex-A9 with NEON™ & Single / Double Precision Floating Point? In the absence of any other guidance, I'm going to proceed down a path of trying the linaro-toolchain-binaries-4.8 on my Ubuntu box to compile the latest U-Boot & Kernel from the Xilinx git repos, attempt to construct a Hardware Pack for the microZed board, and see what happens when I run the Ubuntu Nano build on that. Thanks for any tips or advice you may offer. --wpd

10 years, 10 months

Linaro 13.09 Very slow boot on Pandaboard

by Ola Dahl

Hi, I have downloaded the image for Pandaboard, from http://releases.linaro.org/13.09/ubuntu/panda/panda-raring_developer_201309… I unpack it and copy it to a SD card using Windows Image writer. When the Pandaboard boots, the boot hangs temporarily (circa one minute) after having printed [ 6.891754] init: ureadahead main process (1106) terminated with status 5 [ 7.596893] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro After the minute or so has passed, the printout resumes, and one sees * Setting sensors limits [ OK ] * Loading cpufreq kernel modules... and then the login proceeds with success. When I look in the dmesg printout I see [ 6.143127] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [ 6.891754] init: ureadahead main process (1106) terminated with status 5 [ 7.596893] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro [ 8.069091] udevd[1193]: starting version 175 ing ok [ 10.653472] usb 1-1.1: link qh8-0001/eca3e3c0 start 2 [1/0 us] [ 10.653472] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup [ 10.655517] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 10.904968] init: udev-fallback-graphics main process (1398) terminated with status 1 [ 11.121673] init: plymouth main process (1107) killed by ABRT signal [ 11.128204] init: plymouth-splash main process (1436) terminated with status 2 [ 131.484619] init: alsa-restore main process (1490) terminated with status 99 [ 132.043243] init: plymouth-stop pre-start process (1601) terminated with status 1 [ 132.072296] init: tty1 main process (1602) killed by TERM signal Could it be that some service is started that takes a lot of time? Have you seen this before? Any hints are appreciated! Best regards, Ola

10 years, 10 months

Trusty Tahr open for development

by Matthias Klose

Trusty is now open for development, with syncs from unstable currently running. The development version starts with a new port and with minor updates to the toolchain and some transitions. - GCC 4.8 was updated to the GCC 4.8.2 release and the GCC Linaro 4.8-2013-10 release. Binutils is built from the 2.24 release branch. - An glibc update will follow later during this cycle. - Perl was updated from v5.14 to to v5.18. - Berkeley DB was updated from v5.1 to v5.3. - boost was updated from v1.53 to v1.54. Please check your uploads in a trusty chroot, don't just test in a saucy environment. See [1] how to setup such a development chroot. Trusty is the first development version that sees the AArch64 (arm64) port from the start of the cycle. Buildd resources are still somewhat limited compared to the other architectures, so please ask first on #ubuntu-devel before giving back a build for this port (e.g. compiler complaining about an unreproducible ICE). [1] https://wiki.ubuntu.com/DebootstrapChroot

10 years, 10 months

[question]multi-arch support for arm and arm64

by Zhou Zhu

Hi, We are working on userspace aarch64 and aarch32 apps and we are trying to run 32/64 mode app simultaneously. Is there any multi-arch support for mixed rootfs (has linkers/libs of both arm and arm64)? -- Thanks, -Zhou

10 years, 10 months

Rebuilding Linaro 13.09 panda kernel

by Arun Thomas

Hi, Where can I find the git repo that contains the kernel sources for the Pandaboard 13.09 Ubuntu image? The Linaro wiki mentions the kernel/linux-linaro-3.1.git repo: https://wiki.linaro.org/Resources/HowTo/KernelDeploy I didn't see a kernel/linux-linaro-3.11.git repo, so I'm guessing kernel/linux-linaro-stable.git is the repo I want? To reconstruct the .config that was used to build the kernel, I suppose I should 'cat debug.conf linaro-base.conf omap4.conf panda.conf ubuntu-minimal.conf'? Thanks for your help. Best, Arun

10 years, 10 months

[tool recommendation] tmate terminal sharing

by Christoffer Dall

Hi all, [apologies in advance for the spam nature of this message] I have been using a tool for remote collaboration and problem solving that I find perfect in the context of remote collaboration. It allows you to very easily share a terminal session even behind most firewalls etc. If you're interested, take a look at http://tmate.io/ It's based on tmux keymappings and configuration so if you already use that, you will be extra happy. -Christoffer

10 years, 10 months

auto-serial-console

by Nicolas Dechesne

koen, fathi, riku, i am having issues with auto-serial-console that was initially done by marcin. https://git.linaro.org/gitweb?p=openembedded/meta-linaro.git;a=tree;f=meta-… the main issue is that it conflicts with BSP layer that uses SERIAL_CONSOLE variable. It is very much expected for a BSP layer to set SERIAL_CONSOLE variable. In which case OE will automatically start a serial console http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-core/sysvi… So when using auto-serial-console with a 'proper' BSP layer that set SERIAL_CONSOLE(S) we end up with starting the console twice, one added by OE, one by auto-serial-console. So far, all our OE builds are not using a proper BSP layer, so that's why you don't see the problem, but for our builds we use proper BSP layer... right now, auto-serial-console does 3 things: 1- figure out the serial console port from /proc/cmdline 2- start a console on #1 3- automatically login as root I believe that we should 'do something' to split them into several packages so that we get more granularity. At least #3 needs to be separated out, as #3 is a 'policy'. I would almost expect that 'being able to automatically login as root on the console' is a feature that could (should?) be added to oe-core somehow. What do you think koen? I looked into that, but there isn't any obvious (and trivial) way to do that, but it's certainly doable inside an IMAGE_FEATURE for example. this email is just to start the discussion and get some advices, e.g. i am not asking you to do it ;-) i can work on it, but want to make sure i do it right, with an 'upstream' path if possible. thx nico

10 years, 10 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev October 2013