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