Linaro-android

linaro-android@lists.linaro.org

1073 discussions

How to cope with TARGET_BUILD_VARIANT 'eng' being replaced by 'tests'

by Zygmunt Krynicki

Hey everyone. In light of discussion started by bug: https://bugs.launchpad.net/linaro-android/+bug/1022537 and duplicates I think we need to reconsider non-tests build variants. I'd like to understand how that would work: 0) Which builds need to be split to 'eng' and 'tests' builds? 1) Which images are sent to LAVA for automatic testing? 2) Which images are tested manually? (I don't suppose we'll test both) 3) How do we re-visit the split (do we? how often? on what event?) My current feeling is that: 0: we need to split all builds and slightly re-design the a-b.l.o front page to offer twin links 1: we use the 'eng' variant for LAVA, for now 2: we use the 'eng' variant for manual tests unless everyone agrees that they can reliably test 'tests' builds 3: we look at this policy every time we {loose,gain} {h/w acceleration,board type} and do a check-list each month during monthly planning. Feel free to post your ideas and start the discussion. Thanks! ZK -- Zygmunt Krynicki Linaro Validation Team s/Validation/Android/

13 years, 10 months

Gator fix for 3.5 kernels

by Jon Medhurst (Tixy)

We now have a fix for Gator to stop it deadlocking the system on 3.5 kernels [0]. This fix will find it's way into linux-linaro-core-tracking (llct) when Andrey next updates that with the ARM LT topics. For people managing 3.5 kernels with in-tree Gator code they didn't via llct then then they need to manually re-pull our topic branch [1]. For Android builds which don't use an in-tree version of Gator, I have pushed the patch to the external git branch these Android builds use [2], so they will automatically pick up the fix. -- Tixy [0] http://git.linaro.org/gitweb?p=arm/ds5/gator.git;a=commit;h=2ccfda6ba471ba1… [1] http://git.linaro.org/gitweb?p=landing-teams/working/arm/kernel.git;a=short… [2] http://git.linaro.org/gitweb?p=arm/ds5/gator.git;a=shortlog;h=refs/heads/an…

13 years, 10 months

Re: Powertop-2.0 integration in Android builds

by Amit Kucheria

On Fri, Jul 13, 2012 at 10:36 AM, Amit Kucheria <amit.kucheria(a)linaro.org> wrote: > Can anybody on the Android team help out Rajagopal? Integrating into > android has been pending two weeks now. > > /Amit > > On Mon, Jul 9, 2012 at 10:01 AM, Rajagopal Venkat > <rajagopal.venkat(a)linaro.org> wrote: >> Hi Zach, >> >> Please propose a name from Android team who can integrate new powertop >> release. >> >> Thanks >> Rajagopal >> >> >> On 2 July 2012 10:36, Rajagopal Venkat <rajagopal.venkat(a)linaro.org> wrote: >>> >>> Hi Zach, >>> >>> Can someone from Android team help me integrating powertop-2.0 release to >>> Android release builds? >>> >>> Thanks >>> Rajagopal >>> >>> >>> On 28 June 2012 10:18, Rajagopal Venkat <rajagopal.venkat(a)linaro.org> >>> wrote: >>>> >>>> Hi Zach, >>>> >>>> New Powertop-2.0 version is available for integration in Android builds. >>>> >>>> Git repo : >>>> http://git.linaro.org/gitweb?p=tools/powertop-2.0.git;a=summary >>>> Branch : linaro >>>> >>>> Who can help in integrating this new release? >>>> >>>> Thanks, >>>> Rajagopal >>> >>> >>

13 years, 10 months

Power Meter

by Zach Pfeffer

Check out our new NI power meter: http://www.youtube.com/watch?v=JYRogshDyVo&feature=plcp We're gonna hook this thing up to LAVA. Its a pretty nice piece of equipment. Specs: NI PXIe-1073 with a NI PXIE-4154 Battery Simulator. -- 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

13 years, 10 months

