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 GENERIC_CALIBRATE_DELAY
24 config ARCH_MAY_HAVE_PC_FDC
26 depends on Q40 || (BROKEN && SUN3X)
29 mainmenu "Linux/68k Kernel Configuration"
33 menu "Platform dependent setup"
38 The Extended Industry Standard Architecture (EISA) bus was
39 developed as an open alternative to the IBM MicroChannel bus.
41 The EISA bus provided some of the features of the IBM MicroChannel
42 bus while maintaining backward compatibility with cards made for
43 the older ISA bus. The EISA bus saw limited use between 1988 and
44 1995 when it was made obsolete by the PCI bus.
46 Say Y here if you are building a kernel for an EISA-based machine.
53 MicroChannel Architecture is found in some IBM PS/2 machines and
54 laptops. It is a bus system similar to PCI or ISA. See
55 <file:Documentation/mca.txt> (and especially the web page given
56 there) before attempting to build an MCA bus kernel.
61 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
62 computer. These are credit-card size devices such as network cards,
63 modems or hard drives often used with laptops computers. There are
64 actually two varieties of these cards: the older 16 bit PCMCIA cards
65 and the newer 32 bit CardBus cards. If you want to use CardBus
66 cards, you need to say Y here and also to "CardBus support" below.
68 To use your PC-cards, you will need supporting software from David
69 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
70 for location). Please also read the PCMCIA-HOWTO, available from
71 <http://www.tldp.org/docs.html#howto>.
73 To compile this driver as modules, choose M here: the
74 modules will be called pcmcia_core and ds.
79 select MMU_SUN3 if MMU
81 This option enables support for the Sun 3 series of workstations
82 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
83 that all other hardware types must be disabled, as Sun 3 kernels
84 are incompatible with all other m68k targets (including Sun 3x!).
86 If you don't want to compile a kernel exclusively for a Sun 3, say N.
92 This option enables support for the Amiga series of computers. If
93 you plan to use this kernel on an Amiga, say Y here and browse the
94 material available in <file:Documentation/m68k>; otherwise say N.
100 This option enables support for the 68000-based Atari series of
101 computers (including the TT, Falcon and Medusa). If you plan to use
102 this kernel on an Atari, say Y here and browse the material
103 available in <file:Documentation/m68k>; otherwise say N.
107 depends on ATARI && BROKEN
109 This option enables support for the Hades Atari clone. If you plan
110 to use this kernel on a Hades, say Y here; otherwise say N.
117 Find out whether you have a PCI motherboard. PCI is the name of a
118 bus system, i.e. the way the CPU talks to the other stuff inside
119 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
120 VESA. If you have PCI, say Y, otherwise N.
122 The PCI-HOWTO, available from
123 <http://www.tldp.org/docs.html#howto>, contains valuable
124 information about which PCI hardware does work under Linux and which
128 bool "Macintosh support"
131 This option enables support for the Apple Macintosh series of
132 computers (yes, there is experimental support now, at least for part
135 Say N unless you're willing to code the remaining necessary support.
149 bool "Apollo support"
152 Say Y here if you want to run Linux on an MC680x0-based Apollo
153 Domain workstation such as the DN3500.
156 bool "VME (Motorola and BVM) support"
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.
165 bool "MVME147 support"
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.
174 bool "MVME162, 166 and 167 support"
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
184 bool "BVME4000 and BVME6000 support"
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.
193 bool "HP9000/300 and HP9000/400 support"
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
200 Everybody else says N.
203 bool "DIO bus support"
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
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>.
222 If you don't want to compile a kernel for a Sun 3x, say N.
225 bool "Q40/Q60 support"
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
234 comment "Processor type"
239 If you anticipate running this kernel on a computer with a MC68020
240 processor, say Y. Otherwise, say N. Note that the 68020 requires a
241 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
242 Sun 3, which provides its own version.
248 If you anticipate running this kernel on a computer with a MC68030
249 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
250 work, as it does not include an MMU (Memory Management Unit).
256 If you anticipate running this kernel on a computer with a MC68LC040
257 or MC68040 processor, say Y. Otherwise, say N. Note that an
258 MC68EC040 will not work, as it does not include an MMU (Memory
265 If you anticipate running this kernel on a computer with a MC68060
266 processor, say Y. Otherwise, say N.
270 depends on MMU && !MMU_SUN3
277 bool "Math emulation support (EXPERIMENTAL)"
278 depends on EXPERIMENTAL
280 At some point in the future, this will cause floating-point math
281 instructions to be emulated by the kernel on machines that lack a
282 floating-point math coprocessor. Thrill-seekers and chronically
283 sleep-deprived psychotic hacker types can say Y now, everyone else
284 should probably wait a while.
286 config M68KFPU_EMU_EXTRAPREC
287 bool "Math emulation extra precision"
288 depends on M68KFPU_EMU
290 The fpu uses normally a few bit more during calculations for
291 correct rounding, the emulator can (often) do the same but this
292 extra calculation can cost quite some time, so you can disable
293 it here. The emulator will then "only" calculate with a 64 bit
294 mantissa and round slightly incorrect, what is more then enough
297 config M68KFPU_EMU_ONLY
298 bool "Math emulation only kernel"
299 depends on M68KFPU_EMU
301 This option prevents any floating-point instructions from being
302 compiled into the kernel, thereby the kernel doesn't save any
303 floating point context anymore during task switches, so this
304 kernel will only be usable on machines without a floating-point
305 math coprocessor. This makes the kernel a bit faster as no tests
306 needs to be executed whether a floating-point instruction in the
307 kernel should be executed or not.
310 bool "Advanced configuration options"
312 This gives you access to some advanced options for the CPU. The
313 defaults should be fine for most users, but these options may make
314 it possible for you to improve performance somewhat if you know what
317 Note that the answer to this question won't directly affect the
318 kernel: saying N will just cause the configurator to skip all
319 the questions about these options.
321 Most users should say N to this question.
324 bool "Use read-modify-write instructions"
327 This allows to use certain instructions that work with indivisible
328 read-modify-write bus cycles. While this is faster than the
329 workaround of disabling interrupts, it can conflict with DMA
330 ( = direct memory access) on many Amiga systems, and it is also said
331 to destabilize other machines. It is very likely that this will
332 cause serious problems on any Amiga or Atari Medusa if set. The only
333 configuration where it should work are 68030-based Ataris, where it
334 apparently improves performance. But you've been warned! Unless you
335 really know what you are doing, say N. Try Y only if you're quite
338 config SINGLE_MEMORY_CHUNK
339 bool "Use one physical chunk of memory only"
340 depends on ADVANCED && !SUN3
342 Ignore all but the first contiguous chunk of physical memory for VM
343 purposes. This will save a few bytes kernel size and may speed up
344 some operations. Say N if not sure.
346 config 060_WRITETHROUGH
347 bool "Use write-through caching for 68060 supervisor accesses"
348 depends on ADVANCED && M68060
350 The 68060 generally uses copyback caching of recently accessed data.
351 Copyback caching means that memory writes will be held in an on-chip
352 cache and only written back to memory some time later. Saying Y
353 here will force supervisor (kernel) accesses to use writethrough
354 caching. Writethrough caching means that data is written to memory
355 straight away, so that cache and memory data always agree.
356 Writethrough caching is less efficient, but is needed for some
357 drivers on 68060 based systems where the 68060 bus snooping signal
358 is hardwired on. The 53c710 SCSI driver is known to suffer from
367 source "fs/Kconfig.binfmt"
370 bool "Amiga Zorro (AutoConfig) bus support"
373 This enables support for the Zorro bus in the Amiga. If you have
374 expansion cards in your Amiga that conform to the Amiga
375 AutoConfig(tm) specification, say Y, otherwise N. Note that even
376 expansion cards that do not fit in the Zorro slots but fit in e.g.
377 the CPU slot may fall in this category, so you have to say Y to let
381 bool "Amiga 1200/600 PCMCIA support (EXPERIMENTAL)"
382 depends on AMIGA && EXPERIMENTAL
384 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
385 600. If you intend to use pcmcia cards say Y; otherwise say N.
388 bool "ST-RAM statistics in /proc"
391 Say Y here to report ST-RAM usage statistics in /proc/stram.
394 bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || MAC ||Q40
395 default y if !AMIGA && !APOLLO && !ATARI && !MAC && !Q40 && HP300
397 Use the power-on LED on your machine as a load meter. The exact
398 behavior is platform-dependent, but normally the flash frequency is
399 a hyperbolic function of the 5-minute load average.
401 # We have a dedicated heartbeat LED. :-)
403 bool "/proc/hardware support"
405 Say Y here to support the /proc/hardware file, which gives you
406 access to information about the machine you're running on,
407 including the model, CPU, MMU, clock speed, BogoMIPS rating,
412 depends on Q40 || AMIGA_PCMCIA || GG2
415 Find out whether you have ISA slots on your motherboard. ISA is the
416 name of a bus system, i.e. the way the CPU talks to the other stuff
417 inside your box. Other bus systems are PCI, EISA, MicroChannel
418 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
419 newer boards don't support it. If you have ISA, say Y, otherwise N.
421 config GENERIC_ISA_DMA
423 depends on Q40 || AMIGA_PCMCIA || GG2
426 source "drivers/pci/Kconfig"
428 source "drivers/zorro/Kconfig"
434 source "drivers/Kconfig"
436 menu "Character devices"
439 tristate "Atari MFP serial support"
442 If you like to use the MFP serial ports ("Modem1", "Serial1") under
443 Linux, say Y. The driver equally supports all kinds of MFP serial
444 ports and automatically detects whether Serial1 is available.
446 To compile this driver as a module, choose M here.
448 Note for Falcon users: You also have an MFP port, it's just not
449 wired to the outside... But you could use the port under Linux.
452 tristate "Atari SCC serial support"
455 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
456 LAN) and like to use them under Linux, say Y. All built-in SCC's are
457 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
458 two connectors for channel A (Serial2 and LAN), they are visible as
459 two separate devices.
461 To compile this driver as a module, choose M here.
464 bool "Atari SCC serial DMA support"
467 This enables DMA support for receiving data on channel A of the SCC.
468 If you have a TT you may say Y here and read
469 drivers/char/atari_SCC.README. All other users should say N here,
470 because only the TT has SCC-DMA, even if your machine keeps claiming
474 tristate "Atari MIDI serial support"
477 If you want to use your Atari's MIDI port in Linux, say Y.
479 To compile this driver as a module, choose M here.
482 tristate "Atari DSP56k support (EXPERIMENTAL)"
483 depends on ATARI && EXPERIMENTAL
485 If you want to be able to use the DSP56001 in Falcons, say Y. This
486 driver is still experimental, and if you don't know what it is, or
487 if you don't have this processor, just say N.
489 To compile this driver as a module, choose M here.
491 config AMIGA_BUILTIN_SERIAL
492 tristate "Amiga builtin serial support"
495 If you want to use your Amiga's built-in serial port in Linux,
498 To compile this driver as a module, choose M here.
500 config WHIPPET_SERIAL
501 tristate "Hisoft Whippet PCMCIA serial support"
502 depends on AMIGA_PCMCIA
504 HiSoft has a web page at <http://www.hisoft.co.uk/>, but there
505 is no listing for the Whippet in their Amiga section.
507 config MULTIFACE_III_TTY
508 tristate "Multiface Card III serial support"
511 If you want to use a Multiface III card's serial port in Linux,
514 To compile this driver as a module, choose M here.
517 tristate "GVP IO-Extender support"
518 depends on PARPORT=n && ZORRO
520 If you want to use a GVP IO-Extender serial card in Linux, say Y.
524 tristate "GVP IO-Extender parallel printer support"
527 Say Y to enable driving a printer from the parallel port on your
528 GVP IO-Extender card, N otherwise.
531 tristate "GVP IO-Extender PLIP support"
534 Say Y to enable doing IP over the parallel port on your GVP
535 IO-Extender card, N otherwise.
538 tristate "Macintosh serial support"
543 depends on INPUT_ADBHID
546 config MAC_ADBKEYCODES
547 bool "Support for ADB raw keycodes"
548 depends on INPUT_ADBHID
550 This provides support for sending raw ADB keycodes to console
551 devices. This is the default up to 2.4.0, but in future this may be
552 phased out in favor of generic Linux keycodes. If you say Y here,
553 you can dynamically switch via the
554 /proc/sys/dev/mac_hid/keyboard_sends_linux_keycodes
555 sysctl and with the "keyboard_sends_linux_keycodes=" kernel
558 If unsure, say Y here.
561 bool "Support for ADB keyboard (old driver)"
562 depends on MAC && !INPUT_ADBHID
564 This option allows you to use an ADB keyboard attached to your
565 machine. Note that this disables any other (ie. PS/2) keyboard
566 support, even if your machine is physically capable of using both at
569 If you use an ADB keyboard (4 pin connector), say Y here.
570 If you use a PS/2 keyboard (6 pin connector), say N here.
573 tristate "HP DCA serial support"
574 depends on DIO && SERIAL_8250
576 If you want to use the internal "DCA" serial ports on an HP300
580 tristate "HP APCI serial support"
581 depends on HP300 && SERIAL_8250 && EXPERIMENTAL
583 If you want to use the internal "APCI" serial ports on an HP400
587 bool "SCC support for MVME147 serial ports"
590 This is the driver for the serial ports on the Motorola MVME147
591 boards. Everyone using one of these boards should say Y here.
594 bool "CD2401 support for MVME166/7 serial ports"
595 depends on MVME16x && BROKEN
597 This is the driver for the serial ports on the Motorola MVME166,
598 167, and 172 boards. Everyone using one of these boards should say
602 bool "SCC support for MVME162 serial ports"
605 This is the driver for the serial ports on the Motorola MVME162 and
606 172 boards. Everyone using one of these boards should say Y here.
609 bool "SCC support for BVME6000 serial ports"
612 This is the driver for the serial ports on the BVME4000 and BVME6000
613 boards from BVM Ltd. Everyone using one of these boards should say
617 bool "Support for DN serial port (dummy)"
620 config SERIAL_CONSOLE
621 bool "Support for serial port console"
622 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)
624 If you say Y here, it will be possible to use a serial port as the
625 system console (the system console is the device which receives all
626 kernel messages and warnings and which allows logins in single user
627 mode). This could be useful if some terminal or printer is connected
630 Even if you say Y here, the currently visible virtual console
631 (/dev/tty0) will still be used as the system console by default, but
632 you can alter that using a kernel command line option such as
633 "console=ttyS1". (Try "man bootparam" or see the documentation of
634 your boot loader (lilo or loadlin) about how to pass options to the
635 kernel at boot time.)
637 If you don't have a VGA card installed and you say Y here, the
638 kernel will automatically use the first serial line, /dev/ttyS0, as
647 source "arch/m68k/Kconfig.debug"
649 source "security/Kconfig"
651 source "crypto/Kconfig"