Linaro-android June 2014

linaro-android@lists.linaro.org

11 participants
9 discussions

Upcoming android-build.linaro.org migration (and disk space)

by Paul Sokolovsky

Hello, We're finishing migration of ci.linaro.org to the latest Ubuntu LTS release (14.04). android-build.linaro.org is next in queue. I guess, it makes sense to plan migration for the same time window as ci.l.o - past-release, first week of July. But maybe Android team has special plans or suggestions, so please let us know. This would also be good time to discuss any changes or additional requirements for the migration. Actually, just today Fathi drew my attention to the fact that there were less 5% free on a-b jobs partition. Looking forward to upcoming migration, I did thorough clean up - we now back to 11% free, and that's actually 55Gb. I also did analysis of growth rate, and my calculations give below 7Gb/year. I hope that's not surprising - most builds we produce, also expire soon, so only growing residue is actually release builds. So, based on this analysis, we should be fine for next couple of years. You're free to disagree of course. Then I can propose 2 solutions: 1. Reconsider how 500Gb there is used. What suggests of such approach is example, ci.linaro.org, which has a lot of jobs, but of whose 300Gb, 60% are free. That's apparently because it uses much more aggressive expiration policies - for example, unneeded jobs there are actually deleted. Applying that idea to a-b, the build/CI server, do we really need to host old historical releases there, if their official place is https://releases.linaro.org anyway? I guess, that's Fathi call too. 2. If we don't want to change retention policies, and don't trust small growth rate figure either, then increasing disk space is the obvious choice. But I'd say extra 100Gb would really be enough for foreseeable future - having too big a disk means more money (include back up cost), more time when you need back up soon, more fsck time, etc., etc. I don't think there's much more to vary with this migration between new Jenkins version (implied) and disk space, but if somebody knows other issues which would be nice to fix, let us know (but again, talk is just about Jenkins master, not slaves or something else). Thanks, 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

11 years

Support for java6 and java7 on android-build

by Paul Sokolovsky

Hello, Last Friday, we with Vishal made changes to build scripts on https://android-build.linaro.org/ to support both java-1.6-sun (as was required by previous AOSP versions) and java-1.7-openjdk (as should be required for AOSP master). (Based on https://bugs.launchpad.net/linaro-android-infrastructure/+bug/1310939) To explicitly select java6, add "USE_JAVA_6=1" to build config. For java7 respectively add "USE_JAVA_7=1". The default stays java6 so far, as it appears to be needed by the most jobs so far, but it may be changes in the future. Thanks, and let me know if there're any issues or questions. -- 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

11 years

Suspend / Resume patch

by Genisim Tsilker

Hi Vishal, follow up our IRC conversation I provide patch for review for Suspend / Resume crashes 1. Select "Assume MMC/SD cards are non-removable (DANGEROUS)" "MMC embedded SDIO device support (EXPERIMENTAL)" "Enable paranoid SD card initialization (EXPERIMENTAL)" [X] 2. Use patch below diff --git a/drivers/tty/serial/samsung.c b/drivers/tty/serial/samsung.c index 639b092..1ba2160 100644 --- a/drivers/tty/serial/samsung.c +++ b/drivers/tty/serial/samsung.c @@ -1330,10 +1330,18 @@ static int s3c24xx_serial_remove(struct platform_device *dev) /* UART power management code */ #ifdef CONFIG_PM_SLEEP +static atomic_t suspend_resume = {0}; static int s3c24xx_serial_suspend(struct device *dev) { - struct uart_port *port = s3c24xx_dev_to_port(dev); - + struct uart_port *port; + if (atomic_read(&suspend_resume) > 0) { + printk("%s : Already suspended\n", __func__); + return 0; + } else { + printk("%s : Suspend\n", __func__); + atomic_set(&suspend_resume, 1); + } + port = s3c24xx_dev_to_port(dev); if (port) uart_suspend_port(&s3c24xx_uart_drv, port); @@ -1342,9 +1350,18 @@ static int s3c24xx_serial_suspend(struct device *dev) static int s3c24xx_serial_resume(struct device *dev) { - struct uart_port *port = s3c24xx_dev_to_port(dev); - struct s3c24xx_uart_port *ourport = to_ourport(port); + struct uart_port *port; + struct s3c24xx_uart_port *ourport; + if (atomic_read(&suspend_resume) == 0) { + printk("%s : Already resumed\n", __func__); + return 0; + } else { + printk("%s : Resume\n", __func__); + atomic_set(&suspend_resume, 0); + } + port = s3c24xx_dev_to_port(dev); + ourport = to_ourport(port); if (port) { clk_prepare_enable(ourport->clk); s3c24xx_serial_resetport(port, s3c24xx_port_to_cfg(port)); @@ -1801,7 +1818,6 @@ static int __init s3c24xx_serial_modinit(void) pr_err("Failed to register Samsung UART driver\n"); return ret; } - return platform_driver_register(&samsung_serial_driver); } Genisim Tsilker Platform Development Cel: (408) 966-6285 Cel: (650) 336-4806 Linkedin: http://www.linkedin.com/in/genisimtsilker

11 years, 1 month

Optimizing OVERLAY handling on android-build

by Paul Sokolovsky

Hello, There were increasing Android build times during last month again (going over 3.5hrs). Yesterday, I re-created the seed, but that didn't improve times match. I did more stats on builds and it turns out that we spend almost 1.5hrs in copying ever-growing overlay collection to the slaves via sluggish CopyToSlave Jenkins plugin. That's issues known for at least half-year, and was in queue for being reworked. I didn't work on android-build closely for few months, but now that I'm back on maintenance, I'd like to start with fixing this long-overdue issue. The idea was to pull all the needed overlay, straight to a slave. The complication here was handling of license protected files. ci.linaro.org had the same issue, and used a script to handle automatic downloads for some time. However, as of now, it was switched to other process and the script git bitrotted with recent linaro-license-protection codebase changes. I took a look at revamping it, but then though that it may be a good idea to use simpler and more explicit process, following closely click-thru usage. So, if you want to use a license-protected binaries in a build, you'd need to specify: ACCEPT_LICENSE=<license_id> Where <license_id> is id under which license is registered in linaro-license-protection. One good way to figure it out is to read the license page at all (well, as HTML source, the id is included in some links). Wording of variable name (as well as of commands in underlying implementation) is also explicit to point that its usage construes license acceptance. I prototypes these changes using https://android-build.linaro.org/builds/~pfalcon/panda-jb-gcc47-tilt-tracki… which is down to 2h10m build time. I'm ready to migrate all builds tomorrow, while we're early in cycle start. Please let me know if there're any issues with approach or proposed migration timeframe, otherwise let's make android-build rock again. Thanks, 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

11 years, 1 month

How to configure UEFI to specify the SD card as a boot device

by duqi

Hi, I have tried to boot the android on the versatile express. I have created the SD card according the links： http://releases.linaro.org/13.01/android/images/vexpress-linaro-mp Then I tried update the firmware according this links:http://releases.linaro.org/latest/openembedded/vexpress-lsk/#tabs-4 I set the two switchs to the off(just as both up) and I used the UART0. Now I meet a question about how to configure UEFI to specify the SD card as a boot device. When I give it power ,it does not appear the boot selection menu as expected. Could you give me some advices? Look forward to your favourable reply. duqi.

11 years, 1 month

Running powerdebug on Linaro Android causes kernel crash on Samsung Arndale Board

by Mohammad Merajul Islam Molla

Hello, I ran powerdebug on Linaro Android 14.04 with a custom kernel (config file attached). While exporting gpios, it seems to crash the kernel (detail log attached). I have some printfs, added in powerdebug export_free_gpios() function to assist during log taking. for (i = 0 ; i <= gpio_max ; i++) { char command[50] = ""; printf("exporting gpio: %d\n", i); sprintf(command, "echo %d > /sys/class/gpio/export", i); printf("command: %s\n", command); if ((ret=system(command)) < 0) printf("error: failed to export gpio-%d\n", i); printf("ret: %d\n", ret); } >From log, it looks like while trying to export gpio 8, kernel crash is happening - "Unable to handle kernel NULL pointer dereference at virtual address 00000044" (details in attached log) >From output of /sys/kernel/debug/gpio it looks like gpio 8 is not mapped to any device. Even manually trying to export gpio 8 causes the same crash. root@arndale:/ # cat /sys/kernel/debug/gpio GPIOs 0-7, GPA0: gpio-0 (s3c24xx-uart ) in hi gpio-1 (s3c24xx-uart ) in hi gpio-2 (s3c24xx-uart ) in lo gpio-3 (s3c24xx-uart ) in hi gpio-6 (i2c-bus ) in hi gpio-7 (i2c-bus ) in hi GPIOs 9-14, GPA1: gpio-9 (s3c24xx-uart ) in hi gpio-10 (s3c24xx-uart ) in hi gpio-11 (s3c24xx-uart ) in hi gpio-12 (s3c24xx-uart ) in hi gpio-13 (s3c24xx-uart ) in lo gpio-14 (s3c24xx-uart ) in hi GPIOs 16-23, GPA2: GPIOs 25-29, GPB0: GPIOs 31-35, GPB1: GPIOs 37-40, GPB2: GPIOs 42-45, GPB3: gpio-42 (i2c-bus ) in hi gpio-43 (i2c-bus ) in hi GPIOs 47-53, GPC0: gpio-47 (dw-mci-bus ) in lo gpio-48 (dw-mci-bus ) in hi gpio-50 (dw-mci-bus ) in hi gpio-51 (dw-mci-bus ) in hi gpio-52 (dw-mci-bus ) in hi gpio-53 (dw-mci-bus ) in hi GPIOs 55-58, GPC1: gpio-55 (dw-mci-bus ) in hi gpio-56 (dw-mci-bus ) in hi gpio-57 (dw-mci-bus ) in hi gpio-58 (dw-mci-bus ) in hi GPIOs 60-66, GPC2: GPIOs 68-74, GPC3: gpio-68 (dw-mci-bus ) in lo gpio-69 (dw-mci-bus ) in hi gpio-70 (dw-mci-cd ) in lo gpio-71 (dw-mci-bus ) in hi gpio-72 (dw-mci-bus ) in hi gpio-73 (dw-mci-bus ) in hi gpio-74 (dw-mci-bus ) in hi GPIOs 76-82, GPC4: GPIOs 84-87, GPD0: gpio-84 (s3c24xx-uart ) in lo gpio-85 (s3c24xx-uart ) in hi gpio-86 (s3c24xx-uart ) in lo gpio-87 (s3c24xx-uart ) in hi GPIOs 89-96, GPD1: GPIOs 98-103, GPY0: GPIOs 105-108, GPY1: GPIOs 110-115, GPY2: GPIOs 117-124, GPY3: GPIOs 126-133, GPY4: GPIOs 135-142, GPY5: GPIOs 144-151, GPY6: GPIOs 153-160, GPX0: GPIOs 162-169, GPX1: gpio-163 (VDD_33ON_2.8V ) out hi GPIOs 171-178, GPX2: gpio-174 (S5M8767 DS2 ) out lo gpio-175 (S5M8767 DS3 ) out lo gpio-176 (S5M8767 DS4 ) out lo GPIOs 180-187, GPX3: gpio-187 (HPD ) in lo GPIOs 189-196, GPE0: GPIOs 198-199, GPE1: GPIOs 201-204, GPF0: GPIOs 206-209, GPF1: GPIOs 211-218, GPG0: GPIOs 220-227, GPG1: GPIOs 229-230, GPG2: GPIOs 232-235, GPH0: GPIOs 237-244, GPH1: GPIOs 246-253, GPV0: GPIOs 255-262, GPV1: GPIOs 264-271, GPV2: GPIOs 273-280, GPV3: GPIOs 282-283, GPV4: GPIOs 285-291, GPZ: On the same board, running Linaro Saucy server does not cause any crash with powerdebug. In that case, output from /sys/kernel/debug/gpio looks as follows- GPIOs 0-7, platform/11400000.pinctrl, gpa0: GPIOs 8-13, platform/11400000.pinctrl, gpa1: GPIOs 14-21, platform/11400000.pinctrl, gpa2: GPIOs 22-26, platform/11400000.pinctrl, gpb0: GPIOs 27-31, platform/11400000.pinctrl, gpb1: GPIOs 32-35, platform/11400000.pinctrl, gpb2: GPIOs 36-39, platform/11400000.pinctrl, gpb3: GPIOs 40-46, platform/11400000.pinctrl, gpc0: GPIOs 47-50, platform/11400000.pinctrl, gpc1: GPIOs 51-57, platform/11400000.pinctrl, gpc2: GPIOs 58-64, platform/11400000.pinctrl, gpc3: GPIOs 65-68, platform/11400000.pinctrl, gpd0: GPIOs 69-76, platform/11400000.pinctrl, gpd1: gpio-76 (usb3503 connect ) out hi GPIOs 77-83, platform/11400000.pinctrl, gpc4: GPIOs 84-89, platform/11400000.pinctrl, gpy0: GPIOs 90-93, platform/11400000.pinctrl, gpy1: GPIOs 94-99, platform/11400000.pinctrl, gpy2: GPIOs 100-107, platform/11400000.pinctrl, gpy3: GPIOs 108-115, platform/11400000.pinctrl, gpy4: GPIOs 116-123, platform/11400000.pinctrl, gpy5: GPIOs 124-131, platform/11400000.pinctrl, gpy6: GPIOs 132-139, platform/11400000.pinctrl, gpx0: GPIOs 140-147, platform/11400000.pinctrl, gpx1: gpio-141 (VDD_33ON_2.8V ) out hi gpio-144 (SW-TACT2 ) in hi gpio-145 (SW-TACT3 ) in hi gpio-146 (SW-TACT4 ) in hi gpio-147 (SW-TACT5 ) in hi GPIOs 148-155, platform/11400000.pinctrl, gpx2: gpio-148 (SW-TACT6 ) in hi gpio-149 (SW-TACT7 ) in hi gpio-151 (S5M8767 DS2 ) out lo gpio-152 (S5M8767 DS3 ) out lo gpio-153 (S5M8767 DS4 ) out lo GPIOs 156-163, platform/11400000.pinctrl, gpx3: gpio-161 (usb3503 reset ) out hi gpio-163 (HPD ) in lo GPIOs 164-171, platform/13400000.pinctrl, gpe0: GPIOs 172-173, platform/13400000.pinctrl, gpe1: GPIOs 174-177, platform/13400000.pinctrl, gpf0: GPIOs 178-181, platform/13400000.pinctrl, gpf1: GPIOs 182-189, platform/13400000.pinctrl, gpg0: GPIOs 190-197, platform/13400000.pinctrl, gpg1: GPIOs 198-199, platform/13400000.pinctrl, gpg2: GPIOs 200-203, platform/13400000.pinctrl, gph0: GPIOs 204-211, platform/13400000.pinctrl, gph1: GPIOs 212-219, platform/10d10000.pinctrl, gpv0: GPIOs 220-227, platform/10d10000.pinctrl, gpv1: GPIOs 228-235, platform/10d10000.pinctrl, gpv2: GPIOs 236-243, platform/10d10000.pinctrl, gpv3: GPIOs 244-245, platform/10d10000.pinctrl, gpv4: GPIOs 246-252, platform/3860000.pinctrl, gpz: Questions - 1. Is it kernel bug? 2. Why are some gpios (8, 15, 24, etc) not mapped to any device on android? 3. Total GPIOs count differ on Linaro Saucy and Linaro Android on same board. Is this expected? -- Thanks, -Meraj

