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/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
+ Linaro Android Mailing List
On Fri, Nov 22, 2013 at 7:44 PM, Botao Sun <botao.sun(a)linaro.org> wrote:
> Hi Vishal,
>
> Do you think we need a bug in Launchpad to track this issue?
>
> Thanks.
>
>
> Best Regards
> Botao Sun
>
>
> On Fri, Nov 22, 2013 at 5:38 PM, Soumya Basak <soumya.basak(a)linaro.org>wrote:
>
>> Hi Botao,
>> I have checked twice the image with panda 4460 board:
>>
>> http://snapshots.linaro.org/android/~linaro-android-member-ti/panda-linaro/…
>>
>> http://snapshots.linaro.org/android/~linaro-android-member-ti/panda-linaro/…
>>
>> http://snapshots.linaro.org/android/~linaro-android-member-ti/panda-linaro/…
>>
>> 1. basically, when eth0 cable is plugged in hw, and wifi is not turned on
>> from UI,
>> # busybox ifconfig -a not shown the wlan0
>> only eth0 up and accessing network.
>> 2. when you turn on wifi it will ask you password, after assign password,
>> wifi shown connected (but inactive),
>> # busybox ifconfig -a shown the wlan0 candidate but no inet address,
>> and mask.
>> 3. when unplugged the eth0, wlan0 is get inet address and musk, and
>> connected.
>>
>> on the other hand wifi is working well, there is no issue with Youtube
>> playback, or enable from UI, after assign Password.
>>
>> so, both are not up at the same time.
>>
>> this stuff is observed from since Android version: 4.3
>>
>> @Botao, what is your opinion ?
>>
>> Thank You.
>> Best Regards
>> Soumya Basak.
>>
>>
>>
>>
>> On 21 November 2013 20:40, Botao Sun <botao.sun(a)linaro.org> wrote:
>>
>>> OK, with more tests, the problem is, if no Ethernet cable attached, WiFi
>>> works, otherwise, it shows the error I mentioned in previous 2 emails.
>>>
>>> root@pandaboard:/ # busybox ifconfig -a
>>> eth0 Link encap:Ethernet HWaddr 0E:60:CF:E5:49:01
>>> UP BROADCAST RUNNING MULTICAST MTU:1488 Metric:1
>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:1000
>>> RX bytes:0 (0.0 B) TX bytes:2510 (2.4 KiB)
>>>
>>> ip6tnl0 Link encap:UNSPEC HWaddr
>>> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>>> NOARP MTU:1452 Metric:1
>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:0
>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>>>
>>> lo Link encap:Local Loopback
>>> inet addr:127.0.0.1 Mask:255.0.0.0
>>> UP LOOPBACK RUNNING MTU:16436 Metric:1
>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:0
>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>>>
>>> sit0 Link encap:UNSPEC HWaddr
>>> 00-00-00-00-0F-00-01-00-00-00-00-00-00-00-00-00
>>> NOARP MTU:1480 Metric:1
>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:0
>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>>>
>>> wlan0 Link encap:Ethernet HWaddr 0E:20:CF:E5:49:01
>>> inet addr:10.0.0.25 Bcast:10.0.0.255 Mask:255.255.255.0
>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>> RX packets:96 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:105 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:1000
>>> RX bytes:97780 (95.4 KiB) TX bytes:14813 (14.4 KiB)
>>>
>>> root@pandaboard:/ #
>>>
>>> Is it a "work-as-design" stuff or a bug? If we keep it likes this, then
>>> in order to test WiFi, I have to disable Ethernet first, then restore it
>>> after the test is done.
>>>
>>> Thanks.
>>>
>>>
>>> Best Regards
>>> Botao Sun
>>>
>>>
>>>
>>>
>>> On Fri, Nov 22, 2013 at 2:02 AM, Botao Sun <botao.sun(a)linaro.org> wrote:
>>>
>>>> Hi Soumya,
>>>>
>>>> The WiFi doesn't work on 13.10 release image either:
>>>>
>>>>
>>>> https://android-build.linaro.org/builds/~linaro-android-member-ti/panda-lin…
>>>>
>>>> On my TI Panda 4460 board, same behaviour observed, and following
>>>> output shows:
>>>>
>>>> [ 148.630249] wl1271: loaded
>>>> [ 149.538604] wl1271: firmware booted (Rev 6.3.0.0.77)
>>>> [ 149.556671] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>>>> [ 250.320129] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
>>>> [ 250.383636] wl1271: Association completed.
>>>> [ 251.542541] cfg80211: Calling CRDA to update world regulatory domain
>>>> [ 261.064025] wl1271: Scan completed due to error.
>>>> [ 261.069000] wl1271: Reading FW panic log
>>>> [ 261.074127] wl1271: Hardware recovery in progress. FW ver: Rev
>>>> 6.3.0.0.77 pc: 0x0
>>>> [ 261.074127] wl1271: down
>>>> [ 261.086059] ieee80211 phy0: Hardware restart was requested
>>>> [ 261.714691] wl1271: firmware booted (Rev 6.3.0.0.77)
>>>>
>>>> Would you double check it on your side? Based on the output of
>>>> "ifconfig", there is no IP assigned to wlan0 interface:
>>>>
>>>> root@pandaboard:/ # busybox ifconfig -a
>>>> eth0 Link encap:Ethernet HWaddr 0E:60:CF:E5:49:01
>>>> inet addr:10.0.0.24 Bcast:10.0.0.255 Mask:255.255.255.0
>>>> UP BROADCAST RUNNING MULTICAST MTU:1488 Metric:1
>>>> RX packets:34 errors:0 dropped:2 overruns:0 frame:0
>>>> TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
>>>> collisions:0 txqueuelen:1000
>>>> RX bytes:3870 (3.7 KiB) TX bytes:1901 (1.8 KiB)
>>>>
>>>> ip6tnl0 Link encap:UNSPEC HWaddr
>>>> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>>>> NOARP MTU:1452 Metric:1
>>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>>> collisions:0 txqueuelen:0
>>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>>>>
>>>> lo Link encap:Local Loopback
>>>> inet addr:127.0.0.1 Mask:255.0.0.0
>>>> UP LOOPBACK RUNNING MTU:16436 Metric:1
>>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>>> collisions:0 txqueuelen:0
>>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>>>>
>>>> sit0 Link encap:UNSPEC HWaddr
>>>> 00-00-00-00-0F-00-01-00-00-00-00-00-00-00-00-00
>>>> NOARP MTU:1480 Metric:1
>>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>>> collisions:0 txqueuelen:0
>>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>>>>
>>>> wlan0 Link encap:Ethernet HWaddr 0E:20:CF:E5:49:01
>>>> UP BROADCAST MULTICAST MTU:1500 Metric:1
>>>> RX packets:3 errors:0 dropped:0 overruns:0 frame:0
>>>> TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
>>>> collisions:0 txqueuelen:1000
>>>> RX bytes:607 (607.0 B) TX bytes:655 (655.0 B)
>>>>
>>>> root@pandaboard:/ #
>>>>
>>>> Thanks.
>>>>
>>>>
>>>> Best Regards
>>>> Botao Sun
>>>>
>>>>
>>>> On Fri, Nov 22, 2013 at 12:40 AM, Botao Sun <botao.sun(a)linaro.org>wrote:
>>>>
>>>>> Hi Soumya,
>>>>>
>>>>> Please take a look at WiFi status on TI Panda 4460, with Linaro
>>>>> Android build 479:
>>>>>
>>>>>
>>>>> http://snapshots.linaro.org/android/~linaro-android-member-ti/panda-linaro/…
>>>>>
>>>>> http://snapshots.linaro.org/android/~linaro-android-member-ti/panda-linaro/…
>>>>>
>>>>> http://snapshots.linaro.org/android/~linaro-android-member-ti/panda-linaro/…
>>>>>
>>>>> You can use "wget" to download them in your local terminal if the web
>>>>> page can't be shown up.
>>>>>
>>>>> I ask because I just found WiFi doesn't work via GUI on my side,
>>>>> following log shows in serial console:
>>>>>
>>>>> [ 25.692474] wl1271: loaded
>>>>> [ 26.373870] smsc95xx 1-1.1:1.0: eth0: link up, 100Mbps,
>>>>> full-duplex, lpa 0x45E1
>>>>> [ 27.608551] wl1271: firmware booted (Rev 6.3.0.0.77)
>>>>> [ 27.629058] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>>>>> [ 29.750000] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
>>>>> [ 29.803771] wl1271: Association completed.
>>>>> [ 29.951232] init: sys_prop: permission denied uid:1003
>>>>> name:service.bootanim.exit
>>>>> [ 30.969970] cfg80211: Calling CRDA to update world regulatory domain
>>>>>
>>>>> The access point can be shown successfully in the list, and I can
>>>>> click and enter password as well, but then above output shows, with
>>>>> "Disabled" under the access point name on my screen.
>>>>>
>>>>> Based on our test result spreadsheet, it should at least work on 13.10
>>>>> release image. I'm going to try it soon.
>>>>>
>>>>> Thanks.
>>>>>
>>>>>
>>>>> Best Regards
>>>>> Botao Sun
>>>>>
>>>>
>>>>
>>>
>>
>
Good evening,
Turns out libnl 1.0 isn't enough for Google - they need 2.0 otherwise other
things break. I got libnl 2.0 to compile on kitkat and now I need a
project for it under platform/external.
The 1.0 version was simply labelled "libnl". This one is version 2.0 so I
suggest "libnl20" or "libnl2". I don't have a firm opinion on the matter,
simply do what you think is most appropriate. I will also need a branch to
push to in that repo - I'm fine with following the same convention that we
had for "libnl".
Thanks,
Mathieu
Hi,
Android 4.4.2 was tagged a couple of hours earlier -- I've rebased our tree
and created linaro_android_4.4.2/linaro_android_4.4.2_juice branches.
My test build is still running, so no guarantees (yet) - but looking at the
diffs, I think this is fairly low risk, and we may want to consider cutting
the release from linaro_android_4.4.2.
ttyl
bero
Hi,
I am working on panda board es 4460 and also I have installed image in sd card due to binary image installation.
With HDMI output , there is no problem everything is ok except lcd panel. There is no output to lcd panel.
But I need to use linaro-android 13.11 with lcd touch-screen panel.
is it supported by linaro release 13.11?
or else I have to build android from linaro-android sources with lcd panel support.
thanks in advance