Kconfig (4062B)
1# SPDX-License-Identifier: GPL-2.0 2if MIPS_GENERIC_KERNEL 3 4config LEGACY_BOARDS 5 bool 6 help 7 Select this from your board if the board must use a legacy, non-UHI, 8 boot protocol. This will cause the kernel to scan through the list of 9 supported machines calling their detect functions in turn if the 10 kernel is booted without being provided with an FDT via the UHI 11 boot protocol. 12 13config YAMON_DT_SHIM 14 bool 15 help 16 Select this from your board if the board uses the YAMON bootloader 17 and you wish to include code which helps translate various 18 YAMON-provided environment variables into a device tree properties. 19 20comment "Legacy (non-UHI/non-FIT) Boards" 21 22config LEGACY_BOARD_SEAD3 23 bool "Support MIPS SEAD-3 boards" 24 select LEGACY_BOARDS 25 select YAMON_DT_SHIM 26 help 27 Enable this to include support for booting on MIPS SEAD-3 FPGA-based 28 development boards, which boot using a legacy boot protocol. 29 30comment "MSCC Ocelot doesn't work with SEAD3 enabled" 31 depends on LEGACY_BOARD_SEAD3 32 33config LEGACY_BOARD_OCELOT 34 bool "Legacy support for Ocelot based boards" 35 depends on LEGACY_BOARD_SEAD3=n 36 select LEGACY_BOARDS 37 select SOC_VCOREIII 38 select SYS_HAS_EARLY_PRINTK 39 select USE_GENERIC_EARLY_PRINTK_8250 40 41config SOC_VCOREIII 42 bool 43 select GPIOLIB 44 select MSCC_OCELOT_IRQ 45 select MSCC_OCELOT #will be removed when driver no more use it 46 47#Will be removed when the driver using it will be converted to SOC_VCOREIII 48config MSCC_OCELOT 49 bool 50 51comment "FIT/UHI Boards" 52 53config FIT_IMAGE_FDT_BOSTON 54 bool "Include FDT for MIPS Boston boards" 55 help 56 Enable this to include the FDT for the MIPS Boston development board 57 from Imagination Technologies in the FIT kernel image. You should 58 enable this if you wish to boot on a MIPS Boston board, as it is 59 expected by the bootloader. 60 61config FIT_IMAGE_FDT_MARDUK 62 bool "Include FDT for IMG Pistachio Marduk (CI40) boards" 63 help 64 Enable this to include the FDT for the IMG Pistachio Marduk (CI40) 65 from Imagination Technologies in the FIT kernel image. 66 67config FIT_IMAGE_FDT_NI169445 68 bool "Include FDT for NI 169445" 69 help 70 Enable this to include the FDT for the 169445 platform from 71 National Instruments in the FIT kernel image. 72 73config FIT_IMAGE_FDT_XILFPGA 74 bool "Include FDT for Xilfpga" 75 help 76 Enable this to include the FDT for the MIPSfpga platform 77 from Imagination Technologies in the FIT kernel image. 78 79config FIT_IMAGE_FDT_OCELOT 80 bool "Include FDT for Microsemi Ocelot development platforms" 81 select SOC_VCOREIII 82 help 83 Enable this to include the FDT for the Ocelot development platforms 84 from Microsemi in the FIT kernel image. 85 This requires u-boot on the platform. 86 87config FIT_IMAGE_FDT_LUTON 88 bool "Include FDT for Microsemi Luton development platforms" 89 select SOC_VCOREIII 90 help 91 Enable this to include the FDT for the Luton development platforms 92 from Microsemi in the FIT kernel image. 93 This requires u-boot on the platform. 94 95config FIT_IMAGE_FDT_JAGUAR2 96 bool "Include FDT for Microsemi Jaguar2 development platforms" 97 select SOC_VCOREIII 98 help 99 Enable this to include the FDT for the Jaguar2 development platforms 100 from Microsemi in the FIT kernel image. 101 This requires u-boot on the platform. 102 103config FIT_IMAGE_FDT_SERVAL 104 bool "Include FDT for Microsemi Serval development platforms" 105 select SOC_VCOREIII 106 help 107 Enable this to include the FDT for the Serval development platforms 108 from Microsemi in the FIT kernel image. 109 This requires u-boot on the platform. 110 111config BOARD_INGENIC 112 bool "Support boards based on Ingenic SoCs" 113 select MACH_INGENIC_GENERIC 114 help 115 Enable support for boards based on Ingenic SoCs. 116 117config VIRT_BOARD_RANCHU 118 bool "Support Ranchu platform for Android emulator" 119 help 120 This enables support for the platform used by Android emulator. 121 122 Ranchu platform consists of a set of virtual devices. This platform 123 enables emulation of variety of virtual configurations while using 124 Android emulator. Android emulator is based on Qemu, and contains 125 the support for the same set of virtual devices. 126 127endif