1 # SPDX-License-Identifier: GPL-2.0 <<
2 # 1 #
3 # For a description of the syntax of this conf 2 # For a description of the syntax of this configuration file,
4 # see Documentation/kbuild/kconfig-language.rs !! 3 # see Documentation/kbuild/kconfig-language.txt.
5 # 4 #
>> 5 config M68K
>> 6 bool
>> 7 default y
>> 8 select HAVE_AOUT
>> 9 select HAVE_IDE
6 10
7 config OPENRISC !! 11 config MMU
8 def_bool y !! 12 bool
9 select ARCH_32BIT_OFF_T !! 13 default y
10 select ARCH_HAS_DMA_SET_UNCACHED <<
11 select ARCH_HAS_DMA_CLEAR_UNCACHED <<
12 select ARCH_HAS_SYNC_DMA_FOR_DEVICE <<
13 select COMMON_CLK <<
14 select OF <<
15 select OF_EARLY_FLATTREE <<
16 select IRQ_DOMAIN <<
17 select GPIOLIB <<
18 select HAVE_ARCH_TRACEHOOK <<
19 select SPARSE_IRQ <<
20 select GENERIC_IRQ_CHIP <<
21 select GENERIC_IRQ_PROBE <<
22 select GENERIC_IRQ_SHOW <<
23 select GENERIC_PCI_IOMAP <<
24 select GENERIC_IOREMAP <<
25 select GENERIC_CPU_DEVICES <<
26 select HAVE_PCI <<
27 select HAVE_UID16 <<
28 select HAVE_PAGE_SIZE_8KB <<
29 select GENERIC_ATOMIC64 <<
30 select GENERIC_CLOCKEVENTS_BROADCAST <<
31 select GENERIC_SMP_IDLE_THREAD <<
32 select MODULES_USE_ELF_RELA <<
33 select HAVE_DEBUG_STACKOVERFLOW <<
34 select OR1K_PIC <<
35 select CPU_NO_EFFICIENT_FFS if !OPENRI <<
36 select ARCH_USE_QUEUED_RWLOCKS <<
37 select OMPIC if SMP <<
38 select PCI_DOMAINS_GENERIC if PCI <<
39 select PCI_MSI if PCI <<
40 select ARCH_WANT_FRAME_POINTERS <<
41 select GENERIC_IRQ_MULTI_HANDLER <<
42 select MMU_GATHER_NO_RANGE if MMU <<
43 select TRACE_IRQFLAGS_SUPPORT <<
44 14
45 config CPU_BIG_ENDIAN !! 15 config RWSEM_GENERIC_SPINLOCK
46 def_bool y !! 16 bool
>> 17 default y
47 18
48 config MMU !! 19 config RWSEM_XCHGADD_ALGORITHM
49 def_bool y !! 20 bool
>> 21
>> 22 config ARCH_HAS_ILOG2_U32
>> 23 bool
>> 24 default n
>> 25
>> 26 config ARCH_HAS_ILOG2_U64
>> 27 bool
>> 28 default n
50 29
51 config GENERIC_HWEIGHT 30 config GENERIC_HWEIGHT
52 def_bool y !! 31 bool
>> 32 default y
53 33
54 config NO_IOPORT_MAP !! 34 config GENERIC_CALIBRATE_DELAY
55 def_bool y !! 35 bool
>> 36 default y
56 37
57 # For now, use generic checksum functions !! 38 config TIME_LOW_RES
58 #These can be reimplemented in assembly later !! 39 bool
59 config GENERIC_CSUM !! 40 default y
60 def_bool y <<
61 41
62 config STACKTRACE_SUPPORT !! 42 config GENERIC_IOMAP
63 def_bool y !! 43 bool
>> 44 default y
64 45
65 config LOCKDEP_SUPPORT !! 46 config ARCH_MAY_HAVE_PC_FDC
66 def_bool y !! 47 bool
>> 48 depends on BROKEN && (Q40 || SUN3X)
>> 49 default y
67 50
68 menu "Processor type and features" !! 51 config NO_IOPORT
>> 52 def_bool y
69 53
70 choice !! 54 config NO_DMA
71 prompt "Subarchitecture" !! 55 def_bool SUN3
72 default OR1K_1200 <<
73 56
74 config OR1K_1200 !! 57 config HZ
75 bool "OR1200" !! 58 int
76 help !! 59 default 100
77 Generic OpenRISC 1200 architecture <<
78 60
79 endchoice !! 61 config GENERIC_TIME
>> 62 def_bool y
80 63
81 config DCACHE_WRITETHROUGH !! 64 config ARCH_USES_GETTIMEOFFSET
82 bool "Have write through data caches" !! 65 def_bool y
83 default n <<
84 help <<
85 Select this if your implementation f <<
86 Selecting 'N' here will allow the ke <<
87 caches at relevant times. Most OpenR <<
88 through data caches. <<
89 66
90 If unsure say N here !! 67 mainmenu "Linux/68k Kernel Configuration"
91 68
92 config OPENRISC_BUILTIN_DTB !! 69 source "init/Kconfig"
93 string "Builtin DTB" <<
94 default "" <<
95 70
96 menu "Class II Instructions" !! 71 source "kernel/Kconfig.freezer"
97 72
98 config OPENRISC_HAVE_INST_FF1 !! 73 menu "Platform dependent setup"
99 bool "Have instruction l.ff1" <<
100 default y <<
101 help <<
102 Select this if your implementation h <<
103 74
104 config OPENRISC_HAVE_INST_FL1 !! 75 config EISA
105 bool "Have instruction l.fl1" !! 76 bool
>> 77 ---help---
>> 78 The Extended Industry Standard Architecture (EISA) bus was
>> 79 developed as an open alternative to the IBM MicroChannel bus.
>> 80
>> 81 The EISA bus provided some of the features of the IBM MicroChannel
>> 82 bus while maintaining backward compatibility with cards made for
>> 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
>> 127 help
>> 128 This option enables support for the 68000-based Atari series of
>> 129 computers (including the TT, Falcon and Medusa). If you plan to use
>> 130 this kernel on an Atari, say Y here and browse the material
>> 131 available in <file:Documentation/m68k>; otherwise say N.
>> 132
>> 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).
>> 140
>> 141 Say N unless you're willing to code the remaining necessary support.
>> 142 ;)
>> 143
>> 144 config NUBUS
>> 145 bool
>> 146 depends on MAC
106 default y 147 default y
107 help <<
108 Select this if your implementation h <<
109 148
110 config OPENRISC_HAVE_INST_MUL !! 149 config M68K_L2_CACHE
111 bool "Have instruction l.mul for hardw !! 150 bool
>> 151 depends on MAC
112 default y 152 default y
113 help <<
114 Select this if your implementation h <<
115 153
116 config OPENRISC_HAVE_INST_DIV !! 154 config APOLLO
117 bool "Have instruction l.div for hardw !! 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
118 default y 211 default y
119 help 212 help
120 Select this if your implementation h !! 213 Say Y here to enable support for the "DIO" expansion bus used in
>> 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.
>> 252
>> 253 comment "Processor type"
>> 254
>> 255 config M68020
>> 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
>> 266 help
>> 267 If you anticipate running this kernel on a computer with a MC68030
>> 268 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
>> 269 work, as it does not include an MMU (Memory Management Unit).
>> 270
>> 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
>> 382
>> 383 config NODES_SHIFT
>> 384 int
>> 385 default "3"
>> 386 depends on !SINGLE_MEMORY_CHUNK
121 387
122 config OPENRISC_HAVE_INST_CMOV !! 388 source "mm/Kconfig"
123 bool "Have instruction l.cmov for cond !! 389
124 default n !! 390 endmenu
125 help <<
126 This config enables gcc to generate <<
127 the kernel which in general will imp <<
128 binary size. <<
129 391
130 Select this if your implementation h !! 392 menu "General setup"
131 l.cmov conistional move instruction. <<
132 393
133 Say N if you are unsure. !! 394 source "fs/Kconfig.binfmt"
134 395
135 config OPENRISC_HAVE_INST_ROR !! 396 config ZORRO
136 bool "Have instruction l.ror for rotat !! 397 bool "Amiga Zorro (AutoConfig) bus support"
137 default n !! 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
>> 440 default y
138 help 441 help
139 This config enables gcc to generate !! 442 Find out whether you have ISA slots on your motherboard. ISA is the
140 the kernel which in general will imp !! 443 name of a bus system, i.e. the way the CPU talks to the other stuff
141 binary size. !! 444 inside your box. Other bus systems are PCI, EISA, MicroChannel
>> 445 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
>> 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
142 452
143 Select this if your implementation h !! 453 config ZONE_DMA
144 l.ror rotate right instruction. !! 454 bool
>> 455 default y
145 456
146 Say N if you are unsure. !! 457 source "drivers/pci/Kconfig"
147 458
148 config OPENRISC_HAVE_INST_RORI !! 459 source "drivers/zorro/Kconfig"
149 bool "Have instruction l.rori for rota <<
150 default n <<
151 help <<
152 This config enables gcc to generate <<
153 the kernel which in general will imp <<
154 binary size. <<
155 460
156 Select this if your implementation h !! 461 endmenu
157 l.rori rotate right with immediate i <<
158 462
159 Say N if you are unsure. !! 463 source "net/Kconfig"
160 464
161 config OPENRISC_HAVE_INST_SEXT !! 465 source "drivers/Kconfig"
162 bool "Have instructions l.ext* for sig <<
163 default n <<
164 help <<
165 This config enables gcc to generate <<
166 the kernel which in general will imp <<
167 binary size. <<
168 466
169 Select this if your implementation h !! 467 menu "Character devices"
170 l.exths, l.extbs, l.exthz and l.extb <<
171 468
172 Say N if you are unsure. !! 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.
173 476
174 endmenu !! 477 To compile this driver as a module, choose M here.
175 478
176 config NR_CPUS !! 479 Note for Falcon users: You also have an MFP port, it's just not
177 int "Maximum number of CPUs (2-32)" !! 480 wired to the outside... But you could use the port under Linux.
178 range 2 32 <<
179 depends on SMP <<
180 default "2" <<
181 481
182 config SMP !! 482 config ATARI_MIDI
183 bool "Symmetric Multi-Processing suppo !! 483 tristate "Atari MIDI serial support"
>> 484 depends on ATARI
184 help 485 help
185 This enables support for systems wit !! 486 If you want to use your Atari's MIDI port in Linux, say Y.
186 a system with only one CPU, say N. I <<
187 than one CPU, say Y. <<
188 487
189 If you don't know what to do here, s !! 488 To compile this driver as a module, choose M here.
190 489
191 config FPU !! 490 config ATARI_DSP56K
192 bool "FPU support" !! 491 tristate "Atari DSP56k support (EXPERIMENTAL)"
193 default y !! 492 depends on ATARI && EXPERIMENTAL
194 help 493 help
195 Say N here if you want to disable al !! 494 If you want to be able to use the DSP56001 in Falcons, say Y. This
196 in the kernel and reduce binary size !! 495 driver is still experimental, and if you don't know what it is, or
197 !! 496 if you don't have this processor, just say N.
198 If you don't know what to do here, s <<
199 497
200 source "kernel/Kconfig.hz" !! 498 To compile this driver as a module, choose M here.
201 499
202 config OPENRISC_NO_SPR_SR_DSX !! 500 config AMIGA_BUILTIN_SERIAL
203 bool "use SPR_SR_DSX software emulatio !! 501 tristate "Amiga builtin serial support"
204 default y !! 502 depends on AMIGA
205 help 503 help
206 SPR_SR_DSX bit is status register bi !! 504 If you want to use your Amiga's built-in serial port in Linux,
207 the last exception has happened in d !! 505 answer Y.
208 <<
209 OpenRISC architecture makes it optio <<
210 in hardware and the OR1200 does not <<
211 506
212 Say N here if you know that your Ope !! 507 To compile this driver as a module, choose M here.
213 SPR_SR_DSX bit implemented. Say Y if <<
214 508
215 config OPENRISC_HAVE_SHADOW_GPRS !! 509 config MULTIFACE_III_TTY
216 bool "Support for shadow gpr files" if !! 510 tristate "Multiface Card III serial support"
217 default y if SMP !! 511 depends on AMIGA
218 help 512 help
219 Say Y here if your OpenRISC processo !! 513 If you want to use a Multiface III card's serial port in Linux,
220 register files. They will in such ca !! 514 answer Y.
221 scratch reg storage on exception ent <<
222 515
223 On SMP systems, this feature is mand !! 516 To compile this driver as a module, choose M here.
224 On a unicore system it's safe to say <<
225 517
226 config CMDLINE !! 518 config GVPIOEXT
227 string "Default kernel command string" !! 519 tristate "GVP IO-Extender support"
228 default "" !! 520 depends on PARPORT=n && ZORRO
229 help 521 help
230 On some architectures there is curre !! 522 If you want to use a GVP IO-Extender serial card in Linux, say Y.
231 to pass arguments to the kernel. For !! 523 Otherwise, say N.
232 supply some command-line options at <<
233 here. <<
234 524
235 menu "Debugging options" !! 525 config GVPIOEXT_LP
>> 526 tristate "GVP IO-Extender parallel printer support"
>> 527 depends on GVPIOEXT
>> 528 help
>> 529 Say Y to enable driving a printer from the parallel port on your
>> 530 GVP IO-Extender card, N otherwise.
236 531
237 config JUMP_UPON_UNHANDLED_EXCEPTION !! 532 config GVPIOEXT_PLIP
238 bool "Try to die gracefully" !! 533 tristate "GVP IO-Extender PLIP support"
239 default y !! 534 depends on GVPIOEXT
240 help 535 help
241 Now this puts kernel into infinite l !! 536 Say Y to enable doing IP over the parallel port on your GVP
242 your kernel crashes this doesn't hav !! 537 IO-Extender card, N otherwise.
243 538
244 Say Y if you are unsure. !! 539 config MAC_SCC
>> 540 tristate "Macintosh serial support"
>> 541 depends on MAC
245 542
246 config OPENRISC_ESR_EXCEPTION_BUG_CHECK !! 543 config MAC_HID
247 bool "Check for possible ESR exception !! 544 bool
248 default n !! 545 depends on INPUT_ADBHID
249 help !! 546 default y
250 This option enables some checks that <<
251 in kernel. <<
252 547
253 Say N if you are unsure. !! 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.
>> 554
>> 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.
>> 561
>> 562 config MVME147_SCC
>> 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.
>> 583
>> 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.
254 616
255 endmenu !! 617 If unsure, say N.
256 618
257 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.