---------- Forwarded message ----------
From: Marcus Matten <mmavdev(a)gmail.com>
To: linaro-android <linaro-android(a)lists.linaro.org>, Claude Youn <
claude.youn(a)linaro.org>
Cc:
Date: Thu, 11 Apr 2013 14:38:47 +0200
Subject: Re: Having SATA issues with Arndale
Hi,
insignal has not responded to any of my inquiries yet. We are trying the
latest linaro kernels today, but I have been told off-list here that SATA
is not on linaro's critical path. I am hoping for the best though.
It'd be a start for me if someone confirmed to have SATA working with the
newer arndale boards in question (VERC cpu module, 2012_10_24).
Best regards
Marcus
On Thu, Apr 11, 2013 at 11:46 AM, Fathi Boudra <fathi.boudra(a)linaro.org>
wrote:
> Hi,
>
> On 10 April 2013 09:59, Marcus Matten <mmavdev(a)gmail.com> wrote:
>> Hi,
>>
>> i have 2 batches of arndale boards, for the first batch SATA is working,
for
>> the second batch it isn't.
>>
>> Short fact: First batch boards have a different CPU board revision
>>
>> I've described the issue in the following post in the insignal forums in
>> more detail:
>>
>>
http://forum.insignal.co.kr/viewtopic.php?f=10&t=2505&sid=50a2da79db788d6bb…
>>
>> I gather the sources provided with the arndale project have been done
mostly
>> by linaro, so I am trying to get some help here.
>>
>> If i am addressing this to the wrong list, please give me a pointer whom
i
>> could turn to.
>
> Insignal seems really the right point of contact for your issue.
> Are they (and you also) able to reproduce your issue with their kernel?
>
>> I have 20 of these lying around here and can't get them to work like the
>> first batch boards, which would be a significant investment for me going
to
>> the trash bin as working SATA is mandatory for my use-case.
>>
>> Best regards
>> Marcus
Hi,
i have 2 batches of arndale boards, for the first batch SATA is working,
for the second batch it isn't.
Short fact: First batch boards have a different CPU board revision
I've described the issue in the following post in the insignal forums in
more detail:
http://forum.insignal.co.kr/viewtopic.php?f=10&t=2505&sid=50a2da79db788d6bb…
I gather the sources provided with the arndale project have been done
mostly by linaro, so I am trying to get some help here.
If i am addressing this to the wrong list, please give me a pointer whom i
could turn to.
I have 20 of these lying around here and can't get them to work like the
first batch boards, which would be a significant investment for me going to
the trash bin as working SATA is mandatory for my use-case.
Best regards
Marcus
Hello,
I recently got
https://blueprints.launchpad.net/linaro-infrastructure-misc/+spec/rebasing-…
to verify current state of affairs with repo handling of SHA revisions
for commits which have underlying tags. The blueprints contains full
details, let me in this report mail cover just we most important bits.
1. We have been having problem with repositories used in Android
releases being rebased later for a long time.
2. Trying to resolve that, we established policy that any revision used
in a release must be tagged, to make sure that exact revision stays
across rebases.
3. That didn't really work well with "repo" tool from ~1.5yr ago,
because it did not fetch tags by default, so rebased revisions were
still unreachable.
4. We did our patching to repo and submitted it to Google, which then
was lost in great kernel.org demise of 2011, and later they rejected it
telling they'd do it in different way.
5. Fast forward to modern time, I verified that repo v1.12.2 works as
expected wrt to fetching commits by SHA revs, if they have underlying
tag, so we're covered for policy of p.2.
6. However, few repos were found to still be rebased without tagging
release revisions. To address that, following options are proposed:
a) Disallow to use SHA revs in release manifests. Granted, that would
make more effort to do a release then just get pinned manifest of some
build, but may improve release process by prompting to ensure that
releases are made from Android Team managed mirrors of repositories,
and that all such repositories are tagged in consistent manner (which
how upstream does it).
b) Verify that each SHA has underlying tag. A bit more challenging
technically (i.e. possibility for unexpected behavior), and misses the
chance to move release process to a new level, but should be still
doable.
Note that both choices preserve ability to rebase repositories, which
is considered an important developers' right ;-).
--
Best Regards,
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
I am wondering if you have the necessary android img files (preferably jelly bean version) and the method to run android image on qemu running on regular ubuntu-pc-64bit.
Thank you;
Hi,
Since Google Sync has been terminated from 30 January 2013 (
http://support.google.com/a/bin/answer.py?hl=en&answer=2716936), Calendar &
People apps can't sync with Google server from that time until now.
However, Email app works well.
Calendar: https://bugs.launchpad.net/linaro-android/+bug/1057208
People: https://bugs.launchpad.net/linaro-android/+bug/1029373
As a walk around, we can install GApps manually then set up account to sync
with Google server:
http://wiki.cyanogenmod.org/w/Gapps
But the concern here is we currently don't have GApps pre-installed in our
images. If an end user downloaded our release then he / she will find the
malfunction on Calendar & People apps. The solution is either we
pre-install GApps, or we write something like this in our release notes:
"To enable remote sync with Google server, please install GApps from here:
http://wiki.cyanogenmod.org/w/Gapps"
I will close above 2 bugs if we will do like this.
Thanks.
Best Regards
Botao Sun
Hi,
Here is the test result summary for Linaro-Android jellybean for Different
builds
[1] TI-Panda 4430
[2] TI-Panda 4460
[3] Origen 4412 quad.
Synopsis: Linaro-android jellybean week14 test result, it keeps exactly
same result as Linaro-android jellybean 13.03 Release test result, no new
bug or regression in this week.
[1] TI-Panda 4430 with Linaro-android jellybean (column:AE)
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd…
Please look into the result spreadsheet for details test result and bug
report.
[2] TI-Panda 4460 with Linaro-android jellybean (column:AE)
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd…
Please look into the result spreadsheet for details test result.
[3] origen 4412 quad with Linaro-android jellybean (column:D)
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadDRDV…
Please look into the result spreadsheet for details test result and bug
report.
With Best regards
Soumya Basak.