1 # SPDX-License-Identifier: GPL-2.0 !! 1 #
2 !! 2 # For a description of the syntax of this configuration file,
3 menu "UML-specific options" !! 3 # see Documentation/kbuild/kconfig-language.txt.
4 !! 4 #
5 config UML !! 5 config M68K
6 bool 6 bool
7 default y 7 default y
8 select ARCH_HAS_CPU_FINALIZE_INIT !! 8 select HAVE_AOUT
9 select ARCH_HAS_FORTIFY_SOURCE !! 9 select HAVE_IDE
10 select ARCH_HAS_GCOV_PROFILE_ALL <<
11 select ARCH_HAS_KCOV <<
12 select ARCH_HAS_STRNCPY_FROM_USER <<
13 select ARCH_HAS_STRNLEN_USER <<
14 select HAVE_ARCH_AUDITSYSCALL <<
15 select HAVE_ARCH_KASAN if X86_64 <<
16 select HAVE_ARCH_KASAN_VMALLOC if HAVE <<
17 select HAVE_ARCH_SECCOMP_FILTER <<
18 select HAVE_ASM_MODVERSIONS <<
19 select HAVE_UID16 <<
20 select HAVE_DEBUG_KMEMLEAK <<
21 select HAVE_DEBUG_BUGVERBOSE <<
22 select HAVE_PAGE_SIZE_4KB <<
23 select NO_DMA if !UML_DMA_EMULATION <<
24 select OF_EARLY_FLATTREE if OF <<
25 select GENERIC_IRQ_SHOW <<
26 select GENERIC_CPU_DEVICES <<
27 select HAVE_GCC_PLUGINS <<
28 select ARCH_SUPPORTS_LTO_CLANG <<
29 select ARCH_SUPPORTS_LTO_CLANG_THIN <<
30 select TRACE_IRQFLAGS_SUPPORT <<
31 select TTY # Needed for line.c <<
32 select HAVE_ARCH_VMAP_STACK <<
33 select HAVE_RUST <<
34 select ARCH_HAS_UBSAN <<
35 10
36 config MMU 11 config MMU
37 bool 12 bool
38 default y 13 default y
39 14
40 config UML_DMA_EMULATION !! 15 config RWSEM_GENERIC_SPINLOCK
41 bool 16 bool
42 <<
43 config NO_IOMEM <<
44 bool "disable IOMEM" if EXPERT <<
45 depends on !INDIRECT_IOMEM <<
46 default y 17 default y
47 18
48 config UML_IOMEM_EMULATION !! 19 config RWSEM_XCHGADD_ALGORITHM
49 bool 20 bool
50 select INDIRECT_IOMEM <<
51 select HAS_IOPORT <<
52 select GENERIC_PCI_IOMAP <<
53 select GENERIC_IOMAP <<
54 select NO_GENERIC_PCI_IOPORT_MAP <<
55 21
56 config NO_IOPORT_MAP !! 22 config ARCH_HAS_ILOG2_U32
57 def_bool !UML_IOMEM_EMULATION !! 23 bool
>> 24 default n
58 25
59 config ISA !! 26 config ARCH_HAS_ILOG2_U64
60 bool 27 bool
>> 28 default n
61 29
62 config SBUS !! 30 config GENERIC_HWEIGHT
63 bool 31 bool
>> 32 default y
64 33
65 config LOCKDEP_SUPPORT !! 34 config GENERIC_CALIBRATE_DELAY
66 bool 35 bool
67 default y 36 default y
68 37
69 config STACKTRACE_SUPPORT !! 38 config TIME_LOW_RES
70 bool 39 bool
71 default y 40 default y
72 select STACKTRACE <<
73 41
74 config GENERIC_CALIBRATE_DELAY !! 42 config GENERIC_IOMAP
>> 43 bool
>> 44 default y
>> 45
>> 46 config ARCH_MAY_HAVE_PC_FDC
75 bool 47 bool
>> 48 depends on BROKEN && (Q40 || SUN3X)
76 default y 49 default y
77 50
>> 51 config NO_IOPORT
>> 52 def_bool y
>> 53
>> 54 config NO_DMA
>> 55 def_bool SUN3
>> 56
78 config HZ 57 config HZ
79 int 58 int
80 default 100 59 default 100
81 60
82 config NR_CPUS !! 61 config GENERIC_TIME
83 int !! 62 def_bool y
84 range 1 1 <<
85 default 1 <<
86 63
87 config ARCH_HAS_CACHE_LINE_SIZE !! 64 config ARCH_USES_GETTIMEOFFSET
88 def_bool y 65 def_bool y
89 66
90 source "arch/$(HEADER_ARCH)/um/Kconfig" !! 67 mainmenu "Linux/68k Kernel Configuration"
>> 68
>> 69 source "init/Kconfig"
>> 70
>> 71 source "kernel/Kconfig.freezer"
>> 72
>> 73 menu "Platform dependent setup"
91 74
92 config MAY_HAVE_RUNTIME_DEPS !! 75 config EISA
93 bool 76 bool
>> 77 ---help---
>> 78 The Extended Industry Standard Architecture (EISA) bus was
>> 79 developed as an open alternative to the IBM MicroChannel bus.
94 80
95 config STATIC_LINK !! 81 The EISA bus provided some of the features of the IBM MicroChannel
96 bool "Force a static link" !! 82 bus while maintaining backward compatibility with cards made for
97 depends on CC_CAN_LINK_STATIC_NO_RUNTI !! 83 the older ISA bus. The EISA bus saw limited use between 1988 and
>> 84 1995 when it was made obsolete by the PCI bus.
>> 85
>> 86 Say Y here if you are building a kernel for an EISA-based machine.
>> 87
>> 88 Otherwise, say N.
>> 89
>> 90 config MCA
>> 91 bool
>> 92 help
>> 93 MicroChannel Architecture is found in some IBM PS/2 machines and
>> 94 laptops. It is a bus system similar to PCI or ISA. See
>> 95 <file:Documentation/mca.txt> (and especially the web page given
>> 96 there) before attempting to build an MCA bus kernel.
>> 97
>> 98 config PCMCIA
>> 99 tristate
>> 100 ---help---
>> 101 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
>> 102 computer. These are credit-card size devices such as network cards,
>> 103 modems or hard drives often used with laptops computers. There are
>> 104 actually two varieties of these cards: the older 16 bit PCMCIA cards
>> 105 and the newer 32 bit CardBus cards. If you want to use CardBus
>> 106 cards, you need to say Y here and also to "CardBus support" below.
>> 107
>> 108 To use your PC-cards, you will need supporting software from David
>> 109 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
>> 110 for location). Please also read the PCMCIA-HOWTO, available from
>> 111 <http://www.tldp.org/docs.html#howto>.
>> 112
>> 113 To compile this driver as modules, choose M here: the
>> 114 modules will be called pcmcia_core and ds.
>> 115
>> 116 config AMIGA
>> 117 bool "Amiga support"
>> 118 select MMU_MOTOROLA if MMU
>> 119 help
>> 120 This option enables support for the Amiga series of computers. If
>> 121 you plan to use this kernel on an Amiga, say Y here and browse the
>> 122 material available in <file:Documentation/m68k>; otherwise say N.
>> 123
>> 124 config ATARI
>> 125 bool "Atari support"
>> 126 select MMU_MOTOROLA if MMU
98 help 127 help
99 This option gives you the ability to !! 128 This option enables support for the 68000-based Atari series of
100 Normally, UML is linked as a shared !! 129 computers (including the TT, Falcon and Medusa). If you plan to use
101 use in a chroot jail. So, if you in !! 130 this kernel on an Atari, say Y here and browse the material
102 you probably want to say Y here. !! 131 available in <file:Documentation/m68k>; otherwise say N.
103 Additionally, this option enables us !! 132
104 2.75G) for UML. !! 133 config MAC
>> 134 bool "Macintosh support"
>> 135 select MMU_MOTOROLA if MMU
>> 136 help
>> 137 This option enables support for the Apple Macintosh series of
>> 138 computers (yes, there is experimental support now, at least for part
>> 139 of the series).
105 140
106 NOTE: This option is incompatible wi !! 141 Say N unless you're willing to code the remaining necessary support.
107 depend on features that require bein !! 142 ;)
108 143
109 config LD_SCRIPT_STATIC !! 144 config NUBUS
110 bool 145 bool
>> 146 depends on MAC
111 default y 147 default y
112 depends on STATIC_LINK <<
113 148
114 config LD_SCRIPT_DYN !! 149 config M68K_L2_CACHE
115 bool 150 bool
>> 151 depends on MAC
116 default y 152 default y
117 depends on !LD_SCRIPT_STATIC <<
118 153
119 config LD_SCRIPT_DYN_RPATH !! 154 config APOLLO
120 bool "set rpath in the binary" if EXPE !! 155 bool "Apollo support"
>> 156 select MMU_MOTOROLA if MMU
>> 157 help
>> 158 Say Y here if you want to run Linux on an MC680x0-based Apollo
>> 159 Domain workstation such as the DN3500.
>> 160
>> 161 config VME
>> 162 bool "VME (Motorola and BVM) support"
>> 163 select MMU_MOTOROLA if MMU
>> 164 help
>> 165 Say Y here if you want to build a kernel for a 680x0 based VME
>> 166 board. Boards currently supported include Motorola boards MVME147,
>> 167 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
>> 168 BVME6000 boards from BVM Ltd are also supported.
>> 169
>> 170 config MVME147
>> 171 bool "MVME147 support"
>> 172 depends on VME
>> 173 help
>> 174 Say Y to include support for early Motorola VME boards. This will
>> 175 build a kernel which can run on MVME147 single-board computers. If
>> 176 you select this option you will have to select the appropriate
>> 177 drivers for SCSI, Ethernet and serial ports later on.
>> 178
>> 179 config MVME16x
>> 180 bool "MVME162, 166 and 167 support"
>> 181 depends on VME
>> 182 help
>> 183 Say Y to include support for Motorola VME boards. This will build a
>> 184 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
>> 185 MVME177 boards. If you select this option you will have to select
>> 186 the appropriate drivers for SCSI, Ethernet and serial ports later
>> 187 on.
>> 188
>> 189 config BVME6000
>> 190 bool "BVME4000 and BVME6000 support"
>> 191 depends on VME
>> 192 help
>> 193 Say Y to include support for VME boards from BVM Ltd. This will
>> 194 build a kernel which can run on BVME4000 and BVME6000 boards. If
>> 195 you select this option you will have to select the appropriate
>> 196 drivers for SCSI, Ethernet and serial ports later on.
>> 197
>> 198 config HP300
>> 199 bool "HP9000/300 and HP9000/400 support"
>> 200 select MMU_MOTOROLA if MMU
>> 201 help
>> 202 This option enables support for the HP9000/300 and HP9000/400 series
>> 203 of workstations. Support for these machines is still somewhat
>> 204 experimental. If you plan to try to use the kernel on such a machine
>> 205 say Y here.
>> 206 Everybody else says N.
>> 207
>> 208 config DIO
>> 209 bool "DIO bus support"
>> 210 depends on HP300
121 default y 211 default y
122 depends on LD_SCRIPT_DYN <<
123 help 212 help
124 Add /lib (and /lib64 for 64-bit) to !! 213 Say Y here to enable support for the "DIO" expansion bus used in
125 explicitly. !! 214 HP300 machines. If you are using such a system you almost certainly
>> 215 want this.
>> 216
>> 217 config SUN3X
>> 218 bool "Sun3x support"
>> 219 select MMU_MOTOROLA if MMU
>> 220 select M68030
>> 221 help
>> 222 This option enables support for the Sun 3x series of workstations.
>> 223 Be warned that this support is very experimental.
>> 224 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
>> 225 General Linux information on the Sun 3x series (now discontinued)
>> 226 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
>> 227
>> 228 If you don't want to compile a kernel for a Sun 3x, say N.
>> 229
>> 230 config Q40
>> 231 bool "Q40/Q60 support"
>> 232 select MMU_MOTOROLA if MMU
>> 233 help
>> 234 The Q40 is a Motorola 68040-based successor to the Sinclair QL
>> 235 manufactured in Germany. There is an official Q40 home page at
>> 236 <http://www.q40.de/>. This option enables support for the Q40 and
>> 237 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
>> 238 emulation.
>> 239
>> 240 config SUN3
>> 241 bool "Sun3 support"
>> 242 depends on !MMU_MOTOROLA
>> 243 select MMU_SUN3 if MMU
>> 244 select M68020
>> 245 help
>> 246 This option enables support for the Sun 3 series of workstations
>> 247 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
>> 248 that all other hardware types must be disabled, as Sun 3 kernels
>> 249 are incompatible with all other m68k targets (including Sun 3x!).
>> 250
>> 251 If you don't want to compile a kernel exclusively for a Sun 3, say N.
126 252
127 You may need to turn this off if com !! 253 comment "Processor type"
128 that have their libraries in random <<
129 might otherwise unexpected use libra <<
130 instead of the desired ones. <<
131 254
132 config HOSTFS !! 255 config M68020
133 tristate "Host filesystem" !! 256 bool "68020 support"
>> 257 help
>> 258 If you anticipate running this kernel on a computer with a MC68020
>> 259 processor, say Y. Otherwise, say N. Note that the 68020 requires a
>> 260 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
>> 261 Sun 3, which provides its own version.
>> 262
>> 263 config M68030
>> 264 bool "68030 support"
>> 265 depends on !MMU_SUN3
134 help 266 help
135 While the User-Mode Linux port uses !! 267 If you anticipate running this kernel on a computer with a MC68030
136 booting and normal file access, this !! 268 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
137 access files stored on the host. It !! 269 work, as it does not include an MMU (Memory Management Unit).
138 network connection between the Host !! 270
139 this might be: !! 271 config M68040
>> 272 bool "68040 support"
>> 273 depends on !MMU_SUN3
>> 274 help
>> 275 If you anticipate running this kernel on a computer with a MC68LC040
>> 276 or MC68040 processor, say Y. Otherwise, say N. Note that an
>> 277 MC68EC040 will not work, as it does not include an MMU (Memory
>> 278 Management Unit).
>> 279
>> 280 config M68060
>> 281 bool "68060 support"
>> 282 depends on !MMU_SUN3
>> 283 help
>> 284 If you anticipate running this kernel on a computer with a MC68060
>> 285 processor, say Y. Otherwise, say N.
>> 286
>> 287 config MMU_MOTOROLA
>> 288 bool
>> 289
>> 290 config MMU_SUN3
>> 291 bool
>> 292 depends on MMU && !MMU_MOTOROLA
>> 293
>> 294 config M68KFPU_EMU
>> 295 bool "Math emulation support (EXPERIMENTAL)"
>> 296 depends on EXPERIMENTAL
>> 297 help
>> 298 At some point in the future, this will cause floating-point math
>> 299 instructions to be emulated by the kernel on machines that lack a
>> 300 floating-point math coprocessor. Thrill-seekers and chronically
>> 301 sleep-deprived psychotic hacker types can say Y now, everyone else
>> 302 should probably wait a while.
>> 303
>> 304 config M68KFPU_EMU_EXTRAPREC
>> 305 bool "Math emulation extra precision"
>> 306 depends on M68KFPU_EMU
>> 307 help
>> 308 The fpu uses normally a few bit more during calculations for
>> 309 correct rounding, the emulator can (often) do the same but this
>> 310 extra calculation can cost quite some time, so you can disable
>> 311 it here. The emulator will then "only" calculate with a 64 bit
>> 312 mantissa and round slightly incorrect, what is more than enough
>> 313 for normal usage.
>> 314
>> 315 config M68KFPU_EMU_ONLY
>> 316 bool "Math emulation only kernel"
>> 317 depends on M68KFPU_EMU
>> 318 help
>> 319 This option prevents any floating-point instructions from being
>> 320 compiled into the kernel, thereby the kernel doesn't save any
>> 321 floating point context anymore during task switches, so this
>> 322 kernel will only be usable on machines without a floating-point
>> 323 math coprocessor. This makes the kernel a bit faster as no tests
>> 324 needs to be executed whether a floating-point instruction in the
>> 325 kernel should be executed or not.
>> 326
>> 327 config ADVANCED
>> 328 bool "Advanced configuration options"
>> 329 ---help---
>> 330 This gives you access to some advanced options for the CPU. The
>> 331 defaults should be fine for most users, but these options may make
>> 332 it possible for you to improve performance somewhat if you know what
>> 333 you are doing.
>> 334
>> 335 Note that the answer to this question won't directly affect the
>> 336 kernel: saying N will just cause the configurator to skip all
>> 337 the questions about these options.
>> 338
>> 339 Most users should say N to this question.
>> 340
>> 341 config RMW_INSNS
>> 342 bool "Use read-modify-write instructions"
>> 343 depends on ADVANCED
>> 344 ---help---
>> 345 This allows to use certain instructions that work with indivisible
>> 346 read-modify-write bus cycles. While this is faster than the
>> 347 workaround of disabling interrupts, it can conflict with DMA
>> 348 ( = direct memory access) on many Amiga systems, and it is also said
>> 349 to destabilize other machines. It is very likely that this will
>> 350 cause serious problems on any Amiga or Atari Medusa if set. The only
>> 351 configuration where it should work are 68030-based Ataris, where it
>> 352 apparently improves performance. But you've been warned! Unless you
>> 353 really know what you are doing, say N. Try Y only if you're quite
>> 354 adventurous.
>> 355
>> 356 config SINGLE_MEMORY_CHUNK
>> 357 bool "Use one physical chunk of memory only" if ADVANCED && !SUN3
>> 358 default y if SUN3
>> 359 select NEED_MULTIPLE_NODES
>> 360 help
>> 361 Ignore all but the first contiguous chunk of physical memory for VM
>> 362 purposes. This will save a few bytes kernel size and may speed up
>> 363 some operations. Say N if not sure.
>> 364
>> 365 config 060_WRITETHROUGH
>> 366 bool "Use write-through caching for 68060 supervisor accesses"
>> 367 depends on ADVANCED && M68060
>> 368 ---help---
>> 369 The 68060 generally uses copyback caching of recently accessed data.
>> 370 Copyback caching means that memory writes will be held in an on-chip
>> 371 cache and only written back to memory some time later. Saying Y
>> 372 here will force supervisor (kernel) accesses to use writethrough
>> 373 caching. Writethrough caching means that data is written to memory
>> 374 straight away, so that cache and memory data always agree.
>> 375 Writethrough caching is less efficient, but is needed for some
>> 376 drivers on 68060 based systems where the 68060 bus snooping signal
>> 377 is hardwired on. The 53c710 SCSI driver is known to suffer from
>> 378 this problem.
>> 379
>> 380 config ARCH_DISCONTIGMEM_ENABLE
>> 381 def_bool !SINGLE_MEMORY_CHUNK
140 382
141 mount none /tmp/fromhost -t hostfs - !! 383 config NODES_SHIFT
>> 384 int
>> 385 default "3"
>> 386 depends on !SINGLE_MEMORY_CHUNK
>> 387
>> 388 source "mm/Kconfig"
142 389
143 where /tmp/fromhost is an empty dire !! 390 endmenu
144 /tmp/umlshare is a directory on the <<
145 wishes to access. <<
146 391
147 For more information, see !! 392 menu "General setup"
148 <http://user-mode-linux.sourceforge. <<
149 393
150 If you'd like to be able to work wit !! 394 source "fs/Kconfig.binfmt"
151 say Y or M here; otherwise say N. <<
152 395
153 config MCONSOLE !! 396 config ZORRO
154 bool "Management console" !! 397 bool "Amiga Zorro (AutoConfig) bus support"
155 depends on PROC_FS !! 398 depends on AMIGA
>> 399 help
>> 400 This enables support for the Zorro bus in the Amiga. If you have
>> 401 expansion cards in your Amiga that conform to the Amiga
>> 402 AutoConfig(tm) specification, say Y, otherwise N. Note that even
>> 403 expansion cards that do not fit in the Zorro slots but fit in e.g.
>> 404 the CPU slot may fall in this category, so you have to say Y to let
>> 405 Linux use these.
>> 406
>> 407 config AMIGA_PCMCIA
>> 408 bool "Amiga 1200/600 PCMCIA support (EXPERIMENTAL)"
>> 409 depends on AMIGA && EXPERIMENTAL
>> 410 help
>> 411 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
>> 412 600. If you intend to use pcmcia cards say Y; otherwise say N.
>> 413
>> 414 config STRAM_PROC
>> 415 bool "ST-RAM statistics in /proc"
>> 416 depends on ATARI
>> 417 help
>> 418 Say Y here to report ST-RAM usage statistics in /proc/stram.
>> 419
>> 420 config HEARTBEAT
>> 421 bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || MAC ||Q40
>> 422 default y if !AMIGA && !APOLLO && !ATARI && !MAC && !Q40 && HP300
>> 423 help
>> 424 Use the power-on LED on your machine as a load meter. The exact
>> 425 behavior is platform-dependent, but normally the flash frequency is
>> 426 a hyperbolic function of the 5-minute load average.
>> 427
>> 428 # We have a dedicated heartbeat LED. :-)
>> 429 config PROC_HARDWARE
>> 430 bool "/proc/hardware support"
>> 431 help
>> 432 Say Y here to support the /proc/hardware file, which gives you
>> 433 access to information about the machine you're running on,
>> 434 including the model, CPU, MMU, clock speed, BogoMIPS rating,
>> 435 and memory size.
>> 436
>> 437 config ISA
>> 438 bool
>> 439 depends on Q40 || AMIGA_PCMCIA || GG2
156 default y 440 default y
157 help 441 help
158 The user mode linux management conso !! 442 Find out whether you have ISA slots on your motherboard. ISA is the
159 the kernel, somewhat like the i386 S !! 443 name of a bus system, i.e. the way the CPU talks to the other stuff
160 a full-blown operating system runnin !! 444 inside your box. Other bus systems are PCI, EISA, MicroChannel
161 instance, there is much greater flex !! 445 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
162 SysRq mechanism. !! 446 newer boards don't support it. If you have ISA, say Y, otherwise N.
>> 447
>> 448 config GENERIC_ISA_DMA
>> 449 bool
>> 450 depends on Q40 || AMIGA_PCMCIA || GG2
>> 451 default y
>> 452
>> 453 config ZONE_DMA
>> 454 bool
>> 455 default y
>> 456
>> 457 source "drivers/pci/Kconfig"
>> 458
>> 459 source "drivers/zorro/Kconfig"
>> 460
>> 461 endmenu
>> 462
>> 463 source "net/Kconfig"
>> 464
>> 465 source "drivers/Kconfig"
163 466
164 If you answer 'Y' to this option, to !! 467 menu "Character devices"
165 mconsole client (called uml_mconsole <<
166 2.4.5-9um and later (path /tools/mco <<
167 distribution RPM package in 2.4.6 an <<
168 468
169 It is safe to say 'Y' here. !! 469 config ATARI_MFPSER
>> 470 tristate "Atari MFP serial support"
>> 471 depends on ATARI
>> 472 ---help---
>> 473 If you like to use the MFP serial ports ("Modem1", "Serial1") under
>> 474 Linux, say Y. The driver equally supports all kinds of MFP serial
>> 475 ports and automatically detects whether Serial1 is available.
170 476
171 config MAGIC_SYSRQ !! 477 To compile this driver as a module, choose M here.
172 bool "Magic SysRq key" !! 478
173 depends on MCONSOLE !! 479 Note for Falcon users: You also have an MFP port, it's just not
>> 480 wired to the outside... But you could use the port under Linux.
>> 481
>> 482 config ATARI_MIDI
>> 483 tristate "Atari MIDI serial support"
>> 484 depends on ATARI
174 help 485 help
175 If you say Y here, you will have som !! 486 If you want to use your Atari's MIDI port in Linux, say Y.
176 if the system crashes for example du <<
177 will be able to flush the buffer cac <<
178 immediately or dump some status info <<
179 possible requests is provided. <<
180 487
181 This is the feature normally accompl !! 488 To compile this driver as a module, choose M here.
182 while holding SysRq (Alt+PrintScreen <<
183 489
184 On UML, this is accomplished by send !! 490 config ATARI_DSP56K
185 mconsole, followed by the letter for !! 491 tristate "Atari DSP56k support (EXPERIMENTAL)"
>> 492 depends on ATARI && EXPERIMENTAL
>> 493 help
>> 494 If you want to be able to use the DSP56001 in Falcons, say Y. This
>> 495 driver is still experimental, and if you don't know what it is, or
>> 496 if you don't have this processor, just say N.
>> 497
>> 498 To compile this driver as a module, choose M here.
>> 499
>> 500 config AMIGA_BUILTIN_SERIAL
>> 501 tristate "Amiga builtin serial support"
>> 502 depends on AMIGA
>> 503 help
>> 504 If you want to use your Amiga's built-in serial port in Linux,
>> 505 answer Y.
186 506
187 The keys are documented in <file:Doc !! 507 To compile this driver as a module, choose M here.
188 unless you really know what this hac <<
189 508
190 config KERNEL_STACK_ORDER !! 509 config MULTIFACE_III_TTY
191 int "Kernel stack size order" !! 510 tristate "Multiface Card III serial support"
192 default 2 if 64BIT !! 511 depends on AMIGA
193 range 2 10 if 64BIT <<
194 default 1 if !64BIT <<
195 help 512 help
196 This option determines the size of U !! 513 If you want to use a Multiface III card's serial port in Linux,
197 be 1 << order pages. The default is !! 514 answer Y.
198 on UML, in which case, set this to 3 <<
199 It is possible to reduce the stack t <<
200 older (pre-2017) CPUs. It is not rec <<
201 increase in the size of the state wh <<
202 signals. <<
203 515
204 config MMAPPER !! 516 To compile this driver as a module, choose M here.
205 tristate "iomem emulation driver" !! 517
>> 518 config GVPIOEXT
>> 519 tristate "GVP IO-Extender support"
>> 520 depends on PARPORT=n && ZORRO
206 help 521 help
207 This driver allows a host file to be !! 522 If you want to use a GVP IO-Extender serial card in Linux, say Y.
208 UML. !! 523 Otherwise, say N.
209 524
210 config PGTABLE_LEVELS !! 525 config GVPIOEXT_LP
211 int !! 526 tristate "GVP IO-Extender parallel printer support"
212 default 3 if 3_LEVEL_PGTABLES !! 527 depends on GVPIOEXT
213 default 2 !! 528 help
>> 529 Say Y to enable driving a printer from the parallel port on your
>> 530 GVP IO-Extender card, N otherwise.
214 531
215 config UML_TIME_TRAVEL_SUPPORT !! 532 config GVPIOEXT_PLIP
>> 533 tristate "GVP IO-Extender PLIP support"
>> 534 depends on GVPIOEXT
>> 535 help
>> 536 Say Y to enable doing IP over the parallel port on your GVP
>> 537 IO-Extender card, N otherwise.
>> 538
>> 539 config MAC_SCC
>> 540 tristate "Macintosh serial support"
>> 541 depends on MAC
>> 542
>> 543 config MAC_HID
216 bool 544 bool
217 prompt "Support time-travel mode (e.g. !! 545 depends on INPUT_ADBHID
218 # inf-cpu mode is incompatible with th !! 546 default y
219 depends on !RAID6_PQ_BENCHMARK <<
220 depends on !SMP <<
221 help <<
222 Enable this option to support time t <<
223 <<
224 After enabling this option, two mode <<
225 (selected by the kernel command line <<
226 line help for more details. <<
227 <<
228 It is safe to say Y, but you probabl <<
229 <<
230 config KASAN_SHADOW_OFFSET <<
231 hex <<
232 depends on KASAN <<
233 default 0x100000000000 <<
234 help <<
235 This is the offset at which the ~16T <<
236 mapped and used by KASAN for memory <<
237 address that has at least KASAN_SHAD <<
238 by 8) amount of space so that the KA <<
239 with anything. The default is 0x1000 <<
240 set to a large value. On low-memory <<
241 into the immediate of most instructi <<
242 547
243 endmenu !! 548 config HPDCA
>> 549 tristate "HP DCA serial support"
>> 550 depends on DIO && SERIAL_8250
>> 551 help
>> 552 If you want to use the internal "DCA" serial ports on an HP300
>> 553 machine, say Y here.
244 554
245 source "arch/um/drivers/Kconfig" !! 555 config HPAPCI
>> 556 tristate "HP APCI serial support"
>> 557 depends on HP300 && SERIAL_8250 && EXPERIMENTAL
>> 558 help
>> 559 If you want to use the internal "APCI" serial ports on an HP400
>> 560 machine, say Y here.
246 561
247 config ARCH_SUSPEND_POSSIBLE !! 562 config MVME147_SCC
248 def_bool y !! 563 bool "SCC support for MVME147 serial ports"
>> 564 depends on MVME147 && BROKEN
>> 565 help
>> 566 This is the driver for the serial ports on the Motorola MVME147
>> 567 boards. Everyone using one of these boards should say Y here.
>> 568
>> 569 config SERIAL167
>> 570 bool "CD2401 support for MVME166/7 serial ports"
>> 571 depends on MVME16x
>> 572 help
>> 573 This is the driver for the serial ports on the Motorola MVME166,
>> 574 167, and 172 boards. Everyone using one of these boards should say
>> 575 Y here.
>> 576
>> 577 config MVME162_SCC
>> 578 bool "SCC support for MVME162 serial ports"
>> 579 depends on MVME16x && BROKEN
>> 580 help
>> 581 This is the driver for the serial ports on the Motorola MVME162 and
>> 582 172 boards. Everyone using one of these boards should say Y here.
249 583
250 menu "Power management options" !! 584 config BVME6000_SCC
>> 585 bool "SCC support for BVME6000 serial ports"
>> 586 depends on BVME6000 && BROKEN
>> 587 help
>> 588 This is the driver for the serial ports on the BVME4000 and BVME6000
>> 589 boards from BVM Ltd. Everyone using one of these boards should say
>> 590 Y here.
>> 591
>> 592 config DN_SERIAL
>> 593 bool "Support for DN serial port (dummy)"
>> 594 depends on APOLLO
>> 595
>> 596 config SERIAL_CONSOLE
>> 597 bool "Support for serial port console"
>> 598 depends on (AMIGA || ATARI || MAC || SUN3 || SUN3X || VME || APOLLO) && (ATARI_MFPSER=y || ATARI_MIDI=y || MAC_SCC=y || AMIGA_BUILTIN_SERIAL=y || GVPIOEXT=y || MULTIFACE_III_TTY=y || SERIAL=y || MVME147_SCC || SERIAL167 || MVME162_SCC || BVME6000_SCC || DN_SERIAL)
>> 599 ---help---
>> 600 If you say Y here, it will be possible to use a serial port as the
>> 601 system console (the system console is the device which receives all
>> 602 kernel messages and warnings and which allows logins in single user
>> 603 mode). This could be useful if some terminal or printer is connected
>> 604 to that serial port.
>> 605
>> 606 Even if you say Y here, the currently visible virtual console
>> 607 (/dev/tty0) will still be used as the system console by default, but
>> 608 you can alter that using a kernel command line option such as
>> 609 "console=ttyS1". (Try "man bootparam" or see the documentation of
>> 610 your boot loader (lilo or loadlin) about how to pass options to the
>> 611 kernel at boot time.)
>> 612
>> 613 If you don't have a VGA card installed and you say Y here, the
>> 614 kernel will automatically use the first serial line, /dev/ttyS0, as
>> 615 system console.
251 616
252 source "kernel/power/Kconfig" !! 617 If unsure, say N.
253 618
254 endmenu 619 endmenu
>> 620
>> 621 source "fs/Kconfig"
>> 622
>> 623 source "arch/m68k/Kconfig.debug"
>> 624
>> 625 source "security/Kconfig"
>> 626
>> 627 source "crypto/Kconfig"
>> 628
>> 629 source "lib/Kconfig"
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.