From: Wolfgang Wallner <wolfgang.wallner@br-automation.com>
To: Bernhard Messerklinger <bernhard.messerklinger@br-automation.com>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Cc: Hannes Schmelzer <Hannes.Schmelzer@br-automation.com>
Subject: Re: [PATCH 4/5] include: configs: brppt1: Fix commit 0ea4fc4dcf90
Date: Mon, 29 Aug 2022 12:57:50 +0000 [thread overview]
Message-ID: <VI1PR06MB535846A96D5D2D60776356BCCB769@VI1PR06MB5358.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <20220825065404.161821-5-bernhard.messerklinger@br-automation.com>
From: Bernhard Messerklinger <bernhard.messerklinger@br-automation.com>
Sent: Thursday, August 25, 2022 8:54
Subject: [PATCH 4/5] include: configs: brppt1: Fix commit 0ea4fc4dcf90
> Commit 0ea4fc4dcf90 ("board/BuR: invalidate ${dtbaddr} before cfgscr")
> destroys the boot targets b_t30lgcy#0 and b_t30lgcy#1. The reason behind
> this is, that b_t30lgcy#0 and b_t30lgcy#1 both load the for booting
> needed device trees from mmc and the cfgscr script patches those. Because
> of this, cfgscr is not allowed to destroy the previously loaded device
> tree otherwise cfgscr will fail.
> This patch moves the device trees invalidation on warm restart to the
> PREBOOT cmd to fix that issue.
>
> Fixes: 0ea4fc4dcf90 ("board/BuR: invalidate ${dtbaddr} before cfgscr")
> Signed-off-by: Bernhard Messerklinger <bernhard.messerklinger@br-automation.com>
> ---
>
> configs/brppt1_mmc_defconfig | 2 +-
> include/configs/brppt1.h | 1 -
> 2 files changed, 1 insertion(+), 2 deletions(-)
Reviewed-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>
next prev parent reply other threads:[~2022-08-29 12:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 6:53 [PATCH 0/5] Fix, update and cleanup brppt1 board Bernhard Messerklinger
2022-08-25 6:54 ` [PATCH 1/5] brppt1: Remove unused board variants Bernhard Messerklinger
2022-08-29 12:53 ` Wolfgang Wallner
2022-09-15 21:54 ` Tom Rini
2022-08-25 6:54 ` [PATCH 2/5] brppt1: Fix SPL boot stage Bernhard Messerklinger
2022-08-29 12:55 ` Wolfgang Wallner
2022-09-15 21:54 ` Tom Rini
2022-08-25 6:54 ` [PATCH 3/5] brppt1: Cleanup device tree Bernhard Messerklinger
2022-08-29 12:56 ` Wolfgang Wallner
2022-09-15 21:54 ` Tom Rini
2022-08-25 6:54 ` [PATCH 4/5] include: configs: brppt1: Fix commit 0ea4fc4dcf90 Bernhard Messerklinger
2022-08-29 12:57 ` Wolfgang Wallner [this message]
2022-09-15 21:54 ` Tom Rini
2022-08-25 6:54 ` [PATCH 5/5] brppt1: Update environment to support new boot concept Bernhard Messerklinger
2022-08-29 12:58 ` Wolfgang Wallner
2022-09-15 21:54 ` Tom Rini
2022-08-25 7:01 ` [PATCH 0/5] Fix, update and cleanup brppt1 board Wolfgang Wallner
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=VI1PR06MB535846A96D5D2D60776356BCCB769@VI1PR06MB5358.eurprd06.prod.outlook.com \
--to=wolfgang.wallner@br-automation.com \
--cc=Hannes.Schmelzer@br-automation.com \
--cc=bernhard.messerklinger@br-automation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).