v4l2 issue

by Annamalai Lakshmanan

Dear All, I am facing a V4L2 issue due to latest kernel upgrades to 3.5 rc2 in Origen Android. There are 2 drivers HDMI and FIMC. When Buffer is allocated via HDMI using REQBUF and same buffer is passed as QBUF to FIMC, (dev-dev) operation. QBUF seems failing for FIMC, however same code was working for earlier kernel 3.4 rc7. However, Same dev-dev scenario works for a similar scenario involving Decoder and FIMC. With Regards, Annamalai

13 years, 10 months

Agenda for the 2012/7/11 Linaro Android Platform Team Meeting Posted

by Zach Pfeffer

Take a look: https://wiki.linaro.org/Platform/Android/Meetings/2012-07-11 See everyone tomorrow morning on irc.freenode.net in #linaro-meeting at 8 AM Texas time, 14:00 UTC. -- 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

13 years, 10 months

Linaro Android buils service problems

by Dale Wathen

Hi, I am having a few problems with getting android up and running on my pandaboard ES After getting the final message - Done creating Linaro Android image on /dev/sdb I remove the SD card and place it in my pandaboard but all I get is a blank screen. I also seem to be having some issues with minicom working at this point. I get the message - minicom: cannot open /dev/ttyUSB0: No such file or directory As android in flashed to my SD card this is what it says. I see... Device Mount point Size /dev/sda none 305245MB /dev/sda1 none 10000MB /dev/sda2 none 247569MB /dev/sda3 none 47674MB /dev/sda5 / 43837MB /dev/sda6 none 3836MB /dev/sdb none 7580MB /dev/sdb1 /media/boot 131MB /dev/sdb2 /media/system 512MB /dev/sdb3 /media/cache 256MB /dev/sdb4 none 6680MB /dev/sdb5 /media/userdata 511MB /dev/sdb6 /media/sdcard 6167MB /dev/sr0 none 0MB Are you 100% sure, on selecting [/dev/sdb] (y/n)? y Checking that no-one is using this disk right now ... OK Warning: bad partition start (earliest 1843201) partition ends on cylinder 1023, beyond the end of the disk partition ends on cylinder 1023, beyond the end of the disk Warning: partition 1 does not end at a cylinder boundary end of partition 4 has impossible value for cylinders: 1023 (should be in 0-1020) If you created or changed a DOS partition, /dev/foo7, say, then use dd(1) to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1 (See fdisk(8).) Formating boot partition mkfs.vfat 3.0.12 (29 Oct 2011) mke2fs 1.42 (29-Nov-2011) Filesystem label=userdata OS type: Linux Block size=1024 (log=0) Fragment size=1024 (log=0) Stride=0 blocks, Stripe width=0 blocks 131072 inodes, 524272 blocks 26213 blocks (5.00%) reserved for the super user First data block=1 Maximum filesystem blocks=67633152 64 block groups 8192 blocks per group, 8192 fragments per group 2048 inodes per group Superblock backups stored on blocks: 8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409 Allocating group tables: done Writing inode tables: done Creating journal (8192 blocks): done Writing superblocks and filesystem accounting information: done mke2fs 1.42 (29-Nov-2011) Filesystem label=cache OS type: Linux Block size=1024 (log=0) Fragment size=1024 (log=0) Stride=0 blocks, Stripe width=0 blocks 65536 inodes, 262144 blocks 13107 blocks (5.00%) reserved for the super user First data block=1 Maximum filesystem blocks=67371008 32 block groups 8192 blocks per group, 8192 fragments per group 2048 inodes per group Superblock backups stored on blocks: 8193, 24577, 40961, 57345, 73729, 204801, 221185 Allocating group tables: done Writing inode tables: done Creating journal (8192 blocks): done Writing superblocks and filesystem accounting information: done mke2fs 1.42 (29-Nov-2011) Filesystem label=system OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 32768 inodes, 131072 blocks 6553 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=134217728 4 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304 Allocating group tables: done Writing inode tables: done Creating journal (4096 blocks): done Writing superblocks and filesystem accounting information: done mkfs.vfat 3.0.12 (29 Oct 2011) Image Name: boot script Created: Fri Jul 6 19:31:57 2012 Image Type: ARM Linux Script (uncompressed) Data Size: 385 Bytes = 0.38 kB = 0.00 MB Load Address: 00000000 Entry Point: 00000000 Contents: Image 0: 377 Bytes = 0.37 kB = 0.00 MB Done creating Linaro Android image on /dev/sdb Is there any problems you can see there? Thanks Dale

