1 # SPDX-License-Identifier: GPL-2.0 !! 1 # $Id: config.in,v 1.113 2002/01/24 22:14:44 davem Exp $
2 config ARM !! 2 # For a description of the syntax of this configuration file,
3 bool !! 3 # see Documentation/kbuild/kconfig-language.txt.
4 default y !! 4 #
5 select ARCH_32BIT_OFF_T <<
6 select ARCH_CORRECT_STACKTRACE_ON_KRET <<
7 select ARCH_HAS_BINFMT_FLAT <<
8 select ARCH_HAS_CPU_CACHE_ALIASING <<
9 select ARCH_HAS_CPU_FINALIZE_INIT if M <<
10 select ARCH_HAS_CURRENT_STACK_POINTER <<
11 select ARCH_HAS_DEBUG_VIRTUAL if MMU <<
12 select ARCH_HAS_DMA_ALLOC if MMU <<
13 select ARCH_HAS_DMA_OPS <<
14 select ARCH_HAS_DMA_WRITE_COMBINE if ! <<
15 select ARCH_HAS_ELF_RANDOMIZE <<
16 select ARCH_HAS_FORTIFY_SOURCE <<
17 select ARCH_HAS_KEEPINITRD <<
18 select ARCH_HAS_KCOV <<
19 select ARCH_HAS_MEMBARRIER_SYNC_CORE <<
20 select ARCH_HAS_NON_OVERLAPPING_ADDRES <<
21 select ARCH_HAS_PTE_SPECIAL if ARM_LPA <<
22 select ARCH_HAS_SETUP_DMA_OPS <<
23 select ARCH_HAS_SET_MEMORY <<
24 select ARCH_STACKWALK <<
25 select ARCH_HAS_STRICT_KERNEL_RWX if M <<
26 select ARCH_HAS_STRICT_MODULE_RWX if M <<
27 select ARCH_HAS_SYNC_DMA_FOR_DEVICE <<
28 select ARCH_HAS_SYNC_DMA_FOR_CPU <<
29 select ARCH_HAS_TEARDOWN_DMA_OPS if MM <<
30 select ARCH_HAS_TICK_BROADCAST if GENE <<
31 select ARCH_HAVE_NMI_SAFE_CMPXCHG if C <<
32 select ARCH_HAS_GCOV_PROFILE_ALL <<
33 select ARCH_KEEP_MEMBLOCK <<
34 select ARCH_HAS_UBSAN <<
35 select ARCH_MIGHT_HAVE_PC_PARPORT <<
36 select ARCH_OPTIONAL_KERNEL_RWX if ARC <<
37 select ARCH_OPTIONAL_KERNEL_RWX_DEFAUL <<
38 select ARCH_NEED_CMPXCHG_1_EMU if CPU_ <<
39 select ARCH_SUPPORTS_ATOMIC_RMW <<
40 select ARCH_SUPPORTS_CFI_CLANG <<
41 select ARCH_SUPPORTS_HUGETLBFS if ARM_ <<
42 select ARCH_SUPPORTS_PER_VMA_LOCK <<
43 select ARCH_USE_BUILTIN_BSWAP <<
44 select ARCH_USE_CMPXCHG_LOCKREF <<
45 select ARCH_USE_MEMTEST <<
46 select ARCH_WANT_DEFAULT_TOPDOWN_MMAP_ <<
47 select ARCH_WANT_GENERAL_HUGETLB <<
48 select ARCH_WANT_IPC_PARSE_VERSION <<
49 select ARCH_WANT_LD_ORPHAN_WARN <<
50 select BINFMT_FLAT_ARGVP_ENVP_ON_STACK <<
51 select BUILDTIME_TABLE_SORT if MMU <<
52 select COMMON_CLK if !(ARCH_RPC || ARC <<
53 select CLONE_BACKWARDS <<
54 select CPU_PM if SUSPEND || CPU_IDLE <<
55 select DCACHE_WORD_ACCESS if HAVE_EFFI <<
56 select DMA_DECLARE_COHERENT <<
57 select DMA_GLOBAL_POOL if !MMU <<
58 select DMA_NONCOHERENT_MMAP if MMU <<
59 select EDAC_SUPPORT <<
60 select EDAC_ATOMIC_SCRUB <<
61 select GENERIC_ALLOCATOR <<
62 select GENERIC_ARCH_TOPOLOGY if ARM_CP <<
63 select GENERIC_ATOMIC64 if CPU_V7M || <<
64 select GENERIC_CLOCKEVENTS_BROADCAST i <<
65 select GENERIC_IRQ_IPI if SMP <<
66 select GENERIC_CPU_AUTOPROBE <<
67 select GENERIC_CPU_DEVICES <<
68 select GENERIC_EARLY_IOREMAP <<
69 select GENERIC_IDLE_POLL_SETUP <<
70 select GENERIC_IRQ_MULTI_HANDLER <<
71 select GENERIC_IRQ_PROBE <<
72 select GENERIC_IRQ_SHOW <<
73 select GENERIC_IRQ_SHOW_LEVEL <<
74 select GENERIC_LIB_DEVMEM_IS_ALLOWED <<
75 select GENERIC_PCI_IOMAP <<
76 select GENERIC_SCHED_CLOCK <<
77 select GENERIC_SMP_IDLE_THREAD <<
78 select HARDIRQS_SW_RESEND <<
79 select HAS_IOPORT <<
80 select HAVE_ARCH_AUDITSYSCALL if AEABI <<
81 select HAVE_ARCH_BITREVERSE if (CPU_32 <<
82 select HAVE_ARCH_JUMP_LABEL if !XIP_KE <<
83 select HAVE_ARCH_KFENCE if MMU && !XIP <<
84 select HAVE_ARCH_KGDB if !CPU_ENDIAN_B <<
85 select HAVE_ARCH_KASAN if MMU && !XIP_ <<
86 select HAVE_ARCH_KASAN_VMALLOC if HAVE <<
87 select HAVE_ARCH_MMAP_RND_BITS if MMU <<
88 select HAVE_ARCH_PFN_VALID <<
89 select HAVE_ARCH_SECCOMP <<
90 select HAVE_ARCH_SECCOMP_FILTER if AEA <<
91 select HAVE_ARCH_STACKLEAK <<
92 select HAVE_ARCH_THREAD_STRUCT_WHITELI <<
93 select HAVE_ARCH_TRACEHOOK <<
94 select HAVE_ARCH_TRANSPARENT_HUGEPAGE <<
95 select HAVE_ARM_SMCCC if CPU_V7 <<
96 select HAVE_EBPF_JIT if !CPU_ENDIAN_BE <<
97 select HAVE_CONTEXT_TRACKING_USER <<
98 select HAVE_C_RECORDMCOUNT <<
99 select HAVE_BUILDTIME_MCOUNT_SORT <<
100 select HAVE_DEBUG_KMEMLEAK if !XIP_KER <<
101 select HAVE_DMA_CONTIGUOUS if MMU <<
102 select HAVE_DYNAMIC_FTRACE if !XIP_KER <<
103 select HAVE_DYNAMIC_FTRACE_WITH_REGS i <<
104 select HAVE_EFFICIENT_UNALIGNED_ACCESS <<
105 select HAVE_EXIT_THREAD <<
106 select HAVE_GUP_FAST if ARM_LPAE <<
107 select HAVE_FTRACE_MCOUNT_RECORD if !X <<
108 select HAVE_FUNCTION_ERROR_INJECTION <<
109 select HAVE_FUNCTION_GRAPH_TRACER <<
110 select HAVE_FUNCTION_TRACER if !XIP_KE <<
111 select HAVE_GCC_PLUGINS <<
112 select HAVE_HW_BREAKPOINT if PERF_EVEN <<
113 select HAVE_IRQ_TIME_ACCOUNTING <<
114 select HAVE_KERNEL_GZIP <<
115 select HAVE_KERNEL_LZ4 <<
116 select HAVE_KERNEL_LZMA <<
117 select HAVE_KERNEL_LZO <<
118 select HAVE_KERNEL_XZ <<
119 select HAVE_KPROBES if !XIP_KERNEL && <<
120 select HAVE_KRETPROBES if HAVE_KPROBES <<
121 select HAVE_LD_DEAD_CODE_DATA_ELIMINAT <<
122 select HAVE_MOD_ARCH_SPECIFIC <<
123 select HAVE_NMI <<
124 select HAVE_OPTPROBES if !THUMB2_KERNE <<
125 select HAVE_PAGE_SIZE_4KB <<
126 select HAVE_PCI if MMU <<
127 select HAVE_PERF_EVENTS <<
128 select HAVE_PERF_REGS <<
129 select HAVE_PERF_USER_STACK_DUMP <<
130 select MMU_GATHER_RCU_TABLE_FREE if SM <<
131 select HAVE_REGS_AND_STACK_ACCESS_API <<
132 select HAVE_RSEQ <<
133 select HAVE_STACKPROTECTOR <<
134 select HAVE_SYSCALL_TRACEPOINTS <<
135 select HAVE_UID16 <<
136 select HAVE_VIRT_CPU_ACCOUNTING_GEN <<
137 select HOTPLUG_CORE_SYNC_DEAD if HOTPL <<
138 select IRQ_FORCED_THREADING <<
139 select LOCK_MM_AND_FIND_VMA <<
140 select MODULES_USE_ELF_REL <<
141 select NEED_DMA_MAP_STATE <<
142 select OF_EARLY_FLATTREE if OF <<
143 select OLD_SIGACTION <<
144 select OLD_SIGSUSPEND3 <<
145 select PCI_DOMAINS_GENERIC if PCI <<
146 select PCI_SYSCALL if PCI <<
147 select PERF_USE_VMALLOC <<
148 select RTC_LIB <<
149 select SPARSE_IRQ if !(ARCH_FOOTBRIDGE <<
150 select SYS_SUPPORTS_APM_EMULATION <<
151 select THREAD_INFO_IN_TASK <<
152 select TIMER_OF if OF <<
153 select HAVE_ARCH_VMAP_STACK if MMU && <<
154 select TRACE_IRQFLAGS_SUPPORT if !CPU_ <<
155 select USE_OF if !(ARCH_FOOTBRIDGE || <<
156 # Above selects are sorted alphabetica <<
157 # according to that. Thanks. <<
158 help <<
159 The ARM series is a line of low-powe <<
160 licensed by ARM Ltd and targeted at <<
161 handhelds such as the Compaq IPAQ. <<
162 manufactured, but legacy ARM-based P <<
163 Europe. There is an ARM Linux proje <<
164 <http://www.arm.linux.org.uk/>. <<
165 <<
166 config ARM_HAS_GROUP_RELOCS <<
167 def_bool y <<
168 depends on !LD_IS_LLD || LLD_VERSION > <<
169 depends on !COMPILE_TEST <<
170 help <<
171 Whether or not to use R_ARM_ALU_PC_G <<
172 relocations, which have been around <<
173 supported in LLD until version 14. T <<
174 which is usually sufficient, but not <<
175 this feature when doing compile test <<
176 <<
177 config ARM_DMA_USE_IOMMU <<
178 bool <<
179 select NEED_SG_DMA_LENGTH <<
180 <<
181 if ARM_DMA_USE_IOMMU <<
182 <<
183 config ARM_DMA_IOMMU_ALIGNMENT <<
184 int "Maximum PAGE_SIZE order of alignm <<
185 range 4 9 <<
186 default 8 <<
187 help <<
188 DMA mapping framework by default ali <<
189 PAGE_SIZE order which is greater tha <<
190 size. This works well for buffers up <<
191 for larger buffers it just a waste o <<
192 relatively small addressing window ( <<
193 virtual space with just a few alloca <<
194 <<
195 With this parameter you can specify <<
196 DMA IOMMU buffers. Larger buffers wi <<
197 specified order. The order is expres <<
198 by the PAGE_SIZE. <<
199 <<
200 endif <<
201 <<
202 config SYS_SUPPORTS_APM_EMULATION <<
203 bool <<
204 <<
205 config HAVE_TCM <<
206 bool <<
207 select GENERIC_ALLOCATOR <<
208 5
209 config HAVE_PROC_CPU !! 6 mainmenu "Linux/SPARC Kernel Configuration"
210 bool <<
211 7
212 config NO_IOPORT_MAP !! 8 config MMU
213 bool <<
214 <<
215 config SBUS <<
216 bool 9 bool
>> 10 default y
217 11
218 config STACKTRACE_SUPPORT !! 12 config UID16
219 bool 13 bool
220 default y 14 default y
221 15
222 config LOCKDEP_SUPPORT !! 16 config HIGHMEM
223 bool 17 bool
224 default y 18 default y
225 19
226 config ARCH_HAS_ILOG2_U32 !! 20 config GENERIC_ISA_DMA
227 bool 21 bool
>> 22 default y
228 23
229 config ARCH_HAS_ILOG2_U64 !! 24 source "init/Kconfig"
230 bool <<
231 25
232 config ARCH_HAS_BANDGAP <<
233 bool <<
234 26
235 config FIX_EARLYCON_MEM !! 27 menu "General setup"
236 def_bool y if MMU <<
237 28
238 config GENERIC_HWEIGHT !! 29 config VT
239 bool 30 bool
240 default y 31 default y
>> 32 ---help---
>> 33 If you say Y here, you will get support for terminal devices with
>> 34 display and keyboard devices. These are called "virtual" because you
>> 35 can run several virtual terminals (also called virtual consoles) on
>> 36 one physical terminal. This is rather useful, for example one
>> 37 virtual terminal can collect system messages and warnings, another
>> 38 one can be used for a text-mode user session, and a third could run
>> 39 an X session, all in parallel. Switching between virtual terminals
>> 40 is done with certain key combinations, usually Alt-<function key>.
>> 41
>> 42 The setterm command ("man setterm") can be used to change the
>> 43 properties (such as colors or beeping) of a virtual terminal. The
>> 44 man page console_codes(4) ("man console_codes") contains the special
>> 45 character sequences that can be used to change those properties
>> 46 directly. The fonts used on virtual terminals can be changed with
>> 47 the setfont ("man setfont") command and the key bindings are defined
>> 48 with the loadkeys ("man loadkeys") command.
>> 49
>> 50 You need at least one virtual terminal device in order to make use
>> 51 of your keyboard and monitor. Therefore, only people configuring an
>> 52 embedded system would want to say N here in order to save some
>> 53 memory; the only way to log into such a system is then via a serial
>> 54 or network connection.
>> 55
>> 56 If unsure, say Y, or else you won't be able to do much with your new
>> 57 shiny Linux system :-)
>> 58
>> 59 config VT_CONSOLE
>> 60 bool
>> 61 default y
>> 62 ---help---
>> 63 The system console is the device which receives all kernel messages
>> 64 and warnings and which allows logins in single user mode. If you
>> 65 answer Y here, a virtual terminal (the device used to interact with
>> 66 a physical terminal) can be used as system console. This is the most
>> 67 common mode of operations, so you should say Y here unless you want
>> 68 the kernel messages be output only to a serial port (in which case
>> 69 you should say Y to "Console on serial port", below).
>> 70
>> 71 If you do say Y here, by default the currently visible virtual
>> 72 terminal (/dev/tty0) will be used as system console. You can change
>> 73 that with a kernel command line option such as "console=tty3" which
>> 74 would use the third virtual terminal as system console. (Try "man
>> 75 bootparam" or see the documentation of your boot loader (lilo or
>> 76 loadlin) about how to pass options to the kernel at boot time.)
241 77
242 config GENERIC_CALIBRATE_DELAY !! 78 If unsure, say Y.
>> 79
>> 80 config HW_CONSOLE
243 bool 81 bool
244 default y 82 default y
245 83
246 config ARCH_MAY_HAVE_PC_FDC !! 84 config SMP
247 bool !! 85 bool "Symmetric multi-processing support (does not work on sun4/sun4c)"
>> 86 ---help---
>> 87 This enables support for systems with more than one CPU. If you have
>> 88 a system with only one CPU, like most personal computers, say N. If
>> 89 you have a system with more than one CPU, say Y.
248 90
249 config ARCH_SUPPORTS_UPROBES !! 91 If you say N here, the kernel will run on single and multiprocessor
250 def_bool y !! 92 machines, but will use only one CPU of a multiprocessor machine. If
>> 93 you say Y here, the kernel will run on many, but not all,
>> 94 singleprocessor machines. On a singleprocessor machine, the kernel
>> 95 will run faster if you say N here.
251 96
252 config GENERIC_ISA_DMA !! 97 Note that if you say Y here and choose architecture "586" or
253 bool !! 98 "Pentium" under "Processor family", the kernel will not work on 486
>> 99 architectures. Similarly, multiprocessor kernels for the "PPro"
>> 100 architecture may not work on all Pentium based boards.
>> 101
>> 102 People using multiprocessor machines who say Y here should also say
>> 103 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
>> 104 Management" code will be disabled if you say Y here.
>> 105
>> 106 See also the <file:Documentation/smp.tex>,
>> 107 <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
>> 108 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
>> 109 <http://www.tldp.org/docs.html#howto>.
254 110
255 config FIQ !! 111 If you don't know what to do here, say N.
256 bool <<
257 112
258 config ARCH_MTD_XIP !! 113 config NR_CPUS
259 bool !! 114 int "Maximum number of CPUs (2-32)"
>> 115 depends on SMP
>> 116 default "32"
260 117
261 config ARM_PATCH_PHYS_VIRT !! 118 # Identify this as a Sparc32 build
262 bool "Patch physical to virtual transl !! 119 config SPARC32
>> 120 bool
263 default y 121 default y
264 depends on MMU <<
265 help 122 help
266 Patch phys-to-virt and virt-to-phys !! 123 SPARC is a family of RISC microprocessors designed and marketed by
267 boot and module load time according !! 124 Sun Microsystems, incorporated. They are very widely found in Sun
268 kernel in system memory. !! 125 workstations and clones. This port covers the original 32-bit SPARC;
269 !! 126 it is old and stable and usually considered one of the "big three"
270 This can only be used with non-XIP M !! 127 along with the Intel and Alpha ports. The UltraLinux project
271 of physical memory is at a 2 MiB bou !! 128 maintains both the SPARC32 and SPARC64 ports; its web page is
272 !! 129 available at <http://www.ultralinux.org/>.
273 Only disable this option if you know <<
274 this feature (eg, building a kernel <<
275 you need to shrink the kernel to the <<
276 130
277 config NEED_MACH_IO_H !! 131 # Global things across all Sun machines.
>> 132 config ISA
278 bool 133 bool
279 help 134 help
280 Select this when mach/io.h is requir !! 135 ISA is found on Espresso only and is not supported currently.
281 definitions for this platform. The !! 136 Say N
282 be avoided when possible. <<
283 137
284 config NEED_MACH_MEMORY_H !! 138 config EISA
285 bool 139 bool
286 help 140 help
287 Select this when mach/memory.h is re !! 141 EISA is not supported.
288 definitions for this platform. The !! 142 Say N
289 be avoided when possible. <<
290 <<
291 config PHYS_OFFSET <<
292 hex "Physical address of main memory" <<
293 depends on !ARM_PATCH_PHYS_VIRT || !AU <<
294 default DRAM_BASE if !MMU <<
295 default 0x00000000 if ARCH_FOOTBRIDGE <<
296 default 0x10000000 if ARCH_OMAP1 || AR <<
297 default 0xa0000000 if ARCH_PXA <<
298 default 0xc0000000 if ARCH_EP93XX || A <<
299 default 0 <<
300 help <<
301 Please provide the physical address <<
302 location of main memory in your syst <<
303 <<
304 config GENERIC_BUG <<
305 def_bool y <<
306 depends on BUG <<
307 <<
308 config PGTABLE_LEVELS <<
309 int <<
310 default 3 if ARM_LPAE <<
311 default 2 <<
312 <<
313 menu "System Type" <<
314 <<
315 config MMU <<
316 bool "MMU-based Paged Memory Managemen <<
317 default y <<
318 help <<
319 Select if you want MMU-based virtual <<
320 support by paged memory management. <<
321 <<
322 config ARM_SINGLE_ARMV7M <<
323 def_bool !MMU <<
324 select ARM_NVIC <<
325 select CPU_V7M <<
326 select NO_IOPORT_MAP <<
327 <<
328 config ARCH_MMAP_RND_BITS_MIN <<
329 default 8 <<
330 <<
331 config ARCH_MMAP_RND_BITS_MAX <<
332 default 14 if PAGE_OFFSET=0x40000000 <<
333 default 15 if PAGE_OFFSET=0x80000000 <<
334 default 16 <<
335 <<
336 config ARCH_MULTIPLATFORM <<
337 bool "Require kernel to be portable to <<
338 depends on MMU && !(ARCH_FOOTBRIDGE || <<
339 default y <<
340 help <<
341 In general, all Arm machines can be <<
342 kernel image, covering either Armv4/ <<
343 <<
344 However, some configuration options <<
345 specific physical addresses or enabl <<
346 break other machines. <<
347 <<
348 Selecting N here allows using those <<
349 DEBUG_UNCOMPRESS, XIP_KERNEL and ZBO <<
350 <<
351 source "arch/arm/Kconfig.platforms" <<
352 <<
353 # <<
354 # This is sorted alphabetically by mach-* path <<
355 # Kconfigs may be included either alphabetical <<
356 # plat- suffix) or along side the correspondin <<
357 # <<
358 source "arch/arm/mach-actions/Kconfig" <<
359 <<
360 source "arch/arm/mach-alpine/Kconfig" <<
361 <<
362 source "arch/arm/mach-artpec/Kconfig" <<
363 <<
364 source "arch/arm/mach-aspeed/Kconfig" <<
365 <<
366 source "arch/arm/mach-at91/Kconfig" <<
367 <<
368 source "arch/arm/mach-axxia/Kconfig" <<
369 <<
370 source "arch/arm/mach-bcm/Kconfig" <<
371 <<
372 source "arch/arm/mach-berlin/Kconfig" <<
373 <<
374 source "arch/arm/mach-clps711x/Kconfig" <<
375 <<
376 source "arch/arm/mach-davinci/Kconfig" <<
377 143
378 source "arch/arm/mach-digicolor/Kconfig" !! 144 config MCA
379 !! 145 bool
380 source "arch/arm/mach-dove/Kconfig" <<
381 <<
382 source "arch/arm/mach-ep93xx/Kconfig" <<
383 <<
384 source "arch/arm/mach-exynos/Kconfig" <<
385 <<
386 source "arch/arm/mach-footbridge/Kconfig" <<
387 <<
388 source "arch/arm/mach-gemini/Kconfig" <<
389 <<
390 source "arch/arm/mach-highbank/Kconfig" <<
391 <<
392 source "arch/arm/mach-hisi/Kconfig" <<
393 <<
394 source "arch/arm/mach-hpe/Kconfig" <<
395 <<
396 source "arch/arm/mach-imx/Kconfig" <<
397 <<
398 source "arch/arm/mach-ixp4xx/Kconfig" <<
399 <<
400 source "arch/arm/mach-keystone/Kconfig" <<
401 <<
402 source "arch/arm/mach-lpc32xx/Kconfig" <<
403 <<
404 source "arch/arm/mach-mediatek/Kconfig" <<
405 <<
406 source "arch/arm/mach-meson/Kconfig" <<
407 <<
408 source "arch/arm/mach-milbeaut/Kconfig" <<
409 <<
410 source "arch/arm/mach-mmp/Kconfig" <<
411 <<
412 source "arch/arm/mach-mstar/Kconfig" <<
413 <<
414 source "arch/arm/mach-mv78xx0/Kconfig" <<
415 <<
416 source "arch/arm/mach-mvebu/Kconfig" <<
417 <<
418 source "arch/arm/mach-mxs/Kconfig" <<
419 <<
420 source "arch/arm/mach-nomadik/Kconfig" <<
421 <<
422 source "arch/arm/mach-npcm/Kconfig" <<
423 <<
424 source "arch/arm/mach-omap1/Kconfig" <<
425 <<
426 source "arch/arm/mach-omap2/Kconfig" <<
427 <<
428 source "arch/arm/mach-orion5x/Kconfig" <<
429 <<
430 source "arch/arm/mach-pxa/Kconfig" <<
431 <<
432 source "arch/arm/mach-qcom/Kconfig" <<
433 <<
434 source "arch/arm/mach-realtek/Kconfig" <<
435 <<
436 source "arch/arm/mach-rpc/Kconfig" <<
437 <<
438 source "arch/arm/mach-rockchip/Kconfig" <<
439 <<
440 source "arch/arm/mach-s3c/Kconfig" <<
441 <<
442 source "arch/arm/mach-s5pv210/Kconfig" <<
443 <<
444 source "arch/arm/mach-sa1100/Kconfig" <<
445 <<
446 source "arch/arm/mach-shmobile/Kconfig" <<
447 <<
448 source "arch/arm/mach-socfpga/Kconfig" <<
449 <<
450 source "arch/arm/mach-spear/Kconfig" <<
451 <<
452 source "arch/arm/mach-sti/Kconfig" <<
453 <<
454 source "arch/arm/mach-stm32/Kconfig" <<
455 <<
456 source "arch/arm/mach-sunxi/Kconfig" <<
457 <<
458 source "arch/arm/mach-tegra/Kconfig" <<
459 <<
460 source "arch/arm/mach-ux500/Kconfig" <<
461 <<
462 source "arch/arm/mach-versatile/Kconfig" <<
463 <<
464 source "arch/arm/mach-vt8500/Kconfig" <<
465 <<
466 source "arch/arm/mach-zynq/Kconfig" <<
467 <<
468 # ARMv7-M architecture <<
469 config ARCH_LPC18XX <<
470 bool "NXP LPC18xx/LPC43xx" <<
471 depends on ARM_SINGLE_ARMV7M <<
472 select ARCH_HAS_RESET_CONTROLLER <<
473 select ARM_AMBA <<
474 select CLKSRC_LPC32XX <<
475 select PINCTRL <<
476 help 146 help
477 Support for NXP's LPC18xx Cortex-M3 !! 147 MCA is not supported.
478 high performance microcontrollers. !! 148 Say N
479 149
480 config ARCH_MPS2 !! 150 config PCMCIA
481 bool "ARM MPS2 platform" !! 151 tristate
482 depends on ARM_SINGLE_ARMV7M !! 152 ---help---
483 select ARM_AMBA !! 153 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
484 select CLKSRC_MPS2 !! 154 computer. These are credit-card size devices such as network cards,
485 help !! 155 modems or hard drives often used with laptops computers. There are
486 Support for Cortex-M Prototyping Sys !! 156 actually two varieties of these cards: the older 16 bit PCMCIA cards
487 with a range of available cores like !! 157 and the newer 32 bit CardBus cards. If you want to use CardBus
>> 158 cards, you need to say Y here and also to "CardBus support" below.
488 159
489 Please, note that depends which Appl !! 160 To use your PC-cards, you will need supporting software from David
490 for the platform may vary, so adjust !! 161 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
>> 162 for location). Please also read the PCMCIA-HOWTO, available from
>> 163 <http://www.tldp.org/docs.html#howto>.
491 164
492 # Definitions to make life easier !! 165 To compile this driver as modules, choose M here: the
493 config ARCH_ACORN !! 166 modules will be called pcmcia_core and ds.
494 bool <<
495 167
496 config PLAT_ORION !! 168 config SBUS
497 bool 169 bool
498 select CLKSRC_MMIO !! 170 default y
499 select GENERIC_IRQ_CHIP <<
500 select IRQ_DOMAIN <<
501 171
502 config PLAT_ORION_LEGACY !! 172 config SBUSCHAR
503 bool 173 bool
504 select PLAT_ORION !! 174 default y
505 175
506 config PLAT_VERSATILE !! 176 config SERIAL_CONSOLE
507 bool 177 bool
508 <<
509 source "arch/arm/mm/Kconfig" <<
510 <<
511 config IWMMXT <<
512 bool "Enable iWMMXt support" <<
513 depends on CPU_XSCALE || CPU_XSC3 || C <<
514 default y if PXA27x || PXA3xx || ARCH_ <<
515 help <<
516 Enable support for iWMMXt context sw <<
517 running on a CPU that supports it. <<
518 <<
519 if !MMU <<
520 source "arch/arm/Kconfig-nommu" <<
521 endif <<
522 <<
523 config PJ4B_ERRATA_4742 <<
524 bool "PJ4B Errata 4742: IDLE Wake Up C <<
525 depends on CPU_PJ4B && MACH_ARMADA_370 <<
526 default y 178 default y
527 help !! 179 ---help---
528 When coming out of either a Wait for !! 180 If you say Y here, it will be possible to use a serial port as the
529 Event (WFE) IDLE states, a specific !! 181 system console (the system console is the device which receives all
530 the retiring WFI/WFE instructions an !! 182 kernel messages and warnings and which allows logins in single user
531 instructions. This sensitivity can !! 183 mode). This could be useful if some terminal or printer is connected
532 Workaround: !! 184 to that serial port.
533 The software must insert either a Da <<
534 or Data Memory Barrier (DMB) command <<
535 instruction <<
536 <<
537 config ARM_ERRATA_326103 <<
538 bool "ARM errata: FSR write bit incorr <<
539 depends on CPU_V6 <<
540 help <<
541 Executing a SWP instruction to read- <<
542 of the FSR on the ARM 1136 prior to <<
543 treat the access as a read, preventi <<
544 causing the faulting task to liveloc <<
545 <<
546 config ARM_ERRATA_411920 <<
547 bool "ARM errata: Invalidation of the <<
548 depends on CPU_V6 || CPU_V6K <<
549 help <<
550 Invalidation of the Instruction Cach <<
551 fail. This erratum is present in 113 <<
552 It does not affect the MPCore. This <<
553 recommended workaround. <<
554 <<
555 config ARM_ERRATA_430973 <<
556 bool "ARM errata: Stale prediction on <<
557 depends on CPU_V7 <<
558 help <<
559 This option enables the workaround f <<
560 r1p* erratum. If a code sequence con <<
561 interworking branch is replaced with <<
562 same virtual address, whether due to <<
563 to physical address re-mapping, Cort <<
564 stale interworking branch prediction <<
565 executing the new code sequence in t <<
566 The workaround enables the BTB/BTAC <<
567 and also flushes the branch target c <<
568 Note that setting specific bits in t <<
569 available in non-secure mode. <<
570 <<
571 config ARM_ERRATA_458693 <<
572 bool "ARM errata: Processor deadlock w <<
573 depends on CPU_V7 <<
574 depends on !ARCH_MULTIPLATFORM <<
575 help <<
576 This option enables the workaround f <<
577 erratum. For very specific sequences <<
578 possible for a hazard condition inte <<
579 be incorrectly associated with a dif <<
580 hazard might then cause a processor <<
581 the L1 caching of the NEON accesses <<
582 in the ACTLR register. Note that set <<
583 register may not be available in non <<
584 available on a multiplatform kernel. <<
585 bootloader instead. <<
586 <<
587 config ARM_ERRATA_460075 <<
588 bool "ARM errata: Data written to the <<
589 depends on CPU_V7 <<
590 depends on !ARCH_MULTIPLATFORM <<
591 help <<
592 This option enables the workaround f <<
593 erratum. Any asynchronous access to <<
594 situation in which recent store tran <<
595 and overwritten with stale memory co <<
596 workaround disables the write-alloca <<
597 ACTLR register. Note that setting sp <<
598 may not be available in non-secure m <<
599 a multiplatform kernel. This should <<
600 instead. <<
601 <<
602 config ARM_ERRATA_742230 <<
603 bool "ARM errata: DMB operation may be <<
604 depends on CPU_V7 && SMP <<
605 depends on !ARCH_MULTIPLATFORM <<
606 help <<
607 This option enables the workaround f <<
608 (r1p0..r2p2) erratum. Under rare cir <<
609 between two write operations may not <<
610 ordering of the two writes. This wor <<
611 the diagnostic register of the Corte <<
612 instruction to behave as a DSB, ensu <<
613 the two writes. Note that setting sp <<
614 register may not be available in non <<
615 available on a multiplatform kernel. <<
616 bootloader instead. <<
617 <<
618 config ARM_ERRATA_742231 <<
619 bool "ARM errata: Incorrect hazard han <<
620 depends on CPU_V7 && SMP <<
621 depends on !ARCH_MULTIPLATFORM <<
622 help <<
623 This option enables the workaround f <<
624 (r2p0..r2p2) erratum. Under certain <<
625 Cortex-A9 MPCore micro-architecture, <<
626 accessing some data located in the s <<
627 data due to bad handling of the addr <<
628 replaced from one of the CPUs at the <<
629 accessing it. This workaround sets s <<
630 register of the Cortex-A9 which redu <<
631 capabilities of the processor. Note <<
632 diagnostics register may not be avai <<
633 is not available on a multiplatform <<
634 the bootloader instead. <<
635 <<
636 config ARM_ERRATA_643719 <<
637 bool "ARM errata: LoUIS bit field in C <<
638 depends on CPU_V7 && SMP <<
639 default y <<
640 help <<
641 This option enables the workaround f <<
642 r1p0) erratum. On affected cores the <<
643 register returns zero when it should <<
644 corrects this value, ensuring cache <<
645 it behave as intended and avoiding d <<
646 <<
647 config ARM_ERRATA_720789 <<
648 bool "ARM errata: TLBIASIDIS and TLBIM <<
649 depends on CPU_V7 <<
650 help <<
651 This option enables the workaround f <<
652 r2p0) erratum. A faulty ASID can be <<
653 broadcasted CP15 TLB maintenance ope <<
654 As a consequence of this erratum, so <<
655 invalidated are not, resulting in an <<
656 tables. The workaround changes the T <<
657 entries regardless of the ASID. <<
658 <<
659 config ARM_ERRATA_743622 <<
660 bool "ARM errata: Faulty hazard checki <<
661 depends on CPU_V7 <<
662 depends on !ARCH_MULTIPLATFORM <<
663 help <<
664 This option enables the workaround f <<
665 (r2p*) erratum. Under very rare cond <<
666 optimisation in the Cortex-A9 Store <<
667 corruption. This workaround sets a s <<
668 register of the Cortex-A9 which disa <<
669 optimisation, preventing the defect <<
670 visible impact on the overall perfor <<
671 processor. Note that setting specifi <<
672 may not be available in non-secure m <<
673 multiplatform kernel. This should be <<
674 <<
675 config ARM_ERRATA_751472 <<
676 bool "ARM errata: Interrupted ICIALLUI <<
677 depends on CPU_V7 <<
678 depends on !ARCH_MULTIPLATFORM <<
679 help <<
680 This option enables the workaround f <<
681 to r3p0) erratum. An interrupted ICI <<
682 completion of a following broadcaste <<
683 operation is received by a CPU befor <<
684 potentially leading to corrupted ent <<
685 Note that setting specific bits in t <<
686 not be available in non-secure mode <<
687 a multiplatform kernel. This should <<
688 instead. <<
689 <<
690 config ARM_ERRATA_754322 <<
691 bool "ARM errata: possible faulty MMU <<
692 depends on CPU_V7 <<
693 help <<
694 This option enables the workaround f <<
695 r3p*) erratum. A speculative memory <<
696 which starts prior to an ASID switch <<
697 can populate the micro-TLB with a st <<
698 the new ASID. This workaround places <<
699 switching code so that no page table <<
700 <<
701 config ARM_ERRATA_754327 <<
702 bool "ARM errata: no automatic Store B <<
703 depends on CPU_V7 && SMP <<
704 help <<
705 This option enables the workaround f <<
706 r2p0) erratum. The Store Buffer does <<
707 mechanism and therefore a livelock m <<
708 continuously polls a memory location <<
709 This workaround defines cpu_relax() <<
710 written polling loops from denying v <<
711 <<
712 config ARM_ERRATA_364296 <<
713 bool "ARM errata: Possible cache data <<
714 depends on CPU_V6 <<
715 help <<
716 This options enables the workaround <<
717 r0p2 erratum (possible cache data co <<
718 hit-under-miss enabled). It sets the <<
719 the auxiliary control register and t <<
720 register, thus disabling hit-under-m <<
721 processor into full low interrupt la <<
722 is not affected. <<
723 <<
724 config ARM_ERRATA_764369 <<
725 bool "ARM errata: Data cache line main <<
726 depends on CPU_V7 && SMP <<
727 help <<
728 This option enables the workaround f <<
729 affecting Cortex-A9 MPCore with two <<
730 current revisions). Under certain ti <<
731 cache line maintenance operation by <<
732 Shareable memory region may fail to <<
733 Point of Coherency or to the Point o <<
734 system. This workaround adds a DSB i <<
735 relevant cache maintenance functions <<
736 in the diagnostic control register o <<
737 <<
738 config ARM_ERRATA_764319 <<
739 bool "ARM errata: Read to DBGPRSR and <<
740 depends on CPU_V7 <<
741 help <<
742 This option enables the workaround f <<
743 CP14 read accesses to the DBGPRSR an <<
744 unexpected Undefined Instruction exc <<
745 external pin is set to 0, even when <<
746 from a privileged mode. This work ar <<
747 way the kernel does not stop executi <<
748 <<
749 config ARM_ERRATA_775420 <<
750 bool "ARM errata: A data cache maintena <<
751 depends on CPU_V7 <<
752 help <<
753 This option enables the workaround fo <<
754 r2p6,r2p8,r2p10,r3p0) erratum. In cas <<
755 operation aborts with MMU exception, <<
756 to deadlock. This workaround puts DSB <<
757 an abort may occur on cache maintenan <<
758 <<
759 config ARM_ERRATA_798181 <<
760 bool "ARM errata: TLBI/DSB failure on <<
761 depends on CPU_V7 && SMP <<
762 help <<
763 On Cortex-A15 (r0p0..r3p2) the TLBI* <<
764 adequately shooting down all use of <<
765 option enables the Linux kernel work <<
766 which sends an IPI to the CPUs that <<
767 as the one being invalidated. <<
768 <<
769 config ARM_ERRATA_773022 <<
770 bool "ARM errata: incorrect instructio <<
771 depends on CPU_V7 <<
772 help <<
773 This option enables the workaround f <<
774 (up to r0p4) erratum. In certain rar <<
775 loop buffer may deliver incorrect in <<
776 workaround disables the loop buffer <<
777 <<
778 config ARM_ERRATA_818325_852422 <<
779 bool "ARM errata: A12: some seqs of op <<
780 depends on CPU_V7 <<
781 help <<
782 This option enables the workaround f <<
783 - Cortex-A12 818325: Execution of an <<
784 instruction might deadlock. Fixed <<
785 - Cortex-A12 852422: Execution of a <<
786 lead to either a data corruption o <<
787 any Cortex-A12 cores yet. <<
788 This workaround for all both errata <<
789 Feature Register. This bit disables <<
790 sequence of 2 instructions that use <<
791 <<
792 config ARM_ERRATA_821420 <<
793 bool "ARM errata: A12: sequence of VMO <<
794 depends on CPU_V7 <<
795 help <<
796 This option enables the workaround f <<
797 (all revs) erratum. In very rare tim <<
798 of VMOV to Core registers instructio <<
799 one is in the shadow of a branch or <<
800 deadlock when the VMOV instructions <<
801 <<
802 config ARM_ERRATA_825619 <<
803 bool "ARM errata: A12: DMB NSHST/ISHST <<
804 depends on CPU_V7 <<
805 help <<
806 This option enables the workaround f <<
807 (all revs) erratum. Within rare timi <<
808 DMB NSHST or DMB ISHST instruction f <<
809 and Device/Strongly-Ordered loads an <<
810 <<
811 config ARM_ERRATA_857271 <<
812 bool "ARM errata: A12: CPU might deadl <<
813 depends on CPU_V7 <<
814 help <<
815 This option enables the workaround f <<
816 (all revs) erratum. Under very rare <<
817 hang. The workaround is expected to <<
818 <<
819 config ARM_ERRATA_852421 <<
820 bool "ARM errata: A17: DMB ST might fa <<
821 depends on CPU_V7 <<
822 help <<
823 This option enables the workaround f <<
824 (r1p0, r1p1, r1p2) erratum. Under ve <<
825 execution of a DMB ST instruction mi <<
826 stores from GroupA and stores from G <<
827 <<
828 config ARM_ERRATA_852423 <<
829 bool "ARM errata: A17: some seqs of op <<
830 depends on CPU_V7 <<
831 help <<
832 This option enables the workaround f <<
833 - Cortex-A17 852423: Execution of a <<
834 lead to either a data corruption o <<
835 any Cortex-A17 cores yet. <<
836 This is identical to Cortex-A12 erra <<
837 config option from the A12 erratum d <<
838 for and handled. <<
839 <<
840 config ARM_ERRATA_857272 <<
841 bool "ARM errata: A17: CPU might deadl <<
842 depends on CPU_V7 <<
843 help <<
844 This option enables the workaround f <<
845 This erratum is not known to be fixe <<
846 This is identical to Cortex-A12 erra <<
847 config option from the A12 erratum d <<
848 for and handled. <<
849 185
850 endmenu !! 186 Even if you say Y here, the currently visible virtual console
>> 187 (/dev/tty0) will still be used as the system console by default, but
>> 188 you can alter that using a kernel command line option such as
>> 189 "console=ttyS1". (Try "man bootparam" or see the documentation of
>> 190 your boot loader (lilo or loadlin) about how to pass options to the
>> 191 kernel at boot time.)
851 192
852 source "arch/arm/common/Kconfig" !! 193 If you don't have a VGA card installed and you say Y here, the
>> 194 kernel will automatically use the first serial line, /dev/ttyS0, as
>> 195 system console.
853 196
854 menu "Bus support" !! 197 If unsure, say N.
855 198
856 config ISA !! 199 config SUN_AUXIO
857 bool 200 bool
858 help !! 201 default y
859 Find out whether you have ISA slots <<
860 name of a bus system, i.e. the way t <<
861 inside your box. Other bus systems <<
862 (MCA) or VESA. ISA is an older syst <<
863 newer boards don't support it. If y <<
864 202
865 # Select ISA DMA interface !! 203 config SUN_IO
866 config ISA_DMA_API <<
867 bool 204 bool
>> 205 default y
868 206
869 config ARM_ERRATA_814220 !! 207 config RWSEM_GENERIC_SPINLOCK
870 bool "ARM errata: Cache maintenance by <<
871 depends on CPU_V7 <<
872 help <<
873 The v7 ARM states that all cache and <<
874 operations that do not specify an ad <<
875 each other, in program order. <<
876 However, because of this erratum, an <<
877 operation can overtake an L1 set/way <<
878 This ERRATA only affected the Cortex <<
879 r0p4, r0p5. <<
880 <<
881 endmenu <<
882 <<
883 menu "Kernel Features" <<
884 <<
885 config HAVE_SMP <<
886 bool 208 bool
887 help <<
888 This option should be selected by ma <<
889 capable CPU. <<
890 <<
891 The only effect of this option is to <<
892 options available to the user for co <<
893 <<
894 config SMP <<
895 bool "Symmetric Multi-Processing" <<
896 depends on CPU_V6K || CPU_V7 <<
897 depends on HAVE_SMP <<
898 depends on MMU || ARM_MPU <<
899 select IRQ_WORK <<
900 help <<
901 This enables support for systems wit <<
902 a system with only one CPU, say N. I <<
903 than one CPU, say Y. <<
904 <<
905 If you say N here, the kernel will r <<
906 machines, but will use only one CPU <<
907 you say Y here, the kernel will run <<
908 uniprocessor machines. On a uniproce <<
909 will run faster if you say N here. <<
910 <<
911 See also <file:Documentation/arch/x8 <<
912 <file:Documentation/admin-guide/lock <<
913 <http://tldp.org/HOWTO/SMP-HOWTO.htm <<
914 <<
915 If you don't know what to do here, s <<
916 <<
917 config SMP_ON_UP <<
918 bool "Allow booting SMP kernel on unip <<
919 depends on SMP && MMU <<
920 default y 209 default y
921 help <<
922 SMP kernels contain instructions whi <<
923 Enabling this option allows the kern <<
924 these instructions safe. Disabling <<
925 savings. <<
926 <<
927 If you don't know what to do here, s <<
928 <<
929 <<
930 config CURRENT_POINTER_IN_TPIDRURO <<
931 def_bool y <<
932 depends on CPU_32v6K && !CPU_V6 <<
933 <<
934 config IRQSTACKS <<
935 def_bool y <<
936 select HAVE_IRQ_EXIT_ON_IRQ_STACK <<
937 select HAVE_SOFTIRQ_ON_OWN_STACK <<
938 <<
939 config ARM_CPU_TOPOLOGY <<
940 bool "Support cpu topology definition" <<
941 depends on SMP && CPU_V7 <<
942 default y <<
943 help <<
944 Support ARM cpu topology definition. <<
945 affinity between processors which is <<
946 topology of an ARM System. <<
947 <<
948 config SCHED_MC <<
949 bool "Multi-core scheduler support" <<
950 depends on ARM_CPU_TOPOLOGY <<
951 help <<
952 Multi-core scheduler support improve <<
953 making when dealing with multi-core <<
954 increased overhead in some places. I <<
955 <<
956 config SCHED_SMT <<
957 bool "SMT scheduler support" <<
958 depends on ARM_CPU_TOPOLOGY <<
959 help <<
960 Improves the CPU scheduler's decisio <<
961 MultiThreading at a cost of slightly <<
962 places. If unsure say N here. <<
963 210
964 config HAVE_ARM_SCU !! 211 config RWSEM_XCHGADD_ALGORITHM
965 bool 212 bool
966 help <<
967 This option enables support for the <<
968 <<
969 config HAVE_ARM_ARCH_TIMER <<
970 bool "Architected timer support" <<
971 depends on CPU_V7 <<
972 select ARM_ARCH_TIMER <<
973 help <<
974 This option enables support for the <<
975 213
976 config HAVE_ARM_TWD !! 214 config SUN_PM
977 bool 215 bool
>> 216 default y
978 help 217 help
979 This options enables support for the !! 218 Enable power management and CPU standby features on supported
>> 219 SPARC platforms.
980 220
981 config MCPM !! 221 config SUN4
982 bool "Multi-Cluster Power Management" !! 222 bool "Support for SUN4 machines (disables SUN4[CDM] support)"
983 depends on CPU_V7 && SMP <<
984 help 223 help
985 This option provides the common powe !! 224 Say Y here if, and only if, your machine is a sun4. Note that
986 for (multi-)cluster based systems, s !! 225 a kernel compiled with this option will run only on sun4.
987 systems. !! 226 (And the current version will probably work only on sun4/330.)
988 227
989 config MCPM_QUAD_CLUSTER !! 228 if !SUN4
990 bool <<
991 depends on MCPM <<
992 help <<
993 To avoid wasting resources unnecessa <<
994 to 2 clusters by default. <<
995 Platforms with 3 or 4 clusters that <<
996 option to allow the additional clust <<
997 <<
998 config BIG_LITTLE <<
999 bool "big.LITTLE support (Experimental <<
1000 depends on CPU_V7 && SMP <<
1001 select MCPM <<
1002 help <<
1003 This option enables support selecti <<
1004 system architecture. <<
1005 229
1006 config BL_SWITCHER !! 230 config PCI
1007 bool "big.LITTLE switcher support" !! 231 bool "Support for PCI and PS/2 keyboard/mouse"
1008 depends on BIG_LITTLE && MCPM && HOTP <<
1009 select CPU_PM <<
1010 help 232 help
1011 The big.LITTLE "switcher" provides !! 233 CONFIG_PCI is needed for all JavaStation's (including MrCoffee),
1012 transparently handle transition bet !! 234 CP-1200, JavaEngine-1, Corona, Red October, and Serengeti SGSC.
1013 and a cluster of A7's in a big.LITT !! 235 All of these platforms are extremely obscure, so say N if unsure.
1014 <<
1015 config BL_SWITCHER_DUMMY_IF <<
1016 tristate "Simple big.LITTLE switcher <<
1017 depends on BL_SWITCHER && DEBUG_KERNE <<
1018 help <<
1019 This is a simple and dummy char dev <<
1020 the big.LITTLE switcher core code. <<
1021 debugging purposes only. <<
1022 <<
1023 choice <<
1024 prompt "Memory split" <<
1025 depends on MMU <<
1026 default VMSPLIT_3G <<
1027 help <<
1028 Select the desired split between ke <<
1029 236
1030 If you are not absolutely sure what !! 237 source "drivers/pci/Kconfig"
1031 option alone! <<
1032 238
1033 config VMSPLIT_3G !! 239 endif
1034 bool "3G/1G user/kernel split <<
1035 config VMSPLIT_3G_OPT <<
1036 depends on !ARM_LPAE <<
1037 bool "3G/1G user/kernel split <<
1038 config VMSPLIT_2G <<
1039 bool "2G/2G user/kernel split <<
1040 config VMSPLIT_1G <<
1041 bool "1G/3G user/kernel split <<
1042 endchoice <<
1043 <<
1044 config PAGE_OFFSET <<
1045 hex <<
1046 default PHYS_OFFSET if !MMU <<
1047 default 0x40000000 if VMSPLIT_1G <<
1048 default 0x80000000 if VMSPLIT_2G <<
1049 default 0xB0000000 if VMSPLIT_3G_OPT <<
1050 default 0xC0000000 <<
1051 <<
1052 config KASAN_SHADOW_OFFSET <<
1053 hex <<
1054 depends on KASAN <<
1055 default 0x1f000000 if PAGE_OFFSET=0x4 <<
1056 default 0x5f000000 if PAGE_OFFSET=0x8 <<
1057 default 0x9f000000 if PAGE_OFFSET=0xC <<
1058 default 0x8f000000 if PAGE_OFFSET=0xB <<
1059 default 0xffffffff <<
1060 240
1061 config NR_CPUS !! 241 config SUN_OPENPROMFS
1062 int "Maximum number of CPUs (2-32)" !! 242 tristate "Openprom tree appears in /proc/openprom"
1063 range 2 16 if DEBUG_KMAP_LOCAL <<
1064 range 2 32 if !DEBUG_KMAP_LOCAL <<
1065 depends on SMP <<
1066 default "4" <<
1067 help 243 help
1068 The maximum number of CPUs that the !! 244 If you say Y, the OpenPROM device tree will be available as a
1069 Up to 32 CPUs can be supported, or !! 245 virtual file system, which you can mount to /proc/openprom by "mount
1070 debugging is enabled, which uses ha !! 246 -t openpromfs none /proc/openprom".
1071 slots as guard regions. !! 247
>> 248 To compile the /proc/openprom support as a module, choose M here: the
>> 249 module will be called openpromfs. If unsure, choose M.
>> 250
>> 251 source "fs/Kconfig.binfmt"
>> 252
>> 253 config SUNOS_EMUL
>> 254 bool "SunOS binary emulation"
>> 255 help
>> 256 This allows you to run most SunOS binaries. If you want to do this,
>> 257 say Y here and place appropriate files in /usr/gnemul/sunos. See
>> 258 <http://www.ultralinux.org/faq.html> for more information. If you
>> 259 want to run SunOS binaries on an Ultra you must also say Y to
>> 260 "Kernel support for 32-bit a.out binaries" above.
>> 261
>> 262 source "drivers/parport/Kconfig"
>> 263
>> 264 config PRINTER
>> 265 tristate "Parallel printer support"
>> 266 depends on PARPORT
>> 267 ---help---
>> 268 If you intend to attach a printer to the parallel port of your Linux
>> 269 box (as opposed to using a serial printer; if the connector at the
>> 270 printer has 9 or 25 holes ["female"], then it's serial), say Y.
>> 271 Also read the Printing-HOWTO, available from
>> 272 <http://www.tldp.org/docs.html#howto>.
>> 273
>> 274 It is possible to share one parallel port among several devices
>> 275 (e.g. printer and ZIP drive) and it is safe to compile the
>> 276 corresponding drivers into the kernel. If you want to compile this
>> 277 driver as a module however, choose M here and read
>> 278 <file:Documentation/parport.txt>. The module will be called lp.
>> 279
>> 280 If you have several parallel ports, you can specify which ports to
>> 281 use with the "lp" kernel command line option. (Try "man bootparam"
>> 282 or see the documentation of your boot loader (lilo or loadlin) about
>> 283 how to pass options to the kernel at boot time.) The syntax of the
>> 284 "lp" command line option can be found in <file:drivers/char/lp.c>.
1072 285
1073 config HOTPLUG_CPU !! 286 If you have more than 8 printers, you need to increase the LP_NO
1074 bool "Support for hot-pluggable CPUs" !! 287 macro in lp.c and the PARPORT_MAX macro in parport.h.
1075 depends on SMP <<
1076 select GENERIC_IRQ_MIGRATION <<
1077 help <<
1078 Say Y here to experiment with turni <<
1079 can be controlled through /sys/devi <<
1080 288
1081 config ARM_PSCI !! 289 endmenu
1082 bool "Support for the ARM Power State <<
1083 depends on HAVE_ARM_SMCCC <<
1084 select ARM_PSCI_FW <<
1085 help <<
1086 Say Y here if you want Linux to com <<
1087 implementing the PSCI specification <<
1088 management operations described in <<
1089 0022A ("Power State Coordination In <<
1090 ARM processors"). <<
1091 <<
1092 config HZ_FIXED <<
1093 int <<
1094 default 128 if SOC_AT91RM9200 <<
1095 default 0 <<
1096 <<
1097 choice <<
1098 depends on HZ_FIXED = 0 <<
1099 prompt "Timer frequency" <<
1100 <<
1101 config HZ_100 <<
1102 bool "100 Hz" <<
1103 <<
1104 config HZ_200 <<
1105 bool "200 Hz" <<
1106 <<
1107 config HZ_250 <<
1108 bool "250 Hz" <<
1109 <<
1110 config HZ_300 <<
1111 bool "300 Hz" <<
1112 <<
1113 config HZ_500 <<
1114 bool "500 Hz" <<
1115 <<
1116 config HZ_1000 <<
1117 bool "1000 Hz" <<
1118 <<
1119 endchoice <<
1120 <<
1121 config HZ <<
1122 int <<
1123 default HZ_FIXED if HZ_FIXED != 0 <<
1124 default 100 if HZ_100 <<
1125 default 200 if HZ_200 <<
1126 default 250 if HZ_250 <<
1127 default 300 if HZ_300 <<
1128 default 500 if HZ_500 <<
1129 default 1000 <<
1130 <<
1131 config SCHED_HRTICK <<
1132 def_bool HIGH_RES_TIMERS <<
1133 <<
1134 config THUMB2_KERNEL <<
1135 bool "Compile the kernel in Thumb-2 m <<
1136 depends on (CPU_V7 || CPU_V7M) && !CP <<
1137 default y if CPU_THUMBONLY <<
1138 select ARM_UNWIND <<
1139 help <<
1140 By enabling this option, the kernel <<
1141 Thumb-2 mode. <<
1142 290
1143 If unsure, say N. !! 291 source "drivers/base/Kconfig"
1144 292
1145 config ARM_PATCH_IDIV !! 293 source "drivers/video/Kconfig"
1146 bool "Runtime patch udiv/sdiv instruc <<
1147 depends on CPU_32v7 <<
1148 default y <<
1149 help <<
1150 The ARM compiler inserts calls to _ <<
1151 __aeabi_uidiv() when it needs to pe <<
1152 and unsigned integers. Some v7 CPUs <<
1153 and udiv instructions that can be u <<
1154 functions. <<
1155 <<
1156 Enabling this option allows the ker <<
1157 replace the first two instructions <<
1158 with the sdiv or udiv plus "bx lr" <<
1159 it is running on supports them. Typ <<
1160 and less power intensive than runni <<
1161 code to do integer division. <<
1162 <<
1163 config AEABI <<
1164 bool "Use the ARM EABI to compile the <<
1165 !CPU_V7M && !CPU_V6 && !CPU_V <<
1166 default CPU_V7 || CPU_V7M || CPU_V6 | <<
1167 help <<
1168 This option allows for the kernel t <<
1169 ARM ABI (aka EABI). This is only u <<
1170 space environment that is also comp <<
1171 <<
1172 Since there are major incompatibili <<
1173 EABI, especially with regard to str <<
1174 option also changes the kernel sysc <<
1175 disambiguate both ABIs and allow fo <<
1176 (selected with CONFIG_OABI_COMPAT). <<
1177 <<
1178 To use this you need GCC version 4. <<
1179 <<
1180 config OABI_COMPAT <<
1181 bool "Allow old ABI binaries to run w <<
1182 depends on AEABI && !THUMB2_KERNEL <<
1183 help <<
1184 This option preserves the old sysca <<
1185 new (ARM EABI) one. It also provide <<
1186 intercept syscalls that have struct <<
1187 in memory differs between the legac <<
1188 (only for non "thumb" binaries). Th <<
1189 overhead to all syscalls and produc <<
1190 <<
1191 The seccomp filter system will not <<
1192 selected, since there is no way yet <<
1193 between calling conventions during <<
1194 <<
1195 If you know you'll be using only pu <<
1196 can say N here. If this option is n <<
1197 to execute a legacy ABI binary then <<
1198 UNPREDICTABLE (in fact it can be pr <<
1199 at all). If in doubt say N. <<
1200 <<
1201 config ARCH_SELECT_MEMORY_MODEL <<
1202 def_bool y <<
1203 <<
1204 config ARCH_FLATMEM_ENABLE <<
1205 def_bool !(ARCH_RPC || ARCH_SA1100) <<
1206 <<
1207 config ARCH_SPARSEMEM_ENABLE <<
1208 def_bool !ARCH_FOOTBRIDGE <<
1209 select SPARSEMEM_STATIC if SPARSEMEM <<
1210 294
1211 config HIGHMEM !! 295 source "drivers/mtd/Kconfig"
1212 bool "High Memory Support" <<
1213 depends on MMU <<
1214 select KMAP_LOCAL <<
1215 select KMAP_LOCAL_NON_LINEAR_PTE_ARRA <<
1216 help <<
1217 The address space of ARM processors <<
1218 and it has to accommodate user addr <<
1219 space as well as some memory mapped <<
1220 have a large amount of physical mem <<
1221 memory can be "permanently mapped" <<
1222 memory that is not permanently mapp <<
1223 <<
1224 Depending on the selected kernel/us <<
1225 vmalloc space and actual amount of <<
1226 option which should result in a sli <<
1227 <<
1228 If unsure, say n. <<
1229 <<
1230 config HIGHPTE <<
1231 bool "Allocate 2nd-level pagetables f <<
1232 depends on HIGHMEM <<
1233 default y <<
1234 help <<
1235 The VM uses one page of physical me <<
1236 For systems with a lot of processes <<
1237 precious low memory, eventually lea <<
1238 consumed by page tables. Setting t <<
1239 user-space 2nd level page tables to <<
1240 <<
1241 config ARM_PAN <<
1242 bool "Enable privileged no-access" <<
1243 depends on MMU <<
1244 default y <<
1245 help <<
1246 Increase kernel security by ensurin <<
1247 are unable to access userspace addr <<
1248 use-after-free bugs becoming an exp <<
1249 by ensuring that magic values (such <<
1250 fault when dereferenced. <<
1251 <<
1252 The implementation uses CPU domains <<
1253 disabling of TTBR0 page table walks <<
1254 <<
1255 config CPU_SW_DOMAIN_PAN <<
1256 def_bool y <<
1257 depends on ARM_PAN && !ARM_LPAE <<
1258 help <<
1259 Enable use of CPU domains to implem <<
1260 296
1261 CPUs with low-vector mappings use a !! 297 source "drivers/serial/Kconfig"
1262 Their lower 1MB needs to remain acc <<
1263 the remainder of userspace will bec <<
1264 <<
1265 config CPU_TTBR0_PAN <<
1266 def_bool y <<
1267 depends on ARM_PAN && ARM_LPAE <<
1268 help <<
1269 Enable privileged no-access by disa <<
1270 running in kernel mode. <<
1271 298
1272 config HW_PERF_EVENTS !! 299 if !SUN4
1273 def_bool y !! 300 source "drivers/sbus/char/Kconfig"
1274 depends on ARM_PMU !! 301 endif
1275 <<
1276 config ARM_MODULE_PLTS <<
1277 bool "Use PLTs to allow module memory <<
1278 depends on MODULES <<
1279 select KASAN_VMALLOC if KASAN <<
1280 default y <<
1281 help <<
1282 Allocate PLTs when loading modules <<
1283 targets are too far away for their <<
1284 in the instructions themselves can <<
1285 module's PLT. This allows modules t <<
1286 vmalloc area after the dedicated mo <<
1287 exhausted. The modules will use sli <<
1288 rounding up to page size, the actua <<
1289 the same. <<
1290 <<
1291 Disabling this is usually safe for <<
1292 configurations. If unsure, say y. <<
1293 <<
1294 config ARCH_FORCE_MAX_ORDER <<
1295 int "Order of maximal physically cont <<
1296 default "11" if SOC_AM33XX <<
1297 default "8" if SA1111 <<
1298 default "10" <<
1299 help <<
1300 The kernel page allocator limits th <<
1301 contiguous allocations. The limit i <<
1302 defines the maximal power of two of <<
1303 allocated as a single contiguous bl <<
1304 overriding the default setting when <<
1305 large blocks of physically contiguo <<
1306 <<
1307 Don't change if unsure. <<
1308 <<
1309 config ALIGNMENT_TRAP <<
1310 def_bool CPU_CP15_MMU <<
1311 select HAVE_PROC_CPU if PROC_FS <<
1312 help <<
1313 ARM processors cannot fetch/store i <<
1314 naturally aligned on the bus, i.e., <<
1315 address divisible by 4. On 32-bit A <<
1316 fetch/store instructions will be em <<
1317 here, which has a severe performanc <<
1318 correct operation of some network p <<
1319 configuration it is safe to say N, <<
1320 <<
1321 config UACCESS_WITH_MEMCPY <<
1322 bool "Use kernel mem{cpy,set}() for { <<
1323 depends on MMU <<
1324 default y if CPU_FEROCEON <<
1325 help <<
1326 Implement faster copy_to_user and c <<
1327 cores where a 8-word STM instructio <<
1328 memory write throughput than a sequ <<
1329 <<
1330 A possible side effect is a slight <<
1331 between threads sharing the same ad <<
1332 such copy operations with large buf <<
1333 302
1334 However, if the CPU data cache is u <<
1335 this option is unlikely to provide <<
1336 303
1337 config PARAVIRT !! 304 menu "Block devices"
1338 bool "Enable paravirtualization code" <<
1339 help <<
1340 This changes the kernel so it can m <<
1341 under a hypervisor, potentially imp <<
1342 over full virtualization. <<
1343 <<
1344 config PARAVIRT_TIME_ACCOUNTING <<
1345 bool "Paravirtual steal time accounti <<
1346 select PARAVIRT <<
1347 help <<
1348 Select this option to enable fine g <<
1349 accounting. Time spent executing ot <<
1350 the current vCPU is discounted from <<
1351 that, there can be a small performa <<
1352 <<
1353 If in doubt, say N here. <<
1354 <<
1355 config XEN_DOM0 <<
1356 def_bool y <<
1357 depends on XEN <<
1358 <<
1359 config XEN <<
1360 bool "Xen guest support on ARM" <<
1361 depends on ARM && AEABI && OF <<
1362 depends on CPU_V7 && !CPU_V6 <<
1363 depends on !GENERIC_ATOMIC64 <<
1364 depends on MMU <<
1365 select ARCH_DMA_ADDR_T_64BIT <<
1366 select ARM_PSCI <<
1367 select SWIOTLB <<
1368 select SWIOTLB_XEN <<
1369 select PARAVIRT <<
1370 help <<
1371 Say Y if you want to run Linux in a <<
1372 305
1373 config CC_HAVE_STACKPROTECTOR_TLS !! 306 config BLK_DEV_FD
1374 def_bool $(cc-option,-mtp=cp15 -mstac !! 307 bool "Normal floppy disk support"
>> 308 ---help---
>> 309 If you want to use the floppy disk drive(s) of your PC under Linux,
>> 310 say Y. Information about this driver, especially important for IBM
>> 311 Thinkpad users, is contained in <file:Documentation/floppy.txt>.
>> 312 That file also contains the location of the Floppy driver FAQ as
>> 313 well as location of the fdutils package used to configure additional
>> 314 parameters of the driver at run time.
>> 315
>> 316 To compile this driver as a module, choose M here: the
>> 317 module will be called floppy.
>> 318
>> 319 config BLK_DEV_LOOP
>> 320 tristate "Loopback device support"
>> 321 ---help---
>> 322 Saying Y here will allow you to use a regular file as a block
>> 323 device; you can then create a file system on that block device and
>> 324 mount it just as you would mount other block devices such as hard
>> 325 drive partitions, CD-ROM drives or floppy drives. The loop devices
>> 326 are block special device files with major number 7 and typically
>> 327 called /dev/loop0, /dev/loop1 etc.
>> 328
>> 329 This is useful if you want to check an ISO 9660 file system before
>> 330 burning the CD, or if you want to use floppy images without first
>> 331 writing them to floppy. Furthermore, some Linux distributions avoid
>> 332 the need for a dedicated Linux partition by keeping their complete
>> 333 root file system inside a DOS FAT file using this loop device
>> 334 driver.
>> 335
>> 336 The loop device driver can also be used to "hide" a file system in a
>> 337 disk partition, floppy, or regular file, either using encryption
>> 338 (scrambling the data) or steganography (hiding the data in the low
>> 339 bits of, say, a sound file). This is also safe if the file resides
>> 340 on a remote file server. If you want to do this, you will first have
>> 341 to acquire and install a kernel patch from
>> 342 <ftp://ftp.kerneli.org/pub/kerneli/>, and then you need to
>> 343 say Y to this option.
>> 344
>> 345 Note that alternative ways to use encrypted file systems are
>> 346 provided by the cfs package, which can be gotten from
>> 347 <ftp://ftp.kerneli.org/pub/kerneli/net-source/>, and the newer tcfs
>> 348 package, available at <http://tcfs.dia.unisa.it/>. You do not need
>> 349 to say Y here if you want to use one of these. However, using cfs
>> 350 requires saying Y to "NFS file system support" below while using
>> 351 tcfs requires applying a kernel patch. An alternative steganography
>> 352 solution is provided by StegFS, also available from
>> 353 <ftp://ftp.kerneli.org/pub/kerneli/net-source/>.
>> 354
>> 355 To use the loop device, you need the losetup utility and a recent
>> 356 version of the mount program, both contained in the util-linux
>> 357 package. The location and current version number of util-linux is
>> 358 contained in the file <file:Documentation/Changes>.
>> 359
>> 360 Note that this loop device has nothing to do with the loopback
>> 361 device used for network connections from the machine to itself.
>> 362
>> 363 To compile this driver as a module, choose M here: the
>> 364 module will be called loop.
>> 365
>> 366 Most users will answer N here.
>> 367
>> 368 config BLK_DEV_NBD
>> 369 tristate "Network block device support"
>> 370 depends on NET
>> 371 ---help---
>> 372 Saying Y here will allow your computer to be a client for network
>> 373 block devices, i.e. it will be able to use block devices exported by
>> 374 servers (mount file systems on them etc.). Communication between
>> 375 client and server works over TCP/IP networking, but to the client
>> 376 program this is hidden: it looks like a regular local file access to
>> 377 a block device special file such as /dev/nd0.
>> 378
>> 379 Network block devices also allows you to run a block-device in
>> 380 userland (making server and client physically the same computer,
>> 381 communicating using the loopback network device).
>> 382
>> 383 Read <file:Documentation/nbd.txt> for more information, especially
>> 384 about where to find the server code, which runs in user space and
>> 385 does not need special kernel support.
1375 386
1376 config STACKPROTECTOR_PER_TASK !! 387 Note that this has nothing to do with the network file systems NFS
1377 bool "Use a unique stack canary value !! 388 or Coda; you can say N here even if you intend to use NFS or Coda.
1378 depends on STACKPROTECTOR && CURRENT_ <<
1379 depends on GCC_PLUGINS || CC_HAVE_STA <<
1380 select GCC_PLUGIN_ARM_SSP_PER_TASK if <<
1381 default y <<
1382 help <<
1383 Due to the fact that GCC uses an or <<
1384 which to load the value of the stac <<
1385 change at reboot time on SMP system <<
1386 kernel's address space are forced t <<
1387 the entire duration that the system <<
1388 389
1389 Enable this option to switch to a d !! 390 To compile this driver as a module, choose M here: the
1390 different canary value for each tas !! 391 module will be called nbd.
1391 392
1392 endmenu !! 393 If unsure, say N.
1393 394
1394 menu "Boot options" !! 395 source "drivers/md/Kconfig"
1395 396
1396 config USE_OF !! 397 config BLK_DEV_RAM
1397 bool "Flattened Device Tree support" !! 398 tristate "RAM disk support"
1398 select IRQ_DOMAIN !! 399 ---help---
1399 select OF !! 400 Saying Y here will allow you to use a portion of your RAM memory as
1400 help !! 401 a block device, so that you can make file systems on it, read and
1401 Include support for flattened devic !! 402 write to it and do all the other things that you can do with normal
>> 403 block devices (such as hard drives). It is usually used to load and
>> 404 store a copy of a minimal root file system off of a floppy into RAM
>> 405 during the initial install of Linux.
>> 406
>> 407 Note that the kernel command line option "ramdisk=XX" is now
>> 408 obsolete. For details, read <file:Documentation/ramdisk.txt>.
>> 409
>> 410 To compile this driver as a module, choose M here: the
>> 411 module will be called rd.
>> 412
>> 413 Most normal users won't need the RAM disk functionality, and can
>> 414 thus say N here.
>> 415
>> 416 config BLK_DEV_RAM_SIZE
>> 417 int "Default RAM disk size"
>> 418 depends on BLK_DEV_RAM
>> 419 default "4096"
>> 420 help
>> 421 The default value is 4096. Only change this if you know what are
>> 422 you doing. If you are using IBM S/390, then set this to 8192.
>> 423
>> 424 config BLK_DEV_INITRD
>> 425 bool "Initial RAM disk (initrd) support"
>> 426 depends on BLK_DEV_RAM=y
>> 427 help
>> 428 The initial RAM disk is a RAM disk that is loaded by the boot loader
>> 429 (loadlin or lilo) and that is mounted as root before the normal boot
>> 430 procedure. It is typically used to load modules needed to mount the
>> 431 "real" root file system, etc. See <file:Documentation/initrd.txt>
>> 432 for details.
1402 433
1403 config ARCH_WANT_FLAT_DTB_INSTALL !! 434 endmenu
1404 def_bool y <<
1405 435
1406 config ATAGS !! 436 # Don't frighten a common SBus user
1407 bool "Support for the traditional ATA !! 437 if PCI
1408 default y <<
1409 help <<
1410 This is the traditional way of pass <<
1411 time. If you are solely relying on <<
1412 the ARM_ATAG_DTB_COMPAT option) the <<
1413 to remove ATAGS support from your k <<
1414 <<
1415 config DEPRECATED_PARAM_STRUCT <<
1416 bool "Provide old way to pass kernel <<
1417 depends on ATAGS <<
1418 help <<
1419 This was deprecated in 2001 and ann <<
1420 Some old boot loaders still use thi <<
1421 438
1422 # Compressed boot loader in ROM. Yes, we rea !! 439 source "drivers/ide/Kconfig"
1423 # TEXT and BSS so we preserve their values in <<
1424 config ZBOOT_ROM_TEXT <<
1425 hex "Compressed ROM boot loader base <<
1426 default 0x0 <<
1427 help <<
1428 The physical address at which the R <<
1429 placed in the target. Platforms wh <<
1430 ROM-able zImage formats normally se <<
1431 value in their defconfig file. <<
1432 <<
1433 If ZBOOT_ROM is not enabled, this h <<
1434 <<
1435 config ZBOOT_ROM_BSS <<
1436 hex "Compressed ROM boot loader BSS a <<
1437 default 0x0 <<
1438 help <<
1439 The base address of an area of read <<
1440 for the ROM-able zImage which must <<
1441 decompressor is running. It must be <<
1442 entire decompressed kernel plus an <<
1443 Platforms which normally make use o <<
1444 normally set this to a suitable val <<
1445 <<
1446 If ZBOOT_ROM is not enabled, this h <<
1447 <<
1448 config ZBOOT_ROM <<
1449 bool "Compressed boot loader in ROM/f <<
1450 depends on ZBOOT_ROM_TEXT != ZBOOT_RO <<
1451 depends on !ARM_APPENDED_DTB && !XIP_ <<
1452 help <<
1453 Say Y here if you intend to execute <<
1454 (zImage) directly from ROM or flash <<
1455 440
1456 config ARM_APPENDED_DTB !! 441 endif
1457 bool "Use appended device tree blob t <<
1458 depends on OF <<
1459 help <<
1460 With this option, the boot code wil <<
1461 (DTB) appended to zImage <<
1462 (e.g. cat zImage <filename>.dtb > z <<
1463 <<
1464 This is meant as a backward compati <<
1465 systems with a bootloader that can' <<
1466 the documented boot protocol using <<
1467 <<
1468 Beware that there is very little in <<
1469 this option being confused by lefto <<
1470 look like a DTB header after a rebo <<
1471 to zImage. Do not leave this optio <<
1472 if you don't intend to always appen <<
1473 location into r2 of a bootloader pr <<
1474 to this option. <<
1475 <<
1476 config ARM_ATAG_DTB_COMPAT <<
1477 bool "Supplement the appended DTB wit <<
1478 depends on ARM_APPENDED_DTB <<
1479 help <<
1480 Some old bootloaders can't be updat <<
1481 they provide ATAGs with memory conf <<
1482 the kernel cmdline string, etc. Su <<
1483 provided by the bootloader and can' <<
1484 DTB. To allow a device tree enable <<
1485 bootloaders, this option allows zIm <<
1486 from the ATAG list and store it at <<
1487 <<
1488 choice <<
1489 prompt "Kernel command line type" <<
1490 depends on ARM_ATAG_DTB_COMPAT <<
1491 default ARM_ATAG_DTB_COMPAT_CMDLINE_F <<
1492 442
1493 config ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTL !! 443 source "drivers/isdn/Kconfig"
1494 bool "Use bootloader kernel arguments <<
1495 help <<
1496 Uses the command-line options passe <<
1497 the device tree bootargs property. <<
1498 any, the device tree bootargs prope <<
1499 444
1500 config ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND !! 445 source "drivers/scsi/Kconfig"
1501 bool "Extend with bootloader kernel a <<
1502 help <<
1503 The command-line arguments provided <<
1504 appended to the the device tree boo <<
1505 446
1506 endchoice !! 447 source "drivers/fc4/Kconfig"
1507 448
1508 config CMDLINE !! 449 source "net/Kconfig"
1509 string "Default kernel command string <<
1510 default "" <<
1511 help <<
1512 On some architectures (e.g. CATS), <<
1513 for the boot loader to pass argumen <<
1514 architectures, you should supply so <<
1515 time by entering them here. As a mi <<
1516 memory size and the root device (e. <<
1517 <<
1518 choice <<
1519 prompt "Kernel command line type" <<
1520 depends on CMDLINE != "" <<
1521 default CMDLINE_FROM_BOOTLOADER <<
1522 450
1523 config CMDLINE_FROM_BOOTLOADER !! 451 # This one must be before the filesystem configs. -DaveM
1524 bool "Use bootloader kernel arguments !! 452
1525 help !! 453 menu "Unix98 PTY support"
1526 Uses the command-line options passe !! 454
1527 the boot loader doesn't provide any !! 455 config UNIX98_PTYS
1528 string provided in CMDLINE will be !! 456 bool "Unix98 PTY support"
>> 457 ---help---
>> 458 A pseudo terminal (PTY) is a software device consisting of two
>> 459 halves: a master and a slave. The slave device behaves identical to
>> 460 a physical terminal; the master device is used by a process to
>> 461 read data from and write data to the slave, thereby emulating a
>> 462 terminal. Typical programs for the master side are telnet servers
>> 463 and xterms.
>> 464
>> 465 Linux has traditionally used the BSD-like names /dev/ptyxx for
>> 466 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
>> 467 has a number of problems. The GNU C library glibc 2.1 and later,
>> 468 however, supports the Unix98 naming standard: in order to acquire a
>> 469 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
>> 470 terminal is then made available to the process and the pseudo
>> 471 terminal slave can be accessed as /dev/pts/<number>. What was
>> 472 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
>> 473
>> 474 The entries in /dev/pts/ are created on the fly by a virtual
>> 475 file system; therefore, if you say Y here you should say Y to
>> 476 "/dev/pts file system for Unix98 PTYs" as well.
>> 477
>> 478 If you want to say Y here, you need to have the C library glibc 2.1
>> 479 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
>> 480 Read the instructions in <file:Documentation/Changes> pertaining to
>> 481 pseudo terminals. It's safe to say N.
>> 482
>> 483 config UNIX98_PTY_COUNT
>> 484 int "Maximum number of Unix98 PTYs in use (0-2048)"
>> 485 depends on UNIX98_PTYS
>> 486 default "256"
>> 487 help
>> 488 The maximum number of Unix98 PTYs that can be used at any one time.
>> 489 The default is 256, and should be enough for desktop systems. Server
>> 490 machines which support incoming telnet/rlogin/ssh connections and/or
>> 491 serve several X terminals may want to increase this: every incoming
>> 492 connection and every xterm uses up one PTY.
1529 493
1530 config CMDLINE_EXTEND !! 494 When not in use, each additional set of 256 PTYs occupy
1531 bool "Extend bootloader kernel argume !! 495 approximately 8 KB of kernel memory on 32-bit architectures.
1532 help <<
1533 The command-line arguments provided <<
1534 appended to the default kernel comm <<
1535 496
1536 config CMDLINE_FORCE !! 497 endmenu
1537 bool "Always use the default kernel c <<
1538 help <<
1539 Always use the default kernel comma <<
1540 loader passes other arguments to th <<
1541 This is useful if you cannot or don <<
1542 command-line options your boot load <<
1543 endchoice <<
1544 <<
1545 config XIP_KERNEL <<
1546 bool "Kernel Execute-In-Place from RO <<
1547 depends on !ARM_LPAE && !ARCH_MULTIPL <<
1548 depends on !ARM_PATCH_IDIV && !ARM_PA <<
1549 help <<
1550 Execute-In-Place allows the kernel <<
1551 directly addressable by the CPU, su <<
1552 space since the text section of the <<
1553 to RAM. Read-write sections, such <<
1554 are still copied to RAM. The XIP k <<
1555 it has to run directly from flash, <<
1556 store it. The flash address used t <<
1557 and for storing it, is configuratio <<
1558 say Y here, you must know the prope <<
1559 store the kernel image depending on <<
1560 <<
1561 Also note that the make target beco <<
1562 "make zImage" or "make Image". The <<
1563 ROM memory will be arch/arm/boot/xi <<
1564 498
1565 If unsure, say N. !! 499 source "drivers/input/Kconfig"
1566 500
1567 config XIP_PHYS_ADDR !! 501 source "fs/Kconfig"
1568 hex "XIP Kernel Physical Location" <<
1569 depends on XIP_KERNEL <<
1570 default "0x00080000" <<
1571 help <<
1572 This is the physical address in you <<
1573 be linked for and stored to. This <<
1574 own flash usage. <<
1575 <<
1576 config XIP_DEFLATED_DATA <<
1577 bool "Store kernel .data section comp <<
1578 depends on XIP_KERNEL <<
1579 select ZLIB_INFLATE <<
1580 help <<
1581 Before the kernel is actually execu <<
1582 copied to RAM from ROM. This option <<
1583 in compressed form and decompressed <<
1584 copied, saving some precious ROM sp <<
1585 slightly longer boot delay. <<
1586 <<
1587 config ARCH_SUPPORTS_KEXEC <<
1588 def_bool (!SMP || PM_SLEEP_SMP) && MM <<
1589 <<
1590 config ATAGS_PROC <<
1591 bool "Export atags in procfs" <<
1592 depends on ATAGS && KEXEC <<
1593 default y <<
1594 help <<
1595 Should the atags used to boot the k <<
1596 file in procfs. Useful with kexec. <<
1597 502
1598 config ARCH_SUPPORTS_CRASH_DUMP !! 503 source "sound/Kconfig"
1599 def_bool y <<
1600 504
1601 config AUTO_ZRELADDR !! 505 source "drivers/usb/Kconfig"
1602 bool "Auto calculation of the decompr <<
1603 default !(ARCH_FOOTBRIDGE || ARCH_RPC <<
1604 help <<
1605 ZRELADDR is the physical address wh <<
1606 image will be placed. If AUTO_ZRELA <<
1607 will be determined at run-time, eit <<
1608 with 0xf8000000, or, if invalid, fr <<
1609 This assumes the zImage being place <<
1610 start of memory. <<
1611 506
1612 config EFI_STUB !! 507 menu "Watchdog"
1613 bool <<
1614 508
1615 config EFI !! 509 config SOFT_WATCHDOG
1616 bool "UEFI runtime support" !! 510 tristate "Software watchdog"
1617 depends on OF && !CPU_BIG_ENDIAN && M <<
1618 select UCS2_STRING <<
1619 select EFI_PARAMS_FROM_FDT <<
1620 select EFI_STUB <<
1621 select EFI_GENERIC_STUB <<
1622 select EFI_RUNTIME_WRAPPERS <<
1623 help <<
1624 This option provides support for ru <<
1625 by UEFI firmware (such as non-volat <<
1626 clock, and platform reset). A UEFI <<
1627 allow the kernel to be booted as an <<
1628 is only useful for kernels that may <<
1629 UEFI firmware. <<
1630 <<
1631 config DMI <<
1632 bool "Enable support for SMBIOS (DMI) <<
1633 depends on EFI <<
1634 default y <<
1635 help 511 help
1636 This enables SMBIOS/DMI feature for !! 512 A software monitoring watchdog. This will fail to reboot your system
1637 !! 513 from some situations that the hardware watchdog will recover
1638 This option is only useful on syste !! 514 from. Equally it's a lot cheaper to install.
1639 However, even with this option, the <<
1640 continue to boot on existing non-UE <<
1641 <<
1642 NOTE: This does *NOT* enable or enc <<
1643 i.e., the the practice of identifyi <<
1644 decide whether certain workarounds <<
1645 firmware need to be enabled. This w <<
1646 to be enabled much earlier than we <<
1647 <<
1648 endmenu <<
1649 515
1650 menu "CPU Power Management" !! 516 To compile this driver as a module, choose M here: the
1651 !! 517 module will be called softdog.
1652 source "drivers/cpufreq/Kconfig" <<
1653 <<
1654 source "drivers/cpuidle/Kconfig" <<
1655 518
1656 endmenu 519 endmenu
1657 520
1658 menu "Floating point emulation" <<
1659 521
1660 comment "At least one emulation must be selec !! 522 menu "Kernel hacking"
1661 523
1662 config FPE_NWFPE !! 524 config DEBUG_SLAB
1663 bool "NWFPE math emulation" !! 525 bool "Debug memory allocations"
1664 depends on (!AEABI || OABI_COMPAT) && <<
1665 help <<
1666 Say Y to include the NWFPE floating <<
1667 This is necessary to run most binar <<
1668 support floating point hardware so <<
1669 your machine has an FPA or floating <<
1670 <<
1671 You may say N here if you are going <<
1672 early in the bootup. <<
1673 <<
1674 config FPE_NWFPE_XP <<
1675 bool "Support extended precision" <<
1676 depends on FPE_NWFPE <<
1677 help <<
1678 Say Y to include 80-bit support in <<
1679 emulator. Otherwise, only 32 and 6 <<
1680 Note that gcc does not generate 80- <<
1681 so in most cases this option only e <<
1682 floating point emulator without any <<
1683 <<
1684 You almost surely want to say N her <<
1685 <<
1686 config FPE_FASTFPE <<
1687 bool "FastFPE math emulation (EXPERIM <<
1688 depends on (!AEABI || OABI_COMPAT) && <<
1689 help <<
1690 Say Y here to include the FAST floa <<
1691 This is an experimental much faster <<
1692 precision for the mantissa. It doe <<
1693 It is very simple, and approximatel <<
1694 <<
1695 It should be sufficient for most pr <<
1696 for scientific calculations, but yo <<
1697 If you do not feel you need a faste <<
1698 choose NWFPE. <<
1699 <<
1700 config VFP <<
1701 bool "VFP-format floating point maths <<
1702 depends on CPU_V6 || CPU_V6K || CPU_A <<
1703 help <<
1704 Say Y to include VFP support code i <<
1705 if your hardware includes a VFP uni <<
1706 <<
1707 Please see <file:Documentation/arch <<
1708 release notes and additional status <<
1709 526
1710 Say N if your target does not have !! 527 config MAGIC_SYSRQ
1711 !! 528 bool "Magic SysRq key"
1712 config VFPv3 <<
1713 bool <<
1714 depends on VFP <<
1715 default y if CPU_V7 <<
1716 <<
1717 config NEON <<
1718 bool "Advanced SIMD (NEON) Extension <<
1719 depends on VFPv3 && CPU_V7 <<
1720 help <<
1721 Say Y to include support code for N <<
1722 Extension. <<
1723 <<
1724 config KERNEL_MODE_NEON <<
1725 bool "Support for NEON in kernel mode <<
1726 depends on NEON && AEABI <<
1727 help 529 help
1728 Say Y to include support for NEON i !! 530 If you say Y here, you will have some control over the system even
>> 531 if the system crashes for example during kernel debugging (e.g., you
>> 532 will be able to flush the buffer cache to disk, reboot the system
>> 533 immediately or dump some status information). This is accomplished
>> 534 by pressing various keys while holding SysRq (Alt+PrintScreen). It
>> 535 also works on a serial console (on PC hardware at least), if you
>> 536 send a BREAK and then within 5 seconds a command keypress. The
>> 537 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
>> 538 unless you really know what this hack does.
>> 539
>> 540 config DEBUG_SPINLOCK
>> 541 bool "Spinlock debugging"
>> 542
>> 543 config DEBUG_SPINLOCK_SLEEP
>> 544 bool "Sleep-inside-spinlock checking"
>> 545 help
>> 546 If you say Y here, various routines which may sleep will become very
>> 547 noisy if they are called with a spinlock held.
>> 548
>> 549 config DEBUG_BUGVERBOSE
>> 550 bool "Verbose BUG() reporting (adds 70K)"
>> 551 help
>> 552 Say Y here to make BUG() panics output the file name and line number
>> 553 of the BUG call as well as the EIP and oops trace. This aids
>> 554 debugging but costs about 70-100K of memory.
1729 555
1730 endmenu 556 endmenu
1731 557
1732 menu "Power management options" !! 558 source "security/Kconfig"
1733 <<
1734 source "kernel/power/Kconfig" <<
1735 559
1736 config ARCH_SUSPEND_POSSIBLE !! 560 source "crypto/Kconfig"
1737 depends on CPU_ARM920T || CPU_ARM926T <<
1738 CPU_V6 || CPU_V6K || CPU_V7 | <<
1739 def_bool y <<
1740 561
1741 config ARM_CPU_SUSPEND !! 562 source "lib/Kconfig"
1742 def_bool PM_SLEEP || BL_SWITCHER || A <<
1743 depends on ARCH_SUSPEND_POSSIBLE <<
1744 <<
1745 config ARCH_HIBERNATION_POSSIBLE <<
1746 bool <<
1747 depends on MMU <<
1748 default y if ARCH_SUSPEND_POSSIBLE <<
1749 <<
1750 endmenu <<
1751 563
1752 source "arch/arm/Kconfig.assembler" <<
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.