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