13 years, 10 months

Representativeness of 'panda' builds

by Zygmunt Krynicki

Hey everyone! I need some advice on the following topic: Discuss how representative 'panda-ics-tracking' is vs other builds This is related to this blueprint: https://blueprints.launchpad.net/linaro-android/+spec/build-tests I did all my analysis of tests present in AOSP on the panda tree (both source an binary). I assume that's pretty representative and I don't need to repeat the work for snowball/vexpress/etc but I'd like your opinion on this topic. Thanks ZK -- Zygmunt Krynicki Linaro Validation Team s/Validation/Android/

13 years, 10 months

About the boot of omapzoom and aosp of panda build in LAVA

by YongQin Liu

Hi, all I met a problem that the omapzoom and aosp build of panda can't be booted up in lava. here is the bug link: https://bugs.launchpad.net/lava-dispatcher/+bug/1012546 When we passed the bootcmd and bootargs via u-boot, and run boot to boot the images deployed on partition3, the u-boot load kernel image and initrd file successfully, and displayed the line: "Uncompressing Linux... done, booting the kernel." but after this line, it seems that the board rebooted and boot the master image as default again, not boot up the android image. I guess it has relation with uboot in master image because I have tried to use the MLO and u-boot.bin and u-boot.img in omapzoom build to replace the files on boot partition of master image, then I can boot the omapzoom and aosp build successfully. (also can boot the tracking build) What I did was as following: 1. deploy omapzoom build to sdcard with linaro-android-media-create command 2. copy the MLO and u-boot.bin and u-boot.img 3 file from sdcard to someplace in local 3. use "./lava-create-master -r 2G panda" to create the sdcard used for master image we can get the lava-create-master script from lp:lava-master-image-scripts 4. plug in the sdcard and boot the board 5. wait the board to complete the partition job. after this, the uImage and uInitrd file in boot partition has been change, and then the master image can be booted with the uboot files from omapzoom build but I don't know why and what change has been done. 6. copy the MLO and u-boot.bin and u-boot.img 3 file to the boot partition of sdcard 7. plug the sdcard to the board and boot it, then it can be use to boot the tracking/omapzoom/aosp 3 builds of panda. The version original u-boot for master image is: U-Boot 2011.12 (Feb 16 2012 - 21:46:14) The u-boot version of omapzoom build is: U-Boot 2011.06 (Aug 20 2011 - 18:00:16). The u-boot version of tracking build is : U-Boot SPL 2012.04.01 (Jun 14 2012 - 08:05:54) The tracking build works fine with the original uboot of master image. So I guess there are some differences between the original uboot for master image and the uboot build in omapzoom build. Anyone know the details why it can not boot the omapzoom and aosp build on the 3rd partition, and if I can boot the omapzoom and aosp build of panda with the original u-boot of master image? Thanks, Yongqin Liu

13 years, 10 months

Monkey and long monkey trip over new test apks

by Zygmunt Krynicki

Hey everyone. It seems that monkey trips over new test apks that have been added as a side effect of building TARGET_BUILD_VARIANT=tests images. For example, see: https://pastebin.linaro.org/636/ We may need to blacklist some (all?) of them initially to get meanigful results. Best regards ZK -- Zygmunt Krynicki Linaro Validation Team s/Validation/Android/

13 years, 10 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-android