1 # SPDX-License-Identifier: GPL-2.0 !! 1 #
>> 2 # For a description of the syntax of this configuration file,
>> 3 # see Documentation/kbuild/kconfig-language.txt.
>> 4 #
>> 5 config M68K
>> 6 bool
>> 7 default y
>> 8
2 config MMU 9 config MMU
3 def_bool y !! 10 bool
>> 11 default y
4 12
5 config CPU_BIG_ENDIAN !! 13 config UID16
6 def_bool y !! 14 bool
>> 15 default y
7 16
8 config LOCKDEP_SUPPORT !! 17 config RWSEM_GENERIC_SPINLOCK
9 def_bool y !! 18 bool
>> 19 default y
10 20
11 config STACKTRACE_SUPPORT !! 21 config RWSEM_XCHGADD_ALGORITHM
12 def_bool y !! 22 bool
13 <<
14 config ARCH_HAS_ILOG2_U32 <<
15 def_bool n <<
16 <<
17 config ARCH_HAS_ILOG2_U64 <<
18 def_bool n <<
19 <<
20 config ARCH_PROC_KCORE_TEXT <<
21 def_bool y <<
22 <<
23 config GENERIC_HWEIGHT <<
24 def_bool !HAVE_MARCH_Z196_FEATURES <<
25 <<
26 config GENERIC_BUG <<
27 def_bool y if BUG <<
28 <<
29 config GENERIC_BUG_RELATIVE_POINTERS <<
30 def_bool y <<
31 <<
32 config GENERIC_LOCKBREAK <<
33 def_bool y if PREEMPTION <<
34 <<
35 config PGSTE <<
36 def_bool y if KVM <<
37 <<
38 config AUDIT_ARCH <<
39 def_bool y <<
40 <<
41 config NO_IOPORT_MAP <<
42 def_bool y <<
43 <<
44 config PCI_QUIRKS <<
45 def_bool n <<
46 <<
47 config ARCH_SUPPORTS_UPROBES <<
48 def_bool y <<
49 <<
50 config KASAN_SHADOW_OFFSET <<
51 hex <<
52 depends on KASAN <<
53 default 0x1C000000000000 <<
54 <<
55 config S390 <<
56 def_bool y <<
57 # <<
58 # Note: keep this list sorted alphabet <<
59 # <<
60 imply IMA_SECURE_AND_OR_TRUSTED_BOOT <<
61 select ALTERNATE_USER_ADDRESS_SPACE <<
62 select ARCH_32BIT_USTAT_F_TINODE <<
63 select ARCH_BINFMT_ELF_STATE <<
64 select ARCH_CORRECT_STACKTRACE_ON_KRET <<
65 select ARCH_ENABLE_MEMORY_HOTPLUG if S <<
66 select ARCH_ENABLE_MEMORY_HOTREMOVE <<
67 select ARCH_ENABLE_SPLIT_PMD_PTLOCK if <<
68 select ARCH_HAS_CURRENT_STACK_POINTER <<
69 select ARCH_HAS_DEBUG_VIRTUAL <<
70 select ARCH_HAS_DEBUG_VM_PGTABLE <<
71 select ARCH_HAS_DEBUG_WX <<
72 select ARCH_HAS_DEVMEM_IS_ALLOWED <<
73 select ARCH_HAS_DMA_OPS if PCI <<
74 select ARCH_HAS_ELF_RANDOMIZE <<
75 select ARCH_HAS_FORCE_DMA_UNENCRYPTED <<
76 select ARCH_HAS_FORTIFY_SOURCE <<
77 select ARCH_HAS_GCOV_PROFILE_ALL <<
78 select ARCH_HAS_GIGANTIC_PAGE <<
79 select ARCH_HAS_KCOV <<
80 select ARCH_HAS_MEMBARRIER_SYNC_CORE <<
81 select ARCH_HAS_MEM_ENCRYPT <<
82 select ARCH_HAS_NMI_SAFE_THIS_CPU_OPS <<
83 select ARCH_HAS_PTE_SPECIAL <<
84 select ARCH_HAS_SCALED_CPUTIME <<
85 select ARCH_HAS_SET_DIRECT_MAP <<
86 select ARCH_HAS_SET_MEMORY <<
87 select ARCH_HAS_STRICT_KERNEL_RWX <<
88 select ARCH_HAS_STRICT_MODULE_RWX <<
89 select ARCH_HAS_SYSCALL_WRAPPER <<
90 select ARCH_HAS_UBSAN <<
91 select ARCH_HAS_VDSO_DATA <<
92 select ARCH_HAVE_NMI_SAFE_CMPXCHG <<
93 select ARCH_INLINE_READ_LOCK <<
94 select ARCH_INLINE_READ_LOCK_BH <<
95 select ARCH_INLINE_READ_LOCK_IRQ <<
96 select ARCH_INLINE_READ_LOCK_IRQSAVE <<
97 select ARCH_INLINE_READ_TRYLOCK <<
98 select ARCH_INLINE_READ_UNLOCK <<
99 select ARCH_INLINE_READ_UNLOCK_BH <<
100 select ARCH_INLINE_READ_UNLOCK_IRQ <<
101 select ARCH_INLINE_READ_UNLOCK_IRQREST <<
102 select ARCH_INLINE_SPIN_LOCK <<
103 select ARCH_INLINE_SPIN_LOCK_BH <<
104 select ARCH_INLINE_SPIN_LOCK_IRQ <<
105 select ARCH_INLINE_SPIN_LOCK_IRQSAVE <<
106 select ARCH_INLINE_SPIN_TRYLOCK <<
107 select ARCH_INLINE_SPIN_TRYLOCK_BH <<
108 select ARCH_INLINE_SPIN_UNLOCK <<
109 select ARCH_INLINE_SPIN_UNLOCK_BH <<
110 select ARCH_INLINE_SPIN_UNLOCK_IRQ <<
111 select ARCH_INLINE_SPIN_UNLOCK_IRQREST <<
112 select ARCH_INLINE_WRITE_LOCK <<
113 select ARCH_INLINE_WRITE_LOCK_BH <<
114 select ARCH_INLINE_WRITE_LOCK_IRQ <<
115 select ARCH_INLINE_WRITE_LOCK_IRQSAVE <<
116 select ARCH_INLINE_WRITE_TRYLOCK <<
117 select ARCH_INLINE_WRITE_UNLOCK <<
118 select ARCH_INLINE_WRITE_UNLOCK_BH <<
119 select ARCH_INLINE_WRITE_UNLOCK_IRQ <<
120 select ARCH_INLINE_WRITE_UNLOCK_IRQRES <<
121 select ARCH_MHP_MEMMAP_ON_MEMORY_ENABL <<
122 select ARCH_STACKWALK <<
123 select ARCH_SUPPORTS_ATOMIC_RMW <<
124 select ARCH_SUPPORTS_DEBUG_PAGEALLOC <<
125 select ARCH_SUPPORTS_HUGETLBFS <<
126 select ARCH_SUPPORTS_INT128 if CC_HAS_ <<
127 select ARCH_SUPPORTS_NUMA_BALANCING <<
128 select ARCH_SUPPORTS_PER_VMA_LOCK <<
129 select ARCH_USE_BUILTIN_BSWAP <<
130 select ARCH_USE_CMPXCHG_LOCKREF <<
131 select ARCH_USE_SYM_ANNOTATIONS <<
132 select ARCH_WANTS_NO_INSTR <<
133 select ARCH_WANT_DEFAULT_BPF_JIT <<
134 select ARCH_WANT_IPC_PARSE_VERSION <<
135 select ARCH_WANT_KERNEL_PMD_MKWRITE <<
136 select ARCH_WANT_LD_ORPHAN_WARN <<
137 select ARCH_WANT_OPTIMIZE_HUGETLB_VMEM <<
138 select BUILDTIME_TABLE_SORT <<
139 select CLONE_BACKWARDS2 <<
140 select DCACHE_WORD_ACCESS if !KMSAN <<
141 select DYNAMIC_FTRACE if FUNCTION_TRAC <<
142 select FUNCTION_ALIGNMENT_8B if CC_IS_ <<
143 select FUNCTION_ALIGNMENT_16B if !CC_I <<
144 select GENERIC_ALLOCATOR <<
145 select GENERIC_CPU_DEVICES <<
146 select GENERIC_CPU_AUTOPROBE <<
147 select GENERIC_CPU_VULNERABILITIES <<
148 select GENERIC_ENTRY <<
149 select GENERIC_GETTIMEOFDAY <<
150 select GENERIC_PTDUMP <<
151 select GENERIC_SMP_IDLE_THREAD <<
152 select GENERIC_TIME_VSYSCALL <<
153 select GENERIC_VDSO_TIME_NS <<
154 select GENERIC_IOREMAP if PCI <<
155 select HAVE_ALIGNED_STRUCT_PAGE <<
156 select HAVE_ARCH_AUDITSYSCALL <<
157 select HAVE_ARCH_JUMP_LABEL <<
158 select HAVE_ARCH_JUMP_LABEL_RELATIVE <<
159 select HAVE_ARCH_KASAN <<
160 select HAVE_ARCH_KASAN_VMALLOC <<
161 select HAVE_ARCH_KCSAN <<
162 select HAVE_ARCH_KMSAN <<
163 select HAVE_ARCH_KFENCE <<
164 select HAVE_ARCH_RANDOMIZE_KSTACK_OFFS <<
165 select HAVE_ARCH_SECCOMP_FILTER <<
166 select HAVE_ARCH_SOFT_DIRTY <<
167 select HAVE_ARCH_STACKLEAK <<
168 select HAVE_ARCH_TRACEHOOK <<
169 select HAVE_ARCH_TRANSPARENT_HUGEPAGE <<
170 select HAVE_ARCH_VMAP_STACK <<
171 select HAVE_ASM_MODVERSIONS <<
172 select HAVE_CMPXCHG_DOUBLE <<
173 select HAVE_CMPXCHG_LOCAL <<
174 select HAVE_DEBUG_KMEMLEAK <<
175 select HAVE_DMA_CONTIGUOUS <<
176 select HAVE_DYNAMIC_FTRACE <<
177 select HAVE_DYNAMIC_FTRACE_WITH_ARGS <<
178 select HAVE_DYNAMIC_FTRACE_WITH_DIRECT <<
179 select HAVE_DYNAMIC_FTRACE_WITH_REGS <<
180 select HAVE_EBPF_JIT if HAVE_MARCH_Z19 <<
181 select HAVE_EFFICIENT_UNALIGNED_ACCESS <<
182 select HAVE_GUP_FAST <<
183 select HAVE_FENTRY <<
184 select HAVE_FTRACE_MCOUNT_RECORD <<
185 select HAVE_FUNCTION_ARG_ACCESS_API <<
186 select HAVE_FUNCTION_ERROR_INJECTION <<
187 select HAVE_FUNCTION_GRAPH_RETVAL <<
188 select HAVE_FUNCTION_GRAPH_TRACER <<
189 select HAVE_FUNCTION_TRACER <<
190 select HAVE_GCC_PLUGINS <<
191 select HAVE_GENERIC_VDSO <<
192 select HAVE_IOREMAP_PROT if PCI <<
193 select HAVE_KERNEL_BZIP2 <<
194 select HAVE_KERNEL_GZIP <<
195 select HAVE_KERNEL_LZ4 <<
196 select HAVE_KERNEL_LZMA <<
197 select HAVE_KERNEL_LZO <<
198 select HAVE_KERNEL_UNCOMPRESSED <<
199 select HAVE_KERNEL_XZ <<
200 select HAVE_KERNEL_ZSTD <<
201 select HAVE_KPROBES <<
202 select HAVE_KPROBES_ON_FTRACE <<
203 select HAVE_KRETPROBES <<
204 select HAVE_LIVEPATCH <<
205 select HAVE_MEMBLOCK_PHYS_MAP <<
206 select HAVE_MOD_ARCH_SPECIFIC <<
207 select HAVE_NMI <<
208 select HAVE_NOP_MCOUNT <<
209 select HAVE_PAGE_SIZE_4KB <<
210 select HAVE_PCI <<
211 select HAVE_PERF_EVENTS <<
212 select HAVE_PERF_REGS <<
213 select HAVE_PERF_USER_STACK_DUMP <<
214 select HAVE_REGS_AND_STACK_ACCESS_API <<
215 select HAVE_RELIABLE_STACKTRACE <<
216 select HAVE_RETHOOK <<
217 select HAVE_RSEQ <<
218 select HAVE_SAMPLE_FTRACE_DIRECT <<
219 select HAVE_SAMPLE_FTRACE_DIRECT_MULTI <<
220 select HAVE_SETUP_PER_CPU_AREA <<
221 select HAVE_SOFTIRQ_ON_OWN_STACK <<
222 select HAVE_SYSCALL_TRACEPOINTS <<
223 select HAVE_VIRT_CPU_ACCOUNTING <<
224 select HAVE_VIRT_CPU_ACCOUNTING_IDLE <<
225 select IOMMU_HELPER if PCI <<
226 select IOMMU_SUPPORT if PCI <<
227 select MMU_GATHER_MERGE_VMAS <<
228 select MMU_GATHER_NO_GATHER <<
229 select MMU_GATHER_RCU_TABLE_FREE <<
230 select MODULES_USE_ELF_RELA <<
231 select NEED_DMA_MAP_STATE if PCI <<
232 select NEED_PER_CPU_EMBED_FIRST_CHUNK <<
233 select NEED_SG_DMA_LENGTH if PCI <<
234 select OLD_SIGACTION <<
235 select OLD_SIGSUSPEND3 <<
236 select PCI_DOMAINS if PCI <<
237 select PCI_MSI if PCI <<
238 select PCI_MSI_ARCH_FALLBACKS if PCI <<
239 select SPARSE_IRQ <<
240 select SWIOTLB <<
241 select SYSCTL_EXCEPTION_TRACE <<
242 select THREAD_INFO_IN_TASK <<
243 select TRACE_IRQFLAGS_SUPPORT <<
244 select TTY <<
245 select USER_STACKTRACE_SUPPORT <<
246 select VDSO_GETRANDOM <<
247 select VIRT_CPU_ACCOUNTING <<
248 select ZONE_DMA <<
249 # Note: keep the above list sorted alp <<
250 <<
251 config SCHED_OMIT_FRAME_POINTER <<
252 def_bool y <<
253 <<
254 config PGTABLE_LEVELS <<
255 int <<
256 default 5 <<
257 <<
258 source "kernel/livepatch/Kconfig" <<
259 <<
260 config ARCH_SUPPORTS_KEXEC <<
261 def_bool y <<
262 <<
263 config ARCH_SUPPORTS_KEXEC_FILE <<
264 def_bool y <<
265 <<
266 config ARCH_SUPPORTS_KEXEC_SIG <<
267 def_bool MODULE_SIG_FORMAT <<
268 <<
269 config ARCH_SUPPORTS_KEXEC_PURGATORY <<
270 def_bool y <<
271 <<
272 config ARCH_SUPPORTS_CRASH_DUMP <<
273 def_bool y <<
274 help <<
275 Refer to <file:Documentation/arch/s3 <<
276 This option also enables s390 zfcpdu <<
277 See also <file:Documentation/arch/s3 <<
278 <<
279 menu "Processor type and features" <<
280 <<
281 config HAVE_MARCH_Z10_FEATURES <<
282 def_bool n <<
283 <<
284 config HAVE_MARCH_Z196_FEATURES <<
285 def_bool n <<
286 select HAVE_MARCH_Z10_FEATURES <<
287 <<
288 config HAVE_MARCH_ZEC12_FEATURES <<
289 def_bool n <<
290 select HAVE_MARCH_Z196_FEATURES <<
291 <<
292 config HAVE_MARCH_Z13_FEATURES <<
293 def_bool n <<
294 select HAVE_MARCH_ZEC12_FEATURES <<
295 <<
296 config HAVE_MARCH_Z14_FEATURES <<
297 def_bool n <<
298 select HAVE_MARCH_Z13_FEATURES <<
299 <<
300 config HAVE_MARCH_Z15_FEATURES <<
301 def_bool n <<
302 select HAVE_MARCH_Z14_FEATURES <<
303 <<
304 config HAVE_MARCH_Z16_FEATURES <<
305 def_bool n <<
306 select HAVE_MARCH_Z15_FEATURES <<
307 <<
308 choice <<
309 prompt "Processor type" <<
310 default MARCH_Z196 <<
311 <<
312 config MARCH_Z10 <<
313 bool "IBM System z10" <<
314 select HAVE_MARCH_Z10_FEATURES <<
315 depends on $(cc-option,-march=z10) <<
316 help <<
317 Select this to enable optimizations <<
318 series). This is the oldest machine <<
319 <<
320 config MARCH_Z196 <<
321 bool "IBM zEnterprise 114 and 196" <<
322 select HAVE_MARCH_Z196_FEATURES <<
323 depends on $(cc-option,-march=z196) <<
324 help <<
325 Select this to enable optimizations <<
326 (2818 and 2817 series). The kernel w <<
327 not work on older machines. <<
328 <<
329 config MARCH_ZEC12 <<
330 bool "IBM zBC12 and zEC12" <<
331 select HAVE_MARCH_ZEC12_FEATURES <<
332 depends on $(cc-option,-march=zEC12) <<
333 help <<
334 Select this to enable optimizations <<
335 2827 series). The kernel will be sli <<
336 older machines. <<
337 <<
338 config MARCH_Z13 <<
339 bool "IBM z13s and z13" <<
340 select HAVE_MARCH_Z13_FEATURES <<
341 depends on $(cc-option,-march=z13) <<
342 help <<
343 Select this to enable optimizations <<
344 2964 series). The kernel will be sli <<
345 older machines. <<
346 <<
347 config MARCH_Z14 <<
348 bool "IBM z14 ZR1 and z14" <<
349 select HAVE_MARCH_Z14_FEATURES <<
350 depends on $(cc-option,-march=z14) <<
351 help <<
352 Select this to enable optimizations <<
353 and 3906 series). The kernel will be <<
354 work on older machines. <<
355 <<
356 config MARCH_Z15 <<
357 bool "IBM z15" <<
358 select HAVE_MARCH_Z15_FEATURES <<
359 depends on $(cc-option,-march=z15) <<
360 help <<
361 Select this to enable optimizations <<
362 and 8561 series). The kernel will be <<
363 work on older machines. <<
364 <<
365 config MARCH_Z16 <<
366 bool "IBM z16" <<
367 select HAVE_MARCH_Z16_FEATURES <<
368 depends on $(cc-option,-march=z16) <<
369 help <<
370 Select this to enable optimizations <<
371 3932 series). <<
372 <<
373 endchoice <<
374 <<
375 config MARCH_Z10_TUNE <<
376 def_bool TUNE_Z10 || MARCH_Z10 && TUNE <<
377 <<
378 config MARCH_Z196_TUNE <<
379 def_bool TUNE_Z196 || MARCH_Z196 && TU <<
380 <<
381 config MARCH_ZEC12_TUNE <<
382 def_bool TUNE_ZEC12 || MARCH_ZEC12 && <<
383 <<
384 config MARCH_Z13_TUNE <<
385 def_bool TUNE_Z13 || MARCH_Z13 && TUNE <<
386 <<
387 config MARCH_Z14_TUNE <<
388 def_bool TUNE_Z14 || MARCH_Z14 && TUNE <<
389 <<
390 config MARCH_Z15_TUNE <<
391 def_bool TUNE_Z15 || MARCH_Z15 && TUNE <<
392 <<
393 config MARCH_Z16_TUNE <<
394 def_bool TUNE_Z16 || MARCH_Z16 && TUNE <<
395 <<
396 choice <<
397 prompt "Tune code generation" <<
398 default TUNE_DEFAULT <<
399 help <<
400 Cause the compiler to tune (-mtune) <<
401 This will make the code run faster o <<
402 somewhat slower on other machines. <<
403 This option only changes how the com <<
404 selection of instructions itself, so <<
405 all other machines. <<
406 <<
407 config TUNE_DEFAULT <<
408 bool "Default" <<
409 help <<
410 Tune the generated code for the targ <<
411 will be compiled. <<
412 <<
413 config TUNE_Z10 <<
414 bool "IBM System z10" <<
415 <<
416 config TUNE_Z196 <<
417 bool "IBM zEnterprise 114 and 196" <<
418 depends on $(cc-option,-mtune=z196) <<
419 <<
420 config TUNE_ZEC12 <<
421 bool "IBM zBC12 and zEC12" <<
422 depends on $(cc-option,-mtune=zEC12) <<
423 <<
424 config TUNE_Z13 <<
425 bool "IBM z13s and z13" <<
426 depends on $(cc-option,-mtune=z13) <<
427 <<
428 config TUNE_Z14 <<
429 bool "IBM z14 ZR1 and z14" <<
430 depends on $(cc-option,-mtune=z14) <<
431 <<
432 config TUNE_Z15 <<
433 bool "IBM z15" <<
434 depends on $(cc-option,-mtune=z15) <<
435 <<
436 config TUNE_Z16 <<
437 bool "IBM z16" <<
438 depends on $(cc-option,-mtune=z16) <<
439 <<
440 endchoice <<
441 <<
442 config 64BIT <<
443 def_bool y <<
444 <<
445 config COMMAND_LINE_SIZE <<
446 int "Maximum size of kernel command li <<
447 default 4096 <<
448 range 896 1048576 <<
449 help <<
450 This allows you to specify the maxim <<
451 line. <<
452 <<
453 config COMPAT <<
454 def_bool n <<
455 prompt "Kernel support for 31 bit emul <<
456 select ARCH_WANT_OLD_COMPAT_IPC <<
457 select COMPAT_OLD_SIGACTION <<
458 select HAVE_UID16 <<
459 depends on MULTIUSER <<
460 depends on !CC_IS_CLANG && !LD_IS_LLD <<
461 help <<
462 Select this option if you want to en <<
463 handle system-calls from ELF binarie <<
464 (and some other stuff like libraries <<
465 executing 31 bit applications. <<
466 <<
467 If unsure say N. <<
468 <<
469 config SMP <<
470 def_bool y <<
471 <<
472 config NR_CPUS <<
473 int "Maximum number of CPUs (2-512)" <<
474 range 2 512 <<
475 default "64" <<
476 help <<
477 This allows you to specify the maxim <<
478 kernel will support. The maximum sup <<
479 minimum value which makes sense is 2 <<
480 <<
481 This is purely to save memory - each <<
482 approximately sixteen kilobytes to t <<
483 <<
484 config HOTPLUG_CPU <<
485 def_bool y <<
486 <<
487 config NUMA <<
488 bool "NUMA support" <<
489 depends on SCHED_TOPOLOGY <<
490 default n <<
491 help <<
492 Enable NUMA support <<
493 <<
494 This option adds NUMA support to the <<
495 <<
496 config NODES_SHIFT <<
497 int <<
498 depends on NUMA <<
499 default "1" <<
500 <<
501 config SCHED_SMT <<
502 def_bool n <<
503 <<
504 config SCHED_MC <<
505 def_bool n <<
506 <<
507 config SCHED_TOPOLOGY <<
508 def_bool y <<
509 prompt "Topology scheduler support" <<
510 select SCHED_SMT <<
511 select SCHED_MC <<
512 help <<
513 Topology scheduler support improves <<
514 making when dealing with machines th <<
515 multiple cores or multiple books. <<
516 <<
517 config SCHED_TOPOLOGY_VERTICAL <<
518 def_bool y <<
519 bool "Use vertical CPU polarization by <<
520 depends on SCHED_TOPOLOGY <<
521 help <<
522 Use vertical CPU polarization by def <<
523 The default CPU polarization is hori <<
524 <<
525 config HIPERDISPATCH_ON <<
526 def_bool y <<
527 bool "Use hiperdispatch on vertical po <<
528 depends on SCHED_TOPOLOGY <<
529 depends on PROC_SYSCTL <<
530 help <<
531 Hiperdispatch aims to improve the CP <<
532 making when using vertical polarizat <<
533 capacities dynamically. Set this opt <<
534 on vertical polarization by default. <<
535 by sysctl's s390.hiperdispatch attri <<
536 <<
537 source "kernel/Kconfig.hz" <<
538 <<
539 config CERT_STORE <<
540 bool "Get user certificates via DIAG32 <<
541 depends on KEYS <<
542 select CRYPTO_LIB_SHA256 <<
543 help <<
544 Enable this option if you want to ac <<
545 certificates via DIAG 0x320. <<
546 <<
547 These certificates will be made avai <<
548 'cert_store'. <<
549 <<
550 config KERNEL_NOBP <<
551 def_bool n <<
552 prompt "Enable modified branch predict <<
553 help <<
554 If this option is selected the kerne <<
555 branch prediction mode if the firmwa <<
556 The modified branch prediction mode <<
557 regard to speculative execution. <<
558 23
559 With the option enabled the kernel p <<
560 can be used to run the kernel in the <<
561 24
562 With the option disabled the modifie !! 25 mainmenu "Linux/68k Kernel Configuration"
563 enabled with the "nobp=1" kernel par <<
564 26
565 If unsure, say N. !! 27 source "init/Kconfig"
566 28
567 config EXPOLINE <<
568 def_bool n <<
569 depends on $(cc-option,-mindirect-bran <<
570 prompt "Avoid speculative indirect bra <<
571 help <<
572 Compile the kernel with the expoline <<
573 against kernel-to-user data leaks by <<
574 branches. <<
575 Requires a compiler with -mindirect- <<
576 protection. The kernel may run slowe <<
577 29
578 If unsure, say N. !! 30 menu "Platform dependent setup"
579 31
580 config EXPOLINE_EXTERN !! 32 config EISA
581 def_bool EXPOLINE && CC_IS_GCC && GCC_ !! 33 bool
582 $(success,$(srctree)/arch/s39 !! 34 ---help---
583 help !! 35 The Extended Industry Standard Architecture (EISA) bus was
584 Generate expolines as external funct !! 36 developed as an open alternative to the IBM MicroChannel bus.
585 This option is required for some too <<
586 are enabled. The kernel is compiled <<
587 -mindirect-branch=thunk-extern, whic <<
588 <<
589 choice <<
590 prompt "Expoline default" <<
591 depends on EXPOLINE <<
592 default EXPOLINE_FULL <<
593 <<
594 config EXPOLINE_OFF <<
595 bool "spectre_v2=off" <<
596 <<
597 config EXPOLINE_AUTO <<
598 bool "spectre_v2=auto" <<
599 <<
600 config EXPOLINE_FULL <<
601 bool "spectre_v2=on" <<
602 <<
603 endchoice <<
604 <<
605 config RELOCATABLE <<
606 def_bool y <<
607 help <<
608 This builds a kernel image that reta <<
609 so it can be loaded at an arbitrary <<
610 The relocations make the kernel imag <<
611 10%), but are discarded at runtime. <<
612 Note: this option exists only for do <<
613 not remove it. <<
614 <<
615 config RANDOMIZE_BASE <<
616 bool "Randomize the address of the ker <<
617 default y <<
618 help <<
619 In support of Kernel Address Space L <<
620 this randomizes the address at which <<
621 as a security feature that deters ex <<
622 knowledge of the location of kernel <<
623 <<
624 config RANDOMIZE_IDENTITY_BASE <<
625 bool "Randomize the address of the ide <<
626 depends on RANDOMIZE_BASE <<
627 default DEBUG_VM <<
628 help <<
629 The identity mapping base address is <<
630 Allow randomization of that base to <<
631 notion of physical and virtual addre <<
632 That does not have any impact on the <<
633 kernel image is loaded. <<
634 <<
635 If unsure, say N <<
636 <<
637 config KERNEL_IMAGE_BASE <<
638 hex "Kernel image base address" <<
639 range 0x100000 0x1FFFFFE0000000 if !KA <<
640 range 0x100000 0x1BFFFFE0000000 if KAS <<
641 default 0x3FFE0000000 if !KASAN <<
642 default 0x7FFFE0000000 if KASAN <<
643 help <<
644 This is the address at which the ker <<
645 Kernel Address Space Layout Randomiz <<
646 <<
647 In case the Protected virtualization <<
648 Ultravisor imposes a virtual address <<
649 option leads to the kernel image exc <<
650 this option is ignored and the image <<
651 <<
652 If the value of this option leads to <<
653 the virtual memory where other data <<
654 option is ignored and the image is l <<
655 37
656 endmenu !! 38 The EISA bus provided some of the features of the IBM MicroChannel
>> 39 bus while maintaining backward compatibility with cards made for
>> 40 the older ISA bus. The EISA bus saw limited use between 1988 and
>> 41 1995 when it was made obsolete by the PCI bus.
657 42
658 menu "Memory setup" !! 43 Say Y here if you are building a kernel for an EISA-based machine.
659 44
660 config ARCH_SPARSEMEM_ENABLE !! 45 Otherwise, say N.
661 def_bool y !! 46
662 select SPARSEMEM_VMEMMAP_ENABLE !! 47 config MCA
663 select SPARSEMEM_VMEMMAP !! 48 bool
664 <<
665 config ARCH_SPARSEMEM_DEFAULT <<
666 def_bool y <<
667 <<
668 config MAX_PHYSMEM_BITS <<
669 int "Maximum size of supported physica <<
670 range 42 53 <<
671 default "46" <<
672 help <<
673 This option specifies the maximum su <<
674 in bits. Supported is any size betwe <<
675 Increasing the number of bits also i <<
676 By default 46 bits (64TB) are suppor <<
677 <<
678 config CHECK_STACK <<
679 def_bool y <<
680 depends on !VMAP_STACK <<
681 prompt "Detect kernel stack overflow" <<
682 help <<
683 This option enables the compiler opt <<
684 -mstack-size if they are available. <<
685 it will emit additional code to each <<
686 an illegal operation if the kernel s <<
687 <<
688 Say N if you are unsure. <<
689 <<
690 config STACK_GUARD <<
691 int "Size of the guard area (128-1024) <<
692 range 128 1024 <<
693 depends on CHECK_STACK <<
694 default "256" <<
695 help 49 help
696 This allows you to specify the size !! 50 MicroChannel Architecture is found in some IBM PS/2 machines and
697 end of the kernel stack. If the kern !! 51 laptops. It is a bus system similar to PCI or ISA. See
698 area on function entry an illegal op !! 52 <file:Documentation/mca.txt> (and especially the web page given
699 needs to be a power of 2. Please kee !! 53 there) before attempting to build an MCA bus kernel.
700 interrupt frame is 184 bytes for 31 <<
701 The minimum size for the stack guard <<
702 512 for 64 bit. <<
703 54
704 endmenu !! 55 config PCMCIA
>> 56 tristate
>> 57 ---help---
>> 58 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
>> 59 computer. These are credit-card size devices such as network cards,
>> 60 modems or hard drives often used with laptops computers. There are
>> 61 actually two varieties of these cards: the older 16 bit PCMCIA cards
>> 62 and the newer 32 bit CardBus cards. If you want to use CardBus
>> 63 cards, you need to say Y here and also to "CardBus support" below.
>> 64
>> 65 To use your PC-cards, you will need supporting software from David
>> 66 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
>> 67 for location). Please also read the PCMCIA-HOWTO, available from
>> 68 <http://www.tldp.org/docs.html#howto>.
>> 69
>> 70 To compile this driver as modules, choose M here: the
>> 71 modules will be called pcmcia_core and ds.
>> 72
>> 73 config AMIGA
>> 74 bool "Amiga support"
>> 75 help
>> 76 This option enables support for the Amiga series of computers. If
>> 77 you plan to use this kernel on an Amiga, say Y here and browse the
>> 78 material available in <file:Documentation/m68k>; otherwise say N.
>> 79
>> 80 config ATARI
>> 81 bool "Atari support"
>> 82 help
>> 83 This option enables support for the 68000-based Atari series of
>> 84 computers (including the TT, Falcon and Medusa). If you plan to use
>> 85 this kernel on an Atari, say Y here and browse the material
>> 86 available in <file:Documentation/m68k>; otherwise say N.
>> 87
>> 88 config HADES
>> 89 bool "Hades support"
>> 90 depends on ATARI && BROKEN
>> 91 help
>> 92 This option enables support for the Hades Atari clone. If you plan
>> 93 to use this kernel on a Hades, say Y here; otherwise say N.
>> 94
>> 95 config PCI
>> 96 bool
>> 97 depends on HADES
>> 98 default y
>> 99 help
>> 100 Find out whether you have a PCI motherboard. PCI is the name of a
>> 101 bus system, i.e. the way the CPU talks to the other stuff inside
>> 102 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
>> 103 VESA. If you have PCI, say Y, otherwise N.
>> 104
>> 105 The PCI-HOWTO, available from
>> 106 <http://www.tldp.org/docs.html#howto>, contains valuable
>> 107 information about which PCI hardware does work under Linux and which
>> 108 doesn't.
>> 109
>> 110 config MAC
>> 111 bool "Macintosh support"
>> 112 help
>> 113 This option enables support for the Apple Macintosh series of
>> 114 computers (yes, there is experimental support now, at least for part
>> 115 of the series).
>> 116
>> 117 Say N unless you're willing to code the remaining necessary support.
>> 118 ;)
>> 119
>> 120 config NUBUS
>> 121 bool
>> 122 depends on MAC
>> 123 default y
705 124
706 menu "I/O subsystem" !! 125 config M68K_L2_CACHE
>> 126 bool
>> 127 depends on MAC
>> 128 default y
707 129
708 config QDIO !! 130 config APOLLO
709 def_tristate y !! 131 bool "Apollo support"
710 prompt "QDIO support" <<
711 help 132 help
712 This driver provides the Queued Dire !! 133 Say Y here if you want to run Linux on an MC680x0-based Apollo
713 IBM System z. !! 134 Domain workstation such as the DN3500.
714 135
715 To compile this driver as a module, !! 136 config VME
716 module will be called qdio. !! 137 bool "VME (Motorola and BVM) support"
>> 138 help
>> 139 Say Y here if you want to build a kernel for a 680x0 based VME
>> 140 board. Boards currently supported include Motorola boards MVME147,
>> 141 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
>> 142 BVME6000 boards from BVM Ltd are also supported.
>> 143
>> 144 config MVME147
>> 145 bool "MVME147 support"
>> 146 depends on VME
>> 147 help
>> 148 Say Y to include support for early Motorola VME boards. This will
>> 149 build a kernel which can run on MVME147 single-board computers. If
>> 150 you select this option you will have to select the appropriate
>> 151 drivers for SCSI, Ethernet and serial ports later on.
>> 152
>> 153 config MVME16x
>> 154 bool "MVME162, 166 and 167 support"
>> 155 depends on VME
>> 156 help
>> 157 Say Y to include support for Motorola VME boards. This will build a
>> 158 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
>> 159 MVME177 boards. If you select this option you will have to select
>> 160 the appropriate drivers for SCSI, Ethernet and serial ports later
>> 161 on.
>> 162
>> 163 config BVME6000
>> 164 bool "BVME4000 and BVME6000 support"
>> 165 depends on VME
>> 166 help
>> 167 Say Y to include support for VME boards from BVM Ltd. This will
>> 168 build a kernel which can run on BVME4000 and BVME6000 boards. If
>> 169 you select this option you will have to select the appropriate
>> 170 drivers for SCSI, Ethernet and serial ports later on.
>> 171
>> 172 config HP300
>> 173 bool "HP9000/300 support"
>> 174 help
>> 175 This option enables support for the HP9000/300 series of
>> 176 workstations. Support for these machines is still very experimental.
>> 177 If you plan to try to use the kernel on such a machine say Y here.
>> 178 Everybody else says N.
>> 179
>> 180 config DIO
>> 181 bool "DIO bus support"
>> 182 depends on HP300
>> 183 help
>> 184 Say Y here to enable support for the "DIO" expansion bus used in
>> 185 HP300 machines. If you are using such a system you almost certainly
>> 186 want this.
>> 187
>> 188 config SUN3X
>> 189 bool "Sun3x support"
>> 190 help
>> 191 This option enables support for the Sun 3x series of workstations.
>> 192 Be warned that this support is very experimental. You will also want
>> 193 to say Y to 68030 support and N to the other processors below.
>> 194 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
>> 195 General Linux information on the Sun 3x series (now discontinued)
>> 196 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
>> 197
>> 198 If you don't want to compile a kernel for a Sun 3x, say N.
>> 199
>> 200 config SUN3
>> 201 bool "Sun3 support"
>> 202 help
>> 203 This option enables support for the Sun 3 series of workstations
>> 204 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
>> 205 that all other hardware types must be disabled, as Sun 3 kernels
>> 206 are incompatible with all other m68k targets (including Sun 3x!).
>> 207 Also, you will want to say Y to 68020 support and N to the other
>> 208 processors below.
>> 209
>> 210 If you don't want to compile a kernel exclusively for a Sun 3, say N.
>> 211
>> 212 config Q40
>> 213 bool "Q40/Q60 support"
>> 214 help
>> 215 The Q40 is a Motorola 68040-based successor to the Sinclair QL
>> 216 manufactured in Germany. There is an official Q40 home page at
>> 217 <http://www.q40.de/>. This option enables support for the Q40 and
>> 218 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
>> 219 emulation.
>> 220
>> 221 comment "Processor type"
>> 222
>> 223 config M68020
>> 224 bool "68020 support"
>> 225 help
>> 226 If you anticipate running this kernel on a computer with a MC68020
>> 227 processor, say Y. Otherwise, say N. Note that the 68020 requires a
>> 228 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
>> 229 Sun 3, which provides its own version.
>> 230
>> 231 config M68030
>> 232 bool "68030 support"
>> 233 help
>> 234 If you anticipate running this kernel on a computer with a MC68030
>> 235 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
>> 236 work, as it does not include an MMU (Memory Management Unit).
>> 237
>> 238 config M68040
>> 239 bool "68040 support"
>> 240 help
>> 241 If you anticipate running this kernel on a computer with a MC68LC040
>> 242 or MC68040 processor, say Y. Otherwise, say N. Note that an
>> 243 MC68EC040 will not work, as it does not include an MMU (Memory
>> 244 Management Unit).
>> 245
>> 246 config M68060
>> 247 bool "68060 support"
>> 248 help
>> 249 If you anticipate running this kernel on a computer with a MC68060
>> 250 processor, say Y. Otherwise, say N.
>> 251
>> 252 config M68KFPU_EMU
>> 253 bool "Math emulation support (EXPERIMENTAL)"
>> 254 depends on EXPERIMENTAL
>> 255 help
>> 256 At some point in the future, this will cause floating-point math
>> 257 instructions to be emulated by the kernel on machines that lack a
>> 258 floating-point math coprocessor. Thrill-seekers and chronically
>> 259 sleep-deprived psychotic hacker types can say Y now, everyone else
>> 260 should probably wait a while.
>> 261
>> 262 config M68KFPU_EMU_EXTRAPREC
>> 263 bool "Math emulation extra precision"
>> 264 depends on M68KFPU_EMU
>> 265 help
>> 266 The fpu uses normally a few bit more during calculations for
>> 267 correct rounding, the emulator can (often) do the same but this
>> 268 extra calculation can cost quite some time, so you can disable
>> 269 it here. The emulator will then "only" calculate with a 64 bit
>> 270 mantissa and round slightly incorrect, what is more then enough
>> 271 for normal usage.
>> 272
>> 273 config M68KFPU_EMU_ONLY
>> 274 bool "Math emulation only kernel"
>> 275 depends on M68KFPU_EMU
>> 276 help
>> 277 This option prevents any floating-point instructions from being
>> 278 compiled into the kernel, thereby the kernel doesn't save any
>> 279 floating point context anymore during task switches, so this
>> 280 kernel will only be usable on machines without a floating-point
>> 281 math coprocessor. This makes the kernel a bit faster as no tests
>> 282 needs to be executed whether a floating-point instruction in the
>> 283 kernel should be executed or not.
>> 284
>> 285 config ADVANCED
>> 286 bool "Advanced configuration options"
>> 287 ---help---
>> 288 This gives you access to some advanced options for the CPU. The
>> 289 defaults should be fine for most users, but these options may make
>> 290 it possible for you to improve performance somewhat if you know what
>> 291 you are doing.
>> 292
>> 293 Note that the answer to this question won't directly affect the
>> 294 kernel: saying N will just cause the configurator to skip all
>> 295 the questions about these options.
>> 296
>> 297 Most users should say N to this question.
>> 298
>> 299 config RMW_INSNS
>> 300 bool "Use read-modify-write instructions"
>> 301 depends on ADVANCED
>> 302 ---help---
>> 303 This allows to use certain instructions that work with indivisible
>> 304 read-modify-write bus cycles. While this is faster than the
>> 305 workaround of disabling interrupts, it can conflict with DMA
>> 306 ( = direct memory access) on many Amiga systems, and it is also said
>> 307 to destabilize other machines. It is very likely that this will
>> 308 cause serious problems on any Amiga or Atari Medusa if set. The only
>> 309 configuration where it should work are 68030-based Ataris, where it
>> 310 apparently improves performance. But you've been warned! Unless you
>> 311 really know what you are doing, say N. Try Y only if you're quite
>> 312 adventurous.
>> 313
>> 314 config SINGLE_MEMORY_CHUNK
>> 315 bool "Use one physical chunk of memory only"
>> 316 depends on ADVANCED && !SUN3
>> 317 help
>> 318 Ignore all but the first contiguous chunk of physical memory for VM
>> 319 purposes. This will save a few bytes kernel size and may speed up
>> 320 some operations. Say N if not sure.
>> 321
>> 322 config 060_WRITETHROUGH
>> 323 bool "Use write-through caching for 68060 supervisor accesses"
>> 324 depends on ADVANCED && M68060
>> 325 ---help---
>> 326 The 68060 generally uses copyback caching of recently accessed data.
>> 327 Copyback caching means that memory writes will be held in an on-chip
>> 328 cache and only written back to memory some time later. Saying Y
>> 329 here will force supervisor (kernel) accesses to use writethrough
>> 330 caching. Writethrough caching means that data is written to memory
>> 331 straight away, so that cache and memory data always agree.
>> 332 Writethrough caching is less efficient, but is needed for some
>> 333 drivers on 68060 based systems where the 68060 bus snooping signal
>> 334 is hardwired on. The 53c710 SCSI driver is known to suffer from
>> 335 this problem.
>> 336
>> 337 endmenu
717 338
718 If unsure, say Y. <<
719 339
720 if PCI !! 340 menu "General setup"
721 341
722 config PCI_NR_FUNCTIONS !! 342 source "fs/Kconfig.binfmt"
723 int "Maximum number of PCI functions ( !! 343
724 range 1 4096 !! 344 config ZORRO
725 default "512" !! 345 bool "Amiga Zorro (AutoConfig) bus support"
726 help !! 346 depends on AMIGA
727 This allows you to specify the maxim !! 347 help
728 this kernel will support. !! 348 This enables support for the Zorro bus in the Amiga. If you have
729 !! 349 expansion cards in your Amiga that conform to the Amiga
730 endif # PCI !! 350 AutoConfig(tm) specification, say Y, otherwise N. Note that even
731 !! 351 expansion cards that do not fit in the Zorro slots but fit in e.g.
732 config HAS_IOMEM !! 352 the CPU slot may fall in this category, so you have to say Y to let
733 def_bool PCI !! 353 Linux use these.
734 !! 354
735 config CHSC_SCH !! 355 config AMIGA_PCMCIA
736 def_tristate m !! 356 bool "Amiga 1200/600 PCMCIA support (EXPERIMENTAL)"
737 prompt "Support for CHSC subchannels" !! 357 depends on AMIGA && EXPERIMENTAL
738 help !! 358 help
739 This driver allows usage of CHSC sub !! 359 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
740 is usually present on LPAR only. !! 360 600. If you intend to use pcmcia cards say Y; otherwise say N.
741 The driver creates a device /dev/chs !! 361
742 obtain I/O configuration information !! 362 config STRAM_SWAP
743 to issue asynchronous chsc commands !! 363 bool "Support for ST-RAM as swap space"
744 You will usually only want to use th !! 364 depends on ATARI && BROKEN
745 LPAR designated for system managemen !! 365 ---help---
>> 366 Some Atari 68k macines (including the 520STF and 1020STE) divide
>> 367 their addressible memory into ST and TT sections. The TT section
>> 368 (up to 512MB) is the main memory; the ST section (up to 4MB) is
>> 369 accessible to the built-in graphics board, runs slower, and is
>> 370 present mainly for backward compatibility with older machines.
>> 371
>> 372 This enables support for using (parts of) ST-RAM as swap space,
>> 373 instead of as normal system memory. This can first enhance system
>> 374 performance if you have lots of alternate RAM (compared to the size
>> 375 of ST-RAM), because executable code always will reside in faster
>> 376 memory. ST-RAM will remain as ultra-fast swap space. On the other
>> 377 hand, it allows much improved dynamic allocations of ST-RAM buffers
>> 378 for device driver modules (e.g. floppy, ACSI, SLM printer, DMA
>> 379 sound). The probability that such allocations at module load time
>> 380 fail is drastically reduced.
>> 381
>> 382 config STRAM_PROC
>> 383 bool "ST-RAM statistics in /proc"
>> 384 depends on ATARI
>> 385 help
>> 386 Say Y here to report ST-RAM usage statistics in /proc/stram. See
>> 387 the help for CONFIG_STRAM_SWAP for discussion of ST-RAM and its
>> 388 uses.
>> 389
>> 390 config HEARTBEAT
>> 391 bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || MAC ||Q40
>> 392 default y if !AMIGA && !APOLLO && !ATARI && !MAC && !Q40 && HP300
>> 393 help
>> 394 Use the power-on LED on your machine as a load meter. The exact
>> 395 behavior is platform-dependent, but normally the flash frequency is
>> 396 a hyperbolic function of the 5-minute load average.
>> 397
>> 398 # We have a dedicated heartbeat LED. :-)
>> 399 config PROC_HARDWARE
>> 400 bool "/proc/hardware support"
>> 401 help
>> 402 Say Y here to support the /proc/hardware file, which gives you
>> 403 access to information about the machine you're running on,
>> 404 including the model, CPU, MMU, clock speed, BogoMIPS rating,
>> 405 and memory size.
>> 406
>> 407 config PARPORT
>> 408 tristate "Parallel port support (EXPERIMENTAL)"
>> 409 depends on EXPERIMENTAL
>> 410 ---help---
>> 411 If you want to use devices connected to your machine's parallel port
>> 412 (the connector at the computer with 25 holes), e.g. printer, ZIP
>> 413 drive, PLIP link (Parallel Line Internet Protocol is mainly used to
>> 414 create a mini network by connecting the parallel ports of two local
>> 415 machines) etc., then you need to say Y here; please read
>> 416 <file:Documentation/parport.txt> and
>> 417 <file:drivers/parport/BUGS-parport>.
>> 418
>> 419 For extensive information about drivers for many devices attaching
>> 420 to the parallel port see <http://www.torque.net/linux-pp.html> on
>> 421 the WWW.
>> 422
>> 423 It is possible to share a single parallel port among several devices
>> 424 and it is safe to compile all the corresponding drivers into the
>> 425 kernel. To compile parallel port support as a module, choose M here:
>> 426 the module will be called parport.
>> 427 If you have more than one parallel port and want to specify which
>> 428 port and IRQ to be used by this driver at module load time, take a
>> 429 look at <file:Documentation/parport.txt>.
>> 430
>> 431 If unsure, say Y.
>> 432
>> 433 config PARPORT_AMIGA
>> 434 tristate "Amiga builtin port"
>> 435 depends on AMIGA && PARPORT
>> 436 help
>> 437 Say Y here if you need support for the parallel port hardware on
>> 438 Amiga machines. This code is also available as a module (say M),
>> 439 called parport_amiga. If in doubt, saying N is the safe plan.
>> 440
>> 441 config PARPORT_MFC3
>> 442 tristate "Multiface III parallel port"
>> 443 depends on ZORRO && PARPORT
>> 444 help
>> 445 Say Y here if you need parallel port support for the MFC3 card.
>> 446 This code is also available as a module (say M), called
>> 447 parport_mfc3. If in doubt, saying N is the safe plan.
>> 448
>> 449 config PARPORT_PC
>> 450 bool
>> 451 depends on Q40 && PARPORT
>> 452 default y
>> 453 ---help---
>> 454 You should say Y here if you have a PC-style parallel port. All IBM
>> 455 PC compatible computers and some Alphas have PC-style parallel
>> 456 ports.
746 457
747 To compile this driver as a module, 458 To compile this driver as a module, choose M here: the
748 module will be called chsc_sch. !! 459 module will be called parport_pc.
749 460
750 If unsure, say N. !! 461 If unsure, say Y.
751 462
752 config SCM_BUS !! 463 config PARPORT_ATARI
753 def_bool y !! 464 tristate "Atari builtin port"
754 prompt "SCM bus driver" !! 465 depends on ATARI && PARPORT
755 help !! 466 help
756 Bus driver for Storage Class Memory. !! 467 Say Y here if you need support for the parallel port hardware on
757 !! 468 Atari machines. This code is also available as a module (say M),
758 config EADM_SCH !! 469 called parport_atari. If in doubt, saying N is the safe plan.
759 def_tristate m !! 470
760 prompt "Support for EADM subchannels" !! 471 config PRINTER
761 depends on SCM_BUS !! 472 tristate "Parallel printer support"
>> 473 depends on PARPORT
>> 474 ---help---
>> 475 If you intend to attach a printer to the parallel port of your Linux
>> 476 box (as opposed to using a serial printer; if the connector at the
>> 477 printer has 9 or 25 holes ["female"], then it's serial), say Y.
>> 478 Also read the Printing-HOWTO, available from
>> 479 <http://www.tldp.org/docs.html#howto>.
>> 480
>> 481 It is possible to share one parallel port among several devices
>> 482 (e.g. printer and ZIP drive) and it is safe to compile the
>> 483 corresponding drivers into the kernel.
>> 484 To compile this driver as a module, choose M here and read
>> 485 <file:Documentation/parport.txt>. The module will be called lp.
>> 486
>> 487 If you have several parallel ports, you can specify which ports to
>> 488 use with the "lp" kernel command line option. (Try "man bootparam"
>> 489 or see the documentation of your boot loader (lilo or loadlin) about
>> 490 how to pass options to the kernel at boot time.) The syntax of the
>> 491 "lp" command line option can be found in <file:drivers/char/lp.c>.
>> 492
>> 493 If you have more than 8 printers, you need to increase the LP_NO
>> 494 macro in lp.c and the PARPORT_MAX macro in parport.h.
>> 495
>> 496 config PARPORT_1284
>> 497 bool "IEEE 1284 transfer modes"
>> 498 depends on PRINTER
>> 499 help
>> 500 If you have a printer that supports status readback or device ID, or
>> 501 want to use a device that uses enhanced parallel port transfer modes
>> 502 such as EPP and ECP, say Y here to enable advanced IEEE 1284
>> 503 transfer modes. Also say Y if you want device ID information to
>> 504 appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
>> 505
>> 506 config ISA
>> 507 bool
>> 508 depends on Q40 || AMIGA_PCMCIA || GG2
>> 509 default y
762 help 510 help
763 This driver allows usage of EADM sub !! 511 Find out whether you have ISA slots on your motherboard. ISA is the
764 as a communication vehicle for SCM i !! 512 name of a bus system, i.e. the way the CPU talks to the other stuff
>> 513 inside your box. Other bus systems are PCI, EISA, MicroChannel
>> 514 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
>> 515 newer boards don't support it. If you have ISA, say Y, otherwise N.
>> 516
>> 517 config GENERIC_ISA_DMA
>> 518 bool
>> 519 depends on Q40 || AMIGA_PCMCIA || GG2
>> 520 default y
>> 521
>> 522 source "drivers/pci/Kconfig"
>> 523
>> 524 source "drivers/zorro/Kconfig"
>> 525
>> 526 if Q40
>> 527 source "drivers/pnp/Kconfig"
>> 528 endif
>> 529
>> 530 endmenu
>> 531
>> 532 source "drivers/base/Kconfig"
>> 533
>> 534 source "drivers/mtd/Kconfig"
>> 535
>> 536 source "drivers/block/Kconfig"
>> 537
>> 538 source "drivers/md/Kconfig"
>> 539
>> 540 source "drivers/input/Kconfig"
>> 541
>> 542 source "drivers/ide/Kconfig"
>> 543
>> 544 source "drivers/scsi/Kconfig"
>> 545
>> 546 source "net/Kconfig"
>> 547
>> 548
>> 549 menu "Character devices"
>> 550
>> 551 config SERIAL
>> 552 tristate "Q40 Standard/generic serial support" if Q40
>> 553 default DN_SERIAL if APOLLO
>> 554 ---help---
>> 555 This selects whether you want to include the driver for the standard
>> 556 serial ports. The standard answer is Y. People who might say N
>> 557 here are those that are setting up dedicated Ethernet WWW/FTP
>> 558 servers, or users that have one of the various bus mice instead of a
>> 559 serial mouse and don't intend to use their machine's standard serial
>> 560 port for anything. (Note that the Cyclades and Stallion multi
>> 561 serial port drivers do not need this driver built in for them to
>> 562 work.)
765 563
766 To compile this driver as a module, 564 To compile this driver as a module, choose M here: the
767 module will be called eadm_sch. !! 565 module will be called serial.
>> 566 [WARNING: Do not compile this driver as a module if you are using
>> 567 non-standard serial ports, since the configuration information will
>> 568 be lost when the driver is unloaded. This limitation may be lifted
>> 569 in the future.]
>> 570
>> 571 BTW1: If you have a mouseman serial mouse which is not recognized by
>> 572 the X window system, try running gpm first.
>> 573
>> 574 BTW2: If you intend to use a software modem (also called Winmodem)
>> 575 under Linux, forget it. These modems are crippled and require
>> 576 proprietary drivers which are only available under Windows.
>> 577
>> 578 Most people will say Y or M here, so that they can use serial mice,
>> 579 modems and similar devices connecting to the standard serial ports.
>> 580
>> 581 config SERIAL_EXTENDED
>> 582 bool "Extended dumb serial driver options"
>> 583 depends on SERIAL=y
>> 584 help
>> 585 If you wish to use any non-standard features of the standard "dumb"
>> 586 driver, say Y here. This includes HUB6 support, shared serial
>> 587 interrupts, special multiport support, support for more than the
>> 588 four COM 1/2/3/4 boards, etc.
>> 589
>> 590 Note that the answer to this question won't directly affect the
>> 591 kernel: saying N will just cause the configurator to skip all
>> 592 the questions about serial driver options. If unsure, say N.
>> 593
>> 594 config SERIAL_MANY_PORTS
>> 595 bool "Support more than 4 serial ports"
>> 596 depends on SERIAL_EXTENDED
>> 597 help
>> 598 Say Y here if you have dumb serial boards other than the four
>> 599 standard COM 1/2/3/4 ports. This may happen if you have an AST
>> 600 FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
>> 601 from <http://www.tldp.org/docs.html#howto>), or other custom
>> 602 serial port hardware which acts similar to standard serial port
>> 603 hardware. If you only use the standard COM 1/2/3/4 ports, you can
>> 604 say N here to save some memory. You can also say Y if you have an
>> 605 "intelligent" multiport card such as Cyclades, Digiboards, etc.
>> 606
>> 607 config SERIAL_SHARE_IRQ
>> 608 bool "Support for sharing serial interrupts"
>> 609 depends on SERIAL_EXTENDED
>> 610 help
>> 611 Some serial boards have hardware support which allows multiple dumb
>> 612 serial ports on the same board to share a single IRQ. To enable
>> 613 support for this in the serial driver, say Y here.
>> 614
>> 615 config SERIAL_MULTIPORT
>> 616 bool "Support special multiport boards"
>> 617 depends on SERIAL_EXTENDED
>> 618 help
>> 619 Some multiport serial ports have special ports which are used to
>> 620 signal when there are any serial ports on the board which need
>> 621 servicing. Say Y here to enable the serial driver to take advantage
>> 622 of those special I/O ports.
>> 623
>> 624 config HUB6
>> 625 bool "Support the Bell Technologies HUB6 card"
>> 626 depends on SERIAL_EXTENDED
>> 627 help
>> 628 Say Y here to enable support in the dumb serial driver to support
>> 629 the HUB6 card.
>> 630
>> 631 config VT
>> 632 bool "Virtual terminal"
>> 633 ---help---
>> 634 If you say Y here, you will get support for terminal devices with
>> 635 display and keyboard devices. These are called "virtual" because you
>> 636 can run several virtual terminals (also called virtual consoles) on
>> 637 one physical terminal. This is rather useful, for example one
>> 638 virtual terminal can collect system messages and warnings, another
>> 639 one can be used for a text-mode user session, and a third could run
>> 640 an X session, all in parallel. Switching between virtual terminals
>> 641 is done with certain key combinations, usually Alt-<function key>.
>> 642
>> 643 The setterm command ("man setterm") can be used to change the
>> 644 properties (such as colors or beeping) of a virtual terminal. The
>> 645 man page console_codes(4) ("man console_codes") contains the special
>> 646 character sequences that can be used to change those properties
>> 647 directly. The fonts used on virtual terminals can be changed with
>> 648 the setfont ("man setfont") command and the key bindings are defined
>> 649 with the loadkeys ("man loadkeys") command.
>> 650
>> 651 You need at least one virtual terminal device in order to make use
>> 652 of your keyboard and monitor. Therefore, only people configuring an
>> 653 embedded system would want to say N here in order to save some
>> 654 memory; the only way to log into such a system is then via a serial
>> 655 or network connection.
>> 656
>> 657 If unsure, say Y, or else you won't be able to do much with your new
>> 658 shiny Linux system :-)
>> 659
>> 660 config VT_CONSOLE
>> 661 bool "Support for console on virtual terminal"
>> 662 depends on VT
>> 663 ---help---
>> 664 The system console is the device which receives all kernel messages
>> 665 and warnings and which allows logins in single user mode. If you
>> 666 answer Y here, a virtual terminal (the device used to interact with
>> 667 a physical terminal) can be used as system console. This is the most
>> 668 common mode of operations, so you should say Y here unless you want
>> 669 the kernel messages be output only to a serial port (in which case
>> 670 you should say Y to "Console on serial port", below).
>> 671
>> 672 If you do say Y here, by default the currently visible virtual
>> 673 terminal (/dev/tty0) will be used as system console. You can change
>> 674 that with a kernel command line option such as "console=tty3" which
>> 675 would use the third virtual terminal as system console. (Try "man
>> 676 bootparam" or see the documentation of your boot loader (lilo or
>> 677 loadlin) about how to pass options to the kernel at boot time.)
>> 678
>> 679 If unsure, say Y.
>> 680
>> 681 config HW_CONSOLE
>> 682 bool
>> 683 depends on VT
>> 684 default y
>> 685
>> 686 config NVRAM
>> 687 bool
>> 688 depends on ATARI
>> 689 default y
>> 690 ---help---
>> 691 If you say Y here and create a character special file /dev/nvram
>> 692 with major number 10 and minor number 144 using mknod ("man mknod"),
>> 693 you get read and write access to the 50 bytes of non-volatile memory
>> 694 in the real time clock (RTC), which is contained in every PC and
>> 695 most Ataris.
>> 696
>> 697 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
>> 698 on Ataris. /dev/nvram may be used to view settings there, or to
>> 699 change them (with some utility). It could also be used to frequently
>> 700 save a few bits of very important data that may not be lost over
>> 701 power-off and for which writing to disk is too insecure. Note
>> 702 however that most NVRAM space in a PC belongs to the BIOS and you
>> 703 should NEVER idly tamper with it. See Ralf Brown's interrupt list
>> 704 for a guide to the use of CMOS bytes by your BIOS.
768 705
769 config AP !! 706 On Atari machines, /dev/nvram is always configured and does not need
770 def_tristate y !! 707 to be selected.
771 prompt "Support for Adjunct Processors <<
772 help <<
773 This driver allows usage to Adjunct <<
774 the ap bus, cards and queues. Suppor <<
775 the CryptoExpress Cards (CEX). <<
776 708
777 To compile this driver as a module, 709 To compile this driver as a module, choose M here: the
778 module will be called ap. !! 710 module will be called nvram.
779 711
780 If unsure, say Y (default). !! 712 config ATARI_MFPSER
>> 713 tristate "Atari MFP serial support"
>> 714 depends on ATARI
>> 715 ---help---
>> 716 If you like to use the MFP serial ports ("Modem1", "Serial1") under
>> 717 Linux, say Y. The driver equally supports all kinds of MFP serial
>> 718 ports and automatically detects whether Serial1 is available.
>> 719
>> 720 To compile this driver as a module, choose M here.
>> 721
>> 722 Note for Falcon users: You also have an MFP port, it's just not
>> 723 wired to the outside... But you could use the port under Linux.
>> 724
>> 725 config ATARI_SCC
>> 726 tristate "Atari SCC serial support"
>> 727 depends on ATARI
>> 728 ---help---
>> 729 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
>> 730 LAN) and like to use them under Linux, say Y. All built-in SCC's are
>> 731 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
>> 732 two connectors for channel A (Serial2 and LAN), they are visible as
>> 733 two separate devices.
>> 734
>> 735 To compile this driver as a module, choose M here.
>> 736
>> 737 config ATARI_SCC_DMA
>> 738 bool "Atari SCC serial DMA support"
>> 739 depends on ATARI_SCC
>> 740 help
>> 741 This enables DMA support for receiving data on channel A of the SCC.
>> 742 If you have a TT you may say Y here and read
>> 743 drivers/char/atari_SCC.README. All other users should say N here,
>> 744 because only the TT has SCC-DMA, even if your machine keeps claiming
>> 745 so at boot time.
>> 746
>> 747 config ATARI_MIDI
>> 748 tristate "Atari MIDI serial support"
>> 749 depends on ATARI
>> 750 help
>> 751 If you want to use your Atari's MIDI port in Linux, say Y.
>> 752
>> 753 To compile this driver as a module, choose M here.
>> 754
>> 755 config ATARI_DSP56K
>> 756 tristate "Atari DSP56k support (EXPERIMENTAL)"
>> 757 depends on ATARI && EXPERIMENTAL
>> 758 help
>> 759 If you want to be able to use the DSP56001 in Falcons, say Y. This
>> 760 driver is still experimental, and if you don't know what it is, or
>> 761 if you don't have this processor, just say N.
>> 762
>> 763 To compile this driver as a module, choose M here.
>> 764
>> 765 config AMIGA_BUILTIN_SERIAL
>> 766 tristate "Amiga builtin serial support"
>> 767 depends on AMIGA
>> 768 help
>> 769 If you want to use your Amiga's built-in serial port in Linux,
>> 770 answer Y.
>> 771
>> 772 To compile this driver as a module, choose M here.
>> 773
>> 774 config WHIPPET_SERIAL
>> 775 tristate "Hisoft Whippet PCMCIA serial support"
>> 776 depends on AMIGA_PCMCIA
>> 777 help
>> 778 HiSoft has a web page at <http://www.hisoft.co.uk/>, but there
>> 779 is no listing for the Whippet in their Amiga section.
>> 780
>> 781 config MULTIFACE_III_TTY
>> 782 tristate "Multiface Card III serial support"
>> 783 depends on AMIGA
>> 784 help
>> 785 If you want to use a Multiface III card's serial port in Linux,
>> 786 answer Y.
>> 787
>> 788 To compile this driver as a module, choose M here.
>> 789
>> 790 config A2232
>> 791 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
>> 792 depends on AMIGA && EXPERIMENTAL
>> 793 ---help---
>> 794 This option supports the 2232 7-port serial card shipped with the
>> 795 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
>> 796 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
>> 797 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
>> 798 ports were connected with 8 pin DIN connectors on the card bracket,
>> 799 for which 8 pin to DB25 adapters were supplied. The card also had
>> 800 jumpers internally to toggle various pinning configurations.
>> 801
>> 802 This driver can be built as a module; but then "generic_serial"
>> 803 will also be built as a module. This has to be loaded before
>> 804 "ser_a2232". If you want to do this, answer M here.
>> 805
>> 806 config GVPIOEXT
>> 807 tristate "GVP IO-Extender support"
>> 808 depends on PARPORT=n && ZORRO
>> 809 help
>> 810 If you want to use a GVP IO-Extender serial card in Linux, say Y.
>> 811 Otherwise, say N.
>> 812
>> 813 config GVPIOEXT_LP
>> 814 tristate "GVP IO-Extender parallel printer support"
>> 815 depends on GVPIOEXT
>> 816 help
>> 817 Say Y to enable driving a printer from the parallel port on your
>> 818 GVP IO-Extender card, N otherwise.
>> 819
>> 820 config GVPIOEXT_PLIP
>> 821 tristate "GVP IO-Extender PLIP support"
>> 822 depends on GVPIOEXT
>> 823 help
>> 824 Say Y to enable doing IP over the parallel port on your GVP
>> 825 IO-Extender card, N otherwise.
>> 826
>> 827 config MAC_SCC
>> 828 tristate "Macintosh serial support"
>> 829 depends on MAC
>> 830
>> 831 config ADB
>> 832 bool "Apple Desktop Bus (ADB) support"
>> 833 depends on MAC
>> 834 help
>> 835 Apple Desktop Bus (ADB) support is for support of devices which
>> 836 are connected to an ADB port. ADB devices tend to have 4 pins.
>> 837 If you have an Apple Macintosh prior to the iMac, or a
>> 838 "Blue and White G3", you probably want to say Y here. Otherwise
>> 839 say N.
>> 840
>> 841 config ADB_MACII
>> 842 bool "Include Mac II ADB driver"
>> 843 depends on ADB
>> 844 help
>> 845 Say Y here if want your kernel to support Macintosh systems that use
>> 846 the Mac II style ADB. This includes the II, IIx, IIcx, SE/30, IIci,
>> 847 Quadra 610, Quadra 650, Quadra 700, Quadra 800, Centris 610 and
>> 848 Centris 650.
>> 849
>> 850 config ADB_MACIISI
>> 851 bool "Include Mac IIsi ADB driver"
>> 852 depends on ADB
>> 853 help
>> 854 Say Y here if want your kernel to support Macintosh systems that use
>> 855 the Mac IIsi style ADB. This includes the IIsi, IIvi, IIvx, Classic
>> 856 II, LC, LC II, LC III, Performa 460, and the Performa 600.
>> 857
>> 858 config ADB_CUDA
>> 859 bool "Include CUDA ADB driver"
>> 860 depends on ADB
>> 861 help
>> 862 This provides support for CUDA based Power Macintosh systems. This
>> 863 includes most OldWorld PowerMacs, the first generation iMacs, the
>> 864 Blue&White G3 and the Yikes G4 (PCI Graphics). All later models
>> 865 should use CONFIG_ADB_PMU instead.
>> 866
>> 867 If unsure say Y.
>> 868
>> 869 config ADB_IOP
>> 870 bool "Include IOP (IIfx/Quadra 9x0) ADB driver"
>> 871 depends on ADB
>> 872 help
>> 873 The I/O Processor (IOP) is an Apple custom IC designed to provide
>> 874 intelligent support for I/O controllers. It is described at
>> 875 <http://www.angelfire.com/ca2/dev68k/iopdesc.html> to enable direct
>> 876 support for it, say 'Y' here.
>> 877
>> 878 config ADB_PMU68K
>> 879 bool "Include PMU (Powerbook) ADB driver"
>> 880 depends on ADB
>> 881 help
>> 882 Say Y here if want your kernel to support the m68k based Powerbooks.
>> 883 This includes the PowerBook 140, PowerBook 145, PowerBook 150,
>> 884 PowerBook 160, PowerBook 165, PowerBook 165c, PowerBook 170,
>> 885 PowerBook 180, PowerBook, 180c, PowerBook 190cs, PowerBook 520,
>> 886 PowerBook Duo 210, PowerBook Duo 230, PowerBook Duo 250,
>> 887 PowerBook Duo 270c, PowerBook Duo 280 and PowerBook Duo 280c.
>> 888
>> 889 config INPUT_ADBHID
>> 890 bool "Use input layer for ADB devices"
>> 891 depends on MAC && INPUT=y
>> 892 ---help---
>> 893 Say Y here if you want to have ADB (Apple Desktop Bus) HID devices
>> 894 such as keyboards, mice, joysticks, or graphic tablets handled by
>> 895 the input layer. If you say Y here, make sure to say Y to the
>> 896 corresponding drivers "Keyboard support" (CONFIG_INPUT_KEYBDEV),
>> 897 "Mouse Support" (CONFIG_INPUT_MOUSEDEV) and "Event interface
>> 898 support" (CONFIG_INPUT_EVDEV) as well.
781 899
782 config AP_DEBUG !! 900 If you say N here, you still have the option of using the old ADB
783 def_bool n !! 901 keyboard and mouse drivers.
784 prompt "Enable debug features for Adju <<
785 depends on AP <<
786 help <<
787 Say 'Y' here to enable some addition <<
788 Processor (ap) devices. <<
789 902
790 There will be some more sysfs attrib !! 903 If unsure, say Y.
791 904
792 Do not enable on production level ke !! 905 config MAC_HID
>> 906 bool
>> 907 depends on INPUT_ADBHID
>> 908 default y
>> 909
>> 910 config MAC_ADBKEYCODES
>> 911 bool "Support for ADB raw keycodes"
>> 912 depends on INPUT_ADBHID
>> 913 help
>> 914 This provides support for sending raw ADB keycodes to console
>> 915 devices. This is the default up to 2.4.0, but in future this may be
>> 916 phased out in favor of generic Linux keycodes. If you say Y here,
>> 917 you can dynamically switch via the
>> 918 /proc/sys/dev/mac_hid/keyboard_sends_linux_keycodes
>> 919 sysctl and with the "keyboard_sends_linux_keycodes=" kernel
>> 920 argument.
>> 921
>> 922 If unsure, say Y here.
>> 923
>> 924 config MAC_EMUMOUSEBTN
>> 925 bool "Support for mouse button 2+3 emulation"
>> 926 depends on INPUT_ADBHID
>> 927 help
>> 928 This provides generic support for emulating the 2nd and 3rd mouse
>> 929 button with keypresses. If you say Y here, the emulation is still
>> 930 disabled by default. The emulation is controlled by these sysctl
>> 931 entries:
>> 932 /proc/sys/dev/mac_hid/mouse_button_emulation
>> 933 /proc/sys/dev/mac_hid/mouse_button2_keycode
>> 934 /proc/sys/dev/mac_hid/mouse_button3_keycode
>> 935
>> 936 config ADB_KEYBOARD
>> 937 bool "Support for ADB keyboard (old driver)"
>> 938 depends on MAC && !INPUT_ADBHID
>> 939 help
>> 940 This option allows you to use an ADB keyboard attached to your
>> 941 machine. Note that this disables any other (ie. PS/2) keyboard
>> 942 support, even if your machine is physically capable of using both at
>> 943 the same time.
>> 944
>> 945 If you use an ADB keyboard (4 pin connector), say Y here.
>> 946 If you use a PS/2 keyboard (6 pin connector), say N here.
>> 947
>> 948 config HPDCA
>> 949 tristate "HP DCA serial support"
>> 950 depends on DIO
>> 951 help
>> 952 If you want to use the internal "DCA" serial ports on an HP300
>> 953 machine, say Y here.
>> 954
>> 955 config MVME147_SCC
>> 956 bool "SCC support for MVME147 serial ports"
>> 957 depends on MVME147
>> 958 help
>> 959 This is the driver for the serial ports on the Motorola MVME147
>> 960 boards. Everyone using one of these boards should say Y here.
>> 961
>> 962 config SERIAL167
>> 963 bool "CD2401 support for MVME166/7 serial ports"
>> 964 depends on MVME16x && BROKEN
>> 965 help
>> 966 This is the driver for the serial ports on the Motorola MVME166,
>> 967 167, and 172 boards. Everyone using one of these boards should say
>> 968 Y here.
>> 969
>> 970 config MVME162_SCC
>> 971 bool "SCC support for MVME162 serial ports"
>> 972 depends on MVME16x
>> 973 help
>> 974 This is the driver for the serial ports on the Motorola MVME162 and
>> 975 172 boards. Everyone using one of these boards should say Y here.
>> 976
>> 977 config BVME6000_SCC
>> 978 bool "SCC support for BVME6000 serial ports"
>> 979 depends on BVME6000
>> 980 help
>> 981 This is the driver for the serial ports on the BVME4000 and BVME6000
>> 982 boards from BVM Ltd. Everyone using one of these boards should say
>> 983 Y here.
>> 984
>> 985 config DN_SERIAL
>> 986 bool "Support for DN serial port (dummy)"
>> 987 depends on APOLLO
>> 988
>> 989 config SERIAL_CONSOLE
>> 990 bool "Support for serial port console"
>> 991 depends on (AMIGA || ATARI || MAC || HP300 || SUN3 || SUN3X || VME || APOLLO) && (ATARI_MFPSER=y || ATARI_SCC=y || ATARI_MIDI=y || MAC_SCC=y || AMIGA_BUILTIN_SERIAL=y || GVPIOEXT=y || MULTIFACE_III_TTY=y || HPDCA=y || SERIAL=y || MVME147_SCC || SERIAL167 || MVME162_SCC || BVME6000_SCC || DN_SERIAL)
>> 992 ---help---
>> 993 If you say Y here, it will be possible to use a serial port as the
>> 994 system console (the system console is the device which receives all
>> 995 kernel messages and warnings and which allows logins in single user
>> 996 mode). This could be useful if some terminal or printer is connected
>> 997 to that serial port.
>> 998
>> 999 Even if you say Y here, the currently visible virtual console
>> 1000 (/dev/tty0) will still be used as the system console by default, but
>> 1001 you can alter that using a kernel command line option such as
>> 1002 "console=ttyS1". (Try "man bootparam" or see the documentation of
>> 1003 your boot loader (lilo or loadlin) about how to pass options to the
>> 1004 kernel at boot time.)
>> 1005
>> 1006 If you don't have a VGA card installed and you say Y here, the
>> 1007 kernel will automatically use the first serial line, /dev/ttyS0, as
>> 1008 system console.
793 1009
794 If unsure, say N. 1010 If unsure, say N.
795 1011
796 config VFIO_CCW !! 1012 config USERIAL
797 def_tristate n !! 1013 bool "Support for user serial device modules"
798 prompt "Support for VFIO-CCW subchanne !! 1014
799 depends on VFIO !! 1015 config WATCHDOG
800 select VFIO_MDEV !! 1016 bool "Watchdog Timer Support"
801 help !! 1017 ---help---
802 This driver allows usage of I/O subc !! 1018 If you say Y here (and to one of the following options) and create a
>> 1019 character special file /dev/watchdog with major number 10 and minor
>> 1020 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
>> 1021 subsequently opening the file and then failing to write to it for
>> 1022 longer than 1 minute will result in rebooting the machine. This
>> 1023 could be useful for a networked machine that needs to come back
>> 1024 online as fast as possible after a lock-up. There's both a watchdog
>> 1025 implementation entirely in software (which can sometimes fail to
>> 1026 reboot the machine) and a driver for hardware watchdog boards, which
>> 1027 are more robust and can also keep track of the temperature inside
>> 1028 your computer. For details, read <file:Documentation/watchdog.txt>
>> 1029 in the kernel source.
>> 1030
>> 1031 The watchdog is usually used together with the watchdog daemon
>> 1032 which is available from
>> 1033 <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
>> 1034 also monitor NFS connections and can reboot the machine when the process
>> 1035 table is full.
>> 1036
>> 1037 If unsure, say N.
>> 1038
>> 1039 config WATCHDOG_NOWAYOUT
>> 1040 bool "Disable watchdog shutdown on close"
>> 1041 depends on WATCHDOG
>> 1042 help
>> 1043 The default watchdog behaviour (which you get if you say N here) is
>> 1044 to stop the timer if the process managing it closes the file
>> 1045 /dev/watchdog. It's always remotely possible that this process might
>> 1046 get killed. If you say Y here, the watchdog cannot be stopped once
>> 1047 it has been started.
>> 1048
>> 1049 config SOFT_WATCHDOG
>> 1050 bool "Software watchdog"
>> 1051 depends on WATCHDOG
>> 1052 help
>> 1053 A software monitoring watchdog. This will fail to reboot your system
>> 1054 from some situations that the hardware watchdog will recover
>> 1055 from. Equally it's a lot cheaper to install.
803 1056
804 To compile this driver as a module, 1057 To compile this driver as a module, choose M here: the
805 module will be called vfio_ccw. !! 1058 module will be called softdog.
806 1059
807 config VFIO_AP !! 1060 config GEN_RTC
808 def_tristate n !! 1061 tristate "Generic /dev/rtc emulation" if !SUN3
809 prompt "VFIO support for AP devices" !! 1062 default y if SUN3
810 depends on KVM !! 1063 ---help---
811 depends on VFIO !! 1064 If you say Y here and create a character special file /dev/rtc with
812 depends on AP !! 1065 major number 10 and minor number 135 using mknod ("man mknod"), you
813 select VFIO_MDEV !! 1066 will get access to the real time clock (or hardware clock) built
>> 1067 into your computer.
>> 1068
>> 1069 It reports status information via the file /proc/driver/rtc and its
>> 1070 behaviour is set by various ioctls on /dev/rtc. If you enable the
>> 1071 "extended RTC operation" below it will also provide an emulation
>> 1072 for RTC_UIE which is required by some programs and may improve
>> 1073 precision in some cases.
>> 1074
>> 1075 To compile this driver as a module, choose M here: the
>> 1076 module will be called genrtc. To load the module automatically
>> 1077 add 'alias char-major-10-135 genrtc' to your /etc/modules.conf
>> 1078
>> 1079 config GEN_RTC_X
>> 1080 bool "Extended RTC operation"
>> 1081 depends on GEN_RTC
>> 1082 help
>> 1083 Provides an emulation for RTC_UIE which is required by some programs
>> 1084 and may improve precision of the generic RTC support in some cases.
>> 1085
>> 1086 config UNIX98_PTYS
>> 1087 bool "Unix98 PTY support"
>> 1088 ---help---
>> 1089 A pseudo terminal (PTY) is a software device consisting of two
>> 1090 halves: a master and a slave. The slave device behaves identical to
>> 1091 a physical terminal; the master device is used by a process to
>> 1092 read data from and write data to the slave, thereby emulating a
>> 1093 terminal. Typical programs for the master side are telnet servers
>> 1094 and xterms.
>> 1095
>> 1096 Linux has traditionally used the BSD-like names /dev/ptyxx for
>> 1097 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
>> 1098 has a number of problems. The GNU C library glibc 2.1 and later,
>> 1099 however, supports the Unix98 naming standard: in order to acquire a
>> 1100 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
>> 1101 terminal is then made available to the process and the pseudo
>> 1102 terminal slave can be accessed as /dev/pts/<number>. What was
>> 1103 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
>> 1104
>> 1105 The entries in /dev/pts/ are created on the fly by a virtual
>> 1106 file system; therefore, if you say Y here you should say Y to
>> 1107 "/dev/pts file system for Unix98 PTYs" as well.
>> 1108
>> 1109 If you want to say Y here, you need to have the C library glibc 2.1
>> 1110 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
>> 1111 Read the instructions in <file:Documentation/Changes> pertaining to
>> 1112 pseudo terminals. It's safe to say N.
>> 1113
>> 1114 config UNIX98_PTY_COUNT
>> 1115 int "Maximum number of Unix98 PTYs in use (0-2048)"
>> 1116 depends on UNIX98_PTYS
>> 1117 default "256"
814 help 1118 help
815 This driver grants access to Adjunct !! 1119 The maximum number of Unix98 PTYs that can be used at any one time.
816 via the VFIO mediated device interfa !! 1120 The default is 256, and should be enough for desktop systems. Server
>> 1121 machines which support incoming telnet/rlogin/ssh connections and/or
>> 1122 serve several X terminals may want to increase this: every incoming
>> 1123 connection and every xterm uses up one PTY.
817 1124
818 To compile this driver as a module, !! 1125 When not in use, each additional set of 256 PTYs occupy
819 will be called vfio_ap. !! 1126 approximately 8 KB of kernel memory on 32-bit architectures.
820 1127
821 endmenu 1128 endmenu
822 1129
823 config CCW !! 1130 source "sound/Kconfig"
824 def_bool y <<
825 1131
826 config HAVE_PNETID !! 1132 source "fs/Kconfig"
827 tristate <<
828 default (SMC || CCWGROUP) <<
829 <<
830 menu "Virtualization" <<
831 1133
832 config PFAULT !! 1134 source "drivers/video/Kconfig"
833 def_bool y <<
834 prompt "Pseudo page fault support" <<
835 help <<
836 Select this option, if you want to u <<
837 handling under VM. If running native <<
838 has no effect. If your VM does not s <<
839 pseudo page fault handling will be u <<
840 Note that VM 4.2 supports PFAULT but <<
841 implementation that causes some prob <<
842 Everybody who wants to run Linux und <<
843 this option. <<
844 <<
845 config CMM <<
846 def_tristate n <<
847 prompt "Cooperative memory management" <<
848 help <<
849 Select this option, if you want to e <<
850 to reduce the memory size of the sys <<
851 by allocating pages of memory and pu <<
852 makes sense for a system running und <<
853 will be reused by VM for other guest <<
854 allows an external monitor to balanc <<
855 Everybody who wants to run Linux und <<
856 option. <<
857 <<
858 config CMM_IUCV <<
859 def_bool y <<
860 prompt "IUCV special message interface <<
861 depends on CMM && (SMSGIUCV=y || CMM=S <<
862 help <<
863 Select this option to enable the spe <<
864 the cooperative memory management. <<
865 <<
866 config APPLDATA_BASE <<
867 def_bool n <<
868 prompt "Linux - VM Monitor Stream, bas <<
869 depends on PROC_SYSCTL <<
870 help <<
871 This provides a kernel interface for <<
872 monitor records. The monitor records <<
873 intervals, once the timer is started <<
874 Writing 1 or 0 to /proc/appldata/tim <<
875 i.e. enables or disables monitoring <<
876 A custom interval value (in seconds) <<
877 /proc/appldata/interval. <<
878 <<
879 Defaults are 60 seconds interval and <<
880 The /proc entries can also be read f <<
881 <<
882 config APPLDATA_MEM <<
883 def_tristate m <<
884 prompt "Monitor memory management stat <<
885 depends on APPLDATA_BASE && VM_EVENT_C <<
886 help <<
887 This provides memory management rela <<
888 Stream, like paging/swapping rate, m <<
889 Writing 1 or 0 to /proc/appldata/mem <<
890 APPLDATA monitor record, i.e. enable <<
891 on the z/VM side. <<
892 <<
893 Default is disabled. <<
894 The /proc entry can also be read fro <<
895 <<
896 This can also be compiled as a modul <<
897 appldata_mem.o. <<
898 <<
899 config APPLDATA_OS <<
900 def_tristate m <<
901 prompt "Monitor OS statistics" <<
902 depends on APPLDATA_BASE <<
903 help <<
904 This provides OS related data to the <<
905 CPU utilisation, etc. <<
906 Writing 1 or 0 to /proc/appldata/os <<
907 APPLDATA monitor record, i.e. enable <<
908 on the z/VM side. <<
909 <<
910 Default is disabled. <<
911 This can also be compiled as a modul <<
912 appldata_os.o. <<
913 <<
914 config APPLDATA_NET_SUM <<
915 def_tristate m <<
916 prompt "Monitor overall network statis <<
917 depends on APPLDATA_BASE && NET <<
918 help <<
919 This provides network related data t <<
920 currently there is only a total sum <<
921 per-interface data. <<
922 Writing 1 or 0 to /proc/appldata/net <<
923 APPLDATA monitor record, i.e. enable <<
924 on the z/VM side. <<
925 <<
926 Default is disabled. <<
927 This can also be compiled as a modul <<
928 appldata_net_sum.o. <<
929 <<
930 config S390_HYPFS <<
931 def_bool y <<
932 prompt "s390 hypervisor information" <<
933 help <<
934 This provides several binary files a <<
935 provide accounting information in an <<
936 <<
937 config S390_HYPFS_FS <<
938 def_bool n <<
939 prompt "s390 hypervisor file system su <<
940 select SYS_HYPERVISOR <<
941 depends on S390_HYPFS <<
942 help <<
943 This is a virtual file system intend <<
944 information in an s390 hypervisor en <<
945 is deprecated and should not be used <<
946 <<
947 Say N if you are unsure. <<
948 <<
949 source "arch/s390/kvm/Kconfig" <<
950 <<
951 config S390_GUEST <<
952 def_bool y <<
953 prompt "s390 support for virtio device <<
954 select TTY <<
955 select VIRTUALIZATION <<
956 select VIRTIO <<
957 help <<
958 Enabling this option adds support fo <<
959 drivers on s390. <<
960 1135
961 Select this option if you want to ru !! 1136 menu "Kernel hacking"
962 the KVM hypervisor. <<
963 1137
>> 1138 config DEBUG_KERNEL
>> 1139 bool "Kernel debugging"
>> 1140
>> 1141 config MAGIC_SYSRQ
>> 1142 bool "Magic SysRq key"
>> 1143 depends on DEBUG_KERNEL
>> 1144 help
>> 1145 If you say Y here, you will have some control over the system even
>> 1146 if the system crashes for example during kernel debugging (e.g., you
>> 1147 will be able to flush the buffer cache to disk, reboot the system
>> 1148 immediately or dump some status information). This is accomplished
>> 1149 by pressing various keys while holding SysRq (Alt+PrintScreen). It
>> 1150 also works on a serial console (on PC hardware at least), if you
>> 1151 send a BREAK and then within 5 seconds a command keypress. The
>> 1152 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
>> 1153 unless you really know what this hack does.
>> 1154
>> 1155 config DEBUG_SLAB
>> 1156 bool "Debug memory allocations"
>> 1157 depends on DEBUG_KERNEL
>> 1158
>> 1159 config DEBUG_BUGVERBOSE
>> 1160 bool "Verbose BUG() reporting"
>> 1161 depends on DEBUG_KERNEL
>> 1162
>> 1163 config DEBUG_INFO
>> 1164 bool "Compile the kernel with debug info"
>> 1165 depends on DEBUG_KERNEL
>> 1166 help
>> 1167 If you say Y here the resulting kernel image will include
>> 1168 debugging info resulting in a larger kernel image.
>> 1169 Say Y here only if you plan to use gdb to debug the kernel.
>> 1170 If you don't debug the kernel, you can say N.
>> 1171
964 endmenu 1172 endmenu
965 1173
966 config S390_MODULES_SANITY_TEST_HELPERS !! 1174 source "security/Kconfig"
967 def_bool n <<
968 1175
969 menu "Selftests" !! 1176 source "crypto/Kconfig"
970 1177
971 config S390_UNWIND_SELFTEST !! 1178 source "lib/Kconfig"
972 def_tristate n <<
973 depends on KUNIT <<
974 default KUNIT_ALL_TESTS <<
975 prompt "Test unwind functions" <<
976 help <<
977 This option enables s390 specific st <<
978 module. This option is not useful fo <<
979 kernels, but only for kernel develop <<
980 <<
981 Say N if you are unsure. <<
982 <<
983 config S390_KPROBES_SANITY_TEST <<
984 def_tristate n <<
985 prompt "Enable s390 specific kprobes t <<
986 depends on KPROBES <<
987 depends on KUNIT <<
988 help <<
989 This option enables an s390 specific <<
990 is not useful for distributions or g <<
991 developers working on architecture c <<
992 <<
993 Say N if you are unsure. <<
994 <<
995 config S390_MODULES_SANITY_TEST <<
996 def_tristate n <<
997 depends on KUNIT <<
998 default KUNIT_ALL_TESTS <<
999 prompt "Enable s390 specific modules t <<
1000 select S390_MODULES_SANITY_TEST_HELPE <<
1001 help <<
1002 This option enables an s390 specifi <<
1003 not useful for distributions or gen <<
1004 kernel developers working on archit <<
1005 1179
1006 Say N if you are unsure. <<
1007 endmenu <<
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.