diff options
author | Simon Glass <sjg@chromium.org> | 2023-05-06 08:27:09 -0600 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2023-05-13 09:52:32 -0400 |
commit | d8d40bc392d1ce60660e479a73970666e6a8a7be (patch) | |
tree | a3c9f6adf86620bc867c33c766af65e8a4786384 /cmd/bootflow.c | |
parent | ab16a3d904e440a6f55aedf7a6c32b9d70168b50 (diff) |
bootstd: Correct default boot command
The patch to relax flag requirements was not accepted[1], so we still have
to have separate bootcommands depending on CMD_BOOTFLOW_FULL.
The previous attempt at this did not work, since it used the wrong name
for the options.
Fix this and change the message to mention BOOTSTD_FULL since this affects
not just the flags, but all functionality, so is more likely what the user
wants.
Drop the useless condition on CMD_BOOTFLOW_FULL while we are here.
[1] https://patchwork.ozlabs.org/project/uboot/patch/20230329071655.1959513-2-sjg@chromium.org/
Signed-off-by: Simon Glass <sjg@chromium.org>
Fixes: a91492b6e9c ("bootstd: Provide a default command")
Diffstat (limited to 'cmd/bootflow.c')
-rw-r--r-- | cmd/bootflow.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/cmd/bootflow.c b/cmd/bootflow.c index cfe3422698..6cc58e48c7 100644 --- a/cmd/bootflow.c +++ b/cmd/bootflow.c @@ -125,7 +125,7 @@ static int do_bootflow_scan(struct cmd_tbl *cmdtp, int flag, int argc, dev = std->cur_bootdev; } else { if (has_args) { - printf("Flags not supported: enable CONFIG_BOOTFLOW_FULL\n"); + printf("Flags not supported: enable CONFIG_BOOTSTD_FULL\n"); return CMD_RET_USAGE; } boot = true; |