From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] arm: update processor types
Date: Sat, 14 Feb 2015 15:43:32 +0100 [thread overview]
Message-ID: <54DF5F14.2010900@openwide.fr> (raw)
In-Reply-To: <54D66BEB.6030002@vanguardiasur.com.ar>
Hi Ezequiel,
Le 07/02/2015 20:47, Ezequiel Garcia a ?crit :
> Hi Romain,
>
> First of all, thanks for the great feedback.
You're welcome :)
>
> On 02/02/2015 01:18 PM, Romain Naour wrote:
> [..]
>>> - default BR2_BINFMT_FLAT if BR2_m68k
>>> + default BR2_BINFMT_FLAT if BR2_m68k || BR2_cortex_m3
>>
>> What do you think about adding BR2_ARCH_HAS_EFL_SUPPORT in each architecture
>> Config.in.x instead of black-listing them here ?
>>
>
> I've been thinking about this. At first it seemed like a good idea, but
> then I realised that Cortex-M3 is not really an architecture, but
> a variant.
>
> Introducing BR2_ARCH_HAS_ELF_SUPPORT would mean selecting it on almost each
> architecture and almost each of the ARM variants, except Cortex-M3.
>
> So, it seems like it would be an elegant way of doing this, but I'm not sure
> it's worth such an invasive change.
>
We may introduce BR2_ARCH_HAS_ELF_SUPPORT as an hidden option which is set to y
by default except for BR2_bfin, BR2_m68k and BR2_cortex_m3. (like for BR2_USE_MMU)
config BR2_ARCH_HAS_ELF_SUPPORT
bool
default y if !(BR2_bfin || BR2_m68k || BR2_cortex_m3)
What other developer think ?
Best regards,
Romain
next prev parent reply other threads:[~2015-02-14 14:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 18:33 [Buildroot] [PATCH 0/4] ARM Cortex-M3 support Ezequiel Garcia
2015-01-22 18:33 ` [Buildroot] [PATCH 1/4] arm: conditionally support regular ARM instructions Ezequiel Garcia
2015-02-02 16:17 ` Romain Naour
2015-02-02 20:18 ` Thomas Petazzoni
2015-01-22 18:33 ` [Buildroot] [PATCH 2/4] arm: update processor types Ezequiel Garcia
2015-02-02 16:18 ` Romain Naour
2015-02-07 18:05 ` Ezequiel Garcia
2015-02-14 13:51 ` Romain Naour
2015-02-07 19:47 ` Ezequiel Garcia
2015-02-14 14:43 ` Romain Naour [this message]
2015-01-22 18:33 ` [Buildroot] [PATCH 3/4] toolchain: allow for stupid toolchains Ezequiel Garcia
2015-01-25 19:32 ` Thomas Petazzoni
2015-02-02 16:18 ` Romain Naour
2015-02-02 17:32 ` Yann E. MORIN
2015-01-22 18:33 ` [Buildroot] [PATCH 4/4] toolchain-external: add OSELAS 2013.12.2 Cortex-M3 toolchain Ezequiel Garcia
2015-02-02 16:29 ` Romain Naour
2015-02-02 20:19 ` [Buildroot] [PATCH 0/4] ARM Cortex-M3 support Thomas Petazzoni
2015-02-03 1:05 ` Ezequiel Garcia
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=54DF5F14.2010900@openwide.fr \
--to=romain.naour@openwide.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.