buildroot/arch, branch 2016.02

arch: remove BR2_ARCH_HAS_ATOMICS option

2016-02-06T10:16:00+00:00

Now that BR2_ARCH_HAS_ATOMICS is no longer used anywhere, we can remove it from arch/Config.in*, as well as from the documentation. Signed-off-by: Thomas Petazzoni Acked-by: "Yann E. MORIN"

Add ARM11 MPCore CPU target support

2016-01-03T21:35:22+00:00

gcc differentiates the mpcore-with-vfp from the mcpore-without-vfp CPUs. The former is named just 'mpcore', while the latter is named 'mpcorenovfp'. We only add one entry, 'mpcore' and let the user select whether or not to use the VFP. We then name the CPU according to the user's selection. Signed-off-by: Sergi Granell Tested-by: "Yann E. MORIN" Acked-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

arch/arm: add help text to BR2_ARM_ENABLE_VFP

2015-12-27T11:22:43+00:00

Signed-off-by: Thomas Petazzoni

arch/arm: only expose VFP in FP strategy when the CPU has a VFP unit

2015-12-27T11:17:48+00:00

There's no point in offering the user an option to select an FP strategy when the CPU does not actually have a VFP unit. Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

arch/arm: only expose EABIhf when the CPU has a VFP unit

2015-12-27T11:17:36+00:00

There's no point in offering the user an option to select EABIhf when the CPU does not really have a VFP unit. Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

arch/arm: add option to enable an optional VFP unit

2015-12-27T11:17:23+00:00

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" Cc: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

arch/arm: reorder NEON option

2015-12-27T11:16:45+00:00

Stating whether to use the NEON extensions when it is optional in the CPU really is completing the definition of the CPU we've just selected. Move the ENABLE_NEON option just after the choice of the CPU variant, and before any "software" option (ABI/VFP). This will make sense in a moment, when we introduce a similar option for enabling an optional VFP unit. Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

arch: add tune options for powerpc e5500 and e6500

2015-11-16T23:16:39+00:00

These were forgotten when the subarches were added in cd88e49. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Cc: Alvaro Gamez Cc: Gustavo Zacarias Tested-by: Alvaro G. M Signed-off-by: Peter Korsgaard

arch/arm: VFP and Thumb1 are not compatible

2015-11-03T22:50:01+00:00

gcc will refuse to build with both --with-mode=thumb and --with-fpu=vfp, with error messages during ./configure, like: checking for suffix of object files... configure: error: in `/home/ymor in/dev/buildroot/O/build/host-gcc-initial-4.9.3/build/arm-buildroot-lin ux-uclibcgnueabihf/libgcc': configure: error: cannot compute suffix of object files: cannot compile See `config.log' for more details. And config.log informatively contains: sorry, unimplemented: Thumb-1 hard-float VFP ABI This is an error message that comes deep from gcc source files. If gcc says it does not support VFP with Thumb1, then let's disable that combination in our menuconfig. Prefer VFP over Thumb1, i.e. hide Thumb1 when we're not soft-float. Signed-off-by: "Yann E. MORIN" Cc: Gustavo Zacarias Cc: Thomas Petazzoni Acked-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

arch/arm: use EABIhf by default with VFP

2015-10-25T18:56:20+00:00

Set EABIhf as the default target ABI for the ARM processors that have or may have a VFP unit, since this ABI is the most efficient in that case. Of course, EABI can still be selected manually if needed. [Peter: only default to EABIHF when we are sure the CPU has a VFP] Signed-off-by: Benoît Thébaudeau Signed-off-by: Peter Korsgaard