1config MICROBLAZE 2 def_bool y 3 select ARCH_MIGHT_HAVE_PC_PARPORT 4 select HAVE_MEMBLOCK 5 select HAVE_MEMBLOCK_NODE_MAP 6 select HAVE_FUNCTION_TRACER 7 select HAVE_FUNCTION_TRACE_MCOUNT_TEST 8 select HAVE_FUNCTION_GRAPH_TRACER 9 select HAVE_DYNAMIC_FTRACE 10 select HAVE_FTRACE_MCOUNT_RECORD 11 select ARCH_WANT_OPTIONAL_GPIOLIB 12 select HAVE_OPROFILE 13 select HAVE_ARCH_KGDB 14 select HAVE_DMA_ATTRS 15 select HAVE_DMA_API_DEBUG 16 select TRACING_SUPPORT 17 select OF 18 select OF_EARLY_FLATTREE 19 select ARCH_WANT_IPC_PARSE_VERSION 20 select HAVE_DEBUG_KMEMLEAK 21 select IRQ_DOMAIN 22 select VIRT_TO_BUS 23 select GENERIC_IRQ_PROBE 24 select GENERIC_IRQ_SHOW 25 select GENERIC_PCI_IOMAP 26 select GENERIC_CPU_DEVICES 27 select GENERIC_ATOMIC64 28 select GENERIC_CLOCKEVENTS 29 select GENERIC_IDLE_POLL_SETUP 30 select MODULES_USE_ELF_RELA 31 select CLONE_BACKWARDS3 32 select CLKSRC_OF 33 34config SWAP 35 def_bool n 36 37config RWSEM_GENERIC_SPINLOCK 38 def_bool y 39 40config ZONE_DMA 41 def_bool y 42 43config RWSEM_XCHGADD_ALGORITHM 44 bool 45 46config ARCH_HAS_ILOG2_U32 47 def_bool n 48 49config ARCH_HAS_ILOG2_U64 50 def_bool n 51 52config GENERIC_HWEIGHT 53 def_bool y 54 55config GENERIC_CALIBRATE_DELAY 56 def_bool y 57 58config GENERIC_CSUM 59 def_bool y 60 61config STACKTRACE_SUPPORT 62 def_bool y 63 64config LOCKDEP_SUPPORT 65 def_bool y 66 67config HAVE_LATENCYTOP_SUPPORT 68 def_bool y 69 70source "init/Kconfig" 71 72source "kernel/Kconfig.freezer" 73 74source "arch/microblaze/platform/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 "Advanced setup" 129 130config ADVANCED_OPTIONS 131 bool "Prompt for advanced kernel configuration options" 132 help 133 This option will enable prompting for a variety of advanced kernel 134 configuration options. These options can cause the kernel to not 135 work if they are set incorrectly, but can be used to optimize certain 136 aspects of kernel memory management. 137 138 Unless you know what you are doing, say N here. 139 140comment "Default settings for advanced configuration options are used" 141 depends on !ADVANCED_OPTIONS 142 143config XILINX_UNCACHED_SHADOW 144 bool "Are you using uncached shadow for RAM ?" 145 depends on ADVANCED_OPTIONS && !MMU 146 default n 147 help 148 This is needed to be able to allocate uncachable memory regions. 149 The feature requires the design to define the RAM memory controller 150 window to be twice as large as the actual physical memory. 151 152config HIGHMEM 153 bool "High memory support" 154 depends on MMU 155 help 156 The address space of Microblaze processors is only 4 Gigabytes large 157 and it has to accommodate user address space, kernel address 158 space as well as some memory mapped IO. That means that, if you 159 have a large amount of physical memory and/or IO, not all of the 160 memory can be "permanently mapped" by the kernel. The physical 161 memory that is not permanently mapped is called "high memory". 162 163 If unsure, say n. 164 165config LOWMEM_SIZE_BOOL 166 bool "Set maximum low memory" 167 depends on ADVANCED_OPTIONS && MMU 168 help 169 This option allows you to set the maximum amount of memory which 170 will be used as "low memory", that is, memory which the kernel can 171 access directly, without having to set up a kernel virtual mapping. 172 This can be useful in optimizing the layout of kernel virtual 173 memory. 174 175 Say N here unless you know what you are doing. 176 177config LOWMEM_SIZE 178 hex "Maximum low memory size (in bytes)" if LOWMEM_SIZE_BOOL 179 default "0x30000000" 180 181config MANUAL_RESET_VECTOR 182 hex "Microblaze reset vector address setup" 183 default "0x0" 184 help 185 Set this option to have the kernel override the CPU Reset vector. 186 If zero, no change will be made to the MicroBlaze reset vector at 187 address 0x0. 188 If non-zero, a jump instruction to this address, will be written 189 to the reset vector at address 0x0. 190 If you are unsure, set it to default value 0x0. 191 192config KERNEL_START_BOOL 193 bool "Set custom kernel base address" 194 depends on ADVANCED_OPTIONS 195 help 196 This option allows you to set the kernel virtual address at which 197 the kernel will map low memory (the kernel image will be linked at 198 this address). This can be useful in optimizing the virtual memory 199 layout of the system. 200 201 Say N here unless you know what you are doing. 202 203config KERNEL_START 204 hex "Virtual address of kernel base" if KERNEL_START_BOOL 205 default "0xc0000000" if MMU 206 default KERNEL_BASE_ADDR if !MMU 207 208config TASK_SIZE_BOOL 209 bool "Set custom user task size" 210 depends on ADVANCED_OPTIONS && MMU 211 help 212 This option allows you to set the amount of virtual address space 213 allocated to user tasks. This can be useful in optimizing the 214 virtual memory layout of the system. 215 216 Say N here unless you know what you are doing. 217 218config TASK_SIZE 219 hex "Size of user task space" if TASK_SIZE_BOOL 220 default "0x80000000" 221 222choice 223 prompt "Page size" 224 default MICROBLAZE_4K_PAGES 225 depends on ADVANCED_OPTIONS && !MMU 226 help 227 Select the kernel logical page size. Increasing the page size 228 will reduce software overhead at each page boundary, allow 229 hardware prefetch mechanisms to be more effective, and allow 230 larger dma transfers increasing IO efficiency and reducing 231 overhead. However the utilization of memory will increase. 232 For example, each cached file will using a multiple of the 233 page size to hold its contents and the difference between the 234 end of file and the end of page is wasted. 235 236 If unsure, choose 4K_PAGES. 237 238config MICROBLAZE_4K_PAGES 239 bool "4k page size" 240 241config MICROBLAZE_16K_PAGES 242 bool "16k page size" 243 244config MICROBLAZE_64K_PAGES 245 bool "64k page size" 246 247endchoice 248 249endmenu 250 251source "mm/Kconfig" 252 253menu "Executable file formats" 254 255source "fs/Kconfig.binfmt" 256 257endmenu 258 259menu "Bus Options" 260 261config PCI 262 bool "PCI support" 263 264config PCI_DOMAINS 265 def_bool PCI 266 267config PCI_SYSCALL 268 def_bool PCI 269 270config PCI_XILINX 271 bool "Xilinx PCI host bridge support" 272 depends on PCI 273 274source "drivers/pci/Kconfig" 275 276endmenu 277 278source "net/Kconfig" 279 280source "drivers/Kconfig" 281 282source "fs/Kconfig" 283 284source "arch/microblaze/Kconfig.debug" 285 286source "security/Kconfig" 287 288source "crypto/Kconfig" 289 290source "lib/Kconfig" 291