Linaro-android April 2013

linaro-android@lists.linaro.org

18 participants
25 discussions

Does the linaro source include all the required drivers?

by Guido Romijn

Hi There, I have a question. Does the linaro source include all the required drivers? I'm currently trying to build 13.02 for a Pandaboard ES, but it get's stuck at the boot screen. The kernel is starting, but the infamous "init: untracked pid 1507 exited" message is showing up at the serial log. When scrolling up a bit, my serial log shows the following message: [ 3.250732] PVR_K:(Error): EnableSGXClocks: Unable to scale SGX frequency (-11) [172, /home/guido/linaro02/android/kernel/drivers/g pu/pvr/omap4/sysutils_linux.c] [ 3.266113] omap_sr_disable: omap_sr struct for sr_core not found [ 3.272583] PVR_K:(Error): EnableSGXClocks: Unable to scale SGX frequency (-11) [172, /home/guido/linaro02/android/kernel/drivers/g pu/pvr/omap4/sysutils_linux.c] Scrolling even further up, there is also something I don''t realy understand: [ 0.297973] ------------[ cut here ]------------ [ 0.298004] WARNING: at /home/guido/linaro02/android/kernel/arch/arm/mach-omap2/omap_hwmod.c:1509 _enable+0x234/0x264() [ 0.298004] Modules linked in: [ 0.298065] [<c0019e10>] (unwind_backtrace+0x0/0xf8) from [<c0044b18>] (warn_slowpath_common+0x4c/0x64) [ 0.298065] [<c0044b18>] (warn_slowpath_common+0x4c/0x64) from [<c0044b4c>] (warn_slowpath_null+0x1c/0x24) [ 0.298095] [<c0044b4c>] (warn_slowpath_null+0x1c/0x24) from [<c0022908>] (_enable+0x234/0x264) [ 0.298126] [<c0022908>] (_enable+0x234/0x264) from [<c0022d2c>] (_setup+0xa0/0x170) [ 0.298126] [<c0022d2c>] (_setup+0xa0/0x170) from [<c0022f90>] (omap_hwmod_for_each+0x30/0x5c) [ 0.298156] [<c0022f90>] (omap_hwmod_for_each+0x30/0x5c) from [<c089cd34>] (omap_hwmod_setup_all+0x6c/0x98) [ 0.298187] [<c089cd34>] (omap_hwmod_setup_all+0x6c/0x98) from [<c000864c>] (do_one_initcall+0x110/0x178) [ 0.298217] [<c000864c>] (do_one_initcall+0x110/0x178) from [<c0893854>] (kernel_init+0x8c/0x12c) [ 0.298217] [<c0893854>] (kernel_init+0x8c/0x12c) from [<c001433c>] (kernel_thread_exit+0x0/0x8) [ 0.298278] ---[ end trace 1b75b31a2719ed1c ]--- [ 0.298278] omap_hwmod: mcpdm: cannot be enabled (3)

12 years, 1 month

Agenda posted for Android Platform meeting

by Vishal Bhoj

The agenda has been posted for tomorrow's meeting: https://wiki.linaro.org/Platform/Android/Meetings/2013-04-17 The same agenda is also posted in the doc: https://docs.google.com/a/linaro.org/document/d/1nuqwjLy_Bc3zrRYWOgMBzc4sny… Feel free to add agenda items to discuss. Regards, Vishal

12 years, 1 month

by vipzrx

what is the login-id ？ how can i get one ？ when i $ repo sync , i got this message below : From http://android.git.linaro.org/git-ro/platform/system/media * [new branch] tools_r22 -> aosp/tools_r22 The authenticity of host 'linaro-private.git.linaro.org (91.189.95.50)' can't be established. RSA key fingerprint is 62:1e:b1:73:39:f3:9d:eb:81:87:b8:f8:f7:a8:79:97. Are you sure you want to continue connecting (yes/no)? yes

12 years, 1 month

