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 mainmenu "Linux/68k Kernel Configuration"
59 menu "Platform dependent setup"
64 The Extended Industry Standard Architecture (EISA) bus was
65 developed as an open alternative to the IBM MicroChannel bus.
67 The EISA bus provided some of the features of the IBM MicroChannel
68 bus while maintaining backward compatibility with cards made for
69 the older ISA bus. The EISA bus saw limited use between 1988 and
70 1995 when it was made obsolete by the PCI bus.
72 Say Y here if you are building a kernel for an EISA-based machine.
79 MicroChannel Architecture is found in some IBM PS/2 machines and
80 laptops. It is a bus system similar to PCI or ISA. See
81 <file:Documentation/mca.txt> (and especially the web page given
82 there) before attempting to build an MCA bus kernel.
87 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
88 computer. These are credit-card size devices such as network cards,
89 modems or hard drives often used with laptops computers. There are
90 actually two varieties of these cards: the older 16 bit PCMCIA cards
91 and the newer 32 bit CardBus cards. If you want to use CardBus
92 cards, you need to say Y here and also to "CardBus support" below.
94 To use your PC-cards, you will need supporting software from David
95 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
96 for location). Please also read the PCMCIA-HOWTO, available from
97 <http://www.tldp.org/docs.html#howto>.
99 To compile this driver as modules, choose M here: the
100 modules will be called pcmcia_core and ds.
105 select MMU_SUN3 if MMU
107 This option enables support for the Sun 3 series of workstations
108 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
109 that all other hardware types must be disabled, as Sun 3 kernels
110 are incompatible with all other m68k targets (including Sun 3x!).
112 If you don't want to compile a kernel exclusively for a Sun 3, say N.
118 This option enables support for the Amiga series of computers. If
119 you plan to use this kernel on an Amiga, say Y here and browse the
120 material available in <file:Documentation/m68k>; otherwise say N.
126 This option enables support for the 68000-based Atari series of
127 computers (including the TT, Falcon and Medusa). If you plan to use
128 this kernel on an Atari, say Y here and browse the material
129 available in <file:Documentation/m68k>; otherwise say N.
133 depends on ATARI && BROKEN
135 This option enables support for the Hades Atari clone. If you plan
136 to use this kernel on a Hades, say Y here; otherwise say N.
143 Find out whether you have a PCI motherboard. PCI is the name of a
144 bus system, i.e. the way the CPU talks to the other stuff inside
145 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
146 VESA. If you have PCI, say Y, otherwise N.
149 bool "Macintosh support"
152 This option enables support for the Apple Macintosh series of
153 computers (yes, there is experimental support now, at least for part
156 Say N unless you're willing to code the remaining necessary support.
170 bool "Apollo support"
173 Say Y here if you want to run Linux on an MC680x0-based Apollo
174 Domain workstation such as the DN3500.
177 bool "VME (Motorola and BVM) support"
180 Say Y here if you want to build a kernel for a 680x0 based VME
181 board. Boards currently supported include Motorola boards MVME147,
182 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
183 BVME6000 boards from BVM Ltd are also supported.
186 bool "MVME147 support"
189 Say Y to include support for early Motorola VME boards. This will
190 build a kernel which can run on MVME147 single-board computers. If
191 you select this option you will have to select the appropriate
192 drivers for SCSI, Ethernet and serial ports later on.
195 bool "MVME162, 166 and 167 support"
198 Say Y to include support for Motorola VME boards. This will build a
199 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
200 MVME177 boards. If you select this option you will have to select
201 the appropriate drivers for SCSI, Ethernet and serial ports later
205 bool "BVME4000 and BVME6000 support"
208 Say Y to include support for VME boards from BVM Ltd. This will
209 build a kernel which can run on BVME4000 and BVME6000 boards. If
210 you select this option you will have to select the appropriate
211 drivers for SCSI, Ethernet and serial ports later on.
214 bool "HP9000/300 and HP9000/400 support"
217 This option enables support for the HP9000/300 and HP9000/400 series
218 of workstations. Support for these machines is still somewhat
219 experimental. If you plan to try to use the kernel on such a machine
221 Everybody else says N.
224 bool "DIO bus support"
228 Say Y here to enable support for the "DIO" expansion bus used in
229 HP300 machines. If you are using such a system you almost certainly
237 This option enables support for the Sun 3x series of workstations.
238 Be warned that this support is very experimental.
239 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
240 General Linux information on the Sun 3x series (now discontinued)
241 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
243 If you don't want to compile a kernel for a Sun 3x, say N.
246 bool "Q40/Q60 support"
249 The Q40 is a Motorola 68040-based successor to the Sinclair QL
250 manufactured in Germany. There is an official Q40 home page at
251 <http://www.q40.de/>. This option enables support for the Q40 and
252 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
255 comment "Processor type"
260 If you anticipate running this kernel on a computer with a MC68020
261 processor, say Y. Otherwise, say N. Note that the 68020 requires a
262 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
263 Sun 3, which provides its own version.
269 If you anticipate running this kernel on a computer with a MC68030
270 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
271 work, as it does not include an MMU (Memory Management Unit).
277 If you anticipate running this kernel on a computer with a MC68LC040
278 or MC68040 processor, say Y. Otherwise, say N. Note that an
279 MC68EC040 will not work, as it does not include an MMU (Memory
286 If you anticipate running this kernel on a computer with a MC68060
287 processor, say Y. Otherwise, say N.
291 depends on MMU && !MMU_SUN3
298 bool "Math emulation support (EXPERIMENTAL)"
299 depends on EXPERIMENTAL
301 At some point in the future, this will cause floating-point math
302 instructions to be emulated by the kernel on machines that lack a
303 floating-point math coprocessor. Thrill-seekers and chronically
304 sleep-deprived psychotic hacker types can say Y now, everyone else
305 should probably wait a while.
307 config M68KFPU_EMU_EXTRAPREC
308 bool "Math emulation extra precision"
309 depends on M68KFPU_EMU
311 The fpu uses normally a few bit more during calculations for
312 correct rounding, the emulator can (often) do the same but this
313 extra calculation can cost quite some time, so you can disable
314 it here. The emulator will then "only" calculate with a 64 bit
315 mantissa and round slightly incorrect, what is more then enough
318 config M68KFPU_EMU_ONLY
319 bool "Math emulation only kernel"
320 depends on M68KFPU_EMU
322 This option prevents any floating-point instructions from being
323 compiled into the kernel, thereby the kernel doesn't save any
324 floating point context anymore during task switches, so this
325 kernel will only be usable on machines without a floating-point
326 math coprocessor. This makes the kernel a bit faster as no tests
327 needs to be executed whether a floating-point instruction in the
328 kernel should be executed or not.
331 bool "Advanced configuration options"
333 This gives you access to some advanced options for the CPU. The
334 defaults should be fine for most users, but these options may make
335 it possible for you to improve performance somewhat if you know what
338 Note that the answer to this question won't directly affect the
339 kernel: saying N will just cause the configurator to skip all
340 the questions about these options.
342 Most users should say N to this question.
345 bool "Use read-modify-write instructions"
348 This allows to use certain instructions that work with indivisible
349 read-modify-write bus cycles. While this is faster than the
350 workaround of disabling interrupts, it can conflict with DMA
351 ( = direct memory access) on many Amiga systems, and it is also said
352 to destabilize other machines. It is very likely that this will
353 cause serious problems on any Amiga or Atari Medusa if set. The only
354 configuration where it should work are 68030-based Ataris, where it
355 apparently improves performance. But you've been warned! Unless you
356 really know what you are doing, say N. Try Y only if you're quite
359 config SINGLE_MEMORY_CHUNK
360 bool "Use one physical chunk of memory only" if ADVANCED && !SUN3
362 select NEED_MULTIPLE_NODES
364 Ignore all but the first contiguous chunk of physical memory for VM
365 purposes. This will save a few bytes kernel size and may speed up
366 some operations. Say N if not sure.
368 config 060_WRITETHROUGH
369 bool "Use write-through caching for 68060 supervisor accesses"
370 depends on ADVANCED && M68060
372 The 68060 generally uses copyback caching of recently accessed data.
373 Copyback caching means that memory writes will be held in an on-chip
374 cache and only written back to memory some time later. Saying Y
375 here will force supervisor (kernel) accesses to use writethrough
376 caching. Writethrough caching means that data is written to memory
377 straight away, so that cache and memory data always agree.
378 Writethrough caching is less efficient, but is needed for some
379 drivers on 68060 based systems where the 68060 bus snooping signal
380 is hardwired on. The 53c710 SCSI driver is known to suffer from
383 config ARCH_DISCONTIGMEM_ENABLE
384 def_bool !SINGLE_MEMORY_CHUNK
389 depends on !SINGLE_MEMORY_CHUNK
397 source "fs/Kconfig.binfmt"
400 bool "Amiga Zorro (AutoConfig) bus support"
403 This enables support for the Zorro bus in the Amiga. If you have
404 expansion cards in your Amiga that conform to the Amiga
405 AutoConfig(tm) specification, say Y, otherwise N. Note that even
406 expansion cards that do not fit in the Zorro slots but fit in e.g.
407 the CPU slot may fall in this category, so you have to say Y to let
411 bool "Amiga 1200/600 PCMCIA support (EXPERIMENTAL)"
412 depends on AMIGA && EXPERIMENTAL
414 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
415 600. If you intend to use pcmcia cards say Y; otherwise say N.
418 bool "ST-RAM statistics in /proc"
421 Say Y here to report ST-RAM usage statistics in /proc/stram.
424 bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || MAC ||Q40
425 default y if !AMIGA && !APOLLO && !ATARI && !MAC && !Q40 && HP300
427 Use the power-on LED on your machine as a load meter. The exact
428 behavior is platform-dependent, but normally the flash frequency is
429 a hyperbolic function of the 5-minute load average.
431 # We have a dedicated heartbeat LED. :-)
433 bool "/proc/hardware support"
435 Say Y here to support the /proc/hardware file, which gives you
436 access to information about the machine you're running on,
437 including the model, CPU, MMU, clock speed, BogoMIPS rating,
442 depends on Q40 || AMIGA_PCMCIA || GG2
445 Find out whether you have ISA slots on your motherboard. ISA is the
446 name of a bus system, i.e. the way the CPU talks to the other stuff
447 inside your box. Other bus systems are PCI, EISA, MicroChannel
448 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
449 newer boards don't support it. If you have ISA, say Y, otherwise N.
451 config GENERIC_ISA_DMA
453 depends on Q40 || AMIGA_PCMCIA || GG2
460 source "drivers/pci/Kconfig"
462 source "drivers/zorro/Kconfig"
468 source "drivers/Kconfig"
470 menu "Character devices"
473 tristate "Atari MFP serial support"
476 If you like to use the MFP serial ports ("Modem1", "Serial1") under
477 Linux, say Y. The driver equally supports all kinds of MFP serial
478 ports and automatically detects whether Serial1 is available.
480 To compile this driver as a module, choose M here.
482 Note for Falcon users: You also have an MFP port, it's just not
483 wired to the outside... But you could use the port under Linux.
486 tristate "Atari SCC serial support"
489 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
490 LAN) and like to use them under Linux, say Y. All built-in SCC's are
491 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
492 two connectors for channel A (Serial2 and LAN), they are visible as
493 two separate devices.
495 To compile this driver as a module, choose M here.
498 bool "Atari SCC serial DMA support"
501 This enables DMA support for receiving data on channel A of the SCC.
502 If you have a TT you may say Y here and read
503 drivers/char/atari_SCC.README. All other users should say N here,
504 because only the TT has SCC-DMA, even if your machine keeps claiming
508 tristate "Atari MIDI serial support"
511 If you want to use your Atari's MIDI port in Linux, say Y.
513 To compile this driver as a module, choose M here.
516 tristate "Atari DSP56k support (EXPERIMENTAL)"
517 depends on ATARI && EXPERIMENTAL
519 If you want to be able to use the DSP56001 in Falcons, say Y. This
520 driver is still experimental, and if you don't know what it is, or
521 if you don't have this processor, just say N.
523 To compile this driver as a module, choose M here.
525 config AMIGA_BUILTIN_SERIAL
526 tristate "Amiga builtin serial support"
529 If you want to use your Amiga's built-in serial port in Linux,
532 To compile this driver as a module, choose M here.
534 config WHIPPET_SERIAL
535 tristate "Hisoft Whippet PCMCIA serial support"
536 depends on AMIGA_PCMCIA
538 HiSoft has a web page at <http://www.hisoft.co.uk/>, but there
539 is no listing for the Whippet in their Amiga section.
541 config MULTIFACE_III_TTY
542 tristate "Multiface Card III serial support"
545 If you want to use a Multiface III card's serial port in Linux,
548 To compile this driver as a module, choose M here.
551 tristate "GVP IO-Extender support"
552 depends on PARPORT=n && ZORRO
554 If you want to use a GVP IO-Extender serial card in Linux, say Y.
558 tristate "GVP IO-Extender parallel printer support"
561 Say Y to enable driving a printer from the parallel port on your
562 GVP IO-Extender card, N otherwise.
565 tristate "GVP IO-Extender PLIP support"
568 Say Y to enable doing IP over the parallel port on your GVP
569 IO-Extender card, N otherwise.
572 tristate "Macintosh serial support"
577 depends on INPUT_ADBHID
581 bool "Support for ADB keyboard (old driver)"
582 depends on MAC && !INPUT_ADBHID
584 This option allows you to use an ADB keyboard attached to your
585 machine. Note that this disables any other (ie. PS/2) keyboard
586 support, even if your machine is physically capable of using both at
589 If you use an ADB keyboard (4 pin connector), say Y here.
590 If you use a PS/2 keyboard (6 pin connector), say N here.
593 tristate "HP DCA serial support"
594 depends on DIO && SERIAL_8250
596 If you want to use the internal "DCA" serial ports on an HP300
600 tristate "HP APCI serial support"
601 depends on HP300 && SERIAL_8250 && EXPERIMENTAL
603 If you want to use the internal "APCI" serial ports on an HP400
607 bool "SCC support for MVME147 serial ports"
610 This is the driver for the serial ports on the Motorola MVME147
611 boards. Everyone using one of these boards should say Y here.
614 bool "CD2401 support for MVME166/7 serial ports"
617 This is the driver for the serial ports on the Motorola MVME166,
618 167, and 172 boards. Everyone using one of these boards should say
622 bool "SCC support for MVME162 serial ports"
625 This is the driver for the serial ports on the Motorola MVME162 and
626 172 boards. Everyone using one of these boards should say Y here.
629 bool "SCC support for BVME6000 serial ports"
632 This is the driver for the serial ports on the BVME4000 and BVME6000
633 boards from BVM Ltd. Everyone using one of these boards should say
637 bool "Support for DN serial port (dummy)"
640 config SERIAL_CONSOLE
641 bool "Support for serial port console"
642 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)
644 If you say Y here, it will be possible to use a serial port as the
645 system console (the system console is the device which receives all
646 kernel messages and warnings and which allows logins in single user
647 mode). This could be useful if some terminal or printer is connected
650 Even if you say Y here, the currently visible virtual console
651 (/dev/tty0) will still be used as the system console by default, but
652 you can alter that using a kernel command line option such as
653 "console=ttyS1". (Try "man bootparam" or see the documentation of
654 your boot loader (lilo or loadlin) about how to pass options to the
655 kernel at boot time.)
657 If you don't have a VGA card installed and you say Y here, the
658 kernel will automatically use the first serial line, /dev/ttyS0, as
667 source "arch/m68k/Kconfig.debug"
669 source "security/Kconfig"
671 source "crypto/Kconfig"