public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Lothar Waßmann" <LW@KARO-electronics.de>
To: Peng Fan <peng.fan@nxp.com>
Cc: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
	"festevam@gmail.com" <festevam@gmail.com>,
	"sbabic@denx.de" <sbabic@denx.de>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
	"trini@konsulko.com" <trini@konsulko.com>,
	dl-uboot-imx <uboot-imx@nxp.com>
Subject: Re: [PATCH V2] cpu: imx8_cpu: Avoid revision to corrupt device tree
Date: Thu, 17 Oct 2024 13:25:14 +0200	[thread overview]
Message-ID: <20241017132514.26807534@karo-electronics.de> (raw)
In-Reply-To: <PAXPR04MB84597D20308880039DE8817088472@PAXPR04MB8459.eurprd04.prod.outlook.com>

Hi,

On Thu, 17 Oct 2024 09:21:54 +0000 Peng Fan wrote:
> > Subject: Re: [PATCH V2] cpu: imx8_cpu: Avoid revision to corrupt
> > device tree
> > 
> > Hi,
> > 
> > On Thu, 17 Oct 2024 16:12:36 +0800 Peng Fan (OSS) wrote:  
> > > From: Peng Fan <peng.fan@nxp.com>
> > >
> > > U-Boot device tree is padded just after U-Boot proper.
> > > After the whole stuff loaded to DRAM space, the device tree area is
> > > conflict with BSS region before U-Boot relocation.
> > >
> > > So any write to BSS area before reloc_fdt will corrupt the device
> > > tree. Without the fix, there is issue that "binman_init failed:-2" on
> > > i.MX8MP-EVK board.
> > >  
> > Placing the 'revision' variable into the 'data' section would achieve the
> > same goal without any further code change:
> > static char revision[4] __section(".data");  
> 
> This was not welcomed,
> https://lore.kernel.org/all/20241017034507.GJ4959@bill-the-cat/
> 
Thanks, good to know.



Lothar Waßmann
-- 
___________________________________________________________

Ka-Ro electronics GmbH | Pascalstraße 22 | D - 52076 Aachen
Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10
Geschäftsführer: Matthias Kaussen
Handelsregistereintrag: Amtsgericht Aachen, HRB 4996

www.karo-electronics.de | info@karo-electronics.de
___________________________________________________________

  reply	other threads:[~2024-10-17 11:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17  8:12 [PATCH V2] cpu: imx8_cpu: Avoid revision to corrupt device tree Peng Fan (OSS)
2024-10-17  9:19 ` Lothar Waßmann
2024-10-17  9:21   ` Peng Fan
2024-10-17 11:25     ` Lothar Waßmann [this message]
2024-10-17 12:50 ` Fabio Estevam
2024-10-17 14:25   ` Tom Rini
2024-10-18  1:02   ` Peng Fan

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=20241017132514.26807534@karo-electronics.de \
    --to=lw@karo-electronics.de \
    --cc=festevam@gmail.com \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=sbabic@denx.de \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=uboot-imx@nxp.com \
    /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