linaro-android panda build problem -> No gnu/libc-version.h

by Marcus Williford

I need help figuring out what is wrong with my environment, I have followed all instructions that I can find. The build moves a long for a while, so most things work. As I understood from the instructions, I can use the Toolchain included in the prebuilts for gcc-4.7. Environment: Ubuntu 12.04 LTS Linaro Panda 13.03 pinned-manifest.xml export TARGET_PRODUCT=pandaboard export TARGET_SIMULATOR=false export BUILD_TINY_ANDROID= export CPUS=`grep -c processor /proc/cpuinfo` TARGET_TOOLS_PREFIX=prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7-linaro/bin/arm-linux-androideabi- I can see that I have this header in a few places marcus@dwarf1:~/linaro-13.03-src/android$ find . | grep libc-version.h ./prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.7-4.6/sysroot/usr/include/gnu/libc-version.h ./prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.6/sysroot/usr/include/gnu/libc-version.h ./prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.4.3/sysroot/usr/include/gnu/libc-version.h I'm guessing one of the above sysroot's is my root during crosscompile, but I'm not really familiar enough with this part oft he build system. If so, seems like it should see this header. Let me know if anyone has some advice. Marcus Details below: ------------------------------------------- snip Load Address: 80008000 Entry Point: 80008000 Image arch/arm/boot/uImage is ready make[1]: Leaving directory `/home/marcus/linaro-13.03-src/android/kernel/linaro/pandaboard' export PATH=../out/host/linux-x86/bin:/opt/java/bin:/home/marcus/linaro-13.03-src/android/out/host/linux-x86/bin:/home/marcus/linaro-13.03-src/android/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin:/home/marcus/linaro-13.03-src/android/prebuilts/gcc/linux-x86/mips/mipsel-linux-android-4.6/bin:/home/marcus/linaro-13.03-src/android/development/emulator/qtools:/home/marcus/linaro-13.03-src/android/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin:/home/marcus/linaro-13.03-src/android/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin:/home/marcus/linaro-13.03-src/android/development/scripts:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/opt/java/bin:/opt/hadoop/bin:/opt/hadoop/sbin:/home/marcus/android/bin &&\ cd kernel/linaro/pandaboard/tools/perf &&\ mkdir -p /home/marcus/linaro-13.03-src/android/out/target/product/pandaboard/obj/kernel/tools/perf &&\ if [ -e prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7-linaro/bin/arm-linux-androideabi-ld.bfd ]; then LD=prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7-linaro/bin/arm-linux-androideabi-ld.bfd; else LD=prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7-linaro/bin/arm-linux-androideabi-ld; fi && \ make ANDROID_CFLAGS="-mtune=cortex-a9 -mcpu=cortex-a9 -mno-unaligned-access -isystem /home/marcus/linaro-13.03-src/android/bionic/libc/include -isystem /home/marcus/linaro-13.03-src/android/bionic/libc/kernel/common -isystem /home/marcus/linaro-13.03-src/android/bionic/libc/kernel/arch-arm -isystem /home/marcus/linaro-13.03-src/android/bionic/libc/arch-arm/include -I/home/marcus/linaro-13.03-src/android/external/elfutils/libelf -isystem /home/marcus/linaro-13.03-src/android/bionic/libm/include -isystem prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7-linaro/bin/../include -I/home/marcus/linaro-13.03-src/android/out/target/product/pandaboard/obj/kernel/tools/perf" BASIC_LDFLAGS="-nostdlib -Wl,-dynamic-linker,/system/bin/linker,-z,muldefs,-z,nocopyreloc,--no-undefined -L/home/marcus/linaro-13.03-src/android/ -L/home/marcus/linaro-13.03-src/android/out/target/product/pandaboard/system/lib -L/home/marcus/linaro-13.03-src/android/external/elfutils -L/home/marcus/linaro-13.03-src/android/out/target/product/pandaboard/obj/STATIC_LIBRARIES/libelf_intermediates -lpthread -lelf -lm -lc /home/marcus/linaro-13.03-src/android/out/target/product/pandaboard/obj/lib/crtbegin_dynamic.o /home/marcus/linaro-13.03-src/android/out/target/product/pandaboard/obj/lib/crtend_android.o" O=/home/marcus/linaro-13.03-src/android/out/target/product/pandaboard/obj/kernel/tools/perf/ OUTPUT=/home/marcus/linaro-13.03-src/android/out/target/product/pandaboard/obj/kernel/tools/perf/ ARCH=arm CROSS_COMPILE=prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7-linaro/bin/arm-linux-androideabi- LD=$LD prefix=/system NO_DWARF=1 NO_NEWT=1 NO_LIBPERL=1 NO_LIBPYTHON=1 NO_GTK2=1 NO_STRLCPY=1 WERROR=0 && \ cp -f /home/marcus/linaro-13.03-src/android/out/target/product/pandaboard/obj/kernel/tools/perf/perf /home/marcus/linaro-13.03-src/android/out/target/product/pandaboard/system/bin/ make[1]: Entering directory `/home/marcus/linaro-13.03-src/android/kernel/linaro/pandaboard/tools/perf' Makefile:438: *** No gnu/libc-version.h found, please install glibc-dev[el]/glibc-static. Stop. make[1]: Leaving directory `/home/marcus/linaro-13.03-src/android/kernel/linaro/pandaboard/tools/perf' No gnu/libc-version.h found, please install glibc-dev[el]/glibc-static. Stop.

