public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Nikolay Dimitrov <picmaster@mail.bg>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] embestmx6boards: Increase boot delay to 3s
Date: Sun, 14 Dec 2014 22:56:21 +0200	[thread overview]
Message-ID: <548DF975.9050702@mail.bg> (raw)
In-Reply-To: <548DA446.7@gmail.com>

Hi Iain,

On 12/14/2014 04:52 PM, Iain Paton wrote:
> 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.

I have 2 things to say about this:
1. In theory we can also question why the initial boot delay was 
selected to be 1s.
2. You imply that the "users" want ultra-fast boot times for riotboard. 
Being myself one of the riotboard users, I can assure you that such 
generalization is excessive.

> 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 is a good idea in general, I don't mind it.

> This also leads to a slightly less unreasonable increase in bootdelay to 2s
> from config_distro_defaults.h

Well, this is again subjective - we can always argue that 2s is both too 
long and too short for selected use cases, so I don't understand the 
qualification "less unreasonable".

In summary - I won't carry a war for this change, as it doesn't worth 
it. I just tried to contribute a tiny bit of improvement to the already 
excellent work of Eric, so we can have a silk-smooth out-of-the-box 
U-Boot user experience, and I'm doing this as an actual riotboard user. 
That's all.

Thanks for sharing your viewpoint.

Kind regards,
Nikolay

  parent reply	other threads:[~2014-12-14 20:56 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
2014-12-14 15:20         ` Michael Trimarchi
2014-12-14 20:56         ` Nikolay Dimitrov [this message]
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=548DF975.9050702@mail.bg \
    --to=picmaster@mail.bg \
    --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