2014-10-30 14:57:27 +01:00
|
|
|
choice
|
|
|
|
|
prompt "Target CPU"
|
|
|
|
|
default BR2_arc770d
|
2018-04-01 07:08:34 +02:00
|
|
|
depends on BR2_arc
|
2014-10-30 14:57:27 +01:00
|
|
|
help
|
|
|
|
|
Specific CPU to use
|
|
|
|
|
|
|
|
|
|
config BR2_arc750d
|
|
|
|
|
bool "ARC 750D"
|
|
|
|
|
|
|
|
|
|
config BR2_arc770d
|
|
|
|
|
bool "ARC 770D"
|
|
|
|
|
|
2014-10-30 14:57:29 +01:00
|
|
|
config BR2_archs38
|
|
|
|
|
bool "ARC HS38"
|
2018-11-08 22:59:40 +01:00
|
|
|
help
|
|
|
|
|
Generic ARC HS capable of running Linux, i.e. with MMU,
|
2019-11-12 16:34:43 +01:00
|
|
|
caches and 32-bit multiplier. Also it corresponds to the
|
|
|
|
|
default configuration in older GNU toolchain versions.
|
2018-11-08 22:59:40 +01:00
|
|
|
|
2019-11-12 16:34:43 +01:00
|
|
|
config BR2_archs38_64mpy
|
|
|
|
|
bool "ARC HS38 with 64-bit mpy"
|
|
|
|
|
help
|
|
|
|
|
Fully featured ARC HS capable of running Linux, i.e. with
|
|
|
|
|
MMU, caches and 64-bit multiplier.
|
|
|
|
|
|
|
|
|
|
If you're not sure which version of ARC HS core you build
|
|
|
|
|
for use this one.
|
2018-11-08 22:59:40 +01:00
|
|
|
|
|
|
|
|
config BR2_archs38_full
|
|
|
|
|
bool "ARC HS38 with Quad MAC & FPU"
|
|
|
|
|
help
|
|
|
|
|
Fully featured ARC HS with additional support for
|
|
|
|
|
- Dual- and quad multiply and MC oprations
|
|
|
|
|
- Double-precision FPU
|
|
|
|
|
|
|
|
|
|
It corresponds to "hs38_slc_full" ARC HS template in
|
|
|
|
|
ARChitect.
|
2014-10-30 14:57:29 +01:00
|
|
|
|
2019-06-04 07:39:27 +02:00
|
|
|
config BR2_archs4x_rel31
|
|
|
|
|
bool "ARC HS48 rel 31"
|
2021-01-15 21:03:16 +01:00
|
|
|
help
|
|
|
|
|
Build for HS48 release 3.1
|
|
|
|
|
|
|
|
|
|
config BR2_archs4x
|
|
|
|
|
bool "ARC HS48"
|
2019-06-04 07:39:27 +02:00
|
|
|
help
|
|
|
|
|
Latest release of HS48 processor
|
2021-01-15 21:03:16 +01:00
|
|
|
- Dual and Quad multiply and MAC operations
|
2019-06-04 07:39:27 +02:00
|
|
|
- Double-precision FPU
|
|
|
|
|
|
2014-10-30 14:57:27 +01:00
|
|
|
endchoice
|
|
|
|
|
|
|
|
|
|
# Choice of atomic instructions presence
|
2014-07-31 15:24:42 +02:00
|
|
|
config BR2_ARC_ATOMIC_EXT
|
|
|
|
|
bool "Atomic extension (LLOCK/SCOND instructions)"
|
2021-01-15 21:03:16 +01:00
|
|
|
default y if BR2_arc770d
|
|
|
|
|
default y if BR2_archs38 || BR2_archs38_64mpy || BR2_archs38_full
|
|
|
|
|
default y if BR2_archs4x_rel31 || BR2_archs4x
|
2014-09-11 22:46:46 +02:00
|
|
|
|
2013-05-02 11:51:23 +02:00
|
|
|
config BR2_ARCH
|
|
|
|
|
default "arc" if BR2_arcle
|
|
|
|
|
default "arceb" if BR2_arceb
|
|
|
|
|
|
core: introduce NORMALIZED_ARCH as non-kernel replacement for KERNEL_ARCH
The variable 'KERNEL_ARCH' is actually a normalized version of
'ARCH'/'BR2_ARCH'. For example, 'arcle' and 'arceb' both become 'arc', just
as all powerpc variants become 'powerpc'.
It is presumably called 'KERNEL_ARCH' because the Linux kernel is typically
the first place where support for a new architecture is added, and thus is
the entity that defines the normalized name.
However, the term 'KERNEL_ARCH' can also be interpreted as 'the architecture
used by the kernel', which need not be exactly the same as 'the normalized
name for a certain arch'. In particular, for cases where a 64-bit
architecture is running a 64-bit kernel but 32-bit userspace. Examples
include:
* aarch64 architecture, with aarch64 kernel and 32-bit (ARM) userspace
* x86_64 architecture, with x86_64 kernel and 32-bit (i386) userspace
In such cases, the 'architecture used by the kernel' needs to refer to the
64-bit name (aarch64, x86_64), whereas all userspace applications need to
refer the, potentially normalized, 32-bit name.
This means that there need to be two different variables:
KERNEL_ARCH: the architecture used by the kernel
NORMALIZED_ARCH: the normalized name for the current userspace architecture
At this moment, both will actually have the same content. But a subsequent
patch will add basic support for situations described above, in which
KERNEL_ARCH may become overwritten to the 64-bit architecture, while
NORMALIZED_ARCH needs to remain the same (32-bit) case.
This commit replaces use of KERNEL_ARCH where actually the userspace arch is
needed. Places that use KERNEL_ARCH in combination with building of kernel
modules are not touched.
There may be cases where a package builds both a kernel module as userspace,
in which case it may need to know about both KERNEL_ARCH and
NORMALIZED_ARCH, for the case where they differ. But this is to be fixed on
a per-need basis.
Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Reviewed-by: Romain Naour <romain.naour@gmail.com>
[Arnout: Also rename BR2_KERNEL_ARCH to BR2_NORMALIZED_ARCH]
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2022-01-15 21:03:00 +01:00
|
|
|
config BR2_NORMALIZED_ARCH
|
2022-01-15 21:02:59 +01:00
|
|
|
default "arc"
|
|
|
|
|
|
2013-05-02 11:51:23 +02:00
|
|
|
config BR2_arc
|
|
|
|
|
bool
|
|
|
|
|
default y if BR2_arcle || BR2_arceb
|
|
|
|
|
|
|
|
|
|
config BR2_ENDIAN
|
|
|
|
|
default "LITTLE" if BR2_arcle
|
|
|
|
|
default "BIG" if BR2_arceb
|
|
|
|
|
|
|
|
|
|
config BR2_GCC_TARGET_CPU
|
2014-10-30 14:57:27 +01:00
|
|
|
default "arc700" if BR2_arc750d
|
|
|
|
|
default "arc700" if BR2_arc770d
|
2014-10-30 14:57:29 +01:00
|
|
|
default "archs" if BR2_archs38
|
2019-11-12 16:34:43 +01:00
|
|
|
default "hs38" if BR2_archs38_64mpy
|
2018-11-08 22:59:40 +01:00
|
|
|
default "hs38_linux" if BR2_archs38_full
|
2019-06-04 07:39:27 +02:00
|
|
|
default "hs4x_rel31" if BR2_archs4x_rel31
|
2021-01-15 21:03:16 +01:00
|
|
|
default "hs4x" if BR2_archs4x
|
2015-07-17 11:11:42 +02:00
|
|
|
|
2017-03-19 14:07:51 +01:00
|
|
|
config BR2_READELF_ARCH_NAME
|
2017-03-26 17:05:43 +02:00
|
|
|
default "ARCompact" if BR2_arc750d || BR2_arc770d
|
2021-01-15 21:03:16 +01:00
|
|
|
default "ARCv2" if BR2_archs38 || BR2_archs38_64mpy || BR2_archs38_full
|
|
|
|
|
default "ARCv2" if BR2_archs4x_rel31 || BR2_archs4x
|
2017-03-19 14:07:51 +01:00
|
|
|
|
2015-07-17 11:11:42 +02:00
|
|
|
choice
|
|
|
|
|
prompt "MMU Page Size"
|
|
|
|
|
default BR2_ARC_PAGE_SIZE_8K
|
|
|
|
|
help
|
|
|
|
|
MMU starting from version 3 (found in ARC 770) and now
|
|
|
|
|
version 4 (found in ARC HS38) allows the selection of the
|
|
|
|
|
page size during ASIC design creation.
|
|
|
|
|
|
|
|
|
|
The following options are available for MMU v3 and v4: 4kB,
|
|
|
|
|
8kB and 16 kB.
|
|
|
|
|
|
|
|
|
|
The default is 8 kB (that really matches the only page size
|
|
|
|
|
in MMU v2). It is important to build a toolchain with page
|
|
|
|
|
size matching the hardware configuration. Otherwise
|
|
|
|
|
user-space applications will fail at runtime.
|
|
|
|
|
|
|
|
|
|
config BR2_ARC_PAGE_SIZE_4K
|
|
|
|
|
bool "4KB"
|
2021-01-15 21:03:16 +01:00
|
|
|
depends on !BR2_arc750d
|
2015-07-17 11:11:42 +02:00
|
|
|
|
|
|
|
|
config BR2_ARC_PAGE_SIZE_8K
|
|
|
|
|
bool "8KB"
|
|
|
|
|
help
|
|
|
|
|
This is the one and only option available for MMUv2 and
|
|
|
|
|
default value for MMU v3 and v4.
|
|
|
|
|
|
|
|
|
|
config BR2_ARC_PAGE_SIZE_16K
|
|
|
|
|
bool "16KB"
|
2021-01-15 21:03:16 +01:00
|
|
|
depends on !BR2_arc750d
|
2015-07-17 11:11:42 +02:00
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
|
|
config BR2_ARC_PAGE_SIZE
|
|
|
|
|
string
|
|
|
|
|
default "4K" if BR2_ARC_PAGE_SIZE_4K
|
|
|
|
|
default "8K" if BR2_ARC_PAGE_SIZE_8K
|
|
|
|
|
default "16K" if BR2_ARC_PAGE_SIZE_16K
|
2019-05-03 15:10:17 +02:00
|
|
|
|
|
|
|
|
# vim: ft=kconfig
|
|
|
|
|
# -*- mode:kconfig; -*-
|
