linaro-android

linaro-android@lists.linaro.org

1071 discussions

review.android.git.linaro.org upgraded to common gerrit version/theme

by Paul Sokolovsky

Hello, http://review.android.git.linaro.org is the oldest Linaro Gerrit server, and tailed behind all the other servers in updates. Finally, it was upgraded to the standard Gerrit version we run, 2.8.6.1, and Linaro theme. These changes will enable further sustainable version upgrades in the future. The server works ok for the quick testing I performed, but let me know if you spot any issues. 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

8 years, 11 months

Where's a good location in the source tree layout for Mali code?

by Jon Medhurst (Tixy)

I plan on moving gralloc for Mali into it's own repo an wondering whereabouts in the source tree it should be placed by the manifest? Possibilities are /hardware/arm/mali/ /external/mali/ /mali/ Within whatever directory is chosen I plan on having source for all the versions of mali so, e.g. /hardware/arm/mali/r5p0-06rel0/gralloc /hardware/arm/mali/r5p1-00rel0/gralloc /hardware/arm/mali/r5p1-06rel1/gralloc With the aim being that the correct one gets chosen to match whatever driver version is in the kernel. I also plan similar for vendor tarball contents, so hopefully we get builds where the three pieces are guaranteed to have matching version (kernel module/gralloc/binary blob) -- Tixy

8 years, 11 months

Parameter "abi" dropped by CTS?

by Botao Sun

Hi Guys, I have been investigating this for hours and found that the "--abi" parameter seems has been dropped from CTS console. In the manual it says: http://source.android.com/compatibility/android-cts-manual.pdf --abi 32/64 On 64-bit devices, run the test against only the 32-bit or 64-bit ABI However for the CTS package I use, whatever it comes from Linaro or Google: http://testdata.validation.linaro.org/cts/android-cts-5.1-armv8.zip https://dl.google.com/dl/android/cts/android-cts-5.1_r1-linux_x86-arm.zip it prompted that: Failed to run command: com.android.tradefed.config.ConfigurationException: Could not find option with name abi I tried this on Juno in LAVA, as well as locally on my Nexus 5 phone, both failed. So if abi selection has been dropped by Google then that manual is outdated. Ideas? Thanks. Botao

8 years, 11 months

Re: Juno Android snapshots

by YongQin Liu

Hi, Tim We only run boot test for the master juno build, but it failed to boot on our LAVA as well. One problem I can see there is about getting the value of ro.hardware. You can try with passing "androidboot.hardware=juno" as kernel parameter to check if you can boot the recent builds. Since we don't have much resources before, there was not maintainer for this master juno build for a while. But you can always send mail to linaro-android(a)lists.linaro.org mailing list for any question related to android. Thanks, Yongqin Liu On 28 May 2015 at 04:43, Tim Klein <Tim.Klein(a)arm.com> wrote: > Hi, > > > > I work for ARM and am trying to find someone in Linaro who is responsible > for maintaining the Android master Juno snapshots. After a bit of > searching forums etc. it seems that you may be able to help. If you are > not the correct person then I’d be really grateful if you could point me in > the right direction. > > > > I’ve successfully run build 251 of the snapshots > http://snapshots.linaro.org/android/~linaro-android/armv8-aosp-master-juno-… > , however more recent versions do not seem to run. Before I look into the > problem further it would be really useful to understand what testing is > done on these snapshots and what expectations one should have on their > functionality. > > If they ‘should work out the box’ then I should assume that I’m doing > something wrong and would appreciate help in working what mistakes I’m > making. > > > > > > Many thanks in advance, > > > > Tim Klein > > > > -- 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 > -- Best Regards, Yongqin Liu --------------------------------------------------------------- #mailing list linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> http://lists.linaro.org/mailman/listinfo/linaro-android

8 years, 11 months

help with gerrit setup for AOSP kernel/common repo

by Kevin Hilman

