From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Vagrant Cascadian <vagrant@debian.org>,
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>
Subject: Re: [PATCH v5 8/8] bootstd: Enable BOOTSTD_DEFAULTS by default
Date: Fri, 31 Mar 2023 14:00:01 -0400 [thread overview]
Message-ID: <20230331180001.GA13222@bill-the-cat> (raw)
In-Reply-To: <20230331102559.v5.8.I41a5e66644a895a311889b009116245245c741a5@changeid>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
On Fri, Mar 31, 2023 at 10:26:01AM +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
>
> Exclude boards which have what looks like a custom boot command:
>
> git grep CONFIG_BOOTCOM configs/* |grep -v distro_bootcmd |
> sed -n 's/configs\/\(.*\)_defconfig.*/\1/p'
>
> 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>
I wasn't clear, sorry. What I want to see first is a standalone patch
that disables BOOTSTD on platforms that have their own custom bootcmd,
that is not just a more complex wrapper around distro_bootcmd (those
platforms will require more work to convert, but won't be impacted by
BOOTSTD_DEFAULTS being default). It needs to be on its own so it can be
reviewed. Thanks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-03-31 18:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 21:25 [PATCH v5 1/8] bootstd: Tweak bootflow logic for device tree Simon Glass
2023-03-30 21:25 ` [PATCH v5 2/8] virtio: Ensure PCI is set up first Simon Glass
2023-03-30 21:25 ` [PATCH v5 3/8] bootstd: Support booting EFI where multiple options exist Simon Glass
2023-03-31 18:02 ` Tom Rini
2023-04-01 6:31 ` Simon Glass
2023-04-03 9:56 ` Ilias Apalodimas
2023-04-03 14:17 ` Tom Rini
2023-04-03 16:26 ` Heinrich Schuchardt
2023-04-04 6:09 ` Ilias Apalodimas
2023-04-05 5:28 ` Simon Glass
2023-04-05 14:47 ` Tom Rini
2023-04-05 21:56 ` Mark Kettenis
2023-04-06 5:42 ` Heinrich Schuchardt
2023-04-07 19:38 ` Tom Rini
2023-04-07 18:55 ` Simon Glass
2023-04-07 19:39 ` Tom Rini
2023-04-07 19:44 ` Ilias Apalodimas
2023-04-07 19:56 ` Simon Glass
2023-04-07 19:57 ` Tom Rini
2023-03-30 21:25 ` [PATCH v5 4/8] rockchip: Move to standard boot Simon Glass
2023-03-30 21:25 ` [PATCH v5 5/8] rockchip: Use the same boot_targets for all boards Simon Glass
2023-03-30 21:25 ` [PATCH v5 6/8] bootstd: Show a message sometimes if no bootflows are found Simon Glass
2023-03-30 21:26 ` [PATCH v5 7/8] bootstd: Report missing labels only when asked Simon Glass
2023-03-30 21:26 ` [PATCH v5 8/8] bootstd: Enable BOOTSTD_DEFAULTS by default Simon Glass
2023-03-31 18:00 ` Tom Rini [this message]
2023-04-01 6:31 ` Simon Glass
2023-04-03 14:33 ` Tom Rini
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=20230331180001.GA13222@bill-the-cat \
--to=trini@konsulko.com \
--cc=hl@rock-chips.com \
--cc=jeffy.chen@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=philipp.tomsich@theobroma-systems.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.