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:
Le Fri, 12 Dec 2014 20:16:19 +0200, picmaster@mail.bg a écrit :
From: Nikolay Dimitrov picmaster@mail.bg
Signed-off-by: Nikolay Dimitrov picmaster@mail.bg
include/configs/embestmx6boards.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/configs/embestmx6boards.h b/include/configs/embestmx6boards.h index 185edbe..28099a8 100644 --- a/include/configs/embestmx6boards.h +++ b/include/configs/embestmx6boards.h @@ -120,7 +120,7 @@ #define CONFIG_CMD_SETEXPR #undef CONFIG_CMD_IMLS
-#define CONFIG_BOOTDELAY 1 +#define CONFIG_BOOTDELAY 3
#define CONFIG_LOADADDR 0x12000000 #define CONFIG_SYS_TEXT_BASE 0x17800000
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.
Eric