From: "Lothar Waßmann" <LW@KARO-electronics.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 3/4] arm: imx: m53evk: remove usage of mx53_dram_size
Date: Tue, 19 Dec 2017 10:59:38 +0100 [thread overview]
Message-ID: <20171219105938.4538996f@karo-electronics.de> (raw)
In-Reply-To: <4862545d-5fe3-d32e-95cd-ef0303892b70@denx.de>
Hi,
On Mon, 18 Dec 2017 10:17:03 +0100 Marek Vasut wrote:
> On 12/18/2017 10:02 AM, linux-kernel-dev at beckhoff.com wrote:
> > From: Patrick Bruenn <p.bruenn@beckhoff.com>
> >
> > Static variables are not available during board_init_f().
>
> They are, since the board runs from RAM at that point already.
>
That's not the point. Zero-initialized variables (static or not) are
located in the .bss section, which is overlayed by the .rel.dyn
section. Thus writing to such a variable before relocation will trash
the relocation data.
Lothar Waßmann
next prev parent reply other threads:[~2017-12-19 9:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 9:02 [U-Boot] [PATCH v2 0/4] arm: imx53: remove usage of mx53_dram_size linux-kernel-dev at beckhoff.com
2017-12-18 9:02 ` [U-Boot] [PATCH v2 1/4] arm: imx: cx9020: " linux-kernel-dev at beckhoff.com
2017-12-18 9:02 ` [U-Boot] [PATCH v2 2/4] arm: imx: cx9020: move dram init into common place linux-kernel-dev at beckhoff.com
2017-12-18 9:02 ` [U-Boot] [PATCH v2 3/4] arm: imx: m53evk: remove usage of mx53_dram_size linux-kernel-dev at beckhoff.com
2017-12-18 9:17 ` Marek Vasut
2017-12-18 10:47 ` Patrick Brünn
2017-12-18 10:57 ` Marek Vasut
2017-12-18 11:40 ` Patrick Brünn
2017-12-18 11:52 ` Marek Vasut
2017-12-18 12:16 ` Patrick Brünn
2017-12-18 12:29 ` Marek Vasut
2017-12-19 4:28 ` Patrick Brünn
2017-12-19 11:18 ` Marek Vasut
2017-12-19 7:48 ` Patrick Brünn
2017-12-19 9:59 ` Lothar Waßmann [this message]
2017-12-18 9:02 ` [U-Boot] [PATCH v2 4/4] arm: imx: mx53loco: " linux-kernel-dev at beckhoff.com
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=20171219105938.4538996f@karo-electronics.de \
--to=lw@karo-electronics.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