From: Vagrant Cascadian <vagrant@debian.org>
To: Simon Glass <sjg@chromium.org>,
U-Boot Mailing List <u-boot@lists.denx.de>
Cc: huang lin <hl@rock-chips.com>,
Jeffy Chen <jeffy.chen@rock-chips.com>,
Simon Glass <sjg@chromium.org>,
Kever Yang <kever.yang@rock-chips.com>,
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>,
Tom Rini <trini@konsulko.com>,
Philippe Reynes <philippe.reynes@softathome.com>
Subject: Re: [PATCH 3/3] bootstd: Enable BOOTSTD_DEFAULTS by default
Date: Tue, 21 Feb 2023 15:29:44 -0800 [thread overview]
Message-ID: <878rgqr40n.fsf@contorta> (raw)
In-Reply-To: <20230221193920.3546499-3-sjg@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
On 2023-02-21, Simon Glass wrote:
> This is needed to enable the boot command used to start standard boot.
> Enable it by default. This brings in quite a few features, mostly in
> common with DISTRO_DEFAULTS
Works for booting rockpro64-rk3399, thanks!
Tested-by: Vagrant Cascadian <vagrant@debian.org>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> boot/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/boot/Kconfig b/boot/Kconfig
> index 5f491625c82..8759b863b00 100644
> --- a/boot/Kconfig
> +++ b/boot/Kconfig
> @@ -409,6 +409,7 @@ if BOOTSTD
> config BOOTSTD_DEFAULTS
> bool "Select some common defaults for standard boot"
> depends on BOOTSTD
> + default y
> imply USE_BOOTCOMMAND
> # Bring in some defaults which are generally needed. Boards can drop
> # these as needed to save code space. Bootstd does not generally require
> --
> 2.39.2.637.g21b0678d19-goog
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2023-02-21 23:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 19:39 [PATCH 1/3] rockchip: Drop bootstage stash in TPL and SPL Simon Glass
2023-02-21 19:39 ` [PATCH 2/3] rockchip: Disable DISTRO_DEFAULTS for rockpro64 Simon Glass
2023-02-21 23:30 ` Vagrant Cascadian
2023-02-22 18:19 ` Vagrant Cascadian
2023-02-22 18:24 ` Tom Rini
2023-02-22 18:56 ` Jonas Karlman
2023-02-22 18:58 ` Simon Glass
2023-02-22 19:01 ` Tom Rini
2023-02-22 19:03 ` Simon Glass
2023-02-22 19:15 ` Tom Rini
2023-03-16 11:01 ` Peter Robinson
2023-03-16 18:17 ` Tom Rini
2023-03-17 5:25 ` Simon Glass
2023-02-21 19:39 ` [PATCH 3/3] bootstd: Enable BOOTSTD_DEFAULTS by default Simon Glass
2023-02-21 23:29 ` Vagrant Cascadian [this message]
2023-02-21 23:28 ` [PATCH 1/3] rockchip: Drop bootstage stash in TPL and SPL Vagrant Cascadian
2023-02-22 14:47 ` Quentin Schulz
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=878rgqr40n.fsf@contorta \
--to=vagrant@debian.org \
--cc=hl@rock-chips.com \
--cc=jeffy.chen@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=philipp.tomsich@theobroma-systems.com \
--cc=philippe.reynes@softathome.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.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