From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
Tom Rini <trini@konsulko.com>
Cc: Simon Glass <sjg@chromium.org>, Marek Vasut <marex@denx.de>,
Peter Robinson <pbrobinson@gmail.com>,
Mattijs Korpershoek <mkorpershoek@kernel.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Quentin Schulz <quentin.schulz@cherry.de>,
u-boot@lists.denx.de,
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Subject: Re: [PATCH 1/1] boot: let BOOTSTAGE_RECORD_COUNT default to 50
Date: Wed, 30 Apr 2025 10:55:57 +0200 [thread overview]
Message-ID: <87y0viqb8i.fsf@kernel.org> (raw)
In-Reply-To: <20250430073405.14396-1-heinrich.schuchardt@canonical.com>
Hi Heinrich,
Thank you for the patch.
On mer., avril 30, 2025 at 09:34, Heinrich Schuchardt <heinrich.schuchardt@canonical.com> wrote:
> BOOTSTAGE_RECORD_COUNT=30 is too small to record booting a FIT image
> with EFI kernel, initrd, dtb as seen on the StarFive VisionFive 2
> board.
>
> Increase the default for BOOTSTAGE_RECORD_COUNT to 50.
>
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Reviewed-by: Mattijs Korpershoek <mkorpershoek@kernel.org>
> ---
> boot/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/boot/Kconfig b/boot/Kconfig
> index fb37d912bc9..2456856a572 100644
> --- a/boot/Kconfig
> +++ b/boot/Kconfig
> @@ -1170,7 +1170,7 @@ config BOOTSTAGE_REPORT
> config BOOTSTAGE_RECORD_COUNT
> int "Number of boot stage records to store"
> depends on BOOTSTAGE
> - default 30
> + default 50
> help
> This is the size of the bootstage record list and is the maximum
> number of bootstage records that can be recorded.
> --
> 2.48.1
next prev parent reply other threads:[~2025-04-30 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 7:34 [PATCH 1/1] boot: let BOOTSTAGE_RECORD_COUNT default to 50 Heinrich Schuchardt
2025-04-30 8:32 ` Heinrich Schuchardt
2025-04-30 13:54 ` Simon Glass
2025-04-30 8:55 ` Mattijs Korpershoek [this message]
2025-04-30 14:19 ` Ilias Apalodimas
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=87y0viqb8i.fsf@kernel.org \
--to=mkorpershoek@kernel.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=ilias.apalodimas@linaro.org \
--cc=marex@denx.de \
--cc=pbrobinson@gmail.com \
--cc=quentin.schulz@cherry.de \
--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 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.