From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] arch/Config.in: Allow ARM to select BR2_BINFMT_FLAT
Date: Thu, 5 Sep 2013 23:48:41 +0200 [thread overview]
Message-ID: <20130905234841.3bbfe0d4@skate> (raw)
In-Reply-To: <1378262667.32360.6.camel@phoenix>
Dear Axel Lin,
On Wed, 04 Sep 2013 10:44:27 +0800, Axel Lin wrote:
> diff --git a/arch/Config.in b/arch/Config.in
> index 14899ca..31c23ec 100644
> --- a/arch/Config.in
> +++ b/arch/Config.in
> @@ -223,8 +223,9 @@ config BR2_GCC_TARGET_MODE
> # Set up target binary format
> choice
> prompt "Target Binary Format"
> - depends on BR2_bfin || BR2_m68k
> - default BR2_BINFMT_FDPIC
> + depends on BR2_arm || BR2_bfin || BR2_m68k
> + default BR2_BINFMT_ELF if BR2_arm
> + default BR2_BINFMT_FDPIC if (BR2_bfin || BR2_m68k)
I know it was broken before, but FDPIC isn't supported on BR2_m68k, so
I guess we should have something like:
prompt "Target Binary Format"
depends on BR2_arm || BR2_m68k || BR2_bfin
default BR2_BINFMT_ELF if BR2_arm
default BR2_BINFMT_FDPIC if BR2_bfin
default BR2_BINFMT_FLAT if BR2_m68k
But I'm wondering if we shouldn't go further than that, and make
BR2_BINFMT_FLAT available only for non-MMU ARMs. Something like:
prompt "Target Binary Format"
depends on BR2_arm7tmdi || BR2_arm_cortex_m3 || BR2_arm_cortex_m4 || BR2_m68k || BR2_bfin
default BR2_BINFMT_FLAT if BR2_arm7tmdi || BR2_arm_cortex_m3 || BR2_arm_cortex_m4 || BR2_m68k
default BR2_BINFMT_FDPIC if BR2_bfin
or something like this. This way, users of MMU-capable ARM variants
wouldn't be confused by the availability of FLAT and ELF as binary
formats. Of course, BR2_BINFMT_ELF should gain some !BR2_arm7tmdi
&& !BR2_arm_cortex_m3 && !BR2_arm_cortex_m4 dependencies, or maybe even
a !BR2_USE_MMU dependency. I think there's quite some room for
improvement around the definition of which CPU has an MMU or not, and
which architectures support which binary formats.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-09-05 21:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 2:43 [Buildroot] [PATCH 1/2] package/Makefile.in: Fix dependency for selecting uclinux as TARGET_OS Axel Lin
2013-09-04 2:44 ` [Buildroot] [PATCH 2/2] arch/Config.in: Allow ARM to select BR2_BINFMT_FLAT Axel Lin
2013-09-05 21:48 ` Thomas Petazzoni [this message]
2013-09-06 1:08 ` Thomas De Schampheleire
2013-09-06 6:25 ` Thomas Petazzoni
2013-09-06 10:08 ` Gustavo Zacarias
2013-09-06 10:12 ` Thomas Petazzoni
2013-09-05 21:44 ` [Buildroot] [PATCH 1/2] package/Makefile.in: Fix dependency for selecting uclinux as TARGET_OS Thomas Petazzoni
2013-09-06 2:21 ` Axel Lin
2013-09-06 6:26 ` Thomas Petazzoni
2013-09-06 7:14 ` Axel Lin
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=20130905234841.3bbfe0d4@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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