linaro-dev October 2013

linaro-dev@lists.linaro.org

43 participants
34 discussions

by Trevor Woerner

Hi, Last night I started seeing a strange issue with using Android's repo on my Ubuntu machine: $ repo sync info: A new version of repo is available object e76efdd7b342577c40aa271fa5ded9d66a783a9b type commit tag v1.12.4 tagger Conley Owens <cco3(a)android.com> 1380645867 -0700 repo 1.12.4 gpg: Signature made Tue Oct 1 12:44:27 2013 EDT using RSA key ID 692B382C gpg: Can't check signature: public key not found error: could not verify the tag 'v1.12.4' warning: Skipped upgrade to unverified version Apparently the repo that once was at https://dl-ssl.google.com/dl/googlesource/git-repo/repo is no longer valid and should be obtained from http://commondatastorage.googleapis.com/git-repo-downloads/repo instead. Has anyone else been seeing this? Best regards, Trevor http://www.marshut.com/wrrts/repo-release-1-12-4.html

11 years, 10 months

Release Critical Test Result Summary of Calendar Week 40,for Linaro Android Jellybean

by Soumya Basak

Calendar Week 40 2013: Here is release critical test result summary for Linaro Android Jellybean images on following boards: 1) ARM Versatile Express A9; 2) ARM Versatile Express LSK TC2; 3) Samsung Arndale; 4) Galaxy Nexus; 5) TI Pandaboard 4460; 6) TI Pandaboard 4430; 1. ARM Versatile Express A9 + Linaro Android Jellybean 4.3 (Column: BD) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… 2. ARM Versatile Express LSK TC2 + Linaro Android Jellybean 4.3 (Column: C) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… 3. Samsung Arndale + Linaro Android Jellybean 4.3 (Column:N) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AuNOCeo15fRHdDFaR… 4. Galaxy Nexus + Linaro Android Jellybean 4.3 (Column: I) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AuNOCeo15fRHdFhhe… 5. TI Pandaboard 4460 + Linaro Android Jellybean 4.3 (Column: BD) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… 6. TI Pandaboard 4430 + Linaro Android Jellybean 4.3 (Column: BD) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… Thank you. Best Regards Soumya Basak

11 years, 10 months

Release Critical Test Result Summary of Calendar Week 40, 2013 for Linux Linaro ubuntu Raring.

by Botao Sun

Calendar Week 40 2013: Here is release critical test result summary for Linux Linaro ubuntu Raring image on following boards: 1) ARM Versatile Express A9; 2) Samsung Arndale; 3) TI Panda 4430; 4) TI Panda 4460; 1. ARM Versatile Express A9 + Linux Linaro Raring (Column AO): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdFNmV… 2. Samsung Arndale + Linux Linaro Raring (Column AH): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AgB-fT5LL31CdGZJS… 3. TI Panda 4430 + Linux Linaro Raring (Column AO): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ… 4. TI Panda 4460 + Linux Linaro Raring (Column AO): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ… For the test summary of Linaro 13.09 release (Calendar Week 39), please refer to attachment. Thank you. Best Regards Botao Sun

11 years, 10 months

klibc porting to aarch64 - progress and issues

by Anil Singhar

Hi, I am trying to port klibc to aarch64. My code is available from: git clone git://git.linaro.org/people/anil.singhar/klibc-aarch64.git At this point, I am trying to fix the following issues. Any help / comment / advice / suggestion is highly appreciated. 1. Need to find the correct value for *KLIBCSHAREDFLAGS *(What value should I set *Ttext* to in the aarch64 specific MCONFIG file?). Right now the MCONFIG looks as follows: # -*- makefile -*- # # arch/aarch64/MCONFIG # # Special rules for this architecture. Note that this is actually # included from the main Makefile, and that pathnames should be # accordingly. # CPU_ARCH ?= armv8-a CPU_TUNE ?= generic KLIBCOPTFLAGS += -Os -march=$(CPU_ARCH) -mtune=$(CPU_TUNE) KLIBCBITSIZE = 64 KLIBCREQFLAGS += -fno-exceptions #KLIBCSTRIPFLAGS += -R .ARM.exidx # Extra linkflags when building the shared version of the library # This address needs to be reachable using normal inter-module # calls, and work on the memory models for this architecture *#KLIBCSHAREDFLAGS = -Ttext 0x01800200* *<-- Is this value correct..?* #KLIBCREQFLAGS += #KLIBCOPTFLAGS += -mgeneral-regs-only 2. The *stat* family of syscalls don't work correctly. There is only one actual syscall: fstat, which is used by lstat and stat. The syscall doesn't seem to return valid values for target files. e.g. The following fields are wrong: toot@genericarmv8:~/anilss/AArch64/klibc-aarch64/usr/klibc/tests# ./stat test.out Path = test.out st_dev = 0x11 (0,17) st_ino = 5910539 st_mode = 0 st_nlink = 4295000484 <-- This is wrong st_uid = 0 st_gid = 0 st_rdev = 0x0 (0,0) st_size = 15 st_blksize = 1380537164 st_blocks = 223008806 st_atim = 1048576.000000008 st.mtim = 1380612975.029926968 st.ctim = 1380537164.223008806 Because the fields are wrong, the parsed values are also wrong. Applications such as ls, gzip etc. fail to work because they rely on this syscall. Since I am doing the development on ARMv8 Foundation model using linaro openembedded image, is there a debug version of the kernel (the one * img-foundation.axf*) that I can use to debug the syscall itself in kernel mode using kgdb? Any other debugging ideas..? Thanks and Regards, Anil

11 years, 10 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev October 2013