buildroot/arch/Config.in.microblaze, branch 2017.02.1

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"

arch/microblaze: always has atomic ops

2014-08-18T09:02:31+00:00

Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Cc: Anton Kolesov Signed-off-by: Peter Korsgaard

Fix microblize little endian toolchain

2014-03-20T15:46:29+00:00

Buildroot toolchain creates big endian binaries instead of little endian ones for microblaze architecture. The reason is wrong BR2_ARCH string. KERNEL_ARCH must contain microblaze in both cases. Signed-off-by: Jan Drazil Signed-off-by: Jan Viktorin Acked-by: Gustavo Zacarias Tested-by: Gustavo Zacarias Signed-off-by: Peter Korsgaard

arch: improve definition of gcc mtune, mcpu, etc.

2012-11-15T15:12:46+00:00

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. 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 Acked-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard