Hi,
I've just committed the code needed to build an initial Linaro
JellyBean version (buildable with the Linaro gcc 4.7 compiler):
repo init -u git://android.git.linaro.org/platform/manifest.git -b
linaro_android_4.1.1
repo sync
Currently the build supports only the Galaxy Nexus - didn't want to
run into trouble with potentially incompatible binary blobs before
knowing the rest of the system is working.
Support for our normally supported boards will be added over the next
couple of days. Optimizations that currently aren't on the 4.1 branch
will also be restored in the next couple of days.
There's also 2 problems we need to fix quickly:
E/WVMExtractor( 126): Failed to open libwvm.so entries showing up in
logcat (a quick grep indicates nothing seems to build libwvm - neither
in our tree nor in AOSP)
and
I/v8 ( 1293): ERROR: Binary compiled with -mfloat-abi=hard but
without -DUSE_EABI_HARDFLOAT
(we don't actually use hardfloat (yet), so chances are the check for
hardfloat goes wrong with gcc 4.7.x)
The camera isn't working, but that's not a high priority issue given
the Galaxy Nexus is not a device we're supporting officially.
Of course our gerrit is always happy to receive patches for these and
other issues. ;)
ttyl
bero
hello,
I am using the 4.7.3-201301 toolchain and when trying to compile an android
kernel I get the following exidx warnings:
/home/ggutierrez/android-toolchain-eabi-4.7.3-201301/bin/arm-eabi-ld:
warning: unwinding may not work because EXIDX input section 20 of
arch/arm/common/built-in.o is not in EXIDX output section
/home/ggutierrez/android-toolchain-eabi-4.7.3-201301/bin/arm-eabi-ld:
warning: unwinding may not work because EXIDX input section 11 of
arch/arm/crypto/built-in.o is not in EXIDX output section
/home/ggutierrez/android-toolchain-eabi-4.7.3-201301/bin/arm-eabi-ld:
warning: unwinding may not work because EXIDX input section 52 of
arch/arm/mach-msm/built-in.o is not in EXIDX output section
/home/ggutierrez/android-toolchain-eabi-4.7.3-201301/bin/arm-eabi-ld:
warning: unwinding may not work because EXIDX input section 598 of
kernel/built-in.o is not in EXIDX output section
/home/ggutierrez/android-toolchain-eabi-4.7.3-201301/bin/arm-eabi-ld:
warning: unwinding may not work because EXIDX input section 263 of
mm/built-in.o is not in EXIDX output section
/home/ggutierrez/android-toolchain-eabi-4.7.3-201301/bin/arm-eabi-ld:
warning: unwinding may not work because EXIDX input section 116 of
fs/built-in.o is not in EXIDX output section
/home/ggutierrez/android-toolchain-eabi-4.7.3-201301/bin/arm-eabi-ld:
warning: unwinding may not work because EXIDX input section 37 of
crypto/built-in.o is not in EXIDX output section
/home/ggutierrez/android-toolchain-eabi-4.7.3-201301/bin/arm-eabi-ld:
warning: unwinding may not work because EXIDX input section 203 of
block/built-in.o is not in EXIDX output section
/home/ggutierrez/android-toolchain-eabi-4.7.3-201301/bin/arm-eabi-ld:
warning: unwinding may not work because EXIDX input section 153 of
lib/built-in.o is not in EXIDX output section
/home/ggutierrez/android-toolchain-eabi-4.7.3-201301/bin/arm-eabi-ld:
warning: unwinding may not work because EXIDX input section 39 of
drivers/built-in.o is not in EXIDX output section
/home/ggutierrez/android-toolchain-eabi-4.7.3-201301/bin/arm-eabi-ld:
warning: unwinding may not work because EXIDX input section 11 of
sound/built-in.o is not in EXIDX output section
/home/ggutierrez/android-toolchain-eabi-4.7.3-201301/bin/arm-eabi-ld:
warning: unwinding may not work because EXIDX input section 9 of
arch/arm/oprofile/built-in.o is not in EXIDX output section
/home/ggutierrez/android-toolchain-eabi-4.7.3-201301/bin/arm-eabi-ld:
warning: unwinding may not work because EXIDX input section 506 of
net/built-in.o is not in EXIDX output section
what do I need to do to eliminate these warnings without hiding them?
--
Guillermo Gutierrez
guillermogutierrezjr(a)gmail.com
Zach/Vishal,
During our meeting today we spoke a little about improving CTS in LAVA.
One issue sounds like CTS reboots the target and due to our master-image
uboot commands the device doesn't boot back into Android.
I thought I'd give you pointer on how that could be improved in LAVA:
<http://bazaar.launchpad.net/~linaro-validation/lava-dispatcher/trunk/view/h…>
I think you might be able to somehow doctor that DrainConsole thread to
search for uboot prompts and if hit, run the android boot-cmds to get it
set back up.
Hope it helps once somebody starts investigating,
-andy
I'm sending this email to gauge interest in a proposed change to
host-side ADB:
I'm currently using ADB in conjunction with a USB mass storage device
that must be powered on/off repeatedly via the /sys interface on
Linux[1]. This was working correctly until I recently added ADB into the
workflow. The problem I now see is that this sequence won't work:
power off device
run set of adb commands (that cause the daemon to run in background)
power on device
It seems the probing of my devices entry under /dev/bus/usb is causing
it to enter a weird state. The only way I've gotten it out of that state
is to run "adb kill-server" and then physically unplug/plug the device.
My proposed solution (attached) gives you two options:
* ignore USB devices entirely
* black list certain devices
I would like to see this patch make it to AOSP in some form, but I'm not
sure if my use-case is too specific for you guys. Any interest?
1: http://people.linaro.org/~doanac/sdmux/sdmux.sh
hi calender week 6 2013, here is the test summary for linaro android jb on
different platform
[1] TI-Panda 4430
[2] TI-Panda 4460
[3] ST-Snowball
[4] ARM vexpress A9
[1] TI-Panda 4430 with Linaro android jb (column: AB)
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd…
summary: graphics and colours is distorted, suspend-resume test failed,
wifi and bluetooth is not working, Calender, people, email apps add event
or sync is failed, powertop test is failed. audio, ethernet, youtube is
working well.
please refer to the spread-sheet for details.
[2] TI-Panda 4460 with linaro android jb (column: AD)
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd…
summary: exactly same result as panda 4430 platform. graphics and colours
is distorted, suspend-resume test failed, wifi and bluetooth is not
working, Calender, people, email apps add event or sync is failed, powertop
test is failed. audio, ethernet, youtube is working well.
please refer to the spread-sheet for details
[3] ST-snowball with Linaro android jb (column: X)
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadEF1N…
summary: exactly same result as 13.01 rc image. no major bug is fixed in
this week. suspend-resume fails, vid playback youtube fails, calender sync
people, email sync is not happend.
[4] ARM vexpress-A9 with linaro android jb (column: Y)
summary: exactly same result as linaro android 13.01 rc. sd-card partition
is not avilable, adb test fails, device-tree is not there, adb ethernet is
pass, usb-host is also working fine.
please refer to the spreadsheet for more details.
Thanks & Regards
Soumya Basak.
Hi, Andy Doan & Paul Sokolovsky & Vishal Bhoj & All
Now lava-test-shell is supported by LAVA,
and android team is considering adding the support on android-build.
I want to add following 3 interfaces on the android-build,
*1. lava-test-shell-url(url=
http://cbuild.validation.linaro.org:80/helpers/scheduler/lava/testdef/lava-…
timeout=59400)*
where timeout is optional
when submitted, the action in job will be something like this:
{
"command": "lava_test_shell",
"parameters": {
"testdef_urls": ["
http://cbuild.validation.linaro.org:80/helpers/scheduler/lava/testdef/lava-…
"],
"timeout": 59400
}
}
*2. lava-test-shell-git(repo=git://git.linaro.org/qa/test-definitions.git
revision=master testdef=android/binder.yaml timeout=-1)
*
where revison/testdef/timeout is optional
when submitted, the action in job will be something like this:
{
"command": "lava_test_shell",
"parameters": {
"testdef_repos": [
{
"git-repo": "git://
git.linaro.org/qa/test-definitions.git",
"revision": "master",
"testdef": "android/binder.yaml"
}
],
"timeout": -1
}
}
*3. lava-test-shell-bzr(repo=lp:~terceiro/+junk/lava-dev
revision=112 timeout=-1)*
where revison/testdef/timeout is optional
when submitted, the action in job will be something like this:
{
"command": "lava_test_shell",
"parameters": {
"testdef_repos": [
{
"bzr-repo":
"lp:~terceiro/+junk/lava-dev",
"revision": "112",
"testdef": "jobs/android-busybox.yaml"
}
],
"timeout": -1
}
}
By these 3 types interface, we can do most of the things lava-test-shell
supported.
Although we can't specify the array form with one interface one time,
we can do the same things by specifying multiple times the interface of the
same type.
like *lava-test-shell-url(url=url1),**lava-test-shell-url(url=url2),*
so I think it's enough for us to use on android-build.
About this, how do you think about that?
Please feel free to give your comments. Thanks in advance!
--
Thanks,
Yongqin Liu
---------------------------------------------------------------
#mailing list
linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org>
http://lists.linaro.org/mailman/listinfo/linaro-android
linaro-validation(a)lists.linaro.org <linaro-dev(a)lists.linaro.org>
http://lists.linaro.org/pipermail/linaro-validation
