Linaro-android July 2012

linaro-android@lists.linaro.org

39 participants
59 discussions

by Mike Hommey

Hi, As I was trying to build busybox for Boot2Gecko, I found that the linaro repository had an Android.mk for busybox. However, it was using the source directory to store all temporary files, so I patched it all so that it works more nicely. The attached patch is against the linaro-master branch or platform/external/busybox.git. Cheers, Mike

12 years, 9 months

Fw: [ANN] Support for fetching build configs from git for Android Builds

by Paul Sokolovsky

(This is forward of the original announcement of support of "build configs in git" feature, for reference.) Begin forwarded message: Date: Mon, 20 Feb 2012 18:11:42 +0200 From: Paul Sokolovsky <Paul.Sokolovsky(a)linaro.org> To: linaro-android <linaro-android(a)lists.linaro.org>, linaro-dev <linaro-dev(a)lists.linaro.org>, Zach Pfeffer <zach.pfeffer(a)linaro.org>, Danilo Šegan <danilo.segan(a)linaro.org> Subject: [ANN] Support for fetching build configs from git for Android Builds Hello, As the result of implementation of https://blueprints.launchpad.net/linaro-android-infrastructure/+spec/build-… , android-build.linaro.org now can indirectly fetch build config stored in a git repository. To achieve that, bootstrap config (as specified in android-build.linaro.org) should contain reference to config's repo/branch/file (configuration variables are modeled on the similar MANIFEST_* ones), e.g.: BUILD_CONFIG_REPO=git://git.linaro.org/people/pfalcon/android/linaro/build-… BUILD_CONFIG_BRANCH=master BUILD_CONFIG_FILENAME=panda-ics-gcc46-tilt-tracking-blob.conf http://android.git.linaro.org/gitweb?p=linaro/build-configs.git;a=summary was created to store configs for the official builds in the Gerrit tree. Sample job is available here: https://android-build.linaro.org/builds/~pfalcon/git-build-config/ (it uses personal repo as a test). -- 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 -- 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, 9 months

How to boot into fastboot on the Pandaboard?

by Võ Anh Quốc

Hi everybody. I have a question, i hope the people to help me. I want boot Pandaboard into fastboot. But when i run command: "device/ti/panda/usbboot device/ti/panda/bootloader.bin" follow instruction in the file device/ti/panda/README in the source tree. But it run and stay at screen "using build-in 2ndstage.bin - waiting for OMAP44XX device..." forever. Although i had add code # adb protocol on passion (Nexus One) SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e12", MODE="0600", OWNER="root" # fastboot protocol on passion (Nexus One) SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0fff", MODE="0600", OWNER="root" # adb protocol on crespo/crespo4g (Nexus S) SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e22", MODE="0600", OWNER="root" # fastboot protocol on crespo/crespo4g (Nexus S) SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e20", MODE="0600", OWNER="root" # adb protocol on stingray/wingray (Xoom) SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="70a9", MODE="0600", OWNER="root" # fastboot protocol on stingray/wingray (Xoom) SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="708c", MODE="0600", OWNER="root" # adb protocol on maguro/toro (Galaxy Nexus) SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="root" # fastboot protocol on maguro/toro (Galaxy Nexus) SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="root" # adb protocol on panda (PandaBoard) SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d101", MODE="0600", OWNER="root" # fastboot protocol on panda (PandaBoard) SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d022", MODE="0600", OWNER="root" # usbboot protocol on panda (PandaBoard) SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d00f", MODE="0600", OWNER="root" # usbboot protocol on panda (PandaBoard ES) SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d010", MODE="0600", OWNER="root" into /etc/udev/rules.d/51-android.rules . Anyone have the suggest, please help me. If anyone had done successful about fastboot. Please, for i ask. 1. Which Cable mini-usb OTG is it true?Can you get for me the Picture? 2. How to do i check port mini-usb OTG of Pandaboard to i can know it have work? Thank you! Best Regards. -------------------------------------------------------------------------------------------------- HCMC, July 4th , 2012 <http://xesco.com.vn/vn/>

12 years, 9 months

Android Platform Team 2012/7/4 Agenda Posted

by Zach Pfeffer

See: https://wiki.linaro.org/Platform/Android/Meetings/2012-07-04 Please feel free to add to it. Android team, Please list your status. See everyone tomorrow on #linaro-meeting at 14:00 UTC (8 AM Texas time). We've got more cool stuff to go over. Come, enjoy! -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams 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, 9 months

Publishing source/pinned manifests of failed builds.

by Paul Sokolovsky

Hello, Ever since we moved to archive build artifacts on snapshots.linaro.org, we had a small issue that if a build fails, then its source-manifest.xml/pinned-manifest.xml files were not archived (because that's how SFTP archiving we use now works - if build files, archiving just not executed). This was filed after the initial implementation as a known issue, but only recently got some attention with Zach asking to deal with it. Well, it should be resolved now, with manifests being archived (natively in Jenkins only) even for failed builds, to help investigate the failure. Example is here: https://android-build.linaro.org/builds/~pfalcon/manifest-arc-if-fail/ Bug with more info: https://bugs.launchpad.net/linaro-android-infrastructure/+bug/908134 -- 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, 9 months

Official builds updated to run long monkey and use 'tests' variant.

by Zygmunt Krynicki

Hello everyone. I've updated the following builds to use the 'tests' build variant and to run the 'long monkey' tests in LAVA. https://android-build.linaro.org/builds/~linaro-android/vexpress-ics-gcc47-… https://android-build.linaro.org/builds/~linaro-android/vexpress-rtsm-ics-g… https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-til… https://android-build.linaro.org/builds/~linaro-android/snowball-ics-gcc46-… https://android-build.linaro.org/builds/~linaro-android/origen-ics-gcc47-sa… The following two builds have been updated to run the 'long monkey' tests in LAVA (but are still using the default, eng, variant) https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-oma… https://android-build.linaro.org/builds/~linaro-android/panda-master-gcc44-… This is based on the following two blueprints: 'tests': https://blueprints.launchpad.net/linaro-android/+spec/build-tests 'long monkey': https://blueprints.launchpad.net/linaro-android/+spec/fault-tolerant-monkey Best regards Zygmunt Krynicki -- Zygmunt Krynicki Linaro Validation Team s/Validation/Android/

12 years, 9 months

Harvesting android test results for Graphics WG dashboard

by Alexandros Frantzis

Hi all, I am working on adding some daily Android results in the Graphics WG dashboard. Instead of scheduling yet another set of test runs, I would rather harvest results from the existing daily test runs in '/private/team/linaro/android-daily'. In that stream I see a lot of bundles with different build configurations. I would like to start off with one set of results for each board, for example, with the 'android-stable' set: linaro-android_panda-ics-gcc47-tilt-stable-blob linaro-android_snowball-ics-gcc47-igloo-stable-blob linaro-android_origen-ics-gcc47-samsunglt-stable-blob Are these ok, or do you think other test runs would be better suited for harvesting graphics test results from? Also, would you be willing to add some metadata to the test jobs, to make it easier for the graphics dashboard to categorize and display information? Thanks, Alexandros

12 years, 9 months

Ill

by Zygmunt Krynicki

Hey folks. I don't feel well now. I'm going to take a break and lay down for a while. See you later ZK -- Zygmunt Krynicki Linaro Validation Team s/Validation/Android/

12 years, 9 months

12.07 Android schedule posted

by Zach Pfeffer

https://launchpad.net/linaro-android/+milestone/12.07 has been scheduled. Take a look :) -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams 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, 9 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-android July 2012