From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] buildroot: target: Add Blackfin architecture support in configuration.
Date: Mon, 6 Aug 2012 14:36:07 +0200 [thread overview]
Message-ID: <20120806143607.7dca918a@skate> (raw)
In-Reply-To: <1344251847-7709-1-git-send-email-sonic.adi@gmail.com>
Hello,
Le Mon, 6 Aug 2012 19:17:25 +0800,
Sonic Zhang <sonic.adi@gmail.com> a ?crit :
> From: Sonic Zhang <sonic.zhang@analog.com>
>
> Signed-off-by: Sonic Zhang <sonic.zhang@analog.com>
> ---
> target/Config.in.arch | 19 +++++++++++++++++++
> 1 files changed, 19 insertions(+), 0 deletions(-)
>
> diff --git a/target/Config.in.arch b/target/Config.in.arch
> index 6eaa951..001faf0 100644
> --- a/target/Config.in.arch
> +++ b/target/Config.in.arch
> @@ -131,6 +131,15 @@ config BR2_xtensa
> http://www.tensilica.com/
> endchoice
>
> +config BR2_ABI_FLAT
> + bool
> + default n
> +
> +config BR2_ABI_ELF
> + bool
> + default y
> + depends on !BR2_ABI_FLAT
Could you expand a bit on why this is needed, and where it will be
used? I have seen those used in various places in some of your packages
in your Git repository, but I am not sure the use cases were actually
valid.
> config BR2_microblaze
> bool
> default y if BR2_microblazeel || BR2_microblazebe
> @@ -231,8 +240,18 @@ choice
> default BR2_BFIN_FDPIC
> config BR2_BFIN_FDPIC
> bool "FDPIC"
> + select BR2_ABI_ELF
> config BR2_BFIN_FLAT
> bool "FLAT"
> + select BR2_ABI_FLAT
> + select BR2_PREFER_STATIC_LIB
> +config BR2_BFIN_FLAT_SEP_DATA
> + bool "FLAT (Separate data)"
> + select BR2_ABI_FLAT
> + select BR2_PREFER_STATIC_LIB
> +config BR2_BFIN_SHARED_FLAT
> + bool "Shared FLAT"
> + select BR2_ABI_FLAT
> select BR2_PREFER_STATIC_LIB
> endchoice
Are these "FLAT (Separate data)" and "Shared FLAT" use cases actually
used in practice by people? I'm not a Blackfin expert, so I don't know
what's used in the field.
Thanks!
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:[~2012-08-06 12:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 11:17 [Buildroot] [PATCH 1/3] buildroot: target: Add Blackfin architecture support in configuration Sonic Zhang
2012-08-06 11:17 ` [Buildroot] [PATCH 2/2] buildroot:package: Avoids prefix absolute compiler path when external toolchain path is empty Sonic Zhang
2012-08-06 12:50 ` Thomas Petazzoni
2012-08-06 11:17 ` [Buildroot] [PATCH 3/3] buildroot: toolchain: Allow to build gdbserver when external toolchain is selected Sonic Zhang
2012-08-06 12:54 ` Thomas Petazzoni
[not found] ` <DB904C5425BA6F4E8424B3B51A1414D1714D28600B@NWD2CMBX1.ad.analog.com>
2012-08-08 2:39 ` Sonic Zhang
[not found] ` <05E9E85E39C35B4D96ED3A3190E35A10C3D77B0E41@LIMKCMBX1.ad.analog.com>
2012-08-08 19:23 ` Thomas Petazzoni
[not found] ` <05E9E85E39C35B4D96ED3A3190E35A10C3D786052C@LIMKCMBX1.ad.analog.com>
2012-08-14 12:25 ` Thomas Petazzoni
2012-08-06 12:36 ` Thomas Petazzoni [this message]
[not found] ` <DB904C5425BA6F4E8424B3B51A1414D1714D286001@NWD2CMBX1.ad.analog.com>
2012-08-08 2:42 ` [Buildroot] [PATCH 1/3] buildroot: target: Add Blackfin architecture support in configuration Sonic Zhang
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=20120806143607.7dca918a@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