From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>,
Michael Tretter <m.tretter@pengutronix.de>
Cc: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Subject: Re: [PATCH 0/2] arm: socfpga: agilex5: fix stack in entry function
Date: Wed, 13 May 2026 16:07:24 +0200 [thread overview]
Message-ID: <177868124416.290474.16982266272041035324.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260513-socfpga-agilex5-entry-v1-0-090758694c88@pengutronix.de>
On Wed, 13 May 2026 14:22:21 +0200, Michael Tretter wrote:
> The entry function for the Arrow AXE5 Eagle board places the stack at
> the end of the OCRAM. However, the board firmware uses the same page for
> handoff data for barebox, which is read after barebox is already
> running. This may cause data corruption if the stack grows into the
> handoff data.
>
> Patch 1 fixes the stack location for the Arrow AXE5 Eagle board to avoid
> corrupting the handoff data.
>
> [...]
Applied, thanks!
[1/2] arm: socfpga: axe5-eagle: fix stack location
https://git.pengutronix.de/cgit/barebox/commit/?id=f566c8ecc9af (link may not be stable)
[2/2] arm: socfpga: agilex5: add helper for entry function
https://git.pengutronix.de/cgit/barebox/commit/?id=d5840df6ff29 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-05-13 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 12:22 Michael Tretter
2026-05-13 12:22 ` [PATCH 1/2] arm: socfpga: axe5-eagle: fix stack location Michael Tretter
2026-05-13 12:22 ` [PATCH 2/2] arm: socfpga: agilex5: add helper for entry function Michael Tretter
2026-05-13 14:07 ` Sascha Hauer [this message]
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=177868124416.290474.16982266272041035324.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.tretter@pengutronix.de \
--cc=s.trumtrar@pengutronix.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