From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: Romain Naour <romain.naour@gmail.com>,
yann.morin.1998@free.fr, buildroot@buildroot.org,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
linux-amarula@amarulasolutions.com,
Ben Wolsieffer <Ben.Wolsieffer@hefring.com>
Subject: Re: [Buildroot] [PATCH v2 4/9] arch/arm: add support for FDPIC
Date: Sun, 22 Sep 2024 12:08:17 +0200 [thread overview]
Message-ID: <20240922120817.73b13ea6@windsurf> (raw)
In-Reply-To: <20240922092312.2061358-5-dario.binacchi@amarulasolutions.com>
On Sun, 22 Sep 2024 11:23:07 +0200
Dario Binacchi <dario.binacchi@amarulasolutions.com> wrote:
> The target name for a FDPIC toolchain must be
> arm-<vendor>-uclinuxfdpiceabi, which doesn't follow the standard format
> and requires a special case.
>
> According to the kernel help for CONFIG_BINFMT_ELF_FDPIC, "It is also
> possible to run FDPIC ELF binaries on MMU linux," so FDPIC support is
> available on all ARM platforms, not just no-MMU.
but then I guess the tuple would not be arm-<vendor>-uclinuxfdpiceabi,
but something with "linux" instead? Did you test this support for FDPIC
on MMU systems? Unless it has been tested to be working, I believe I
would prefer to allow FDPIC only on noMMU systems, for which it has
been tested.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-09-22 10:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-22 9:23 [Buildroot] [PATCH v2 0/9] add ARM FDPIC support Dario Binacchi
2024-09-22 9:23 ` [Buildroot] [PATCH v2 1/9] Revert: "arch: drop now useless support for FDPIC" Dario Binacchi
2024-09-22 9:23 ` [Buildroot] [PATCH v2 2/9] arch: don't enable FDPIC binaries by default Dario Binacchi
2024-09-22 9:23 ` [Buildroot] [PATCH v2 3/9] arch: make FDPIC dependent on toolchain support Dario Binacchi
2024-09-22 10:06 ` Thomas Petazzoni via buildroot
2024-09-22 9:23 ` [Buildroot] [PATCH v2 4/9] arch/arm: add support for FDPIC Dario Binacchi
2024-09-22 10:08 ` Thomas Petazzoni via buildroot [this message]
2024-09-22 9:23 ` [Buildroot] [PATCH v2 5/9] boot/uboot: pass -mno-fdpic if FDPIC is enabled Dario Binacchi
2024-09-22 10:10 ` Thomas Petazzoni via buildroot
2024-09-22 9:23 ` [Buildroot] [PATCH v2 6/9] linux: " Dario Binacchi
2024-09-22 9:23 ` [Buildroot] [PATCH v2 7/9] package/uclibc: enable NPTL on no-MMU ARM w/ FDPIC Dario Binacchi
2024-09-22 9:23 ` [Buildroot] [PATCH v2 8/9] package/busybox: remove STATIC from busybox-minimal.config Dario Binacchi
2024-09-22 9:23 ` [Buildroot] [PATCH v2 9/9] configs/stm32f746_disco_sd: new defconfig Dario Binacchi
2024-09-22 10:14 ` [Buildroot] [PATCH v2 0/9] add ARM FDPIC support Thomas Petazzoni via buildroot
2024-09-22 15:36 ` Waldemar Brodkorb
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=20240922120817.73b13ea6@windsurf \
--to=buildroot@buildroot.org \
--cc=Ben.Wolsieffer@hefring.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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