2012-12-13 23:20:48 +01:00
|
|
|
# arm cpu features
|
|
|
|
|
config BR2_ARM_CPU_HAS_NEON
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
# for some cores, NEON support is optional
|
|
|
|
|
config BR2_ARM_CPU_MAYBE_HAS_NEON
|
|
|
|
|
bool
|
|
|
|
|
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
# for some cores, VFPv2 is optional
|
|
|
|
|
config BR2_ARM_CPU_MAYBE_HAS_VFPV2
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config BR2_ARM_CPU_HAS_VFPV2
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
# for some cores, VFPv3 is optional
|
|
|
|
|
config BR2_ARM_CPU_MAYBE_HAS_VFPV3
|
|
|
|
|
bool
|
|
|
|
|
select BR2_ARM_CPU_MAYBE_HAS_VFPV2
|
|
|
|
|
|
|
|
|
|
config BR2_ARM_CPU_HAS_VFPV3
|
|
|
|
|
bool
|
|
|
|
|
select BR2_ARM_CPU_HAS_VFPV2
|
|
|
|
|
|
|
|
|
|
# for some cores, VFPv4 is optional
|
|
|
|
|
config BR2_ARM_CPU_MAYBE_HAS_VFPV4
|
|
|
|
|
bool
|
|
|
|
|
select BR2_ARM_CPU_MAYBE_HAS_VFPV3
|
|
|
|
|
|
|
|
|
|
config BR2_ARM_CPU_HAS_VFPV4
|
|
|
|
|
bool
|
|
|
|
|
select BR2_ARM_CPU_HAS_VFPV3
|
|
|
|
|
|
2016-11-30 22:12:08 +01:00
|
|
|
config BR2_ARM_CPU_HAS_FP_ARMV8
|
|
|
|
|
bool
|
|
|
|
|
select BR2_ARM_CPU_HAS_VFPV4
|
|
|
|
|
|
2015-01-22 19:33:25 +01:00
|
|
|
config BR2_ARM_CPU_HAS_ARM
|
|
|
|
|
bool
|
|
|
|
|
|
2013-07-17 17:39:15 +02:00
|
|
|
config BR2_ARM_CPU_HAS_THUMB
|
|
|
|
|
bool
|
|
|
|
|
|
2013-07-16 10:03:22 +02:00
|
|
|
config BR2_ARM_CPU_HAS_THUMB2
|
|
|
|
|
bool
|
|
|
|
|
|
2014-10-21 22:26:48 +02:00
|
|
|
config BR2_ARM_CPU_ARMV4
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config BR2_ARM_CPU_ARMV5
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config BR2_ARM_CPU_ARMV6
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config BR2_ARM_CPU_ARMV7A
|
|
|
|
|
bool
|
|
|
|
|
|
2016-03-18 22:08:03 +01:00
|
|
|
config BR2_ARM_CPU_ARMV7M
|
|
|
|
|
bool
|
|
|
|
|
|
2016-11-30 22:12:06 +01:00
|
|
|
config BR2_ARM_CPU_ARMV8
|
|
|
|
|
bool
|
|
|
|
|
|
Split target/Config.in.arch into multiple Config.in.* in arch/
target/Config.in.arch had become too long, and we want to remove the
target/ directory. So let's move it to arch/ and split it this way:
* An initial Config.in that lists the top-level architecture, and
sources the arch-specific Config.in.<arch> files, as well as
Config.in.common (see below)
* One Config.in.<arch> per architecture, listing the CPU families,
ABI choices, etc.
* One Config.in.common that defines the gcc mtune, march, mcpu values
and other hidden options.
[Peter: space->tab fix, mipsel64 little endian, mips3 as noted by Arnout]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-03 09:27:59 +01:00
|
|
|
choice
|
|
|
|
|
prompt "Target Architecture Variant"
|
2013-04-04 09:29:45 +02:00
|
|
|
default BR2_arm926t
|
Split target/Config.in.arch into multiple Config.in.* in arch/
target/Config.in.arch had become too long, and we want to remove the
target/ directory. So let's move it to arch/ and split it this way:
* An initial Config.in that lists the top-level architecture, and
sources the arch-specific Config.in.<arch> files, as well as
Config.in.common (see below)
* One Config.in.<arch> per architecture, listing the CPU families,
ABI choices, etc.
* One Config.in.common that defines the gcc mtune, march, mcpu values
and other hidden options.
[Peter: space->tab fix, mipsel64 little endian, mips3 as noted by Arnout]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-03 09:27:59 +01:00
|
|
|
help
|
|
|
|
|
Specific CPU variant to use
|
|
|
|
|
|
|
|
|
|
config BR2_arm920t
|
|
|
|
|
bool "arm920t"
|
2015-01-22 19:33:25 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
2013-07-17 17:39:15 +02:00
|
|
|
select BR2_ARM_CPU_HAS_THUMB
|
2014-10-21 22:26:48 +02:00
|
|
|
select BR2_ARM_CPU_ARMV4
|
2015-06-04 00:34:03 +02:00
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
Split target/Config.in.arch into multiple Config.in.* in arch/
target/Config.in.arch had become too long, and we want to remove the
target/ directory. So let's move it to arch/ and split it this way:
* An initial Config.in that lists the top-level architecture, and
sources the arch-specific Config.in.<arch> files, as well as
Config.in.common (see below)
* One Config.in.<arch> per architecture, listing the CPU families,
ABI choices, etc.
* One Config.in.common that defines the gcc mtune, march, mcpu values
and other hidden options.
[Peter: space->tab fix, mipsel64 little endian, mips3 as noted by Arnout]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-03 09:27:59 +01:00
|
|
|
config BR2_arm922t
|
|
|
|
|
bool "arm922t"
|
2015-01-22 19:33:25 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
2013-07-17 17:39:15 +02:00
|
|
|
select BR2_ARM_CPU_HAS_THUMB
|
2014-10-21 22:26:48 +02:00
|
|
|
select BR2_ARM_CPU_ARMV4
|
2015-06-04 00:34:03 +02:00
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
Split target/Config.in.arch into multiple Config.in.* in arch/
target/Config.in.arch had become too long, and we want to remove the
target/ directory. So let's move it to arch/ and split it this way:
* An initial Config.in that lists the top-level architecture, and
sources the arch-specific Config.in.<arch> files, as well as
Config.in.common (see below)
* One Config.in.<arch> per architecture, listing the CPU families,
ABI choices, etc.
* One Config.in.common that defines the gcc mtune, march, mcpu values
and other hidden options.
[Peter: space->tab fix, mipsel64 little endian, mips3 as noted by Arnout]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-03 09:27:59 +01:00
|
|
|
config BR2_arm926t
|
|
|
|
|
bool "arm926t"
|
2015-01-22 19:33:25 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
2013-07-17 02:32:45 +02:00
|
|
|
select BR2_ARM_CPU_MAYBE_HAS_VFPV2
|
2013-07-17 17:39:15 +02:00
|
|
|
select BR2_ARM_CPU_HAS_THUMB
|
2014-10-21 22:26:48 +02:00
|
|
|
select BR2_ARM_CPU_ARMV5
|
2015-06-04 00:34:03 +02:00
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
2015-08-24 00:43:12 +02:00
|
|
|
config BR2_arm1136j_s
|
|
|
|
|
bool "arm1136j-s"
|
|
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
|
|
|
|
select BR2_ARM_CPU_HAS_THUMB
|
|
|
|
|
select BR2_ARM_CPU_ARMV6
|
|
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
arch/arm: do not distinguish revisions of ARM1136JF-S
In commit 88cf3bb91792c9c04586e14f293d89a6e0c13e1d
("arch/Config.in.arm: Use armv6k for arm1136jf-s rev1"), Benoît
Thébaudeau added separate options for the revision 0 and revision 1 of
the ARM1136JF-S processor, so that different -march values could be
used (armv6j for revision 0, armv6k for revision 1).
However, this is preventing the removal of the BR2_GCC_TARGET_ARCH
option, which we need to do to give only the CPU type to gcc, and let
it decide the architecture variant that matches. This is because this
story of revision 0 vs. revision 1 is the only case where -mcpu
doesn't fully define the CPU.
Moreover, a quick test with gcc shows that -march=armv6j
-mcpu=arm1136jf-s is accepted, while -march=armv6k -mcpu=arm1136jf-s
makes gcc complain: " warning: switch -mcpu=arm1136jf-s conflicts with
-march=armv6k switch".
In addition, gcc 5 will apparently no longer allow to pass all of
--with-arch, --with-cpu and --with-tune, so we will anyway have to
rely only on one of them.
As a consequence, this commit basically reverts
88cf3bb91792c9c04586e14f293d89a6e0c13e1d and provides only one option
for ARM1136JF-S. If the two revisions are really different, then they
should be supported in upstream gcc with different -mcpu values.
Note that the removal of the two options should not break existing
full .config, since the hidden option BR2_arm1136jf_s becomes again a
visible option to select the CPU.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Benoît Thébaudeau <benoit.thebaudeau@advansee.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-10-21 22:27:08 +02:00
|
|
|
config BR2_arm1136jf_s
|
|
|
|
|
bool "arm1136jf-s"
|
2015-01-22 19:33:25 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
select BR2_ARM_CPU_HAS_VFPV2
|
2013-07-17 17:39:15 +02:00
|
|
|
select BR2_ARM_CPU_HAS_THUMB
|
2014-10-21 22:26:48 +02:00
|
|
|
select BR2_ARM_CPU_ARMV6
|
2015-06-04 00:34:03 +02:00
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
Split target/Config.in.arch into multiple Config.in.* in arch/
target/Config.in.arch had become too long, and we want to remove the
target/ directory. So let's move it to arch/ and split it this way:
* An initial Config.in that lists the top-level architecture, and
sources the arch-specific Config.in.<arch> files, as well as
Config.in.common (see below)
* One Config.in.<arch> per architecture, listing the CPU families,
ABI choices, etc.
* One Config.in.common that defines the gcc mtune, march, mcpu values
and other hidden options.
[Peter: space->tab fix, mipsel64 little endian, mips3 as noted by Arnout]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-03 09:27:59 +01:00
|
|
|
config BR2_arm1176jz_s
|
|
|
|
|
bool "arm1176jz-s"
|
2015-01-22 19:33:25 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
2013-07-17 17:39:15 +02:00
|
|
|
select BR2_ARM_CPU_HAS_THUMB
|
2014-10-21 22:26:48 +02:00
|
|
|
select BR2_ARM_CPU_ARMV6
|
2015-06-04 00:34:03 +02:00
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
Split target/Config.in.arch into multiple Config.in.* in arch/
target/Config.in.arch had become too long, and we want to remove the
target/ directory. So let's move it to arch/ and split it this way:
* An initial Config.in that lists the top-level architecture, and
sources the arch-specific Config.in.<arch> files, as well as
Config.in.common (see below)
* One Config.in.<arch> per architecture, listing the CPU families,
ABI choices, etc.
* One Config.in.common that defines the gcc mtune, march, mcpu values
and other hidden options.
[Peter: space->tab fix, mipsel64 little endian, mips3 as noted by Arnout]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-03 09:27:59 +01:00
|
|
|
config BR2_arm1176jzf_s
|
|
|
|
|
bool "arm1176jzf-s"
|
2015-01-22 19:33:25 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
select BR2_ARM_CPU_HAS_VFPV2
|
2013-07-17 17:39:15 +02:00
|
|
|
select BR2_ARM_CPU_HAS_THUMB
|
2014-10-21 22:26:48 +02:00
|
|
|
select BR2_ARM_CPU_ARMV6
|
2015-06-04 00:34:03 +02:00
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
2015-11-28 15:55:21 +01:00
|
|
|
config BR2_arm11mpcore
|
|
|
|
|
bool "mpcore"
|
|
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
|
|
|
|
select BR2_ARM_CPU_MAYBE_HAS_VFPV2
|
|
|
|
|
select BR2_ARM_CPU_HAS_THUMB
|
|
|
|
|
select BR2_ARM_CPU_ARMV6
|
|
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
2012-12-09 12:54:03 +01:00
|
|
|
config BR2_cortex_a5
|
|
|
|
|
bool "cortex-A5"
|
2015-01-22 19:33:25 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
2012-12-13 23:20:48 +01:00
|
|
|
select BR2_ARM_CPU_MAYBE_HAS_NEON
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
select BR2_ARM_CPU_MAYBE_HAS_VFPV4
|
2013-07-16 10:03:22 +02:00
|
|
|
select BR2_ARM_CPU_HAS_THUMB2
|
2014-10-21 22:26:48 +02:00
|
|
|
select BR2_ARM_CPU_ARMV7A
|
2015-06-04 00:34:03 +02:00
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
2013-06-09 04:53:50 +02:00
|
|
|
config BR2_cortex_a7
|
|
|
|
|
bool "cortex-A7"
|
2015-01-22 19:33:25 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
2013-06-09 04:53:50 +02:00
|
|
|
select BR2_ARM_CPU_HAS_NEON
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
select BR2_ARM_CPU_HAS_VFPV4
|
2013-07-16 10:03:22 +02:00
|
|
|
select BR2_ARM_CPU_HAS_THUMB2
|
2014-10-21 22:26:48 +02:00
|
|
|
select BR2_ARM_CPU_ARMV7A
|
2015-06-04 00:34:03 +02:00
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
Split target/Config.in.arch into multiple Config.in.* in arch/
target/Config.in.arch had become too long, and we want to remove the
target/ directory. So let's move it to arch/ and split it this way:
* An initial Config.in that lists the top-level architecture, and
sources the arch-specific Config.in.<arch> files, as well as
Config.in.common (see below)
* One Config.in.<arch> per architecture, listing the CPU families,
ABI choices, etc.
* One Config.in.common that defines the gcc mtune, march, mcpu values
and other hidden options.
[Peter: space->tab fix, mipsel64 little endian, mips3 as noted by Arnout]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-03 09:27:59 +01:00
|
|
|
config BR2_cortex_a8
|
|
|
|
|
bool "cortex-A8"
|
2015-01-22 19:33:25 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
2012-12-13 23:20:48 +01:00
|
|
|
select BR2_ARM_CPU_HAS_NEON
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
select BR2_ARM_CPU_HAS_VFPV3
|
2013-07-16 10:03:22 +02:00
|
|
|
select BR2_ARM_CPU_HAS_THUMB2
|
2014-10-21 22:26:48 +02:00
|
|
|
select BR2_ARM_CPU_ARMV7A
|
2015-06-04 00:34:03 +02:00
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
Split target/Config.in.arch into multiple Config.in.* in arch/
target/Config.in.arch had become too long, and we want to remove the
target/ directory. So let's move it to arch/ and split it this way:
* An initial Config.in that lists the top-level architecture, and
sources the arch-specific Config.in.<arch> files, as well as
Config.in.common (see below)
* One Config.in.<arch> per architecture, listing the CPU families,
ABI choices, etc.
* One Config.in.common that defines the gcc mtune, march, mcpu values
and other hidden options.
[Peter: space->tab fix, mipsel64 little endian, mips3 as noted by Arnout]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-03 09:27:59 +01:00
|
|
|
config BR2_cortex_a9
|
|
|
|
|
bool "cortex-A9"
|
2015-01-22 19:33:25 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
2012-12-13 23:20:48 +01:00
|
|
|
select BR2_ARM_CPU_MAYBE_HAS_NEON
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
select BR2_ARM_CPU_MAYBE_HAS_VFPV3
|
2013-07-16 10:03:22 +02:00
|
|
|
select BR2_ARM_CPU_HAS_THUMB2
|
2014-10-21 22:26:48 +02:00
|
|
|
select BR2_ARM_CPU_ARMV7A
|
2015-06-04 00:34:03 +02:00
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
2014-04-24 03:00:31 +02:00
|
|
|
config BR2_cortex_a12
|
|
|
|
|
bool "cortex-A12"
|
2015-01-22 19:33:25 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
2014-04-24 03:00:31 +02:00
|
|
|
select BR2_ARM_CPU_HAS_NEON
|
|
|
|
|
select BR2_ARM_CPU_HAS_VFPV4
|
|
|
|
|
select BR2_ARM_CPU_HAS_THUMB2
|
2014-10-21 22:26:48 +02:00
|
|
|
select BR2_ARM_CPU_ARMV7A
|
2015-06-04 00:34:03 +02:00
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
2012-12-09 12:54:03 +01:00
|
|
|
config BR2_cortex_a15
|
|
|
|
|
bool "cortex-A15"
|
2015-01-22 19:33:25 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
2012-12-13 23:20:48 +01:00
|
|
|
select BR2_ARM_CPU_HAS_NEON
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
select BR2_ARM_CPU_HAS_VFPV4
|
2013-07-16 10:03:22 +02:00
|
|
|
select BR2_ARM_CPU_HAS_THUMB2
|
2014-10-21 22:26:48 +02:00
|
|
|
select BR2_ARM_CPU_ARMV7A
|
2015-06-04 00:34:03 +02:00
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
2016-02-21 14:12:10 +01:00
|
|
|
config BR2_cortex_a17
|
|
|
|
|
bool "cortex-A17"
|
|
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
|
|
|
|
select BR2_ARM_CPU_HAS_NEON
|
|
|
|
|
select BR2_ARM_CPU_HAS_VFPV4
|
|
|
|
|
select BR2_ARM_CPU_HAS_THUMB2
|
|
|
|
|
select BR2_ARM_CPU_ARMV7A
|
|
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
2016-11-30 22:12:10 +01:00
|
|
|
config BR2_cortex_a53
|
|
|
|
|
bool "cortex-A53"
|
2016-12-07 10:25:20 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM if !BR2_ARCH_IS_64
|
2016-12-07 10:25:21 +01:00
|
|
|
select BR2_ARM_CPU_HAS_NEON if !BR2_ARCH_IS_64
|
2016-12-07 10:25:22 +01:00
|
|
|
select BR2_ARM_CPU_HAS_THUMB2 if !BR2_ARCH_IS_64
|
2016-11-30 22:12:10 +01:00
|
|
|
select BR2_ARM_CPU_HAS_FP_ARMV8
|
|
|
|
|
select BR2_ARM_CPU_ARMV8
|
|
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:11 +01:00
|
|
|
config BR2_cortex_a57
|
|
|
|
|
bool "cortex-A57"
|
2016-12-07 10:25:20 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM if !BR2_ARCH_IS_64
|
2016-12-07 10:25:21 +01:00
|
|
|
select BR2_ARM_CPU_HAS_NEON if !BR2_ARCH_IS_64
|
2016-12-07 10:25:22 +01:00
|
|
|
select BR2_ARM_CPU_HAS_THUMB2 if !BR2_ARCH_IS_64
|
2016-11-30 22:12:11 +01:00
|
|
|
select BR2_ARM_CPU_HAS_FP_ARMV8
|
|
|
|
|
select BR2_ARM_CPU_ARMV8
|
|
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
|
|
|
|
config BR2_cortex_a72
|
|
|
|
|
bool "cortex-A72"
|
2016-12-07 10:25:20 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM if !BR2_ARCH_IS_64
|
2016-12-07 10:25:21 +01:00
|
|
|
select BR2_ARM_CPU_HAS_NEON if !BR2_ARCH_IS_64
|
2016-12-07 10:25:22 +01:00
|
|
|
select BR2_ARM_CPU_HAS_THUMB2 if !BR2_ARCH_IS_64
|
2016-11-30 22:12:11 +01:00
|
|
|
select BR2_ARM_CPU_HAS_FP_ARMV8
|
|
|
|
|
select BR2_ARM_CPU_ARMV8
|
|
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2015-06-26 19:33:19 +02:00
|
|
|
config BR2_cortex_m3
|
|
|
|
|
bool "cortex-M3"
|
|
|
|
|
select BR2_ARM_CPU_HAS_THUMB2
|
2016-03-18 22:08:03 +01:00
|
|
|
select BR2_ARM_CPU_ARMV7M
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
2016-03-18 22:08:05 +01:00
|
|
|
config BR2_cortex_m4
|
|
|
|
|
bool "cortex-M4"
|
|
|
|
|
select BR2_ARM_CPU_HAS_THUMB2
|
|
|
|
|
select BR2_ARM_CPU_ARMV7M
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
2013-04-04 09:29:45 +02:00
|
|
|
config BR2_fa526
|
|
|
|
|
bool "fa526/626"
|
2015-01-22 19:33:25 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
2014-10-21 22:26:48 +02:00
|
|
|
select BR2_ARM_CPU_ARMV4
|
2015-06-04 00:34:03 +02:00
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
2013-04-29 10:54:24 +02:00
|
|
|
config BR2_pj4
|
|
|
|
|
bool "pj4"
|
2015-01-22 19:33:25 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
select BR2_ARM_CPU_HAS_VFPV3
|
2014-10-21 22:26:48 +02:00
|
|
|
select BR2_ARM_CPU_ARMV7A
|
2015-06-04 00:34:03 +02:00
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
2013-04-04 09:29:45 +02:00
|
|
|
config BR2_strongarm
|
|
|
|
|
bool "strongarm sa110/sa1100"
|
2015-01-22 19:33:25 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
2014-10-21 22:26:48 +02:00
|
|
|
select BR2_ARM_CPU_ARMV4
|
2015-06-04 00:34:03 +02:00
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
Split target/Config.in.arch into multiple Config.in.* in arch/
target/Config.in.arch had become too long, and we want to remove the
target/ directory. So let's move it to arch/ and split it this way:
* An initial Config.in that lists the top-level architecture, and
sources the arch-specific Config.in.<arch> files, as well as
Config.in.common (see below)
* One Config.in.<arch> per architecture, listing the CPU families,
ABI choices, etc.
* One Config.in.common that defines the gcc mtune, march, mcpu values
and other hidden options.
[Peter: space->tab fix, mipsel64 little endian, mips3 as noted by Arnout]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-03 09:27:59 +01:00
|
|
|
config BR2_xscale
|
|
|
|
|
bool "xscale"
|
2015-01-22 19:33:25 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
2013-07-17 17:39:15 +02:00
|
|
|
select BR2_ARM_CPU_HAS_THUMB
|
2014-10-21 22:26:48 +02:00
|
|
|
select BR2_ARM_CPU_ARMV5
|
2015-06-04 00:34:03 +02:00
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
Split target/Config.in.arch into multiple Config.in.* in arch/
target/Config.in.arch had become too long, and we want to remove the
target/ directory. So let's move it to arch/ and split it this way:
* An initial Config.in that lists the top-level architecture, and
sources the arch-specific Config.in.<arch> files, as well as
Config.in.common (see below)
* One Config.in.<arch> per architecture, listing the CPU families,
ABI choices, etc.
* One Config.in.common that defines the gcc mtune, march, mcpu values
and other hidden options.
[Peter: space->tab fix, mipsel64 little endian, mips3 as noted by Arnout]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-03 09:27:59 +01:00
|
|
|
config BR2_iwmmxt
|
|
|
|
|
bool "iwmmxt"
|
2015-01-22 19:33:25 +01:00
|
|
|
select BR2_ARM_CPU_HAS_ARM
|
2014-10-21 22:26:48 +02:00
|
|
|
select BR2_ARM_CPU_ARMV5
|
2015-06-04 00:34:03 +02:00
|
|
|
select BR2_ARCH_HAS_MMU_OPTIONAL
|
2016-11-30 22:12:05 +01:00
|
|
|
depends on !BR2_ARCH_IS_64
|
Split target/Config.in.arch into multiple Config.in.* in arch/
target/Config.in.arch had become too long, and we want to remove the
target/ directory. So let's move it to arch/ and split it this way:
* An initial Config.in that lists the top-level architecture, and
sources the arch-specific Config.in.<arch> files, as well as
Config.in.common (see below)
* One Config.in.<arch> per architecture, listing the CPU families,
ABI choices, etc.
* One Config.in.common that defines the gcc mtune, march, mcpu values
and other hidden options.
[Peter: space->tab fix, mipsel64 little endian, mips3 as noted by Arnout]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-03 09:27:59 +01:00
|
|
|
endchoice
|
|
|
|
|
|
2015-12-26 17:05:41 +01:00
|
|
|
config BR2_ARM_ENABLE_NEON
|
|
|
|
|
bool "Enable NEON SIMD extension support"
|
|
|
|
|
depends on BR2_ARM_CPU_MAYBE_HAS_NEON
|
|
|
|
|
select BR2_ARM_CPU_HAS_NEON
|
|
|
|
|
help
|
|
|
|
|
For some CPU cores, the NEON SIMD extension is optional.
|
|
|
|
|
Select this option if you are certain your particular
|
|
|
|
|
implementation has NEON support and you want to use it.
|
|
|
|
|
|
arch/arm: add option to enable an optional VFP unit
Currently, the VFP selection for ARM is a little bit muddy:
- some CPUs definitely do not have a VFP or NEON,
- some CPUs definitely do have a VFP or NEON,
- some CPUs may have a VFP or NEON.
However, we currently conflate the availability of the VFP/NEON with the
possibility to use them. Even is the user chooses a floating point
strategy with a 'lower' solution (i.e. VFPv2 when a VFPv3 exists, or not
using NEON when the CPU has it), some packages are still using the
CPU-defined HW availaibility rather thean the usr's selection.
Furthermore, for CPU that may have a VFP/NEON, there is no way for the
user to actually specify that the HW is indeed available; the user can
only specify the floating point strategy. This means that some packages
or some package versions, like nodejs for example, can not be properly
selected on some CPU cores, like Cortex-A9 which only may have a VFP.
Like we have an option to enable an optional NEON unit, add a similar
option to enable an optional VFP unit.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-26 17:05:42 +01:00
|
|
|
config BR2_ARM_ENABLE_VFP
|
|
|
|
|
bool "Enable VFP extension support"
|
|
|
|
|
depends on BR2_ARM_CPU_MAYBE_HAS_VFPV2
|
|
|
|
|
select BR2_ARM_CPU_HAS_VFPV4 if BR2_ARM_CPU_MAYBE_HAS_VFPV4
|
|
|
|
|
select BR2_ARM_CPU_HAS_VFPV3 if BR2_ARM_CPU_MAYBE_HAS_VFPV3
|
|
|
|
|
select BR2_ARM_CPU_HAS_VFPV2 if BR2_ARM_CPU_MAYBE_HAS_VFPV2
|
2015-12-27 12:22:43 +01:00
|
|
|
help
|
|
|
|
|
For some CPU cores, the VFP extension is optional. Select
|
|
|
|
|
this option if you are certain your particular
|
|
|
|
|
implementation has VFP support and you want to use it.
|
arch/arm: add option to enable an optional VFP unit
Currently, the VFP selection for ARM is a little bit muddy:
- some CPUs definitely do not have a VFP or NEON,
- some CPUs definitely do have a VFP or NEON,
- some CPUs may have a VFP or NEON.
However, we currently conflate the availability of the VFP/NEON with the
possibility to use them. Even is the user chooses a floating point
strategy with a 'lower' solution (i.e. VFPv2 when a VFPv3 exists, or not
using NEON when the CPU has it), some packages are still using the
CPU-defined HW availaibility rather thean the usr's selection.
Furthermore, for CPU that may have a VFP/NEON, there is no way for the
user to actually specify that the HW is indeed available; the user can
only specify the floating point strategy. This means that some packages
or some package versions, like nodejs for example, can not be properly
selected on some CPU cores, like Cortex-A9 which only may have a VFP.
Like we have an option to enable an optional NEON unit, add a similar
option to enable an optional VFP unit.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-26 17:05:42 +01:00
|
|
|
|
Split target/Config.in.arch into multiple Config.in.* in arch/
target/Config.in.arch had become too long, and we want to remove the
target/ directory. So let's move it to arch/ and split it this way:
* An initial Config.in that lists the top-level architecture, and
sources the arch-specific Config.in.<arch> files, as well as
Config.in.common (see below)
* One Config.in.<arch> per architecture, listing the CPU families,
ABI choices, etc.
* One Config.in.common that defines the gcc mtune, march, mcpu values
and other hidden options.
[Peter: space->tab fix, mipsel64 little endian, mips3 as noted by Arnout]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-03 09:27:59 +01:00
|
|
|
choice
|
|
|
|
|
prompt "Target ABI"
|
|
|
|
|
depends on BR2_arm || BR2_armeb
|
2015-10-25 16:19:40 +01:00
|
|
|
default BR2_ARM_EABIHF if BR2_ARM_CPU_HAS_VFPV2
|
Split target/Config.in.arch into multiple Config.in.* in arch/
target/Config.in.arch had become too long, and we want to remove the
target/ directory. So let's move it to arch/ and split it this way:
* An initial Config.in that lists the top-level architecture, and
sources the arch-specific Config.in.<arch> files, as well as
Config.in.common (see below)
* One Config.in.<arch> per architecture, listing the CPU families,
ABI choices, etc.
* One Config.in.common that defines the gcc mtune, march, mcpu values
and other hidden options.
[Peter: space->tab fix, mipsel64 little endian, mips3 as noted by Arnout]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-03 09:27:59 +01:00
|
|
|
default BR2_ARM_EABI
|
|
|
|
|
help
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
Application Binary Interface to use. The Application Binary
|
|
|
|
|
Interface describes the calling conventions (how arguments
|
|
|
|
|
are passed to functions, how the return value is passed, how
|
|
|
|
|
system calls are made, etc.).
|
Split target/Config.in.arch into multiple Config.in.* in arch/
target/Config.in.arch had become too long, and we want to remove the
target/ directory. So let's move it to arch/ and split it this way:
* An initial Config.in that lists the top-level architecture, and
sources the arch-specific Config.in.<arch> files, as well as
Config.in.common (see below)
* One Config.in.<arch> per architecture, listing the CPU families,
ABI choices, etc.
* One Config.in.common that defines the gcc mtune, march, mcpu values
and other hidden options.
[Peter: space->tab fix, mipsel64 little endian, mips3 as noted by Arnout]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-03 09:27:59 +01:00
|
|
|
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
config BR2_ARM_EABI
|
Split target/Config.in.arch into multiple Config.in.* in arch/
target/Config.in.arch had become too long, and we want to remove the
target/ directory. So let's move it to arch/ and split it this way:
* An initial Config.in that lists the top-level architecture, and
sources the arch-specific Config.in.<arch> files, as well as
Config.in.common (see below)
* One Config.in.<arch> per architecture, listing the CPU families,
ABI choices, etc.
* One Config.in.common that defines the gcc mtune, march, mcpu values
and other hidden options.
[Peter: space->tab fix, mipsel64 little endian, mips3 as noted by Arnout]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-03 09:27:59 +01:00
|
|
|
bool "EABI"
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
help
|
|
|
|
|
The EABI is currently the standard ARM ABI, which is used in
|
|
|
|
|
most projects. It supports both the 'soft' floating point
|
|
|
|
|
model (in which floating point instructions are emulated in
|
|
|
|
|
software) and the 'softfp' floating point model (in which
|
|
|
|
|
floating point instructions are executed using an hardware
|
|
|
|
|
floating point unit, but floating point arguments to
|
|
|
|
|
functions are passed in integer registers).
|
Split target/Config.in.arch into multiple Config.in.* in arch/
target/Config.in.arch had become too long, and we want to remove the
target/ directory. So let's move it to arch/ and split it this way:
* An initial Config.in that lists the top-level architecture, and
sources the arch-specific Config.in.<arch> files, as well as
Config.in.common (see below)
* One Config.in.<arch> per architecture, listing the CPU families,
ABI choices, etc.
* One Config.in.common that defines the gcc mtune, march, mcpu values
and other hidden options.
[Peter: space->tab fix, mipsel64 little endian, mips3 as noted by Arnout]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-03 09:27:59 +01:00
|
|
|
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
The 'softfp' floating point model is link-compatible with
|
|
|
|
|
the 'soft' floating point model, i.e you can link a library
|
|
|
|
|
built 'soft' with some other code built 'softfp'.
|
2013-02-06 14:51:24 +01:00
|
|
|
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
However, passing the floating point arguments in integer
|
|
|
|
|
registers is a bit inefficient, so if your ARM processor has
|
|
|
|
|
a floating point unit, and you don't have pre-compiled
|
|
|
|
|
'soft' or 'softfp' code, using the EABIhf ABI will provide
|
|
|
|
|
better floating point performances.
|
|
|
|
|
|
|
|
|
|
If your processor does not have a floating point unit, then
|
|
|
|
|
you must use this ABI.
|
|
|
|
|
|
|
|
|
|
config BR2_ARM_EABIHF
|
|
|
|
|
bool "EABIhf"
|
2015-12-26 17:05:43 +01:00
|
|
|
depends on BR2_ARM_CPU_HAS_VFPV2
|
2013-07-16 10:03:13 +02:00
|
|
|
help
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
The EABIhf is an extension of EABI which supports the 'hard'
|
|
|
|
|
floating point model. This model uses the floating point
|
|
|
|
|
unit to execute floating point instructions, and passes
|
|
|
|
|
floating point arguments in floating point registers.
|
|
|
|
|
|
|
|
|
|
It is more efficient than EABI for floating point related
|
|
|
|
|
workload. However, it does not allow to link against code
|
|
|
|
|
that has been pre-built for the 'soft' or 'softfp' floating
|
|
|
|
|
point models.
|
|
|
|
|
|
|
|
|
|
If your processor has a floating point unit, and you don't
|
|
|
|
|
depend on existing pre-compiled code, this option is most
|
|
|
|
|
likely the best choice.
|
|
|
|
|
|
|
|
|
|
endchoice
|
2013-07-16 10:03:13 +02:00
|
|
|
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
choice
|
|
|
|
|
prompt "Floating point strategy"
|
2016-11-30 22:12:08 +01:00
|
|
|
default BR2_ARM_FPU_FP_ARMV8 if BR2_ARM_CPU_HAS_FP_ARMV8
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
default BR2_ARM_FPU_VFPV4D16 if BR2_ARM_CPU_HAS_VFPV4
|
|
|
|
|
default BR2_ARM_FPU_VFPV3D16 if BR2_ARM_CPU_HAS_VFPV3
|
|
|
|
|
default BR2_ARM_FPU_VFPV2 if BR2_ARM_CPU_HAS_VFPV2
|
|
|
|
|
default BR2_ARM_SOFT_FLOAT if !BR2_ARM_CPU_HAS_VFPV2
|
|
|
|
|
|
|
|
|
|
config BR2_ARM_SOFT_FLOAT
|
|
|
|
|
bool "Soft float"
|
|
|
|
|
depends on BR2_ARM_EABI
|
|
|
|
|
select BR2_SOFT_FLOAT
|
|
|
|
|
help
|
|
|
|
|
This option allows to use software emulated floating
|
|
|
|
|
point. It should be used for ARM cores that do not include a
|
|
|
|
|
Vector Floating Point unit, such as ARMv5 cores (ARM926 for
|
|
|
|
|
example) or certain ARMv6 cores.
|
|
|
|
|
|
|
|
|
|
config BR2_ARM_FPU_VFPV2
|
|
|
|
|
bool "VFPv2"
|
2015-12-26 17:05:44 +01:00
|
|
|
depends on BR2_ARM_CPU_HAS_VFPV2
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
help
|
|
|
|
|
This option allows to use the VFPv2 floating point unit, as
|
2013-07-17 22:30:50 +02:00
|
|
|
available in some ARMv5 processors (ARM926EJ-S) and some
|
|
|
|
|
ARMv6 processors (ARM1136JF-S, ARM1176JZF-S and ARM11
|
|
|
|
|
MPCore).
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
|
|
|
|
|
Note that this option is also safe to use for newer cores
|
|
|
|
|
such as Cortex-A, because the VFPv3 and VFPv4 units are
|
|
|
|
|
backward compatible with VFPv2.
|
|
|
|
|
|
|
|
|
|
config BR2_ARM_FPU_VFPV3
|
|
|
|
|
bool "VFPv3"
|
2015-12-26 17:05:44 +01:00
|
|
|
depends on BR2_ARM_CPU_HAS_VFPV3
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
help
|
|
|
|
|
This option allows to use the VFPv3 floating point unit, as
|
|
|
|
|
available in some ARMv7 processors (Cortex-A{8, 9}). This
|
|
|
|
|
option requires a VFPv3 unit that has 32 double-precision
|
|
|
|
|
registers, which is not necessarily the case in all SOCs
|
|
|
|
|
based on Cortex-A{8, 9}. If you're unsure, use VFPv3-D16
|
|
|
|
|
instead, which is guaranteed to work on all Cortex-A{8, 9}.
|
|
|
|
|
|
|
|
|
|
Note that this option is also safe to use for newer cores
|
|
|
|
|
that have a VFPv4 unit, because VFPv4 is backward compatible
|
|
|
|
|
with VFPv3. They must of course also have 32
|
|
|
|
|
double-precision registers.
|
|
|
|
|
|
|
|
|
|
config BR2_ARM_FPU_VFPV3D16
|
|
|
|
|
bool "VFPv3-D16"
|
2015-12-26 17:05:44 +01:00
|
|
|
depends on BR2_ARM_CPU_HAS_VFPV3
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
help
|
|
|
|
|
This option allows to use the VFPv3 floating point unit, as
|
|
|
|
|
available in some ARMv7 processors (Cortex-A{8, 9}). This
|
|
|
|
|
option requires a VFPv3 unit that has 16 double-precision
|
|
|
|
|
registers, which is generally the case in all SOCs based on
|
|
|
|
|
Cortex-A{8, 9}, even though VFPv3 is technically optional on
|
|
|
|
|
Cortex-A9. This is the safest option for those cores.
|
|
|
|
|
|
|
|
|
|
Note that this option is also safe to use for newer cores
|
|
|
|
|
such that have a VFPv4 unit, because the VFPv4 is backward
|
|
|
|
|
compatible with VFPv3.
|
|
|
|
|
|
|
|
|
|
config BR2_ARM_FPU_VFPV4
|
|
|
|
|
bool "VFPv4"
|
2015-12-26 17:05:44 +01:00
|
|
|
depends on BR2_ARM_CPU_HAS_VFPV4
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
help
|
|
|
|
|
This option allows to use the VFPv4 floating point unit, as
|
|
|
|
|
available in some ARMv7 processors (Cortex-A{5, 7, 12,
|
|
|
|
|
15}). This option requires a VFPv4 unit that has 32
|
|
|
|
|
double-precision registers, which is not necessarily the
|
|
|
|
|
case in all SOCs based on Cortex-A{5, 7, 12, 15}. If you're
|
|
|
|
|
unsure, you should probably use VFPv4-D16 instead.
|
|
|
|
|
|
|
|
|
|
Note that if you want binary code that works on all ARMv7
|
|
|
|
|
cores, including the earlier Cortex-A{8, 9}, you should
|
|
|
|
|
instead select VFPv3.
|
|
|
|
|
|
|
|
|
|
config BR2_ARM_FPU_VFPV4D16
|
|
|
|
|
bool "VFPv4-D16"
|
2015-12-26 17:05:44 +01:00
|
|
|
depends on BR2_ARM_CPU_HAS_VFPV4
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
help
|
|
|
|
|
This option allows to use the VFPv4 floating point unit, as
|
|
|
|
|
available in some ARMv7 processors (Cortex-A{5, 7, 12,
|
|
|
|
|
15}). This option requires a VFPv4 unit that has 16
|
|
|
|
|
double-precision registers, which is always available on
|
|
|
|
|
Cortex-A12 and Cortex-A15, but optional on Cortex-A5 and
|
|
|
|
|
Cortex-A7.
|
|
|
|
|
|
|
|
|
|
Note that if you want binary code that works on all ARMv7
|
|
|
|
|
cores, including the earlier Cortex-A{8, 9}, you should
|
|
|
|
|
instead select VFPv3-D16.
|
|
|
|
|
|
|
|
|
|
config BR2_ARM_FPU_NEON
|
|
|
|
|
bool "NEON"
|
|
|
|
|
depends on BR2_ARM_CPU_HAS_NEON
|
|
|
|
|
help
|
|
|
|
|
This option allows to use the NEON SIMD unit, as available
|
|
|
|
|
in some ARMv7 processors, as a floating-point unit. It
|
|
|
|
|
should however be noted that using NEON for floating point
|
|
|
|
|
operations doesn't provide a complete compatibility with the
|
|
|
|
|
IEEE 754.
|
|
|
|
|
|
|
|
|
|
config BR2_ARM_FPU_NEON_VFPV4
|
|
|
|
|
bool "NEON/VFPv4"
|
2015-12-26 17:05:44 +01:00
|
|
|
depends on BR2_ARM_CPU_HAS_VFPV4
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
depends on BR2_ARM_CPU_HAS_NEON
|
|
|
|
|
help
|
|
|
|
|
This option allows to use both the VFPv4 and the NEON SIMD
|
|
|
|
|
units for floating point operations. Note that some ARMv7
|
|
|
|
|
cores do not necessarily have VFPv4 and/or NEON support, for
|
|
|
|
|
example on Cortex-A5 and Cortex-A7, support for VFPv4 and
|
|
|
|
|
NEON is optional.
|
|
|
|
|
|
2016-11-30 22:12:08 +01:00
|
|
|
config BR2_ARM_FPU_FP_ARMV8
|
|
|
|
|
bool "FP-ARMv8"
|
|
|
|
|
depends on BR2_ARM_CPU_HAS_FP_ARMV8
|
|
|
|
|
help
|
|
|
|
|
This option allows to use the ARMv8 floating point unit.
|
|
|
|
|
|
|
|
|
|
config BR2_ARM_FPU_NEON_FP_ARMV8
|
|
|
|
|
bool "NEON/FP-ARMv8"
|
|
|
|
|
depends on BR2_ARM_CPU_HAS_FP_ARMV8
|
|
|
|
|
depends on BR2_ARM_CPU_HAS_NEON
|
|
|
|
|
help
|
|
|
|
|
This option allows to use both the ARMv8 floating point unit
|
|
|
|
|
and the NEON SIMD unit for floating point operations.
|
|
|
|
|
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
endchoice
|
|
|
|
|
|
2013-07-16 10:03:22 +02:00
|
|
|
choice
|
|
|
|
|
prompt "ARM instruction set"
|
arch: merge Config.in.aarch64 into Config.in.arm
The 64 bits ARM processors are capable of running 32 bits ARM code, and
some platforms are indeed using this capability. Due to this, if we were
to keep the separation between Config.in.aarch64 and Config.in.arm, we
would have to duplicate the definition of all 64-bits capable ARM cores
into both files.
Instead of going down this route, let's take the same route as the x86
one: a single Config.in.x86 file, used for both x86 32 bits and x86 64
bits, with the appropriate logic to only show the relevant cores
depending on which architecture is selected.
In order to do this, we:
- Make the "ARM instruction set" choice only visible on ARM 32 bits,
since we currently don't support ARM vs. Thumb on AArch64.
- Add the relevant values for the BR2_ARCH option.
- Add the relevant values for the BR2_ENDIAN option.
- Make the "aapcs-linux" BR2_GCC_TARGET_ABI value only used on ARM 32
bits, since this ABI doesn't mean anything on AArch64.
- Make the BR2_GCC_TARGET_FPU option depends on ARM 32 bits, since
there is no -mfpu option on AArch64.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-11-30 22:12:04 +01:00
|
|
|
depends on BR2_arm || BR2_armeb
|
2013-07-16 10:03:22 +02:00
|
|
|
|
2015-01-22 19:33:25 +01:00
|
|
|
config BR2_ARM_INSTRUCTIONS_ARM
|
2013-07-16 10:03:22 +02:00
|
|
|
bool "ARM"
|
2015-01-22 19:33:25 +01:00
|
|
|
depends on BR2_ARM_CPU_HAS_ARM
|
2013-07-16 10:03:22 +02:00
|
|
|
help
|
|
|
|
|
This option instructs the compiler to generate regular ARM
|
|
|
|
|
instructions, that are all 32 bits wide.
|
|
|
|
|
|
2013-07-17 17:39:15 +02:00
|
|
|
config BR2_ARM_INSTRUCTIONS_THUMB
|
|
|
|
|
bool "Thumb"
|
|
|
|
|
depends on BR2_ARM_CPU_HAS_THUMB
|
2015-11-03 00:34:37 +01:00
|
|
|
# Thumb-1 and VFP are not compatible
|
|
|
|
|
depends on BR2_ARM_SOFT_FLOAT
|
2013-07-17 17:39:15 +02:00
|
|
|
help
|
|
|
|
|
This option instructions the compiler to generate Thumb
|
|
|
|
|
instructions, which allows to mix 16 bits instructions and
|
|
|
|
|
32 bits instructions. This generally provides a much smaller
|
|
|
|
|
compiled binary size.
|
|
|
|
|
|
2015-11-03 00:34:37 +01:00
|
|
|
comment "Thumb1 is not compatible with VFP"
|
|
|
|
|
depends on BR2_ARM_CPU_HAS_THUMB
|
|
|
|
|
depends on !BR2_ARM_SOFT_FLOAT
|
|
|
|
|
|
2013-07-16 10:03:22 +02:00
|
|
|
config BR2_ARM_INSTRUCTIONS_THUMB2
|
|
|
|
|
bool "Thumb2"
|
2013-07-17 17:39:15 +02:00
|
|
|
depends on BR2_ARM_CPU_HAS_THUMB2
|
2013-07-16 10:03:22 +02:00
|
|
|
help
|
|
|
|
|
This option instructions the compiler to generate Thumb2
|
|
|
|
|
instructions, which allows to mix 16 bits instructions and
|
|
|
|
|
32 bits instructions. This generally provides a much smaller
|
|
|
|
|
compiled binary size.
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
arch: improve definition of gcc mtune, mcpu, etc.
As suggested by Yann E. Morin, there is a better way than our current
big Config.in.common to define the gcc mtune, mcpu, march,
etc. values. We can split the setting of those values in each
architecture file, which makes a lot more sense.
Therefore, the Config.in file now creates empty kconfig variables
BR2_ARCH, BR2_ENDIAN, BR2_GCC_TARGET_TUNE, BR2_GCC_TARGET_ARCH,
BR2_GCC_TARGET_ABI and BR2_GCC_TARGET_CPU. The values of those
variables are set by the individual Config.in.<arch> files. This is
possible because such files are now only conditionally included
depending on the top-level architecture that has been selected.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-15 04:53:48 +01:00
|
|
|
config BR2_ARCH
|
arch: merge Config.in.aarch64 into Config.in.arm
The 64 bits ARM processors are capable of running 32 bits ARM code, and
some platforms are indeed using this capability. Due to this, if we were
to keep the separation between Config.in.aarch64 and Config.in.arm, we
would have to duplicate the definition of all 64-bits capable ARM cores
into both files.
Instead of going down this route, let's take the same route as the x86
one: a single Config.in.x86 file, used for both x86 32 bits and x86 64
bits, with the appropriate logic to only show the relevant cores
depending on which architecture is selected.
In order to do this, we:
- Make the "ARM instruction set" choice only visible on ARM 32 bits,
since we currently don't support ARM vs. Thumb on AArch64.
- Add the relevant values for the BR2_ARCH option.
- Add the relevant values for the BR2_ENDIAN option.
- Make the "aapcs-linux" BR2_GCC_TARGET_ABI value only used on ARM 32
bits, since this ABI doesn't mean anything on AArch64.
- Make the BR2_GCC_TARGET_FPU option depends on ARM 32 bits, since
there is no -mfpu option on AArch64.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-11-30 22:12:04 +01:00
|
|
|
default "arm" if BR2_arm
|
|
|
|
|
default "armeb" if BR2_armeb
|
|
|
|
|
default "aarch64" if BR2_aarch64
|
|
|
|
|
default "aarch64_be" if BR2_aarch64_be
|
arch: improve definition of gcc mtune, mcpu, etc.
As suggested by Yann E. Morin, there is a better way than our current
big Config.in.common to define the gcc mtune, mcpu, march,
etc. values. We can split the setting of those values in each
architecture file, which makes a lot more sense.
Therefore, the Config.in file now creates empty kconfig variables
BR2_ARCH, BR2_ENDIAN, BR2_GCC_TARGET_TUNE, BR2_GCC_TARGET_ARCH,
BR2_GCC_TARGET_ABI and BR2_GCC_TARGET_CPU. The values of those
variables are set by the individual Config.in.<arch> files. This is
possible because such files are now only conditionally included
depending on the top-level architecture that has been selected.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-15 04:53:48 +01:00
|
|
|
|
|
|
|
|
config BR2_ENDIAN
|
arch: merge Config.in.aarch64 into Config.in.arm
The 64 bits ARM processors are capable of running 32 bits ARM code, and
some platforms are indeed using this capability. Due to this, if we were
to keep the separation between Config.in.aarch64 and Config.in.arm, we
would have to duplicate the definition of all 64-bits capable ARM cores
into both files.
Instead of going down this route, let's take the same route as the x86
one: a single Config.in.x86 file, used for both x86 32 bits and x86 64
bits, with the appropriate logic to only show the relevant cores
depending on which architecture is selected.
In order to do this, we:
- Make the "ARM instruction set" choice only visible on ARM 32 bits,
since we currently don't support ARM vs. Thumb on AArch64.
- Add the relevant values for the BR2_ARCH option.
- Add the relevant values for the BR2_ENDIAN option.
- Make the "aapcs-linux" BR2_GCC_TARGET_ABI value only used on ARM 32
bits, since this ABI doesn't mean anything on AArch64.
- Make the BR2_GCC_TARGET_FPU option depends on ARM 32 bits, since
there is no -mfpu option on AArch64.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-11-30 22:12:04 +01:00
|
|
|
default "LITTLE" if (BR2_arm || BR2_aarch64)
|
|
|
|
|
default "BIG" if (BR2_armeb || BR2_aarch64_be)
|
arch: improve definition of gcc mtune, mcpu, etc.
As suggested by Yann E. Morin, there is a better way than our current
big Config.in.common to define the gcc mtune, mcpu, march,
etc. values. We can split the setting of those values in each
architecture file, which makes a lot more sense.
Therefore, the Config.in file now creates empty kconfig variables
BR2_ARCH, BR2_ENDIAN, BR2_GCC_TARGET_TUNE, BR2_GCC_TARGET_ARCH,
BR2_GCC_TARGET_ABI and BR2_GCC_TARGET_CPU. The values of those
variables are set by the individual Config.in.<arch> files. This is
possible because such files are now only conditionally included
depending on the top-level architecture that has been selected.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-15 04:53:48 +01:00
|
|
|
|
2013-11-02 16:39:06 +01:00
|
|
|
config BR2_GCC_TARGET_CPU
|
2012-11-15 04:53:53 +01:00
|
|
|
default "arm920t" if BR2_arm920t
|
|
|
|
|
default "arm922t" if BR2_arm922t
|
|
|
|
|
default "arm926ej-s" if BR2_arm926t
|
|
|
|
|
default "arm1136j-s" if BR2_arm1136j_s
|
|
|
|
|
default "arm1136jf-s" if BR2_arm1136jf_s
|
|
|
|
|
default "arm1176jz-s" if BR2_arm1176jz_s
|
|
|
|
|
default "arm1176jzf-s" if BR2_arm1176jzf_s
|
2015-11-28 15:55:21 +01:00
|
|
|
default "mpcore" if BR2_arm11mpcore && BR2_ARM_CPU_HAS_VFPV2
|
|
|
|
|
default "mpcorenovfp" if BR2_arm11mpcore
|
2012-12-09 12:54:03 +01:00
|
|
|
default "cortex-a5" if BR2_cortex_a5
|
2013-06-09 04:53:50 +02:00
|
|
|
default "cortex-a7" if BR2_cortex_a7
|
2012-11-15 04:53:53 +01:00
|
|
|
default "cortex-a8" if BR2_cortex_a8
|
|
|
|
|
default "cortex-a9" if BR2_cortex_a9
|
2014-04-24 03:00:31 +02:00
|
|
|
default "cortex-a12" if BR2_cortex_a12
|
2012-12-09 12:54:03 +01:00
|
|
|
default "cortex-a15" if BR2_cortex_a15
|
2016-02-21 14:12:10 +01:00
|
|
|
default "cortex-a17" if BR2_cortex_a17
|
2015-06-26 19:33:19 +02:00
|
|
|
default "cortex-m3" if BR2_cortex_m3
|
2016-03-18 22:08:05 +01:00
|
|
|
default "cortex-m4" if BR2_cortex_m4
|
2013-04-04 09:29:45 +02:00
|
|
|
default "fa526" if BR2_fa526
|
2013-04-29 10:54:24 +02:00
|
|
|
default "marvell-pj4" if BR2_pj4
|
2013-04-04 09:29:45 +02:00
|
|
|
default "strongarm" if BR2_strongarm
|
2012-11-15 04:53:53 +01:00
|
|
|
default "xscale" if BR2_xscale
|
|
|
|
|
default "iwmmxt" if BR2_iwmmxt
|
2016-11-30 22:12:10 +01:00
|
|
|
default "cortex-a53" if (BR2_cortex_a53 && !BR2_ARCH_IS_64)
|
|
|
|
|
default "cortex-a53+fp" if (BR2_cortex_a53 && BR2_ARCH_IS_64 && BR2_ARM_FPU_FP_ARMV8)
|
|
|
|
|
default "cortex-a53+fp+simd" if (BR2_cortex_a53 && BR2_ARCH_IS_64 && BR2_ARM_FPU_NEON_FP_ARMV8)
|
2016-11-30 22:12:11 +01:00
|
|
|
default "cortex-a57" if (BR2_cortex_a57 && !BR2_ARCH_IS_64)
|
|
|
|
|
default "cortex-a57+fp" if (BR2_cortex_a57 && BR2_ARCH_IS_64 && BR2_ARM_FPU_FP_ARMV8)
|
|
|
|
|
default "cortex-a57+fp+simd" if (BR2_cortex_a57 && BR2_ARCH_IS_64 && BR2_ARM_FPU_NEON_FP_ARMV8)
|
|
|
|
|
default "cortex-a72" if (BR2_cortex_a72 && !BR2_ARCH_IS_64)
|
|
|
|
|
default "cortex-a72+fp" if (BR2_cortex_a72 && BR2_ARCH_IS_64 && BR2_ARM_FPU_FP_ARMV8)
|
|
|
|
|
default "cortex-a72+fp+simd" if (BR2_cortex_a72 && BR2_ARCH_IS_64 && BR2_ARM_FPU_NEON_FP_ARMV8)
|
arch: improve definition of gcc mtune, mcpu, etc.
As suggested by Yann E. Morin, there is a better way than our current
big Config.in.common to define the gcc mtune, mcpu, march,
etc. values. We can split the setting of those values in each
architecture file, which makes a lot more sense.
Therefore, the Config.in file now creates empty kconfig variables
BR2_ARCH, BR2_ENDIAN, BR2_GCC_TARGET_TUNE, BR2_GCC_TARGET_ARCH,
BR2_GCC_TARGET_ABI and BR2_GCC_TARGET_CPU. The values of those
variables are set by the individual Config.in.<arch> files. This is
possible because such files are now only conditionally included
depending on the top-level architecture that has been selected.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-15 04:53:48 +01:00
|
|
|
|
|
|
|
|
config BR2_GCC_TARGET_ABI
|
arch: merge Config.in.aarch64 into Config.in.arm
The 64 bits ARM processors are capable of running 32 bits ARM code, and
some platforms are indeed using this capability. Due to this, if we were
to keep the separation between Config.in.aarch64 and Config.in.arm, we
would have to duplicate the definition of all 64-bits capable ARM cores
into both files.
Instead of going down this route, let's take the same route as the x86
one: a single Config.in.x86 file, used for both x86 32 bits and x86 64
bits, with the appropriate logic to only show the relevant cores
depending on which architecture is selected.
In order to do this, we:
- Make the "ARM instruction set" choice only visible on ARM 32 bits,
since we currently don't support ARM vs. Thumb on AArch64.
- Add the relevant values for the BR2_ARCH option.
- Add the relevant values for the BR2_ENDIAN option.
- Make the "aapcs-linux" BR2_GCC_TARGET_ABI value only used on ARM 32
bits, since this ABI doesn't mean anything on AArch64.
- Make the BR2_GCC_TARGET_FPU option depends on ARM 32 bits, since
there is no -mfpu option on AArch64.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-11-30 22:12:04 +01:00
|
|
|
default "aapcs-linux" if BR2_arm || BR2_armeb
|
2016-11-30 22:12:09 +01:00
|
|
|
default "lp64" if BR2_aarch64 || BR2_aarch64_be
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
|
|
|
|
|
config BR2_GCC_TARGET_FPU
|
arch: merge Config.in.aarch64 into Config.in.arm
The 64 bits ARM processors are capable of running 32 bits ARM code, and
some platforms are indeed using this capability. Due to this, if we were
to keep the separation between Config.in.aarch64 and Config.in.arm, we
would have to duplicate the definition of all 64-bits capable ARM cores
into both files.
Instead of going down this route, let's take the same route as the x86
one: a single Config.in.x86 file, used for both x86 32 bits and x86 64
bits, with the appropriate logic to only show the relevant cores
depending on which architecture is selected.
In order to do this, we:
- Make the "ARM instruction set" choice only visible on ARM 32 bits,
since we currently don't support ARM vs. Thumb on AArch64.
- Add the relevant values for the BR2_ARCH option.
- Add the relevant values for the BR2_ENDIAN option.
- Make the "aapcs-linux" BR2_GCC_TARGET_ABI value only used on ARM 32
bits, since this ABI doesn't mean anything on AArch64.
- Make the BR2_GCC_TARGET_FPU option depends on ARM 32 bits, since
there is no -mfpu option on AArch64.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-11-30 22:12:04 +01:00
|
|
|
depends on BR2_arm || BR2_armeb
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
default "vfp" if BR2_ARM_FPU_VFPV2
|
|
|
|
|
default "vfpv3" if BR2_ARM_FPU_VFPV3
|
|
|
|
|
default "vfpv3-d16" if BR2_ARM_FPU_VFPV3D16
|
|
|
|
|
default "vfpv4" if BR2_ARM_FPU_VFPV4
|
|
|
|
|
default "vfpv4-d16" if BR2_ARM_FPU_VFPV4D16
|
|
|
|
|
default "neon" if BR2_ARM_FPU_NEON
|
|
|
|
|
default "neon-vfpv4" if BR2_ARM_FPU_NEON_VFPV4
|
2016-11-30 22:12:08 +01:00
|
|
|
default "fp-armv8" if BR2_ARM_FPU_FP_ARMV8
|
|
|
|
|
default "neon-fp-armv8" if BR2_ARM_FPU_NEON_FP_ARMV8
|
arch: improve ARM floating point support and add support for EABIhf
This commit introduces the support for the EABIhf ABI, next to the
existing support we have for EABI and OABI (even though OABI support
is deprecated). EABIhf allows to improve performance of floating point
workload by using floating point registers to transfer floating point
arguments when calling functions, instead of using integer registers
to do, as is done in the 'softfp' floating point model of EABI.
In addition to this, this commit introduces a list of options for the
floating point support:
* Software floating point
* VFP
* VFPv3
* VFPv3-D16
* VFPv4
* VFPv4-D16
and it introduces some logic to make sure the options are only visible
when it makes sense, depending on the ARM core being selected. This is
however made complicated by the fact that certain VFP capabilities are
mandatory on some cores, but optional on some other cores. The kconfig
logic tries to achieve the following goals:
* Hide options that are definitely not possible.
* Use safe default values (i.e for Cortex-A5 and A7, the presence of
the VFPv4 unit is optional, so we default on software floating
point on these cores)..
* Show the available possibilities, even if some of them are not
necessarily working on a particular core (again, for the Cortex-A5
and A7 cores, there is no way of knowing whether the particular
variant used by the user has VFPv4 or not, so we select software
floating point by default, but still show VFP/VFPv3/VFPv4 options).
It is worth noting that this commit doesn't add support for all
possible -mfpu= values on ARM. We haven't added support for fpa, fpe2,
fpe3, maverick (those four are only used on very old ARM cores), for
vfpv3-fp16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-fp16,
vfpv4-sp-d16. They can be added quite easily if needed thanks to the
new organization of the Config.in options.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-16 10:03:14 +02:00
|
|
|
|
|
|
|
|
config BR2_GCC_TARGET_FLOAT_ABI
|
|
|
|
|
default "soft" if BR2_ARM_SOFT_FLOAT
|
|
|
|
|
default "softfp" if !BR2_ARM_SOFT_FLOAT && BR2_ARM_EABI
|
|
|
|
|
default "hard" if !BR2_ARM_SOFT_FLOAT && BR2_ARM_EABIHF
|
2013-07-16 10:03:22 +02:00
|
|
|
|
|
|
|
|
config BR2_GCC_TARGET_MODE
|
|
|
|
|
default "arm" if BR2_ARM_INSTRUCTIONS_ARM
|
2013-07-17 17:39:15 +02:00
|
|
|
default "thumb" if BR2_ARM_INSTRUCTIONS_THUMB || BR2_ARM_INSTRUCTIONS_THUMB2
|
