From: Vagrant Cascadian <vagrant@debian.org>
To: u-boot@lists.denx.de
Subject: [PATCH] configs: add PineTab defconfig
Date: Sun, 07 Mar 2021 12:34:14 -0800 [thread overview]
Message-ID: <87eegqsny1.fsf@yucca> (raw)
In-Reply-To: <YETM5Nx10Fi8uwN2@nicolasthinkpad>
On 2021-03-07, Nicolas Boulenguez wrote:
> From: Arnaud Ferraris <arnaud.ferraris@collabora.com>
>
> The PineTab device-tree is already in u-boot, this commit adds the corresponding
> defconfig, based on pinephone_defconfig.
>
> Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>
...
> --- /dev/null
> +++ b/configs/pinetab_defconfig
...
> +CONFIG_BOOTDELAY=0
Setting bootdelay to 0 it almost impossible to debug issues in a running
u-boot.
The default of 2 seconds that distro_bootcmd uses tries to strike a
balance between not slowing the boot down too much while still being
reasonably able to get into a u-boot shell when something goes wrong.
Individual users or vendors can set this value as they see fit, but this
doesn't seem like a good default for mainline u-boot, at least to me.
live well,
vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210307/db8a451a/attachment.sig>
next prev parent reply other threads:[~2021-03-07 20:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 12:53 [PATCH] configs: add PineTab defconfig Nicolas Boulenguez
2021-03-07 13:58 ` Peter Robinson
2021-03-07 20:34 ` Vagrant Cascadian [this message]
2021-03-07 22:15 ` Andre Przywara
2021-03-08 0:12 ` Andre Przywara
2021-03-08 0:13 ` Icenowy Zheng
2021-03-13 15:32 ` Arnaud Ferraris
-- strict thread matches above, loose matches on Subject: below --
2021-09-06 21:06 Arnaud Ferraris
2021-09-06 23:47 ` Andre Przywara
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=87eegqsny1.fsf@yucca \
--to=vagrant@debian.org \
--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