From: Tom Rini <trini@konsulko.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: Fabio Estevam <festevam@gmail.com>,
"Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
Simon Glass <sjg@chromium.org>, "sbabic@denx.de" <sbabic@denx.de>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
dl-uboot-imx <uboot-imx@nxp.com>,
Gilles Talis <gilles.talis@nxp.com>
Subject: Re: [PATCH] cpu: imx8_cpu: Avoid revision to corrupt device tree
Date: Wed, 16 Oct 2024 12:45:39 -0600 [thread overview]
Message-ID: <20241016184539.GF4959@bill-the-cat> (raw)
In-Reply-To: <PAXPR04MB845979AC895A90D969E5F216887A2@PAXPR04MB8459.eurprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 597 bytes --]
On Sat, Oct 12, 2024 at 12:16:14AM +0000, Peng Fan wrote:
> > Subject: Re: [PATCH] cpu: imx8_cpu: Avoid revision to corrupt device
> > tree
> >
> > > Why isn't this padding and alignment with the BSS being taken care
> > of
> > > in either the linker script or the binman dts?
>
> Sorry, I am not sure what you mean.
I mean, why are things placed in this position to start with? Why is the
device tree not already in a place where we aren't smashing it at run
time? Is this a problem of the alignment / placement of items in a blob?
A runtime placement problem? What?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-10-16 18:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 10:58 [PATCH] cpu: imx8_cpu: Avoid revision to corrupt device tree Peng Fan (OSS)
2024-10-11 16:56 ` Tom Rini
2024-10-11 18:06 ` Fabio Estevam
2024-10-12 0:16 ` Peng Fan
2024-10-16 18:45 ` Tom Rini [this message]
2024-10-17 1:10 ` Peng Fan
2024-10-17 3:05 ` Tom Rini
2024-10-17 3:07 ` Peng Fan
2024-10-16 18:22 ` Fabio Estevam
2024-10-17 3:11 ` Tom Rini
2024-10-17 3:14 ` Peng Fan
2024-10-17 3:45 ` Tom Rini
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=20241016184539.GF4959@bill-the-cat \
--to=trini@konsulko.com \
--cc=festevam@gmail.com \
--cc=gilles.talis@nxp.com \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=sbabic@denx.de \
--cc=sjg@chromium.org \
--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 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.