2022-07-20 04:45:30 +02:00
|
|
|
# Architecture
|
|
|
|
|
BR2_riscv=y
|
|
|
|
|
BR2_RISCV_64=y
|
|
|
|
|
BR2_riscv_custom=y
|
2023-08-18 12:42:59 +02:00
|
|
|
BR2_RISCV_ISA_RVM=y
|
|
|
|
|
BR2_RISCV_ISA_RVA=y
|
|
|
|
|
BR2_RISCV_ISA_RVF=y
|
|
|
|
|
BR2_RISCV_ISA_RVD=y
|
|
|
|
|
BR2_RISCV_ISA_RVC=y
|
arch: rework MMU option handling and move to "Target architecture" menu
The MMU option is currently located in the "Toolchain" menu, but it
doesn't make sense as it's really architecture related. In addition,
the selection of MMU has an impact on the choice of binary format
available, which is visible in the architecture menu.
Therefore, this commit moves the MMU option into the architecture
menu.
However, if we simply move it in arch/Config.in, it means that we
would have the following order of options:
Target architecture
Target architecture variant
ABI
MMU
Binary format
But really, the MMU option should be right below the Target
architecture variant, and the available ABIs derived from that.
The variant and ABI are arch-specfic, and defined in the per-arch
Config.in fragments; a Kconfig option can have only one prompt defined,
even under conditions, and appears at the place in the menu where its
prompt was defined. So, there is no (easy) possibility to have a
generic option appear where we want it.
Since in fact only 2 architectures show a visible prompt for the MMU
option (RISC-V and Xtensa), we move this option in
arch/Config.in.riscv and arch/Config.in.xtensa.
Some walkthrough the commit:
- BR2_ARCH_HAS_MMU_MANDATORY and BR2_ARCH_HAS_MMU_OPTIONAL are
removed as they are no longer needed
- BR2_USE_MMU becomes a hidden boolean
- All the places where we used to select BR2_ARCH_HAS_MMU_MANDATORY
now select BR2_USE_MMU directly.
- Introduce BR2_RISCV_USE_MMU and BR2_XTENSA_USE_MMU.
- All defconfigs that used "# BR2_USE_MMU is not set" are switched to
using the new option.
All in all, this simplifies things quite a bit, and allows to have a
good option ordering in the Target architecture menu.
This commit might raise a concern in terms of backward compatibility
with existing configurations. The only configurations that will be
broken by this change are RISC-V noMMU (which was very recently
introduced) and Xtensa noMMU (which we can probably agree is not such
a widely popular configuration).
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Tested-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
[yann.morin.1998@free.fr:
- expand further why we need per-arch MMU options
]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-07-26 18:39:51 +02:00
|
|
|
# BR2_RISCV_USE_MMU is not set
|
2022-07-20 04:45:30 +02:00
|
|
|
BR2_RISCV_ABI_LP64D=y
|
|
|
|
|
|
2022-10-04 21:50:37 +02:00
|
|
|
# Linux headers same as kernel, a 5.19 series
|
|
|
|
|
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_19=y
|
|
|
|
|
|
2022-07-20 04:45:30 +02:00
|
|
|
# Binary format
|
|
|
|
|
BR2_BINFMT_FLAT=y
|
|
|
|
|
BR2_BINFMT_FLAT_ONE=y
|
|
|
|
|
# BR2_TARGET_ENABLE_ROOT_LOGIN is not set
|
|
|
|
|
|
|
|
|
|
# Kernel
|
|
|
|
|
BR2_LINUX_KERNEL=y
|
|
|
|
|
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
|
2022-08-10 13:50:55 +02:00
|
|
|
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.19"
|
2022-07-20 04:45:30 +02:00
|
|
|
BR2_LINUX_KERNEL_DEFCONFIG="nommu_k210"
|
|
|
|
|
BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES="board/sipeed/maix-go/linux-cpio.config"
|
|
|
|
|
BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM=y
|
|
|
|
|
BR2_LINUX_KERNEL_IMAGE_NAME="loader.bin"
|
|
|
|
|
|
|
|
|
|
# Packages
|
|
|
|
|
BR2_PACKAGE_HOST_PYTHON_KFLASH=y
|
|
|
|
|
BR2_PACKAGE_BUSYBOX_CONFIG_FRAGMENT_FILES="board/canaan/k210-soc/busybox-tiny.config"
|
|
|
|
|
# BR2_PACKAGE_IFUPDOWN_SCRIPTS is not set
|
|
|
|
|
|
|
|
|
|
# Filesystem
|
|
|
|
|
BR2_INIT_NONE=y
|
|
|
|
|
BR2_TARGET_ROOTFS_INITRAMFS=y
|
|
|
|
|
BR2_ROOTFS_OVERLAY="board/canaan/k210-soc/rootfs_overlay"
|
