All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
	huang lin <hl@rock-chips.com>,
	Jeffy Chen <jeffy.chen@rock-chips.com>,
	Kever Yang <kever.yang@rock-chips.com>,
	Philipp Tomsich <philipp.tomsich@theobroma-systems.com>,
	Vagrant Cascadian <vagrant@debian.org>,
	"Albert ARIBAUD (3ADEV)" <albert.aribaud@3adev.fr>,
	Eugen Hristev <eugen.hristev@collabora.com>,
	Greg Gallagher <greg@embeddedgreg.com>,
	Heiko Schocher <hs@denx.de>, Michal Simek <michal.simek@amd.com>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	Philippe Reynes <philippe.reynes@softathome.com>,
	Tony Dinh <mibodhi@gmail.com>
Subject: Re: [PATCH v4 1/4] bootstd: Enable BOOTSTD_DEFAULTS by default
Date: Wed, 29 Mar 2023 10:15:24 -0400	[thread overview]
Message-ID: <20230329141524.GB6083@bill-the-cat> (raw)
In-Reply-To: <20230329201631.v4.1.I41a5e66644a895a311889b009116245245c741a5@changeid>

[-- Attachment #1: Type: text/plain, Size: 2594 bytes --]

On Wed, Mar 29, 2023 at 08:16:36PM +1300, 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
> 
> Disable this option for boards which don't have enough space.
> 
> Disable CONFIG_ENV_VARS_UBOOT_CONFIG for some Xilinx boards which have
> a very small environment. Disable BOOTSTD_DEFAULTS for smartweb since
> it is too close to its limit.
> 
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
> 
> Changes in v4:
> - Rebase to -next
> 
>  boot/Kconfig                                 | 1 +
>  configs/bk4r1_defconfig                      | 1 +
>  configs/sama5d27_giantboard_defconfig        | 1 +
>  configs/sama5d27_som1_ek_mmc1_defconfig      | 1 +
>  configs/sama5d27_som1_ek_mmc_defconfig       | 1 +
>  configs/sama5d27_som1_ek_qspiflash_defconfig | 1 +
>  configs/sama5d27_wlsom1_ek_mmc_defconfig     | 1 +
>  configs/sama5d2_icp_mmc_defconfig            | 1 +
>  configs/sama5d2_xplained_emmc_defconfig      | 1 +
>  configs/sama5d2_xplained_mmc_defconfig       | 1 +
>  configs/sama5d2_xplained_qspiflash_defconfig | 1 +
>  configs/sheevaplug_defconfig                 | 1 +
>  configs/smartweb_defconfig                   | 1 +
>  configs/taurus_defconfig                     | 1 +
>  configs/tools-only_defconfig                 | 2 +-
>  configs/xilinx_versal_mini_emmc0_defconfig   | 1 +
>  configs/xilinx_versal_mini_emmc1_defconfig   | 1 +
>  configs/xilinx_zynqmp_mini_emmc0_defconfig   | 2 +-
>  configs/xilinx_zynqmp_mini_emmc1_defconfig   | 2 +-
>  19 files changed, 19 insertions(+), 3 deletions(-)
> 
> diff --git a/boot/Kconfig b/boot/Kconfig
> index d95a2a702665..61ebc2750154 100644
> --- a/boot/Kconfig
> +++ b/boot/Kconfig
> @@ -435,6 +435,7 @@ if BOOTSTD
>  config BOOTSTD_DEFAULTS
>  	bool "Select some common defaults for standard boot"
>  	depends on BOOTSTD
> +	default y
>  	imply USE_BOOTCOMMAND
>  	select BOOT_DEFAULTS

I intentionally did not do this before, and I don't think it's right,
certainly right now. This fixes some boards (such as some mediatek SoCs
for example) that have boostd, have no bootcmd in environment and so
don't autoboot before bootstd, but do now. But it also bloats all of the
platforms that don't want bootstd because they have a real bootcmd
that's not some variant of "prepare to and then run distro_bootcmd".
Those should get bootstd disabled, first. Then we can evaluate if this
ends up being the right option.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      parent reply	other threads:[~2023-03-29 14:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29  7:16 [PATCH v4 1/4] bootstd: Enable BOOTSTD_DEFAULTS by default Simon Glass
2023-03-29  7:16 ` [PATCH v4 2/4] rockchip: Move to standard boot Simon Glass
2023-03-29  7:16 ` [PATCH v4 3/4] bootstd: Relax the argument requirements for bootflow scan Simon Glass
2023-03-29 14:17   ` Tom Rini
2023-03-29  7:16 ` [PATCH v4 4/4] rockchip: Use the same boot_targets for all boards Simon Glass
2023-03-29 14:19   ` Tom Rini
2023-03-29  7:41 ` [PATCH v4 1/4] bootstd: Enable BOOTSTD_DEFAULTS by default Michal Simek
2023-03-29  7:55 ` Nicolas Ferre
2023-03-30  9:17   ` Simon Glass
2023-03-30 14:09     ` Tom Rini
2023-03-29 14:15 ` Tom Rini [this message]

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=20230329141524.GB6083@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=albert.aribaud@3adev.fr \
    --cc=eugen.hristev@collabora.com \
    --cc=greg@embeddedgreg.com \
    --cc=hl@rock-chips.com \
    --cc=hs@denx.de \
    --cc=jeffy.chen@rock-chips.com \
    --cc=kever.yang@rock-chips.com \
    --cc=mibodhi@gmail.com \
    --cc=michal.simek@amd.com \
    --cc=nicolas.ferre@microchip.com \
    --cc=philipp.tomsich@theobroma-systems.com \
    --cc=philippe.reynes@softathome.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --cc=vagrant@debian.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.