Hello, I have the AOSP kernel/common tree cloned, but I'm not in a full android dev environment (not using repo for all the rest of android.) I'd like to make some minor cleanup/fix patches for the kernel, but need to setup gerrit for this repo. Can anyone share what the .gitreview file should look like for this? Thanks Kevin

8 years, 12 months

LSK Android builds: AOSP kconfig fragments vs Linaro kconfig fragments

by Kevin Hilman

In working on the lsk-v3.18-android tree, I noticed that the android tree has an android/configs directory with an android-base and android-recommended config fragments. Is there a reason we are using linaro specific config fragments in our CI loops instead of these? If there are Linaro specific addtions, we should switch to using the android fragments plus smaller linaro-specific fragments, and put comments in our linaro fragments as to why the extra options are needed. Kevin

8 years, 12 months

Android kernel update

by Rodrigo Santos

Hello, I am working on a Pandaboard ES and I can boot Android with the following release: http://releases.linaro.org/14.02/android/panda However, I need some components from a newer version of the kernel. I found a version[1] which has everything that I need. However, I cannot boot it properly just by using the uImage that I generated from that kernel. You can see the log here: https://gist.github.com/rlvrs/846aec4730a28674557d As it is possible to see, the problem occurs on the init process. I am using the same ramdisk from the working release. If it is that the problem, can you tell me a way to generate a compatible ramdisk image (rootfs). [1] https://git.linaro.org/?p=kernel/linux-linaro-stable.git;a=log;h=refs/heads… Thanks in advance, Rodrigo Santos

9 years

linaro-android_nexus10-aosp-master build failure, need help

by Zhizhou Tian

hello There is something wrong with linaro-android_nexus10-aosp-master build. Could some one help? Thanks. cp out/target/product/manta/obj/STATIC_LIBRARIES/libbt-brcm_bta_intermediates/./dm/bta_dm_cfg.d out/target/product/manta/obj/STATIC_LIBRARIES/libbt-brcm_bta_intermediates/./dm/bta_dm_cfg.P; sed -e 's/#.*//' -e 's/^[^:]*: *//' -e 's/ *\\$//' -e '/^$/ d' -e 's/$/ :/' < out/target/product/manta/obj/STATIC_LIBRARIES/libbt-brcm_bta_intermediates/./dm/bta_dm_cfg.d >> out/target/product/manta/obj/STATIC_LIBRARIES/libbt-brcm_bta_intermediates/./dm/bta_dm_cfg.P; rm -f out/target/product/manta/obj/STATIC_LIBRARIES/libbt-brcm_bta_intermediates/./dm/bta_dm_cfg.d > system/bt/bta/./dm/bta_dm_api.c: In function 'BTA_DmBleConfirmReply': > system/bt/bta/./dm/bta_dm_api.c:811:28: error: 'BTA_DM_API_BLE_CONFIRM_REPLY_EVT' undeclared (first use in this function) > p_msg->hdr.event = BTA_DM_API_BLE_CONFIRM_REPLY_EVT; > ^ > system/bt/bta/./dm/bta_dm_api.c:811:28: note: each undeclared identifier is reported only once for each function it appears in > make: *** [out/target/product/manta/obj/STATIC_LIBRARIES/libbt-brcm_bta_intermediates/./dm/bta_dm_api.o] Error 1 > cp out/target/product/manta/obj/STATIC_LIBRARIES/libbt-brcm_bta_intermediates/./dm/bta_dm_pm.d out/target/product/manta/obj/STATIC_LIBRARIES/libbt-brcm_bta_intermediates/./dm/bta_dm_pm.P; sed -e 's/#.*//' -e 's/^[^:]*: *//' -e 's/ *\\$//' -e '/^$/ d' -e 's/$/ :/' < out/target/product/manta/obj/STATIC_LIBRARIES/libbt-brcm_bta_intermediates/./dm/bta_dm_pm.d >> out/target/product/manta/obj/STATIC_LIBRARIES/libbt-brcm_bta_intermediates/./dm/bta_dm_pm.P; rm -f out/target/product/manta/obj/STATIC_LIBRARIES/libbt-brcm_bta_intermediates/./dm/bta_dm_pm.d > cp out/host/linux-x86/obj/EXECUTABLES/clang-tblgen_intermediates/ClangAttrEmitter.d out/host/linux-x86/obj/EXECUTABLES/clang-tblgen_intermediates/ClangAttrEmitter.P; sed -e 's/#.*//' -e 's/^[^:]*: *//' -e 's/ *\\$//' -e '/^$/ d' -e 's/$/ :/' < out/host/linux-x86/obj/EXECUTABLES/clang-tblgen_intermediates/ClangAttrEmitter.d >> out/host/linux-x86/obj/EXECUTABLES/clang-tblgen_intermediates/ClangAttrEmitter.P; rm -f out/host/linux-x86/obj/EXECUTABLES/clang-tblgen_intermediates/ClangAttrEmitter.d > cp out/host/linux-x86/obj/EXECUTABLES/clang-tblgen_intermediates/NeonEmitter.d out/host/linux-x86/obj/EXECUTABLES/clang-tblgen_intermediates/NeonEmitter.P; sed -e 's/#.*//' -e 's/^[^:]*: *//' -e 's/ *\\$//' -e '/^$/ d' -e 's/$/ :/' < out/host/linux-x86/obj/EXECUTABLES/clang-tblgen_intermediates/NeonEmitter.d >> out/host/linux-x86/obj/EXECUTABLES/clang-tblgen_intermediates/NeonEmitter.P; rm -f out/host/linux-x86/obj/EXECUTABLES/clang-tblgen_intermediates/NeonEmitter.d > make: *** wait: No child processes. Stop. > Build step 'Execute shell and set build status' changed build result to FAILURE > Build step 'Execute shell and set build status' marked build as failure > Archiving artifacts > Recording fingerprints > Finished: FAILURE > >

