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