On 10:11 Thu 03 Oct , Geert Uytterhoeven wrote:
> On Thu, Oct 3, 2013 at 9:31 AM, Jean-Christophe PLAGNIOL-VILLARD
> <plagn...@jcrosoft.com> wrote:
> >> Android boot time could be dramatically improved by leveraging
> >> checkpoints/snapshots approaches (might be sufficient for variety of
> >> products/use cases), on the other side it would be great to study
> >> deeper if Android cold boot speed could be improved, at least for
> >> automotive/IVI scenarios (get display/video/audio enabled early)
> >
> > what is the booting target?
> >
> > I've done in the past on non optimised android < 30s from cold start to UI
> > on arm926ejs with base Android < 30s
> > on more complex and full feature Android on Cortex-A9 (5 MiB kernel) < 30s
> > with optimised bootloader (barebox)
>
> Hmm, 30 seconds can be a long time ;-)
>
> For user interaction, the typical guideline is: upon any user activity,
> the system should respond within 500 ms, either by performing the
> operation, or by giving an indication about it's progress.
>
> if I e.g. fetch my camera and turn it on, I want to take a picture within
> 500 ms.
That is exactly the issue here what means boot time.
here I get board with a full system + QT UI in 300ms running from cold start.
You must specify what means boot time because boot time can be up to the
prompt or up to specific application feature that is customer specific not
general purpose
Best Regards,
J.
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
> ge...@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like
> that.
> -- Linus Torvalds
_______________________________________________
Celinux-dev mailing list
Celinux-dev@lists.celinuxforum.org
https://lists.celinuxforum.org/mailman/listinfo/celinux-dev
