1config MICROBLAZE 2 def_bool y 3 select ARCH_HAS_GCOV_PROFILE_ALL 4 select ARCH_MIGHT_HAVE_PC_PARPORT 5 select ARCH_WANT_IPC_PARSE_VERSION 6 select BUILDTIME_EXTABLE_SORT 7 select CLKSRC_OF 8 select CLONE_BACKWARDS3 9 select COMMON_CLK 10 select GENERIC_ATOMIC64 11 select GENERIC_CLOCKEVENTS 12 select GENERIC_CPU_DEVICES 13 select GENERIC_IDLE_POLL_SETUP 14 select GENERIC_IRQ_PROBE 15 select GENERIC_IRQ_SHOW 16 select GENERIC_PCI_IOMAP 17 select GENERIC_SCHED_CLOCK 18 select HAVE_ARCH_HASH 19 select HAVE_ARCH_KGDB 20 select HAVE_DEBUG_KMEMLEAK 21 select HAVE_DMA_API_DEBUG 22 select HAVE_DYNAMIC_FTRACE 23 select HAVE_FTRACE_MCOUNT_RECORD 24 select HAVE_FUNCTION_GRAPH_TRACER 25 select HAVE_FUNCTION_TRACER 26 select HAVE_MEMBLOCK 27 select HAVE_MEMBLOCK_NODE_MAP 28 select HAVE_OPROFILE 29 select IRQ_DOMAIN 30 select MODULES_USE_ELF_RELA 31 select OF 32 select OF_EARLY_FLATTREE 33 select TRACING_SUPPORT 34 select VIRT_TO_BUS 35 select CPU_NO_EFFICIENT_FFS 36 37config SWAP 38 def_bool n 39 40config RWSEM_GENERIC_SPINLOCK 41 def_bool y 42 43config ZONE_DMA 44 def_bool y 45 46config RWSEM_XCHGADD_ALGORITHM 47 bool 48 49config ARCH_HAS_ILOG2_U32 50 def_bool n 51 52config ARCH_HAS_ILOG2_U64 53 def_bool n 54 55config GENERIC_HWEIGHT 56 def_bool y 57 58config GENERIC_CALIBRATE_DELAY 59 def_bool y 60 61config GENERIC_CSUM 62 def_bool y 63 64config STACKTRACE_SUPPORT 65 def_bool y 66 67config LOCKDEP_SUPPORT 68 def_bool y 69 70source "init/Kconfig" 71 72source "kernel/Kconfig.freezer" 73 74source "arch/microblaze/Kconfig.platform" 75 76menu "Processor type and features" 77 78source "kernel/Kconfig.preempt" 79 80source "kernel/Kconfig.hz" 81 82config MMU 83 bool "MMU support" 84 default n 85 86comment "Boot options" 87 88config CMDLINE_BOOL 89 bool "Default bootloader kernel arguments" 90 91config CMDLINE 92 string "Default kernel command string" 93 depends on CMDLINE_BOOL 94 default "console=ttyUL0,115200" 95 help 96 On some architectures there is currently no way for the boot loader 97 to pass arguments to the kernel. For these architectures, you should 98 supply some command-line options at build time by entering them 99 here. 100 101config CMDLINE_FORCE 102 bool "Force default kernel command string" 103 depends on CMDLINE_BOOL 104 default n 105 help 106 Set this to have arguments from the default kernel command string 107 override those passed by the boot loader. 108 109config SECCOMP 110 bool "Enable seccomp to safely compute untrusted bytecode" 111 depends on PROC_FS 112 default y 113 help 114 This kernel feature is useful for number crunching applications 115 that may need to compute untrusted bytecode during their 116 execution. By using pipes or other transports made available to 117 the process as file descriptors supporting the read/write 118 syscalls, it's possible to isolate those applications in 119 their own address space using seccomp. Once seccomp is 120 enabled via /proc/<pid>/seccomp, it cannot be disabled 121 and the task is only allowed to execute a few safe syscalls 122 defined by each seccomp mode. 123 124 If unsure, say Y. Only embedded should say N here. 125 126endmenu 127 128menu "Kernel features" 129 130config NR_CPUS 131 int 132 default "1" 133 134config ADVANCED_OPTIONS 135 bool "Prompt for advanced kernel configuration options" 136 help 137 This option will enable prompting for a variety of advanced kernel 138 configuration options. These options can cause the kernel to not 139 work if they are set incorrectly, but can be used to optimize certain 140 aspects of kernel memory management. 141 142 Unless you know what you are doing, say N here. 143 144comment "Default settings for advanced configuration options are used" 145 depends on !ADVANCED_OPTIONS 146 147config XILINX_UNCACHED_SHADOW 148 bool "Are you using uncached shadow for RAM ?" 149 depends on ADVANCED_OPTIONS && !MMU 150 default n 151 help 152 This is needed to be able to allocate uncachable memory regions. 153 The feature requires the design to define the RAM memory controller 154 window to be twice as large as the actual physical memory. 155 156config HIGHMEM 157 bool "High memory support" 158 depends on MMU 159 help 160 The address space of Microblaze processors is only 4 Gigabytes large 161 and it has to accommodate user address space, kernel address 162 space as well as some memory mapped IO. That means that, if you 163 have a large amount of physical memory and/or IO, not all of the 164 memory can be "permanently mapped" by the kernel. The physical 165 memory that is not permanently mapped is called "high memory". 166 167 If unsure, say n. 168 169config LOWMEM_SIZE_BOOL 170 bool "Set maximum low memory" 171 depends on ADVANCED_OPTIONS && MMU 172 help 173 This option allows you to set the maximum amount of memory which 174 will be used as "low memory", that is, memory which the kernel can 175 access directly, without having to set up a kernel virtual mapping. 176 This can be useful in optimizing the layout of kernel virtual 177 memory. 178 179 Say N here unless you know what you are doing. 180 181config LOWMEM_SIZE 182 hex "Maximum low memory size (in bytes)" if LOWMEM_SIZE_BOOL 183 default "0x30000000" 184 185config MANUAL_RESET_VECTOR 186 hex "Microblaze reset vector address setup" 187 default "0x0" 188 help 189 Set this option to have the kernel override the CPU Reset vector. 190 If zero, no change will be made to the MicroBlaze reset vector at 191 address 0x0. 192 If non-zero, a jump instruction to this address, will be written 193 to the reset vector at address 0x0. 194 If you are unsure, set it to default value 0x0. 195 196config KERNEL_START_BOOL 197 bool "Set custom kernel base address" 198 depends on ADVANCED_OPTIONS 199 help 200 This option allows you to set the kernel virtual address at which 201 the kernel will map low memory (the kernel image will be linked at 202 this address). This can be useful in optimizing the virtual memory 203 layout of the system. 204 205 Say N here unless you know what you are doing. 206 207config KERNEL_START 208 hex "Virtual address of kernel base" if KERNEL_START_BOOL 209 default "0xc0000000" if MMU 210 default KERNEL_BASE_ADDR if !MMU 211 212config TASK_SIZE_BOOL 213 bool "Set custom user task size" 214 depends on ADVANCED_OPTIONS && MMU 215 help 216 This option allows you to set the amount of virtual address space 217 allocated to user tasks. This can be useful in optimizing the 218 virtual memory layout of the system. 219 220 Say N here unless you know what you are doing. 221 222config TASK_SIZE 223 hex "Size of user task space" if TASK_SIZE_BOOL 224 default "0x80000000" 225 226choice 227 prompt "Page size" 228 default MICROBLAZE_4K_PAGES 229 depends on ADVANCED_OPTIONS && !MMU 230 help 231 Select the kernel logical page size. Increasing the page size 232 will reduce software overhead at each page boundary, allow 233 hardware prefetch mechanisms to be more effective, and allow 234 larger dma transfers increasing IO efficiency and reducing 235 overhead. However the utilization of memory will increase. 236 For example, each cached file will using a multiple of the 237 page size to hold its contents and the difference between the 238 end of file and the end of page is wasted. 239 240 If unsure, choose 4K_PAGES. 241 242config MICROBLAZE_4K_PAGES 243 bool "4k page size" 244 245config MICROBLAZE_16K_PAGES 246 bool "16k page size" 247 248config MICROBLAZE_64K_PAGES 249 bool "64k page size" 250 251endchoice 252 253source "mm/Kconfig" 254 255endmenu 256 257menu "Executable file formats" 258 259source "fs/Kconfig.binfmt" 260 261endmenu 262 263menu "Bus Options" 264 265config PCI 266 bool "PCI support" 267 268config PCI_DOMAINS 269 def_bool PCI 270 271config PCI_DOMAINS_GENERIC 272 def_bool PCI_DOMAINS 273 274config PCI_SYSCALL 275 def_bool PCI 276 277config PCI_XILINX 278 bool "Xilinx PCI host bridge support" 279 depends on PCI 280 281source "drivers/pci/Kconfig" 282 283endmenu 284 285source "net/Kconfig" 286 287source "drivers/Kconfig" 288 289source "fs/Kconfig" 290 291source "arch/microblaze/Kconfig.debug" 292 293source "security/Kconfig" 294 295source "crypto/Kconfig" 296 297source "lib/Kconfig" 298