2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
13 config RWSEM_GENERIC_SPINLOCK
17 config RWSEM_XCHGADD_ALGORITHM
20 config ARCH_HAS_ILOG2_U32
24 config ARCH_HAS_ILOG2_U64
28 config GENERIC_HWEIGHT
32 config GENERIC_CALIBRATE_DELAY
44 config ARCH_MAY_HAVE_PC_FDC
46 depends on Q40 || (BROKEN && SUN3X)
55 config ARCH_SUPPORTS_AOUT
62 mainmenu "Linux/68k Kernel Configuration"
66 menu "Platform dependent setup"
71 The Extended Industry Standard Architecture (EISA) bus was
72 developed as an open alternative to the IBM MicroChannel bus.
74 The EISA bus provided some of the features of the IBM MicroChannel
75 bus while maintaining backward compatibility with cards made for
76 the older ISA bus. The EISA bus saw limited use between 1988 and
77 1995 when it was made obsolete by the PCI bus.
79 Say Y here if you are building a kernel for an EISA-based machine.
86 MicroChannel Architecture is found in some IBM PS/2 machines and
87 laptops. It is a bus system similar to PCI or ISA. See
88 <file:Documentation/mca.txt> (and especially the web page given
89 there) before attempting to build an MCA bus kernel.
94 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
95 computer. These are credit-card size devices such as network cards,
96 modems or hard drives often used with laptops computers. There are
97 actually two varieties of these cards: the older 16 bit PCMCIA cards
98 and the newer 32 bit CardBus cards. If you want to use CardBus
99 cards, you need to say Y here and also to "CardBus support" below.
101 To use your PC-cards, you will need supporting software from David
102 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
103 for location). Please also read the PCMCIA-HOWTO, available from
104 <http://www.tldp.org/docs.html#howto>.
106 To compile this driver as modules, choose M here: the
107 modules will be called pcmcia_core and ds.
112 select MMU_SUN3 if MMU
114 This option enables support for the Sun 3 series of workstations
115 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
116 that all other hardware types must be disabled, as Sun 3 kernels
117 are incompatible with all other m68k targets (including Sun 3x!).
119 If you don't want to compile a kernel exclusively for a Sun 3, say N.
125 This option enables support for the Amiga series of computers. If
126 you plan to use this kernel on an Amiga, say Y here and browse the
127 material available in <file:Documentation/m68k>; otherwise say N.
133 This option enables support for the 68000-based Atari series of
134 computers (including the TT, Falcon and Medusa). If you plan to use
135 this kernel on an Atari, say Y here and browse the material
136 available in <file:Documentation/m68k>; otherwise say N.
140 depends on ATARI && BROKEN
142 This option enables support for the Hades Atari clone. If you plan
143 to use this kernel on a Hades, say Y here; otherwise say N.
150 Find out whether you have a PCI motherboard. PCI is the name of a
151 bus system, i.e. the way the CPU talks to the other stuff inside
152 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
153 VESA. If you have PCI, say Y, otherwise N.
156 bool "Macintosh support"
159 This option enables support for the Apple Macintosh series of
160 computers (yes, there is experimental support now, at least for part
163 Say N unless you're willing to code the remaining necessary support.
177 bool "Apollo support"
180 Say Y here if you want to run Linux on an MC680x0-based Apollo
181 Domain workstation such as the DN3500.
184 bool "VME (Motorola and BVM) support"
187 Say Y here if you want to build a kernel for a 680x0 based VME
188 board. Boards currently supported include Motorola boards MVME147,
189 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
190 BVME6000 boards from BVM Ltd are also supported.
193 bool "MVME147 support"
196 Say Y to include support for early Motorola VME boards. This will
197 build a kernel which can run on MVME147 single-board computers. If
198 you select this option you will have to select the appropriate
199 drivers for SCSI, Ethernet and serial ports later on.
202 bool "MVME162, 166 and 167 support"
205 Say Y to include support for Motorola VME boards. This will build a
206 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
207 MVME177 boards. If you select this option you will have to select
208 the appropriate drivers for SCSI, Ethernet and serial ports later
212 bool "BVME4000 and BVME6000 support"
215 Say Y to include support for VME boards from BVM Ltd. This will
216 build a kernel which can run on BVME4000 and BVME6000 boards. If
217 you select this option you will have to select the appropriate
218 drivers for SCSI, Ethernet and serial ports later on.
221 bool "HP9000/300 and HP9000/400 support"
224 This option enables support for the HP9000/300 and HP9000/400 series
225 of workstations. Support for these machines is still somewhat
226 experimental. If you plan to try to use the kernel on such a machine
228 Everybody else says N.
231 bool "DIO bus support"
235 Say Y here to enable support for the "DIO" expansion bus used in
236 HP300 machines. If you are using such a system you almost certainly
244 This option enables support for the Sun 3x series of workstations.
245 Be warned that this support is very experimental.
246 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
247 General Linux information on the Sun 3x series (now discontinued)
248 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
250 If you don't want to compile a kernel for a Sun 3x, say N.
253 bool "Q40/Q60 support"
256 The Q40 is a Motorola 68040-based successor to the Sinclair QL
257 manufactured in Germany. There is an official Q40 home page at
258 <http://www.q40.de/>. This option enables support for the Q40 and
259 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
262 comment "Processor type"
267 If you anticipate running this kernel on a computer with a MC68020
268 processor, say Y. Otherwise, say N. Note that the 68020 requires a
269 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
270 Sun 3, which provides its own version.
276 If you anticipate running this kernel on a computer with a MC68030
277 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
278 work, as it does not include an MMU (Memory Management Unit).
284 If you anticipate running this kernel on a computer with a MC68LC040
285 or MC68040 processor, say Y. Otherwise, say N. Note that an
286 MC68EC040 will not work, as it does not include an MMU (Memory
293 If you anticipate running this kernel on a computer with a MC68060
294 processor, say Y. Otherwise, say N.
298 depends on MMU && !MMU_SUN3
305 bool "Math emulation support (EXPERIMENTAL)"
306 depends on EXPERIMENTAL
308 At some point in the future, this will cause floating-point math
309 instructions to be emulated by the kernel on machines that lack a
310 floating-point math coprocessor. Thrill-seekers and chronically
311 sleep-deprived psychotic hacker types can say Y now, everyone else
312 should probably wait a while.
314 config M68KFPU_EMU_EXTRAPREC
315 bool "Math emulation extra precision"
316 depends on M68KFPU_EMU
318 The fpu uses normally a few bit more during calculations for
319 correct rounding, the emulator can (often) do the same but this
320 extra calculation can cost quite some time, so you can disable
321 it here. The emulator will then "only" calculate with a 64 bit
322 mantissa and round slightly incorrect, what is more then enough
325 config M68KFPU_EMU_ONLY
326 bool "Math emulation only kernel"
327 depends on M68KFPU_EMU
329 This option prevents any floating-point instructions from being
330 compiled into the kernel, thereby the kernel doesn't save any
331 floating point context anymore during task switches, so this
332 kernel will only be usable on machines without a floating-point
333 math coprocessor. This makes the kernel a bit faster as no tests
334 needs to be executed whether a floating-point instruction in the
335 kernel should be executed or not.
338 bool "Advanced configuration options"
340 This gives you access to some advanced options for the CPU. The
341 defaults should be fine for most users, but these options may make
342 it possible for you to improve performance somewhat if you know what
345 Note that the answer to this question won't directly affect the
346 kernel: saying N will just cause the configurator to skip all
347 the questions about these options.
349 Most users should say N to this question.
352 bool "Use read-modify-write instructions"
355 This allows to use certain instructions that work with indivisible
356 read-modify-write bus cycles. While this is faster than the
357 workaround of disabling interrupts, it can conflict with DMA
358 ( = direct memory access) on many Amiga systems, and it is also said
359 to destabilize other machines. It is very likely that this will
360 cause serious problems on any Amiga or Atari Medusa if set. The only
361 configuration where it should work are 68030-based Ataris, where it
362 apparently improves performance. But you've been warned! Unless you
363 really know what you are doing, say N. Try Y only if you're quite
366 config SINGLE_MEMORY_CHUNK
367 bool "Use one physical chunk of memory only" if ADVANCED && !SUN3
369 select NEED_MULTIPLE_NODES
371 Ignore all but the first contiguous chunk of physical memory for VM
372 purposes. This will save a few bytes kernel size and may speed up
373 some operations. Say N if not sure.
375 config 060_WRITETHROUGH
376 bool "Use write-through caching for 68060 supervisor accesses"
377 depends on ADVANCED && M68060
379 The 68060 generally uses copyback caching of recently accessed data.
380 Copyback caching means that memory writes will be held in an on-chip
381 cache and only written back to memory some time later. Saying Y
382 here will force supervisor (kernel) accesses to use writethrough
383 caching. Writethrough caching means that data is written to memory
384 straight away, so that cache and memory data always agree.
385 Writethrough caching is less efficient, but is needed for some
386 drivers on 68060 based systems where the 68060 bus snooping signal
387 is hardwired on. The 53c710 SCSI driver is known to suffer from
390 config ARCH_DISCONTIGMEM_ENABLE
391 def_bool !SINGLE_MEMORY_CHUNK
396 depends on !SINGLE_MEMORY_CHUNK
404 source "fs/Kconfig.binfmt"
407 bool "Amiga Zorro (AutoConfig) bus support"
410 This enables support for the Zorro bus in the Amiga. If you have
411 expansion cards in your Amiga that conform to the Amiga
412 AutoConfig(tm) specification, say Y, otherwise N. Note that even
413 expansion cards that do not fit in the Zorro slots but fit in e.g.
414 the CPU slot may fall in this category, so you have to say Y to let
418 bool "Amiga 1200/600 PCMCIA support (EXPERIMENTAL)"
419 depends on AMIGA && EXPERIMENTAL
421 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
422 600. If you intend to use pcmcia cards say Y; otherwise say N.
425 bool "ST-RAM statistics in /proc"
428 Say Y here to report ST-RAM usage statistics in /proc/stram.
431 bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || MAC ||Q40
432 default y if !AMIGA && !APOLLO && !ATARI && !MAC && !Q40 && HP300
434 Use the power-on LED on your machine as a load meter. The exact
435 behavior is platform-dependent, but normally the flash frequency is
436 a hyperbolic function of the 5-minute load average.
438 # We have a dedicated heartbeat LED. :-)
440 bool "/proc/hardware support"
442 Say Y here to support the /proc/hardware file, which gives you
443 access to information about the machine you're running on,
444 including the model, CPU, MMU, clock speed, BogoMIPS rating,
449 depends on Q40 || AMIGA_PCMCIA || GG2
452 Find out whether you have ISA slots on your motherboard. ISA is the
453 name of a bus system, i.e. the way the CPU talks to the other stuff
454 inside your box. Other bus systems are PCI, EISA, MicroChannel
455 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
456 newer boards don't support it. If you have ISA, say Y, otherwise N.
458 config GENERIC_ISA_DMA
460 depends on Q40 || AMIGA_PCMCIA || GG2
467 source "drivers/pci/Kconfig"
469 source "drivers/zorro/Kconfig"
475 source "drivers/Kconfig"
477 menu "Character devices"
480 tristate "Atari MFP serial support"
483 If you like to use the MFP serial ports ("Modem1", "Serial1") under
484 Linux, say Y. The driver equally supports all kinds of MFP serial
485 ports and automatically detects whether Serial1 is available.
487 To compile this driver as a module, choose M here.
489 Note for Falcon users: You also have an MFP port, it's just not
490 wired to the outside... But you could use the port under Linux.
493 tristate "Atari SCC serial support"
496 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
497 LAN) and like to use them under Linux, say Y. All built-in SCC's are
498 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
499 two connectors for channel A (Serial2 and LAN), they are visible as
500 two separate devices.
502 To compile this driver as a module, choose M here.
505 bool "Atari SCC serial DMA support"
508 This enables DMA support for receiving data on channel A of the SCC.
509 If you have a TT you may say Y here and read
510 drivers/char/atari_SCC.README. All other users should say N here,
511 because only the TT has SCC-DMA, even if your machine keeps claiming
515 tristate "Atari MIDI serial support"
518 If you want to use your Atari's MIDI port in Linux, say Y.
520 To compile this driver as a module, choose M here.
523 tristate "Atari DSP56k support (EXPERIMENTAL)"
524 depends on ATARI && EXPERIMENTAL
526 If you want to be able to use the DSP56001 in Falcons, say Y. This
527 driver is still experimental, and if you don't know what it is, or
528 if you don't have this processor, just say N.
530 To compile this driver as a module, choose M here.
532 config AMIGA_BUILTIN_SERIAL
533 tristate "Amiga builtin serial support"
536 If you want to use your Amiga's built-in serial port in Linux,
539 To compile this driver as a module, choose M here.
541 config WHIPPET_SERIAL
542 tristate "Hisoft Whippet PCMCIA serial support"
543 depends on AMIGA_PCMCIA
545 HiSoft has a web page at <http://www.hisoft.co.uk/>, but there
546 is no listing for the Whippet in their Amiga section.
548 config MULTIFACE_III_TTY
549 tristate "Multiface Card III serial support"
552 If you want to use a Multiface III card's serial port in Linux,
555 To compile this driver as a module, choose M here.
558 tristate "GVP IO-Extender support"
559 depends on PARPORT=n && ZORRO
561 If you want to use a GVP IO-Extender serial card in Linux, say Y.
565 tristate "GVP IO-Extender parallel printer support"
568 Say Y to enable driving a printer from the parallel port on your
569 GVP IO-Extender card, N otherwise.
572 tristate "GVP IO-Extender PLIP support"
575 Say Y to enable doing IP over the parallel port on your GVP
576 IO-Extender card, N otherwise.
579 tristate "Macintosh serial support"
584 depends on INPUT_ADBHID
588 bool "Support for ADB keyboard (old driver)"
589 depends on MAC && !INPUT_ADBHID
591 This option allows you to use an ADB keyboard attached to your
592 machine. Note that this disables any other (ie. PS/2) keyboard
593 support, even if your machine is physically capable of using both at
596 If you use an ADB keyboard (4 pin connector), say Y here.
597 If you use a PS/2 keyboard (6 pin connector), say N here.
600 tristate "HP DCA serial support"
601 depends on DIO && SERIAL_8250
603 If you want to use the internal "DCA" serial ports on an HP300
607 tristate "HP APCI serial support"
608 depends on HP300 && SERIAL_8250 && EXPERIMENTAL
610 If you want to use the internal "APCI" serial ports on an HP400
614 bool "SCC support for MVME147 serial ports"
617 This is the driver for the serial ports on the Motorola MVME147
618 boards. Everyone using one of these boards should say Y here.
621 bool "CD2401 support for MVME166/7 serial ports"
624 This is the driver for the serial ports on the Motorola MVME166,
625 167, and 172 boards. Everyone using one of these boards should say
629 bool "SCC support for MVME162 serial ports"
632 This is the driver for the serial ports on the Motorola MVME162 and
633 172 boards. Everyone using one of these boards should say Y here.
636 bool "SCC support for BVME6000 serial ports"
639 This is the driver for the serial ports on the BVME4000 and BVME6000
640 boards from BVM Ltd. Everyone using one of these boards should say
644 bool "Support for DN serial port (dummy)"
647 config SERIAL_CONSOLE
648 bool "Support for serial port console"
649 depends on (AMIGA || ATARI || MAC || SUN3 || SUN3X || VME || APOLLO) && (ATARI_MFPSER=y || ATARI_SCC=y || ATARI_MIDI=y || MAC_SCC=y || AMIGA_BUILTIN_SERIAL=y || GVPIOEXT=y || MULTIFACE_III_TTY=y || SERIAL=y || MVME147_SCC || SERIAL167 || MVME162_SCC || BVME6000_SCC || DN_SERIAL)
651 If you say Y here, it will be possible to use a serial port as the
652 system console (the system console is the device which receives all
653 kernel messages and warnings and which allows logins in single user
654 mode). This could be useful if some terminal or printer is connected
657 Even if you say Y here, the currently visible virtual console
658 (/dev/tty0) will still be used as the system console by default, but
659 you can alter that using a kernel command line option such as
660 "console=ttyS1". (Try "man bootparam" or see the documentation of
661 your boot loader (lilo or loadlin) about how to pass options to the
662 kernel at boot time.)
664 If you don't have a VGA card installed and you say Y here, the
665 kernel will automatically use the first serial line, /dev/ttyS0, as
674 source "arch/m68k/Kconfig.debug"
676 source "security/Kconfig"
678 source "crypto/Kconfig"