11 years, 1 month

Get an error when run "linaro_android_build_cmds.sh"

by Julien Yin

Hi, I try to download and build Linaro Android source code. I downloaded "linaro_android_build_cmds.sh" from http://releases.linaro.org/14.05/android/arndale/ . But when I run this script I got an error of repo. The error message is "./repo: line 1: syntax error near unexpected token 'newline'". You are very appreciated if you can help to check this issue. Thanks, Julien -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782

11 years, 1 month

Android ICS improved and stable version

by monica.villegas＠coffee-electronics.com

Hi, I'm Michelle, is it possible that you could tell me which is the most stable and improved version of Android ICS build for Pandaboard? Thank you very much. Best Regards. --- --- --- --- Mónica Michelle Villegas Arias Electronics Engineer Drivers Development Department Coffee Electronics (Pte. Ltd.) monica.villegas(a)coffee-electronics.com --- --- --- --- CONFIDENTIALITY NOTICE: This e-mail and any attachments thereto may contain private, confidential, and privileged material for the sole use of the intended recipient. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this e-mail message in error, please contact the sender immediately and permanently delete the original and any copies of this e-mail and any attachments thereto. linaro-android(a)lists.linaro.org

11 years, 1 month

SNOWBALL problems

by Réda Oualifi

Hi, I have a snowball board and I have a lot of problems in installing the RIFFon it. I was wondering if you can send me the instruction to install it. Thanks.

11 years, 1 month

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-android June 2014