Hi,
I have an Arndale Octa board 5420, searching from where to get the latest linaro android build (which supports kitkat or lollipop).
Could you please help?
Regards,
Smit.
Hi,
About the patch http://review.android.git.linaro.org/#/c/15529/, we got
an issue report from member. It could improve the micro benchmark but
hurt general benchmark actually. Here is their test result:
bionic-benchmarks32 BM_string_memcpy:
Size AOSP Linaro Perf Improvement
8 450.7 329.5 -37%
64 1715.7 2225.3 23%
512 3100.7 4253.0 27%
1K 3271.8 4652.3 30%
8K 2460.9 3174.7 22%
16K 2267.4 2953.2 23%
32K 2222.9 2800.7 21%
64K 2204.3 2640.1 17%
without patch with patch perf delta
Quadrant mem 3400 2100 -38%
GeekBench3
single-core 436 260 -40%
multi-core 434 358 -18%
I am wondering whether this is an known issue or not for this list.
Thanks in advance.
Regards
Yin, Fengwei
Hello,
All Linaro Gerrit services (4 of them) currently run Gerrit 2.8.6.1,
the latest of 2.8 branch, which is now 1 year old, and 3 major releases
behind the latest, 2.11.
We (Systems) regularly get requests regarding features available in
newer Gerrit versions, and regularly face issues, which are not even
reportable upstream, as we run a pretty old version.
With all the improvements we did to Gerrit management across different
installs lately, we're now ready to raise the question of the version
upgrade. Here're basic facts about recent Gerrit versions:
1. Major change in 2.9 is introduction of new change summary screen.
It's pretty different by both looks and feel and it's fair to say taht
one needs to relearn Gerrit a bit with its introduction. It's still
possible to use old screen, until it's removed in further versions.
2. 2.11 does remove support for old change summary screen.
3. 2.10 and 2.11 are actively supported and maintained (e.g. 2.10.6
released Jun 29, 2.11.2 - Jul, 14).
Based on this, we would like to propose upgrade to 2.10, to let people
some leeway to learn the new change screen, and be able to switch back
to the old screen in the meantime.
As usual, we'd like to select single server for pilot upgrade first,
and among 4 we have, Linaro Android Gerrit,
https://android-review.linaro.org seems like a good candidate, as it's
used just by subset of Linaro teams, and at the same time, used
regularly to call it "tested" after the pilot period.
Things you can do/help with in the meantime:
1. Provide feedback on the general idea of the upgrade.
2. Let us know if you'd like a server you regularly use to be upgraded
sooner rather than later. We in particular would like to know whether
Android Team (and other stakeholders) agree to pilot new version on
https://android-review.linaro.org
3. Get feedback from any stakeholders which may be affected, first of
all, from Builds&Baselines, who run CI with Gerrit integration.
4. Get acquainted with new change screen "extramurally", by reviewing
documentation with extensive screenshots:
https://gerrit-documentation.storage.googleapis.com/Documentation/2.9/user-…
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
Hello Android Team,
For this past weekend, there was scheduled an LDAP authentication
upgrade for review.android.git.linaro.org - sorry, it wasn't announced
to the list, because it should be pretty transparent change, so I just
got an ack from Vishal on IRC.
However, the migration was postponed last-minute because new auth
setup requires having SSL on review.android.git.linaro.org, and we lack
it there. It's not enabled because it has pretty deep 5-level domain
name, we never had such a wildcard certificate, and apparently never
ordered a dedicated certificate for it. During last year or so we
actually gave up many 4-level domain names, by switching to use dashes
as separators instead of dots. That's more cost-effective and much
easier to maintain and avoid situation with expired certificates, etc.
So, what we'd like to do is migrate Android services to contemporary
Linaro naming convention either. It would be:
review.android.git.linaro.org -> android-review.linaro.organdroid.git.linaro.org -> android-git.linaro.org
Note that older names will remain active and will be supported
indefinitely. How it will look like, is that if you access
review.android.git.linaro.org via web browser, you will be
automatically redirected to android-review.linaro.org. Access via
gerrit, git, ssh will work as before.
Overall, the upgrade should be seamless, but as there will be several
moving parts, there may be risk of something breaking for short periods
of time. So, we would like to make sure that there're no concerns and
that e.g. end of next week is good time to proceed.
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
Adding subject.
On Mon, Jul 13, 2015 at 11:42 PM, $rik@nth <srikanth007m(a)gmail.com> wrote:
> Hi All,
>
> AFAIK the current RT tests [1] doesn't have an Android.mk by default to
> compile with android tool chain.
>
> Seems somebody would have already been tried to cross compile the current
> version of rt tests to arm android.
>
> It would be great if someone can share the exact steps to be followed for
> cross compiling.
>
> [1] *git*://*git*.kernel.org/pub/scm/*linux*/kernel/*git*/clrkwllms/*rt*
> -tests.*git*
>
> --
> Thanks & Regards,
> M.Srikanth Kumar.
>
--
Thanks & Regards,
M.Srikanth Kumar.
Hi All,
AFAIK the current RT tests [1] doesn't have an Android.mk by default to
compile with android tool chain.
Seems somebody would have already been tried to cross compile the current
version of rt tests to arm android.
It would be great if someone can share the exact steps to be followed for
cross compiling.
[1] *git*://*git*.kernel.org/pub/scm/*linux*/kernel/*git*/clrkwllms/*rt*
-tests.*git*
--
Thanks & Regards,
M.Srikanth Kumar.
Hi Vishal,
I saw the local manifest git tree
(ssh://git@dev-private-git.linaro.org/linaro-art/platform/manifest.git)
had following comment merged:
commit fc4cd0977538e46dd479a117958b8d0c6ab20017
Author: Vishal Bhoj <vishal.bhoj(a)linaro.org>
Date: Sun Jul 5 11:03:22 2015 +0100
Clean up manifest to have only ART specific components
Signed-off-by: Vishal Bhoj <vishal.bhoj(a)linaro.org>
Change-Id: I6b066e9504a0ad0d8b137eae0f92edf53f978c85
Two questions regarding this change:
1. It make me can't download the old LCR drop like 15.06/15.05. Because
it removed some projects
which were included in 15.06. I need to revert this commit.
2. I saw you remove all other changes except ART. Does this mean the
coming mem-lcr just inlcudes
ART related changes?
I also saw a new remote branch linaro-lollipop which match the old
mem-lcr exactly. Should we
update the the linaro_android_build_cmds.sh for old mem-lcr release so
people don't need to play
with local manifest for old mem-lcr downloading? Thanks.
Regards
Yin, Fengwei
