From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Frank Wunderlich <frank-w@public-files.de>
Cc: u-boot@lists.denx.de
Subject: Re: distro_boot vs. env-based bootmenu
Date: Sat, 1 Jul 2023 11:08:01 +0900 [thread overview]
Message-ID: <ZJ-KgdjSsXhU78_e@laputa> (raw)
In-Reply-To: <trinity-55cac001-7a03-4c1d-b48f-c48a32d36ac2-1681291343429@3c-app-gmx-bap50>
Hi,
On Wed, Apr 12, 2023 at 11:22:23AM +0200, Frank Wunderlich wrote:
> Hi,
>
> i try to move from distro-boot (extlinux-config files) to an env-based bootmenu (builtin-environment) for
> my bananapi r2pro.
>
> basicly it works, but i see more bootmenu-entries than i have defined in my environment
>
> *** U-Boot Boot Menu ***
>
> 1. Boot from SD/EMMC.
> mmc 1:2
> mmc 1:3
> mmc 1:4
> U-Boot consoleHit any key to stop autoboot: 2
>
> i have only defined one botmenu-entry (first one in uEnv_r2pro.txt)
>
> bootmenu_0=1. Boot from SD/EMMC.=run newboot
> bootmenu_default=0
>
> i guess the 3 mmc 1:x entries are part from distro-boot. i see a series from simon where he drops
> distroboot for rockchip-boards.
Probably they came from UEFI's removable media support, specifically
commit c606c0059f7f
Author: Masahisa Kojima <masahisa.kojima@linaro.org>
Date: Thu Apr 28 17:09:42 2022 +0900
bootmenu: add UEFI boot entry into bootmenu
> https://patchwork.ozlabs.org/project/uboot/patch/20230409084454.v9.8.I4cf7708a1ba953b9abd81375d93af34665c7b251@changeid/
>
> can anyone explain me where i can disable the mmc 1:x entries? i wanted to leave distro_boot as
> fallback but it seems this is not possible.
Try to disable either CONFIG_CMD_EFICONFIG or CONFIG_CMD_BOOTEFI_BOOTMGR,
even CONFIG_EFI_LOADER if you don't need UEFI subsystem at all.
-Takahiro Akashi
> maybe i have to disable these?
>
> BOOTMETH_DISTRO [=y]
> DISTRO_DEFAULTS [=y]
>
> can i keep distro-boot (seems to works with env too, but overridden by my builtin env) somehow and drop the mmc-entries from my bootmenu?
>
> any idea why i have no linebreak after u-Boot console?
>
> i use u-boot 2023.04 my source for this conversion/tests is there:
> https://github.com/frank-w/u-boot/tree/2023-04-bpi-r2pro
> using modified configs/evb-rk3568_defconfig
>
> regards Frank
next prev parent reply other threads:[~2023-07-01 2:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 9:22 distro_boot vs. env-based bootmenu Frank Wunderlich
[not found] ` <9A8289C2-7C4C-4BD5-8339-68B2B4CFC145@public-files.de>
2023-04-24 19:44 ` Simon Glass
2023-04-24 21:22 ` Frank Wunderlich
2023-04-26 1:03 ` Simon Glass
2023-04-30 13:25 ` Aw: " Frank Wunderlich
2023-04-30 17:40 ` Jonas Karlman
2023-06-30 17:51 ` Aw: " Frank Wunderlich
2023-07-01 8:12 ` Jonas Karlman
2023-07-01 9:16 ` Aw: " Frank Wunderlich
2023-07-01 2:08 ` AKASHI Takahiro [this message]
2023-07-01 9:09 ` Aw: " Frank Wunderlich
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=ZJ-KgdjSsXhU78_e@laputa \
--to=takahiro.akashi@linaro.org \
--cc=frank-w@public-files.de \
--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