+ Linaro Dev mailing list
Hi Phung-Te,
I don't have Samsung Arndale Octa board on my hand, haven't started testing
on it.
@Fathi, do you know anything about the u-boot source code for Arndale Octa?
Thanks.
Best Regards
Botao Sun
Hello Botao,
I am looking for the source of u-boot for arndale-octa and couldn't find
it. Your u-boot git, both stable and next only have support for arndale,
not arndale-octa.
I could get to the binary which worked fine:
arndale-octa-saucy_server_20140323-616.img.gz
Can you please point me to the source of that build.
Thank you.
Phung-Te
On Fri, Mar 28, 2014 at 2:58 PM, Botao Sun (Google Drive) <
Botao.Sun(a)linaro.org> wrote:
> I've shared an item with you.
> [image: Spreadsheet] Arndale Linux Linaro Test Result<https://docs.google.com/spreadsheet/ccc?key=0AgB-fT5LL31CdGZJSFdTUWFFYVdhZl…>
> Google Drive: create, share, and keep all your stuff in one place. [image:
> Logo for Google Drive] <https://drive.google.com>
>
Hello,
There is an issue related to perf which I am facing since 15 days. Hoping that the great minds here will help me to solve this.
I have a requirement to make perf tool work on a device having ARM architecture. But, on recording the tracepoint events and then running ./perf report, it shows the shared objects name as [unknown] and Symbols as 00000, whereas for software and hardware events I do not experience this issue.I have cross compiled the perf tool available on mailine and ported it on a device having ARM architecture.
Output on ARM based device with kernel 3.4.
./perf record -e kmem:kmalloc cal
[ perf record: Woken up 1 times to write data ][ perf record: Captured and wrote 0.007 MB perf.data (~321 samples) ]
./perf report
Overhead Command Shared Object Symbol
........................... ................................ ...........................................40.78% cal [unknown] [.]0000000031.6% cal [unknown] [.]00000000
[...]
On ubuntu 12.04, system (kernel 3.10) it works perfectly fine.
Output on x86 architecture
./perf record -e kmem:kmalloc gcalctool
[ perf record: Woken up 3 times to write data ][ perf record: Captured and wrote 0.27 MB perf.data (~845 samples) ]
./perf report --stdio
Overhead Command Shared Object Symbol
........................... ................................ ...........................................96.55% cal [kernel.kallsyms] [k] kmem_cache_alloc_trace3.45% cal [kernel.kallsyms] [.]__kmalloc
[...]
Keenly, awaiting for you help.
Thanks.
Sneha.
Hi,
I am looking at in cpufreq.c
__cpufreq_governor(policy, CPUFREQ_GOV_STOP);
up_write(&policy->rwsem);
__cpufreq_governor(policy, CPUFREQ_GOV_POLICY_EXIT);
down_write(&policy->rwsem);
Why do we need to unlock the lock before calling CPUFREQ_GOV_POLICY_EXIT.
Wont this result in a race condition when 2 cpus are calling policy
exit, one after another during governor switch?
--
Regards,
Sriram
Hi,
These are a few cleanups around idlestat commandline options while I was
working on reformating the report.
Regards,
Amit
Amit Kucheria (9):
'verbose' option isn't used anywhere, remove it
Sort options in alphabetic order of the single-char options
Adding missing 'duration' option in long_options
Specify which options need arguments and which don't to help
getopt_long()
Stick to -d for debug according to widely used convention
Make getopt_long handling more robust
struct option long_options doesn't need to be global
improve help - show all available options
idledebug? When did we ever call it that?
README | 7 +++++--
idlestat.c | 71 +++++++++++++++++++++++++++++++++++---------------------------
2 files changed, 45 insertions(+), 33 deletions(-)
--
1.9.1
When trying to build gcc-runtime_linaro-4.9.bb for qemuarm, I get the
following error:
===
[...]
| checking whether the arm-angstrom-linux-gnueabi-gcc -march=armv5te -marm
-mthumb-interwork
--sysroot=/mnt/work/setup-scripts/build/tmp-angstrom_v2014_06-eglibc/sysroots/qemuarm
linker (arm-angstrom-linux-gnueabi-ld
--sysroot=/mnt/work/setup-scripts/build/tmp-angstrom_v2014_06-eglibc/sysroots/qemuarm
) supports shared libraries... yes
| checking whether -lc should be explicitly linked in... no
| checking dynamic linker characteristics... configure: error: Link tests
are not allowed after GCC_NO_EXECUTABLES.
[...]
===
The problem reared its head with 4.8 about a month ago, but I am not sure
which update to my OE tree broke it.
Host is gentoo with profile: default/linux/amd64/13.0/desktop/gnome
(multilib) is enabled.
My gut feel is it is a host gcc problem?
===
gcc -v
Using built-in specs.
COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.7.3/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.7.3/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with:
/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/gcc-4.7.3/configure
--host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr
--bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.7.3
--includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/include
--datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3
--mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3/man
--infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3/info
--with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/include/g++-v4
--with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.7.3/python
--enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt
--disable-werror --with-system-zlib --enable-nls --without-included-gettext
--enable-checking=release --with-bugurl=https://bugs.gentoo.org/
--with-pkgversion='Gentoo 4.7.3-r1 p1.4, pie-0.5.5' --enable-libstdcxx-time
--enable-shared --enable-threads=posix --enable-__cxa_atexit
--enable-clocale=gnu --enable-multilib --with-multilib-list=m32,m64
--disable-altivec --disable-fixed-point --enable-targets=all
--disable-libgcj --enable-libgomp --disable-libmudflap --disable-libssp
--enable-lto --without-cloog --without-ppl
Thread model: posix
gcc version 4.7.3 (Gentoo 4.7.3-r1 p1.4, pie-0.5.5)
===
Non-linaro gcc-runtime-4.9.0.bb builds fine (as did 4.8).
Any help is appreciated.
--Tim
== Progress ==
* Enabling UEFI Fastboot on Panda - Tested Fastboot App in UEFI Shell
(CARD-198: 30 %)
* Enabling U-boot Fastboot for Panda - Built the code for Panda (CARD-1103:
50%)
* Flash support on u-boot fastboot - Analysis (CARD-1103: 10%)
* Testing u-boot fastboot on Panda, In Progress (10%)
== Plans ==
* CARD-198: UEFI Fastboot, work on enabling protocols and test
them(CARD-198: 20 %)
* U-boot Fastboot for Panda/Beaglebone - Test the commands (CARD-1103: 30%)
* Flash support on u-boot fastboot (CARD-1103: 50%)
== Issues ==
* None
== Progress ==
* found a workaround for FVP Base model boot failure with OE minimal armv8 prebuilt image (bug 1282076, 65%)
* few updates to ll and its topics to get the workaround above into 14.05 release (CARD-788, 10%)
* added the [ku]probes patches to ll, moved llct to the next v3.15-rc7 (CARD-788, 10%)
== Plans ==
* upload the schedule for ll updates in 2014.06, move ll to the most recent llct (CARD-788)
* update the wiki doc for DEVPLAT-204
* bug 1282076 - try to narrow down the issue: find the problematic topic branch at least (bug 1282076)
== Issues ==
* None
== Progress ==
* Investigated why QT4 uploads are failing (DEVPLAT-217: 8%)
* Built gcc-4.9 and gdb cycle (CARD-722 20%)
* Built and upload texlive-bin (CARD-722: 10%)
* Failed to build python-numpy/cython loop (CARD-722: 10%)
* Tested debootstrap from debian-ports repo. Uploaded images to Arm64Port wiki (DEVPLAT-219 15%)
* Set up 3 accounts for DDs to work on packages on porterbox (DEVPLAT-222: 15%)
* Updated wiki, wrote and sent invitation to Bootstrap Sprint (DEVPLAT-220: 10%)
* GSOC bootstrap mentoring (3%)
* Reviewed Chen's packages and DD applcation (2%)
* Tried (and failed) to run compulsory ARM training (java+flash) (8%)
* Tried to get ARM timesheeting fixed (4%)
* Booked hotel for Connect LCU (2%)
== Plans ==
* Build poppler. (DEVPLAT-221)
* Build/upload QT4. (DEVPLAT-217)
== Issues ==
* ARM admin is windows-centric PITA.
* QT4 uploads getting lost due to wrong keys
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
== Progress ==
Upgrading the ARM trusted firmware with fip binaries : Able to boot the
kernel But got stuck at not mounting the root file system to boot android
(DEVPLAT-216 : 60%)
== Plans ==
Get boot android on fastmodel with FIP binaries (DEVPLAT-216)
== Issues ==
None
--
Thanks and Regards,
HariGopal G
Android Engineer