12 years, 1 month

Re: Having SATA issues with Arndale

by Vishal Bhoj

---------- Forwarded message ---------- From: Marcus Matten <mmavdev(a)gmail.com> To: linaro-android <linaro-android(a)lists.linaro.org>, Claude Youn < claude.youn(a)linaro.org> Cc: Date: Thu, 11 Apr 2013 14:38:47 +0200 Subject: Re: Having SATA issues with Arndale Hi, insignal has not responded to any of my inquiries yet. We are trying the latest linaro kernels today, but I have been told off-list here that SATA is not on linaro's critical path. I am hoping for the best though. It'd be a start for me if someone confirmed to have SATA working with the newer arndale boards in question (VERC cpu module, 2012_10_24). Best regards Marcus On Thu, Apr 11, 2013 at 11:46 AM, Fathi Boudra <fathi.boudra(a)linaro.org> wrote: > Hi, > > On 10 April 2013 09:59, Marcus Matten <mmavdev(a)gmail.com> wrote: >> Hi, >> >> i have 2 batches of arndale boards, for the first batch SATA is working, for >> the second batch it isn't. >> >> Short fact: First batch boards have a different CPU board revision >> >> I've described the issue in the following post in the insignal forums in >> more detail: >> >> http://forum.insignal.co.kr/viewtopic.php?f=10&t=2505&sid=50a2da79db788d6bb… >> >> I gather the sources provided with the arndale project have been done mostly >> by linaro, so I am trying to get some help here. >> >> If i am addressing this to the wrong list, please give me a pointer whom i >> could turn to. > > Insignal seems really the right point of contact for your issue. > Are they (and you also) able to reproduce your issue with their kernel? > >> I have 20 of these lying around here and can't get them to work like the >> first batch boards, which would be a significant investment for me going to >> the trash bin as working SATA is mandatory for my use-case. >> >> Best regards >> Marcus

12 years, 1 month

Linaro-android Test result summary for Calender week 15

by Soumya Basak

