From: Iain Paton <ipaton0@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] embestmx6boards: Increase boot delay to 3s
Date: Sun, 14 Dec 2014 14:52:54 +0000 [thread overview]
Message-ID: <548DA446.7@gmail.com> (raw)
In-Reply-To: <20141213180310.76512e06@e6520eb.localdomain>
On 13/12/14 17:03, Eric B?nard wrote:
> Hi Nikolay,
>
> Le Sat, 13 Dec 2014 18:05:15 +0200,
> Nikolay Dimitrov <picmaster@mail.bg> a ?crit :
>> On 12/13/2014 04:16 PM, Eric B?nard wrote:
>>> This will increase the boot time by 2 seconds : why is that needed ?
>>
>> Thanks for commenting. My intent is to give by default a reasonable
>> time for the end-user to react and break the boot-sequence if needed
>> (and avoid the nasty racing against the clock for this precious
>> key-press).
>>
>> My motivation for this is that I see RIoTboard/MarsBoard mostly as
>> boards that people can use for experimentation/prototyping, and not as
>> a finished end-product, thus my thinking that the slightly increased
>> boot-time won't be a critical issue for such applications. Still
>> everyone can change the delay at will if they want to optimize the boot.
>>
>> Other hobby boards also have similarly handy boot-timings, like
>> Wandboard (5s), Novena (5s), Udoo (3s).
>>
> OK seems reasonable.
I disagree. I think it's an unnecessary, unneeded, unreasonable tripling
of the boot time.
Rather than leaving people to patch out this unwanted behaviour, I'd suggest
promoting CONFIG_BOOTDELAY into a Kconfig option, leaving the default as-is.
This allows the people who want it to configure it easily.
In any case the rationale given, that the Riotboard is a dev board used for
experimenting, doesn't imply a change like this one. It implies a conversion
to use config_distro_bootcmd.h like the patches I've just posted.
This also leads to a slightly less unreasonable increase in bootdelay to 2s
from config_distro_defaults.h
Using config_distro_bootcmd also means that we can largely ignore the u-boot
shell altogether and just use extlinux.conf instead
next prev parent reply other threads:[~2014-12-14 14:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 18:16 [U-Boot] [PATCH] embestmx6boards: Increase boot delay to 3s picmaster at mail.bg
2014-12-13 14:16 ` Eric Bénard
2014-12-13 14:32 ` Michael Trimarchi
2014-12-13 16:07 ` Nikolay Dimitrov
2014-12-13 16:14 ` Michael Trimarchi
2014-12-13 16:25 ` Nikolay Dimitrov
2014-12-13 16:05 ` Nikolay Dimitrov
2014-12-13 17:03 ` Eric Bénard
2014-12-14 14:52 ` Iain Paton [this message]
2014-12-14 15:20 ` Michael Trimarchi
2014-12-14 20:56 ` Nikolay Dimitrov
2014-12-14 21:14 ` Eric Bénard
2014-12-14 23:07 ` Iain Paton
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=548DA446.7@gmail.com \
--to=ipaton0@gmail.com \
--cc=u-boot@lists.denx.de \
/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