2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
17 config RWSEM_GENERIC_SPINLOCK
21 config RWSEM_XCHGADD_ALGORITHM
24 mainmenu "Linux/68k Kernel Configuration"
28 menu "Platform dependent setup"
33 The Extended Industry Standard Architecture (EISA) bus was
34 developed as an open alternative to the IBM MicroChannel bus.
36 The EISA bus provided some of the features of the IBM MicroChannel
37 bus while maintaining backward compatibility with cards made for
38 the older ISA bus. The EISA bus saw limited use between 1988 and
39 1995 when it was made obsolete by the PCI bus.
41 Say Y here if you are building a kernel for an EISA-based machine.
48 MicroChannel Architecture is found in some IBM PS/2 machines and
49 laptops. It is a bus system similar to PCI or ISA. See
50 <file:Documentation/mca.txt> (and especially the web page given
51 there) before attempting to build an MCA bus kernel.
56 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
57 computer. These are credit-card size devices such as network cards,
58 modems or hard drives often used with laptops computers. There are
59 actually two varieties of these cards: the older 16 bit PCMCIA cards
60 and the newer 32 bit CardBus cards. If you want to use CardBus
61 cards, you need to say Y here and also to "CardBus support" below.
63 To use your PC-cards, you will need supporting software from David
64 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
65 for location). Please also read the PCMCIA-HOWTO, available from
66 <http://www.tldp.org/docs.html#howto>.
68 To compile this driver as modules, choose M here: the
69 modules will be called pcmcia_core and ds.
74 select MMU_SUN3 if MMU
76 This option enables support for the Sun 3 series of workstations
77 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
78 that all other hardware types must be disabled, as Sun 3 kernels
79 are incompatible with all other m68k targets (including Sun 3x!).
81 If you don't want to compile a kernel exclusively for a Sun 3, say N.
87 This option enables support for the Amiga series of computers. If
88 you plan to use this kernel on an Amiga, say Y here and browse the
89 material available in <file:Documentation/m68k>; otherwise say N.
95 This option enables support for the 68000-based Atari series of
96 computers (including the TT, Falcon and Medusa). If you plan to use
97 this kernel on an Atari, say Y here and browse the material
98 available in <file:Documentation/m68k>; otherwise say N.
102 depends on ATARI && BROKEN
104 This option enables support for the Hades Atari clone. If you plan
105 to use this kernel on a Hades, say Y here; otherwise say N.
112 Find out whether you have a PCI motherboard. PCI is the name of a
113 bus system, i.e. the way the CPU talks to the other stuff inside
114 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
115 VESA. If you have PCI, say Y, otherwise N.
117 The PCI-HOWTO, available from
118 <http://www.tldp.org/docs.html#howto>, contains valuable
119 information about which PCI hardware does work under Linux and which
123 bool "Macintosh support"
126 This option enables support for the Apple Macintosh series of
127 computers (yes, there is experimental support now, at least for part
130 Say N unless you're willing to code the remaining necessary support.
144 bool "Apollo support"
147 Say Y here if you want to run Linux on an MC680x0-based Apollo
148 Domain workstation such as the DN3500.
151 bool "VME (Motorola and BVM) support"
154 Say Y here if you want to build a kernel for a 680x0 based VME
155 board. Boards currently supported include Motorola boards MVME147,
156 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
157 BVME6000 boards from BVM Ltd are also supported.
160 bool "MVME147 support"
163 Say Y to include support for early Motorola VME boards. This will
164 build a kernel which can run on MVME147 single-board computers. If
165 you select this option you will have to select the appropriate
166 drivers for SCSI, Ethernet and serial ports later on.
169 bool "MVME162, 166 and 167 support"
172 Say Y to include support for Motorola VME boards. This will build a
173 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
174 MVME177 boards. If you select this option you will have to select
175 the appropriate drivers for SCSI, Ethernet and serial ports later
179 bool "BVME4000 and BVME6000 support"
182 Say Y to include support for VME boards from BVM Ltd. This will
183 build a kernel which can run on BVME4000 and BVME6000 boards. If
184 you select this option you will have to select the appropriate
185 drivers for SCSI, Ethernet and serial ports later on.
188 bool "HP9000/300 support"
191 This option enables support for the HP9000/300 series of
192 workstations. Support for these machines is still very experimental.
193 If you plan to try to use the kernel on such a machine say Y here.
194 Everybody else says N.
197 bool "DIO bus support"
200 Say Y here to enable support for the "DIO" expansion bus used in
201 HP300 machines. If you are using such a system you almost certainly
209 This option enables support for the Sun 3x series of workstations.
210 Be warned that this support is very experimental.
211 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
212 General Linux information on the Sun 3x series (now discontinued)
213 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
215 If you don't want to compile a kernel for a Sun 3x, say N.
218 bool "Q40/Q60 support"
221 The Q40 is a Motorola 68040-based successor to the Sinclair QL
222 manufactured in Germany. There is an official Q40 home page at
223 <http://www.q40.de/>. This option enables support for the Q40 and
224 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
227 comment "Processor type"
232 If you anticipate running this kernel on a computer with a MC68020
233 processor, say Y. Otherwise, say N. Note that the 68020 requires a
234 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
235 Sun 3, which provides its own version.
241 If you anticipate running this kernel on a computer with a MC68030
242 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
243 work, as it does not include an MMU (Memory Management Unit).
249 If you anticipate running this kernel on a computer with a MC68LC040
250 or MC68040 processor, say Y. Otherwise, say N. Note that an
251 MC68EC040 will not work, as it does not include an MMU (Memory
258 If you anticipate running this kernel on a computer with a MC68060
259 processor, say Y. Otherwise, say N.
263 depends on MMU && !MMU_SUN3
270 bool "Math emulation support (EXPERIMENTAL)"
271 depends on EXPERIMENTAL
273 At some point in the future, this will cause floating-point math
274 instructions to be emulated by the kernel on machines that lack a
275 floating-point math coprocessor. Thrill-seekers and chronically
276 sleep-deprived psychotic hacker types can say Y now, everyone else
277 should probably wait a while.
279 config M68KFPU_EMU_EXTRAPREC
280 bool "Math emulation extra precision"
281 depends on M68KFPU_EMU
283 The fpu uses normally a few bit more during calculations for
284 correct rounding, the emulator can (often) do the same but this
285 extra calculation can cost quite some time, so you can disable
286 it here. The emulator will then "only" calculate with a 64 bit
287 mantissa and round slightly incorrect, what is more then enough
290 config M68KFPU_EMU_ONLY
291 bool "Math emulation only kernel"
292 depends on M68KFPU_EMU
294 This option prevents any floating-point instructions from being
295 compiled into the kernel, thereby the kernel doesn't save any
296 floating point context anymore during task switches, so this
297 kernel will only be usable on machines without a floating-point
298 math coprocessor. This makes the kernel a bit faster as no tests
299 needs to be executed whether a floating-point instruction in the
300 kernel should be executed or not.
303 bool "Advanced configuration options"
305 This gives you access to some advanced options for the CPU. The
306 defaults should be fine for most users, but these options may make
307 it possible for you to improve performance somewhat if you know what
310 Note that the answer to this question won't directly affect the
311 kernel: saying N will just cause the configurator to skip all
312 the questions about these options.
314 Most users should say N to this question.
317 bool "Use read-modify-write instructions"
320 This allows to use certain instructions that work with indivisible
321 read-modify-write bus cycles. While this is faster than the
322 workaround of disabling interrupts, it can conflict with DMA
323 ( = direct memory access) on many Amiga systems, and it is also said
324 to destabilize other machines. It is very likely that this will
325 cause serious problems on any Amiga or Atari Medusa if set. The only
326 configuration where it should work are 68030-based Ataris, where it
327 apparently improves performance. But you've been warned! Unless you
328 really know what you are doing, say N. Try Y only if you're quite
331 config SINGLE_MEMORY_CHUNK
332 bool "Use one physical chunk of memory only"
333 depends on ADVANCED && !SUN3
335 Ignore all but the first contiguous chunk of physical memory for VM
336 purposes. This will save a few bytes kernel size and may speed up
337 some operations. Say N if not sure.
339 config 060_WRITETHROUGH
340 bool "Use write-through caching for 68060 supervisor accesses"
341 depends on ADVANCED && M68060
343 The 68060 generally uses copyback caching of recently accessed data.
344 Copyback caching means that memory writes will be held in an on-chip
345 cache and only written back to memory some time later. Saying Y
346 here will force supervisor (kernel) accesses to use writethrough
347 caching. Writethrough caching means that data is written to memory
348 straight away, so that cache and memory data always agree.
349 Writethrough caching is less efficient, but is needed for some
350 drivers on 68060 based systems where the 68060 bus snooping signal
351 is hardwired on. The 53c710 SCSI driver is known to suffer from
358 source "fs/Kconfig.binfmt"
361 bool "Amiga Zorro (AutoConfig) bus support"
364 This enables support for the Zorro bus in the Amiga. If you have
365 expansion cards in your Amiga that conform to the Amiga
366 AutoConfig(tm) specification, say Y, otherwise N. Note that even
367 expansion cards that do not fit in the Zorro slots but fit in e.g.
368 the CPU slot may fall in this category, so you have to say Y to let
372 bool "Amiga 1200/600 PCMCIA support (EXPERIMENTAL)"
373 depends on AMIGA && EXPERIMENTAL
375 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
376 600. If you intend to use pcmcia cards say Y; otherwise say N.
379 bool "Support for ST-RAM as swap space"
380 depends on ATARI && BROKEN
382 Some Atari 68k macines (including the 520STF and 1020STE) divide
383 their addressible memory into ST and TT sections. The TT section
384 (up to 512MB) is the main memory; the ST section (up to 4MB) is
385 accessible to the built-in graphics board, runs slower, and is
386 present mainly for backward compatibility with older machines.
388 This enables support for using (parts of) ST-RAM as swap space,
389 instead of as normal system memory. This can first enhance system
390 performance if you have lots of alternate RAM (compared to the size
391 of ST-RAM), because executable code always will reside in faster
392 memory. ST-RAM will remain as ultra-fast swap space. On the other
393 hand, it allows much improved dynamic allocations of ST-RAM buffers
394 for device driver modules (e.g. floppy, ACSI, SLM printer, DMA
395 sound). The probability that such allocations at module load time
396 fail is drastically reduced.
399 bool "ST-RAM statistics in /proc"
402 Say Y here to report ST-RAM usage statistics in /proc/stram. See
403 the help for CONFIG_STRAM_SWAP for discussion of ST-RAM and its
407 bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || MAC ||Q40
408 default y if !AMIGA && !APOLLO && !ATARI && !MAC && !Q40 && HP300
410 Use the power-on LED on your machine as a load meter. The exact
411 behavior is platform-dependent, but normally the flash frequency is
412 a hyperbolic function of the 5-minute load average.
414 # We have a dedicated heartbeat LED. :-)
416 bool "/proc/hardware support"
418 Say Y here to support the /proc/hardware file, which gives you
419 access to information about the machine you're running on,
420 including the model, CPU, MMU, clock speed, BogoMIPS rating,
425 depends on Q40 || AMIGA_PCMCIA || GG2
428 Find out whether you have ISA slots on your motherboard. ISA is the
429 name of a bus system, i.e. the way the CPU talks to the other stuff
430 inside your box. Other bus systems are PCI, EISA, MicroChannel
431 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
432 newer boards don't support it. If you have ISA, say Y, otherwise N.
434 config GENERIC_ISA_DMA
436 depends on Q40 || AMIGA_PCMCIA || GG2
439 source "drivers/pci/Kconfig"
441 source "drivers/zorro/Kconfig"
445 source "drivers/Kconfig"
447 menu "Character devices"
450 tristate "Atari MFP serial support"
453 If you like to use the MFP serial ports ("Modem1", "Serial1") under
454 Linux, say Y. The driver equally supports all kinds of MFP serial
455 ports and automatically detects whether Serial1 is available.
457 To compile this driver as a module, choose M here.
459 Note for Falcon users: You also have an MFP port, it's just not
460 wired to the outside... But you could use the port under Linux.
463 tristate "Atari SCC serial support"
466 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
467 LAN) and like to use them under Linux, say Y. All built-in SCC's are
468 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
469 two connectors for channel A (Serial2 and LAN), they are visible as
470 two separate devices.
472 To compile this driver as a module, choose M here.
475 bool "Atari SCC serial DMA support"
478 This enables DMA support for receiving data on channel A of the SCC.
479 If you have a TT you may say Y here and read
480 drivers/char/atari_SCC.README. All other users should say N here,
481 because only the TT has SCC-DMA, even if your machine keeps claiming
485 tristate "Atari MIDI serial support"
488 If you want to use your Atari's MIDI port in Linux, say Y.
490 To compile this driver as a module, choose M here.
493 tristate "Atari DSP56k support (EXPERIMENTAL)"
494 depends on ATARI && EXPERIMENTAL
496 If you want to be able to use the DSP56001 in Falcons, say Y. This
497 driver is still experimental, and if you don't know what it is, or
498 if you don't have this processor, just say N.
500 To compile this driver as a module, choose M here.
502 config AMIGA_BUILTIN_SERIAL
503 tristate "Amiga builtin serial support"
506 If you want to use your Amiga's built-in serial port in Linux,
509 To compile this driver as a module, choose M here.
511 config WHIPPET_SERIAL
512 tristate "Hisoft Whippet PCMCIA serial support"
513 depends on AMIGA_PCMCIA
515 HiSoft has a web page at <http://www.hisoft.co.uk/>, but there
516 is no listing for the Whippet in their Amiga section.
518 config MULTIFACE_III_TTY
519 tristate "Multiface Card III serial support"
522 If you want to use a Multiface III card's serial port in Linux,
525 To compile this driver as a module, choose M here.
528 tristate "GVP IO-Extender support"
529 depends on PARPORT=n && ZORRO
531 If you want to use a GVP IO-Extender serial card in Linux, say Y.
535 tristate "GVP IO-Extender parallel printer support"
538 Say Y to enable driving a printer from the parallel port on your
539 GVP IO-Extender card, N otherwise.
542 tristate "GVP IO-Extender PLIP support"
545 Say Y to enable doing IP over the parallel port on your GVP
546 IO-Extender card, N otherwise.
549 tristate "Macintosh serial support"
554 depends on INPUT_ADBHID
557 config MAC_ADBKEYCODES
558 bool "Support for ADB raw keycodes"
559 depends on INPUT_ADBHID
561 This provides support for sending raw ADB keycodes to console
562 devices. This is the default up to 2.4.0, but in future this may be
563 phased out in favor of generic Linux keycodes. If you say Y here,
564 you can dynamically switch via the
565 /proc/sys/dev/mac_hid/keyboard_sends_linux_keycodes
566 sysctl and with the "keyboard_sends_linux_keycodes=" kernel
569 If unsure, say Y here.
572 bool "Support for ADB keyboard (old driver)"
573 depends on MAC && !INPUT_ADBHID
575 This option allows you to use an ADB keyboard attached to your
576 machine. Note that this disables any other (ie. PS/2) keyboard
577 support, even if your machine is physically capable of using both at
580 If you use an ADB keyboard (4 pin connector), say Y here.
581 If you use a PS/2 keyboard (6 pin connector), say N here.
584 tristate "HP DCA serial support"
587 If you want to use the internal "DCA" serial ports on an HP300
591 bool "SCC support for MVME147 serial ports"
594 This is the driver for the serial ports on the Motorola MVME147
595 boards. Everyone using one of these boards should say Y here.
598 bool "CD2401 support for MVME166/7 serial ports"
599 depends on MVME16x && BROKEN
601 This is the driver for the serial ports on the Motorola MVME166,
602 167, and 172 boards. Everyone using one of these boards should say
606 bool "SCC support for MVME162 serial ports"
609 This is the driver for the serial ports on the Motorola MVME162 and
610 172 boards. Everyone using one of these boards should say Y here.
613 bool "SCC support for BVME6000 serial ports"
616 This is the driver for the serial ports on the BVME4000 and BVME6000
617 boards from BVM Ltd. Everyone using one of these boards should say
621 bool "Support for DN serial port (dummy)"
624 config SERIAL_CONSOLE
625 bool "Support for serial port console"
626 depends on (AMIGA || ATARI || MAC || HP300 || 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 || HPDCA=y || SERIAL=y || MVME147_SCC || SERIAL167 || MVME162_SCC || BVME6000_SCC || DN_SERIAL)
628 If you say Y here, it will be possible to use a serial port as the
629 system console (the system console is the device which receives all
630 kernel messages and warnings and which allows logins in single user
631 mode). This could be useful if some terminal or printer is connected
634 Even if you say Y here, the currently visible virtual console
635 (/dev/tty0) will still be used as the system console by default, but
636 you can alter that using a kernel command line option such as
637 "console=ttyS1". (Try "man bootparam" or see the documentation of
638 your boot loader (lilo or loadlin) about how to pass options to the
639 kernel at boot time.)
641 If you don't have a VGA card installed and you say Y here, the
642 kernel will automatically use the first serial line, /dev/ttyS0, as
651 source "arch/m68k/Kconfig.debug"
653 source "kernel/vserver/Kconfig"
655 source "security/Kconfig"
657 source "crypto/Kconfig"