mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Marc Reilly <marc@cpdesign.com.au>
To: barebox@lists.infradead.org
Cc: Krzysztof Halasa <khc@pm.waw.pl>
Subject: Re: RFC: Force a 2s delay on startup to allow bypassing /dev/env0.
Date: Mon, 7 May 2012 10:14:24 +1000	[thread overview]
Message-ID: <201205071014.25217.marc@cpdesign.com.au> (raw)
In-Reply-To: <m3bom1yzah.fsf@intrepid.localdomain>


[-- Attachment #1.1: Type: text/plain, Size: 854 bytes --]

On Monday, May 07, 2012 03:50:14 AM Krzysztof Halasa wrote:
> Sascha Hauer <s.hauer@pengutronix.de> writes:
> > Being able to interrupt before environment processing is a good thing to
> > have, the delay though is not acceptable because it would increase the
> > boot time on some systems by 400%. It should work without the delay
> > aswell.

I agree, adding 2 seconds to boot time wouldn't be very well received.

Our board has several gpio buttons which are checked for a specific press 
configuration at startup, eg, when buttons 1,3 and 4 only are held down, the 
auto boot is delayed.
This is obviously dependent on board hardware, but does make any delay 
optional. 

This is in our init script itself, but could just as easily be coded to check 
before the init script is run. You could set it up as a board installed 
callback...

Cheers,
Marc

[-- Attachment #1.2: Type: text/html, Size: 3756 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      parent reply	other threads:[~2012-05-07  0:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-05 21:26 Krzysztof Halasa
2012-05-06 17:16 ` Sascha Hauer
2012-05-06 17:50   ` Krzysztof Halasa
2012-05-06 18:08     ` Sascha Hauer
2012-05-07  0:14     ` Marc Reilly [this message]

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=201205071014.25217.marc@cpdesign.com.au \
    --to=marc@cpdesign.com.au \
    --cc=barebox@lists.infradead.org \
    --cc=khc@pm.waw.pl \
    /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