Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] Compile Linux with Buildroot for i.MX28 EVK
Date: Sat, 25 Feb 2012 08:35:06 -0600	[thread overview]
Message-ID: <201202250835.08165.minimod@morethan.org> (raw)
In-Reply-To: <20120224211027.51454463@skate>

On Fri February 24 2012, Thomas Petazzoni wrote:
> Le Fri, 24 Feb 2012 11:10:04 -0600,
> "Michael S. Zick" <minimod@morethan.org> a ?crit :
> 
> > A better solution -
> > Put your device to sleep (suspend to ram).
> > It can __resume__ in less than 1 sec.
> > It only needs to __re-boot__ after loss of battery power (rare).
> 
> While this is a great solution, it may not apply to the automotive
> industry: you may want to reduce the power consumption of the device
> down to 0, so that the car battery doesn't empty itself if the car is
> unused during a long period of time. 
>

The O.P. did not state they where using a vacuum tube computer.

The keep-alive current of a modern, silicon, SoC based system is far
less than the self-discharge rate of a lead-acid battery.

Its even less than the capacity change with temperature - presuming the
battery was charged while warm and is now at environment temperature.
(And the charging warmed the battery, even if not exposed to heat sources.)

So I think you are safe to let the vehicle sit - the battery will die
of old age before an i.MX28 system in deep sleep will run it down.

Mike
> I guess in terms of boot time 
> there is no one-size-fits-all solution, the solution very much depends
> on the environment and constraints (hardware, allowed power
> consumption, etc.).
> 
> Best regards,
> 
> Thomas

  reply	other threads:[~2012-02-25 14:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 11:22 [Buildroot] Compile Linux with Buildroot for i.MX28 EVK Mikael Åsberg
2012-02-23 12:11 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-23 12:38 ` Baruch Siach
     [not found]   ` <63D6870D443E63419AC4A0C97B86C092030FCA18@MBXCLUSTER.mdh.local>
2012-02-23 17:17     ` Baruch Siach
2012-02-24 13:19       ` Mikael Åsberg
2012-02-24 13:33         ` Yegor Yefremov
2012-02-24 13:53           ` Mikael Åsberg
2012-02-24 14:06             ` Yegor Yefremov
2012-02-24 14:33               ` Mikael Åsberg
2012-02-24 15:10                 ` Yegor Yefremov
2012-02-24 15:22                   ` Mikael Åsberg
2012-02-24 15:40                     ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-24 15:58                       ` Mikael Åsberg
2012-02-24 16:35                         ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-24 16:46                           ` Mikael Åsberg
2012-02-24 16:56                             ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-24 20:31                             ` Thomas Petazzoni
2012-02-25  8:39                               ` Mikael Åsberg
2012-02-26  9:34                                 ` Baruch Siach
2012-02-24 17:10                     ` Michael S. Zick
2012-02-24 20:10                       ` Thomas Petazzoni
2012-02-25 14:35                         ` Michael S. Zick [this message]
2012-02-24 15:38           ` Jean-Christophe PLAGNIOL-VILLARD

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201202250835.08165.minimod@morethan.org \
    --to=minimod@morethan.org \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox