From: Sascha Hauer <s.hauer@pengutronix.de>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: barebox@lists.infradead.org
Subject: Re: RFC: Force a 2s delay on startup to allow bypassing /dev/env0.
Date: Sun, 6 May 2012 20:08:35 +0200 [thread overview]
Message-ID: <20120506180835.GY4141@pengutronix.de> (raw)
In-Reply-To: <m3bom1yzah.fsf@intrepid.localdomain>
On Sun, May 06, 2012 at 07:50:14PM +0200, 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.
>
> Actually the delay is a bit problematic for me as well.
> Unfortunately the boot code has to initialize the serial port, clearing
> the incoming FIFO. This means I can't "queue" the ^C character, barebox
> has to wait for it (maybe not for the whole 2 seconds).
>
> Or am I mistaken?
On my boards I can still interrupt even with autoboot_timeout=0. Have
you tried it? It may be a bit dependent on the UART driver, I don't
know.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-05-06 18:08 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 [this message]
2012-05-07 0:14 ` Marc Reilly
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=20120506180835.GY4141@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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