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