9 years

Android kernel update

by Rodrigo Santos

Hello, I am working on a Pandaboard ES and I can boot Android with the following release: http://releases.linaro.org/14.02/android/panda However, I need some components from a newer version of the kernel. I found a version[1] which has everything that I need. However, I cannot boot it properly just by using the uImage that I generated from that kernel. You can see the log here: https://gist.github.com/rlvrs/846aec4730a28674557d As it is possible to see, the problem occurs on the init process. I am using the same ramdisk from the working release. If it is that the problem, can you tell me a way to generate a compatible ramdisk image (rootfs)? I did not see any build with a kernel as updated. [1] https://git.linaro.org/?p=kernel/linux-linaro-stable.git;a=log;h=refs/heads… Thanks in advance, Rodrigo Santos

9 years

Parsing Android boot properties from device tree

by Amit Pundir

AOSP master do not parse "/proc/cpuinfo" anymore to set ro.hardware and other boot related properties [1]. We can still boot by either adding "androidboot.hardware=XXX" bootarg (where XXX could be juno/hikey/ifc6410 or any other supported hardware platform) Or by embedding this boot information in the platform device tree blob as suggested by this AOSP commit [2]. I was wondering if ARMLT would be interested in keeping this Android boot related information in dts for Juno? I have never touched anything related to device-trees, but by looking at [2], it seem the device-tree changes for Android won't be much complicated. The following device-tree hack worked for me: -------------------- diff --git a/arch/arm64/boot/dts/juno.dts b/arch/arm64/boot/dts/juno.dts index 9ad05e4..82471db 100644 --- a/arch/arm64/boot/dts/juno.dts +++ b/arch/arm64/boot/dts/juno.dts @@ -26,6 +26,13 @@ stdout-path = &soc_uart0; }; + firmware { + android { + compatible = "android,firmware"; + hardware = "juno"; + }; + }; + psci { compatible = "arm,psci-0.2"; method = "smc"; -------------------- Regards, Amit Pundir [1] https://android.googlesource.com/platform/system/core/+/74b34f3cb79aa8f2c5b… [2] https://android.googlesource.com/platform/system/core.git/+/6a52443d31d4de5…

9 years

← Newer
1
...
4
5
6
7
8
9
10
...
108
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-android