From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Brandon Maier via buildroot <buildroot@buildroot.org>
Cc: Maeva Manuel <maeva.manuel@oss.nxp.com>,
Gilles Talis <gilles.talis@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
Stephane Viau <stephane.viau@oss.nxp.com>,
Brandon Maier <brandon.maier@collins.com>
Subject: Re: [Buildroot] [PATCH 1/4] board/freescale: fix arm-trusted-firmware for binutils 2.39+
Date: Sat, 30 Sep 2023 17:20:24 +0200 [thread overview]
Message-ID: <20230930172024.5aaf0df6@windsurf> (raw)
In-Reply-To: <20230921215633.34828-1-brandon.maier@collins.com>
On Thu, 21 Sep 2023 21:56:30 +0000
Brandon Maier via buildroot <buildroot@buildroot.org> wrote:
> The NXP arm-trusted-firmware forks use an older version of ATF that will
> error with "LOAD segment with RWX permissions". Similar patches are
> present in boot/arm-trusted-firmware/ for older ATF versions.
>
> Signed-off-by: Brandon Maier <brandon.maier@collins.com>
> ---
> ...dd-support-for-new-binutils-versions.patch | 61 +++++++++++++++++++
> configs/freescale_imx8mmevk_defconfig | 1 +
> configs/freescale_imx8mnevk_defconfig | 1 +
> configs/freescale_imx8mpevk_defconfig | 1 +
> configs/freescale_imx8mqevk_defconfig | 1 +
> configs/freescale_imx8qmmek_defconfig | 1 +
> configs/freescale_imx8qxpmek_defconfig | 1 +
> configs/ls1028ardb_defconfig | 3 +
> 8 files changed, 70 insertions(+)
> create mode 100644 board/freescale/common/patches/arm-trusted-firmware/0001-feat-build-add-support-for-new-binutils-versions.patch
Applied to master after references to the Gitlab CI failures that are
fixed by this change. If you have the boards at hand, it would be even
nicer to upgrade to newer BSP component versions. Perhaps this is
something that Maeva, Stephane or Gilles can help with?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-30 15:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 21:56 [Buildroot] [PATCH 1/4] board/freescale: fix arm-trusted-firmware for binutils 2.39+ Brandon Maier via buildroot
2023-09-21 21:56 ` [Buildroot] [PATCH 2/4] board/freescale: fix imx arm-trusted-firmware for GCC12 Brandon Maier via buildroot
2023-09-30 15:20 ` Thomas Petazzoni via buildroot
2023-10-13 6:03 ` Peter Korsgaard
2023-09-21 21:56 ` [Buildroot] [PATCH 3/4] package/qoriq-fm-ucode: add package for QorIQ FMan microcode Brandon Maier via buildroot
2023-09-30 15:58 ` Thomas Petazzoni via buildroot
2023-09-21 21:56 ` [Buildroot] [PATCH 4/4] configs/ls1046a-frwy: new defconfig Brandon Maier via buildroot
2023-09-30 15:58 ` Thomas Petazzoni via buildroot
2023-09-30 14:23 ` [Buildroot] [PATCH 1/4] board/freescale: fix arm-trusted-firmware for binutils 2.39+ Romain Naour
2023-09-30 15:20 ` Thomas Petazzoni via buildroot [this message]
2023-10-02 16:21 ` [Buildroot] [External] " Maier, Brandon L Collins via buildroot
2023-10-04 21:58 ` Thomas Petazzoni via buildroot
2023-10-13 6:03 ` [Buildroot] " Peter Korsgaard
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=20230930172024.5aaf0df6@windsurf \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.com \
--cc=festevam@gmail.com \
--cc=gilles.talis@gmail.com \
--cc=maeva.manuel@oss.nxp.com \
--cc=stephane.viau@oss.nxp.com \
--cc=thomas.petazzoni@bootlin.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