[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linaro-validation
Subject:    [Linaro-validation] Android/Panda Failures
From:       paul.larson () linaro ! org (Paul Larson)
Date:       2012-03-31 15:44:35
Message-ID: CAD69n1Dp2a2xOwy9h24o8onc8ssGfiw2ze6a4Kp7=erSgdRb1g () mail ! gmail ! com
[Download RAW message or body]

Notification would have been nice, but it would be even better if we didn't
have to modify this file at all.  Long term, that will be possible through
the use of this dual SD device, but I think there are good possibilities
for a short term solution.  We don't have to deal with this sort of thing
on ubuntu because ubuntu allows us to use named partitions.  I was really
hoping that android wouldn't still be using hardcoded partitions after all
this time. Is there really nothing that can be done there? I suspect its
not just lava that this causes trouble with.  The other possibility for a
near term solution which I think we should do regardless of whether the
hard coded partitions are fixed, is this idea I discussed recently about
having a very slim initramfs based master image that can boot completely.
Off of the shared boot / testboot partition. This would mean that we no
longer have to make any changes to the mounts in android, and would
simultaneously solve Zygmunt's issue with corruption on hard reboots.

Thanks,
Paul Larson
On Mar 31, 2012 6:43 AM, "Alexander Sack" <asac at linaro.org> wrote:

> On Sat, Mar 31, 2012 at 10:08:27AM +0200, Le.chi Thu wrote:
> > I found the problem. The init.rc in the ramdisk image (uInitrd) has
> > changed. The lava-dispatcher patch the partition tables in the init.rc
> > file. Now the partition tables have moved to the init.partitions.rc
> > file and the init.rc import that file.
> >
>
> We need to coordinate things better imo. AFAIK Zach and his team knew
> that he was changing this file, so if he would have known that this
> file change requires coordination with the LAVA team he probably would
> have done that.
>
> May I propose to a list of the files we patch/touch and coordinate
> with Zach so he can remember to coordinate with LAVA team such a
> change?
>
> In this way we can avoid LAVA team finding out about this through job
> bustage :).
>
>
> --
> Alexander Sack <asac at linaro.org>
> Technical Director, Linaro Platform Teams
> http://www.linaro.org | Open source software for ARM SoCs
> http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
>
>
> _______________________________________________
> linaro-validation mailing list
> linaro-validation at lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-validation
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linaro.org/pipermail/linaro-validation/attachments/20120331/ab6c569c/attachment.html>

[prev in list] [next in list] [prev in thread] [next in thread]