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