Hi, Here is the test result summary for Linaro-Android jellybean for Different builds [1] TI-Panda 4430 [2] TI-Panda 4460 [3] Samsung Origen 4412 quad. [4] ARM vexpress A9 Synopsis: Linaro-android jellybean week15 test result, it keeps exactly same result as last week no new bug or known issues fixed in this week. [1] TI-Panda 4430 with Linaro-android jellybean (column:AF) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… Please look into the result spreadsheet for details test result and bug report. [2] TI-Panda 4460 with Linaro-android jellybean (column:AF) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… Please look into the result spreadsheet for details test result. [3] origen 4412 quad with Linaro-android jellybean (column:E) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadDRDV… Please look into the result spreadsheet for details test result and bug report. [4] ARM vexpress-A9 with Linaro-android jellybean (column: AE) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… please look into the result spreadsheet for details result and bug report. With Best regards Soumya Basak

12 years, 1 month

Having SATA issues with Arndale

by Marcus Matten

Hi, i have 2 batches of arndale boards, for the first batch SATA is working, for the second batch it isn't. Short fact: First batch boards have a different CPU board revision I've described the issue in the following post in the insignal forums in more detail: http://forum.insignal.co.kr/viewtopic.php?f=10&t=2505&sid=50a2da79db788d6bb… I gather the sources provided with the arndale project have been done mostly by linaro, so I am trying to get some help here. If i am addressing this to the wrong list, please give me a pointer whom i could turn to. I have 20 of these lying around here and can't get them to work like the first batch boards, which would be a significant investment for me going to the trash bin as working SATA is mandatory for my use-case. Best regards Marcus

12 years, 1 month

Current test case status of Linaro-android Daily Dashboard image report

by Soumya Basak

Hi, As observed from our linux-linaro Android Daily Dashboard image report, http://validation.linaro.org/lava-server/dashboard/image-reports/ it seems that most of the test cases not actively run Daily builds. http://validation.linaro.org/lava-server/dashboard/image-reports/linaro-and… e.g: homescreen, monkeyrunner, shell-binder etc would you please look into the matter, so that shall we remove those test cases in future which are not presently active for the builds .. With Best regards Soumya Basak.

12 years, 1 month

Agenda posted for Android Platform meeting

by Vishal Bhoj

Hi, The agenda has been posted for tomorrow's meeting: https://wiki.linaro.org/Platform/Android/Meetings/2013-04-10 The same agenda is also posted in the doc: https://docs.google.com/a/linaro.org/document/d/1nuqwjLy_Bc3zrRYWOgMBzc4sny… Feel free to add agenda items to discuss. Regards, Vishal

12 years, 1 month

Repo manifests and rebased repositories

by Paul Sokolovsky

Hello, I recently got https://blueprints.launchpad.net/linaro-infrastructure-misc/+spec/rebasing-… to verify current state of affairs with repo handling of SHA revisions for commits which have underlying tags. The blueprints contains full details, let me in this report mail cover just we most important bits. 1. We have been having problem with repositories used in Android releases being rebased later for a long time. 2. Trying to resolve that, we established policy that any revision used in a release must be tagged, to make sure that exact revision stays across rebases. 3. That didn't really work well with "repo" tool from ~1.5yr ago, because it did not fetch tags by default, so rebased revisions were still unreachable. 4. We did our patching to repo and submitted it to Google, which then was lost in great kernel.org demise of 2011, and later they rejected it telling they'd do it in different way. 5. Fast forward to modern time, I verified that repo v1.12.2 works as expected wrt to fetching commits by SHA revs, if they have underlying tag, so we're covered for policy of p.2. 6. However, few repos were found to still be rebased without tagging release revisions. To address that, following options are proposed: a) Disallow to use SHA revs in release manifests. Granted, that would make more effort to do a release then just get pinned manifest of some build, but may improve release process by prompting to ensure that releases are made from Android Team managed mirrors of repositories, and that all such repositories are tagged in consistent manner (which how upstream does it). b) Verify that each SHA has underlying tag. A bit more challenging technically (i.e. possibility for unexpected behavior), and misses the chance to move release process to a new level, but should be still doable. Note that both choices preserve ability to rebase repositories, which is considered an important developers' right ;-). -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

12 years, 1 month

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-android April 2013