2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
14 config RWSEM_GENERIC_SPINLOCK
18 config RWSEM_XCHGADD_ALGORITHM
21 config ARCH_HAS_ILOG2_U32
25 config ARCH_HAS_ILOG2_U64
29 config GENERIC_HWEIGHT
33 config GENERIC_CALIBRATE_DELAY
45 config ARCH_MAY_HAVE_PC_FDC
47 depends on BROKEN && (Q40 || SUN3X)
56 config ARCH_SUPPORTS_AOUT
63 mainmenu "Linux/68k Kernel Configuration"
67 menu "Platform dependent setup"
72 The Extended Industry Standard Architecture (EISA) bus was
73 developed as an open alternative to the IBM MicroChannel bus.
75 The EISA bus provided some of the features of the IBM MicroChannel
76 bus while maintaining backward compatibility with cards made for
77 the older ISA bus. The EISA bus saw limited use between 1988 and
78 1995 when it was made obsolete by the PCI bus.
80 Say Y here if you are building a kernel for an EISA-based machine.
87 MicroChannel Architecture is found in some IBM PS/2 machines and
88 laptops. It is a bus system similar to PCI or ISA. See
89 <file:Documentation/mca.txt> (and especially the web page given
90 there) before attempting to build an MCA bus kernel.
95 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
96 computer. These are credit-card size devices such as network cards,
97 modems or hard drives often used with laptops computers. There are
98 actually two varieties of these cards: the older 16 bit PCMCIA cards
99 and the newer 32 bit CardBus cards. If you want to use CardBus
100 cards, you need to say Y here and also to "CardBus support" below.
102 To use your PC-cards, you will need supporting software from David
103 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
104 for location). Please also read the PCMCIA-HOWTO, available from
105 <http://www.tldp.org/docs.html#howto>.
107 To compile this driver as modules, choose M here: the
108 modules will be called pcmcia_core and ds.
113 select MMU_SUN3 if MMU
115 This option enables support for the Sun 3 series of workstations
116 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
117 that all other hardware types must be disabled, as Sun 3 kernels
118 are incompatible with all other m68k targets (including Sun 3x!).
120 If you don't want to compile a kernel exclusively for a Sun 3, say N.
126 This option enables support for the Amiga series of computers. If
127 you plan to use this kernel on an Amiga, say Y here and browse the
128 material available in <file:Documentation/m68k>; otherwise say N.
134 This option enables support for the 68000-based Atari series of
135 computers (including the TT, Falcon and Medusa). If you plan to use
136 this kernel on an Atari, say Y here and browse the material
137 available in <file:Documentation/m68k>; otherwise say N.
141 depends on ATARI && BROKEN
143 This option enables support for the Hades Atari clone. If you plan
144 to use this kernel on a Hades, say Y here; otherwise say N.
151 Find out whether you have a PCI motherboard. PCI is the name of a
152 bus system, i.e. the way the CPU talks to the other stuff inside
153 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
154 VESA. If you have PCI, say Y, otherwise N.
157 bool "Macintosh support"
160 This option enables support for the Apple Macintosh series of
161 computers (yes, there is experimental support now, at least for part
164 Say N unless you're willing to code the remaining necessary support.
178 bool "Apollo support"
181 Say Y here if you want to run Linux on an MC680x0-based Apollo
182 Domain workstation such as the DN3500.
185 bool "VME (Motorola and BVM) support"
188 Say Y here if you want to build a kernel for a 680x0 based VME
189 board. Boards currently supported include Motorola boards MVME147,
190 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
191 BVME6000 boards from BVM Ltd are also supported.
194 bool "MVME147 support"
197 Say Y to include support for early Motorola VME boards. This will
198 build a kernel which can run on MVME147 single-board computers. If
199 you select this option you will have to select the appropriate
200 drivers for SCSI, Ethernet and serial ports later on.
203 bool "MVME162, 166 and 167 support"
206 Say Y to include support for Motorola VME boards. This will build a
207 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
208 MVME177 boards. If you select this option you will have to select
209 the appropriate drivers for SCSI, Ethernet and serial ports later
213 bool "BVME4000 and BVME6000 support"
216 Say Y to include support for VME boards from BVM Ltd. This will
217 build a kernel which can run on BVME4000 and BVME6000 boards. If
218 you select this option you will have to select the appropriate
219 drivers for SCSI, Ethernet and serial ports later on.
222 bool "HP9000/300 and HP9000/400 support"
225 This option enables support for the HP9000/300 and HP9000/400 series
226 of workstations. Support for these machines is still somewhat
227 experimental. If you plan to try to use the kernel on such a machine
229 Everybody else says N.
232 bool "DIO bus support"
236 Say Y here to enable support for the "DIO" expansion bus used in
237 HP300 machines. If you are using such a system you almost certainly
245 This option enables support for the Sun 3x series of workstations.
246 Be warned that this support is very experimental.
247 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
248 General Linux information on the Sun 3x series (now discontinued)
249 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
251 If you don't want to compile a kernel for a Sun 3x, say N.
254 bool "Q40/Q60 support"
257 The Q40 is a Motorola 68040-based successor to the Sinclair QL
258 manufactured in Germany. There is an official Q40 home page at
259 <http://www.q40.de/>. This option enables support for the Q40 and
260 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
263 comment "Processor type"
268 If you anticipate running this kernel on a computer with a MC68020
269 processor, say Y. Otherwise, say N. Note that the 68020 requires a
270 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
271 Sun 3, which provides its own version.
277 If you anticipate running this kernel on a computer with a MC68030
278 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
279 work, as it does not include an MMU (Memory Management Unit).
285 If you anticipate running this kernel on a computer with a MC68LC040
286 or MC68040 processor, say Y. Otherwise, say N. Note that an
287 MC68EC040 will not work, as it does not include an MMU (Memory
294 If you anticipate running this kernel on a computer with a MC68060
295 processor, say Y. Otherwise, say N.
299 depends on MMU && !MMU_SUN3
306 bool "Math emulation support (EXPERIMENTAL)"
307 depends on EXPERIMENTAL
309 At some point in the future, this will cause floating-point math
310 instructions to be emulated by the kernel on machines that lack a
311 floating-point math coprocessor. Thrill-seekers and chronically
312 sleep-deprived psychotic hacker types can say Y now, everyone else
313 should probably wait a while.
315 config M68KFPU_EMU_EXTRAPREC
316 bool "Math emulation extra precision"
317 depends on M68KFPU_EMU
319 The fpu uses normally a few bit more during calculations for
320 correct rounding, the emulator can (often) do the same but this
321 extra calculation can cost quite some time, so you can disable
322 it here. The emulator will then "only" calculate with a 64 bit
323 mantissa and round slightly incorrect, what is more then enough
326 config M68KFPU_EMU_ONLY
327 bool "Math emulation only kernel"
328 depends on M68KFPU_EMU
330 This option prevents any floating-point instructions from being
331 compiled into the kernel, thereby the kernel doesn't save any
332 floating point context anymore during task switches, so this
333 kernel will only be usable on machines without a floating-point
334 math coprocessor. This makes the kernel a bit faster as no tests
335 needs to be executed whether a floating-point instruction in the
336 kernel should be executed or not.
339 bool "Advanced configuration options"
341 This gives you access to some advanced options for the CPU. The
342 defaults should be fine for most users, but these options may make
343 it possible for you to improve performance somewhat if you know what
346 Note that the answer to this question won't directly affect the
347 kernel: saying N will just cause the configurator to skip all
348 the questions about these options.
350 Most users should say N to this question.
353 bool "Use read-modify-write instructions"
356 This allows to use certain instructions that work with indivisible
357 read-modify-write bus cycles. While this is faster than the
358 workaround of disabling interrupts, it can conflict with DMA
359 ( = direct memory access) on many Amiga systems, and it is also said
360 to destabilize other machines. It is very likely that this will
361 cause serious problems on any Amiga or Atari Medusa if set. The only
362 configuration where it should work are 68030-based Ataris, where it
363 apparently improves performance. But you've been warned! Unless you
364 really know what you are doing, say N. Try Y only if you're quite
367 config SINGLE_MEMORY_CHUNK
368 bool "Use one physical chunk of memory only" if ADVANCED && !SUN3
370 select NEED_MULTIPLE_NODES
372 Ignore all but the first contiguous chunk of physical memory for VM
373 purposes. This will save a few bytes kernel size and may speed up
374 some operations. Say N if not sure.
376 config 060_WRITETHROUGH
377 bool "Use write-through caching for 68060 supervisor accesses"
378 depends on ADVANCED && M68060
380 The 68060 generally uses copyback caching of recently accessed data.
381 Copyback caching means that memory writes will be held in an on-chip
382 cache and only written back to memory some time later. Saying Y
383 here will force supervisor (kernel) accesses to use writethrough
384 caching. Writethrough caching means that data is written to memory
385 straight away, so that cache and memory data always agree.
386 Writethrough caching is less efficient, but is needed for some
387 drivers on 68060 based systems where the 68060 bus snooping signal
388 is hardwired on. The 53c710 SCSI driver is known to suffer from
391 config ARCH_DISCONTIGMEM_ENABLE
392 def_bool !SINGLE_MEMORY_CHUNK
397 depends on !SINGLE_MEMORY_CHUNK
405 source "fs/Kconfig.binfmt"
408 bool "Amiga Zorro (AutoConfig) bus support"
411 This enables support for the Zorro bus in the Amiga. If you have
412 expansion cards in your Amiga that conform to the Amiga
413 AutoConfig(tm) specification, say Y, otherwise N. Note that even
414 expansion cards that do not fit in the Zorro slots but fit in e.g.
415 the CPU slot may fall in this category, so you have to say Y to let
419 bool "Amiga 1200/600 PCMCIA support (EXPERIMENTAL)"
420 depends on AMIGA && EXPERIMENTAL
422 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
423 600. If you intend to use pcmcia cards say Y; otherwise say N.
426 bool "ST-RAM statistics in /proc"
429 Say Y here to report ST-RAM usage statistics in /proc/stram.
432 bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || MAC ||Q40
433 default y if !AMIGA && !APOLLO && !ATARI && !MAC && !Q40 && HP300
435 Use the power-on LED on your machine as a load meter. The exact
436 behavior is platform-dependent, but normally the flash frequency is
437 a hyperbolic function of the 5-minute load average.
439 # We have a dedicated heartbeat LED. :-)
441 bool "/proc/hardware support"
443 Say Y here to support the /proc/hardware file, which gives you
444 access to information about the machine you're running on,
445 including the model, CPU, MMU, clock speed, BogoMIPS rating,
450 depends on Q40 || AMIGA_PCMCIA || GG2
453 Find out whether you have ISA slots on your motherboard. ISA is the
454 name of a bus system, i.e. the way the CPU talks to the other stuff
455 inside your box. Other bus systems are PCI, EISA, MicroChannel
456 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
457 newer boards don't support it. If you have ISA, say Y, otherwise N.
459 config GENERIC_ISA_DMA
461 depends on Q40 || AMIGA_PCMCIA || GG2
468 source "drivers/pci/Kconfig"
470 source "drivers/zorro/Kconfig"
476 source "drivers/Kconfig"
478 menu "Character devices"
481 tristate "Atari MFP serial support"
484 If you like to use the MFP serial ports ("Modem1", "Serial1") under
485 Linux, say Y. The driver equally supports all kinds of MFP serial
486 ports and automatically detects whether Serial1 is available.
488 To compile this driver as a module, choose M here.
490 Note for Falcon users: You also have an MFP port, it's just not
491 wired to the outside... But you could use the port under Linux.
494 tristate "Atari SCC serial support"
497 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
498 LAN) and like to use them under Linux, say Y. All built-in SCC's are
499 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
500 two connectors for channel A (Serial2 and LAN), they are visible as
501 two separate devices.
503 To compile this driver as a module, choose M here.
506 bool "Atari SCC serial DMA support"
509 This enables DMA support for receiving data on channel A of the SCC.
510 If you have a TT you may say Y here and read
511 drivers/char/atari_SCC.README. All other users should say N here,
512 because only the TT has SCC-DMA, even if your machine keeps claiming
516 tristate "Atari MIDI serial support"
519 If you want to use your Atari's MIDI port in Linux, say Y.
521 To compile this driver as a module, choose M here.
524 tristate "Atari DSP56k support (EXPERIMENTAL)"
525 depends on ATARI && EXPERIMENTAL
527 If you want to be able to use the DSP56001 in Falcons, say Y. This
528 driver is still experimental, and if you don't know what it is, or
529 if you don't have this processor, just say N.
531 To compile this driver as a module, choose M here.
533 config AMIGA_BUILTIN_SERIAL
534 tristate "Amiga builtin serial support"
537 If you want to use your Amiga's built-in serial port in Linux,
540 To compile this driver as a module, choose M here.
542 config MULTIFACE_III_TTY
543 tristate "Multiface Card III serial support"
546 If you want to use a Multiface III card's serial port in Linux,
549 To compile this driver as a module, choose M here.
552 tristate "GVP IO-Extender support"
553 depends on PARPORT=n && ZORRO
555 If you want to use a GVP IO-Extender serial card in Linux, say Y.
559 tristate "GVP IO-Extender parallel printer support"
562 Say Y to enable driving a printer from the parallel port on your
563 GVP IO-Extender card, N otherwise.
566 tristate "GVP IO-Extender PLIP support"
569 Say Y to enable doing IP over the parallel port on your GVP
570 IO-Extender card, N otherwise.
573 tristate "Macintosh serial support"
578 depends on INPUT_ADBHID
582 tristate "HP DCA serial support"
583 depends on DIO && SERIAL_8250
585 If you want to use the internal "DCA" serial ports on an HP300
589 tristate "HP APCI serial support"
590 depends on HP300 && SERIAL_8250 && EXPERIMENTAL
592 If you want to use the internal "APCI" serial ports on an HP400
596 bool "SCC support for MVME147 serial ports"
599 This is the driver for the serial ports on the Motorola MVME147
600 boards. Everyone using one of these boards should say Y here.
603 bool "CD2401 support for MVME166/7 serial ports"
606 This is the driver for the serial ports on the Motorola MVME166,
607 167, and 172 boards. Everyone using one of these boards should say
611 bool "SCC support for MVME162 serial ports"
614 This is the driver for the serial ports on the Motorola MVME162 and
615 172 boards. Everyone using one of these boards should say Y here.
618 bool "SCC support for BVME6000 serial ports"
621 This is the driver for the serial ports on the BVME4000 and BVME6000
622 boards from BVM Ltd. Everyone using one of these boards should say
626 bool "Support for DN serial port (dummy)"
629 config SERIAL_CONSOLE
630 bool "Support for serial port console"
631 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)
633 If you say Y here, it will be possible to use a serial port as the
634 system console (the system console is the device which receives all
635 kernel messages and warnings and which allows logins in single user
636 mode). This could be useful if some terminal or printer is connected
639 Even if you say Y here, the currently visible virtual console
640 (/dev/tty0) will still be used as the system console by default, but
641 you can alter that using a kernel command line option such as
642 "console=ttyS1". (Try "man bootparam" or see the documentation of
643 your boot loader (lilo or loadlin) about how to pass options to the
644 kernel at boot time.)
646 If you don't have a VGA card installed and you say Y here, the
647 kernel will automatically use the first serial line, /dev/ttyS0, as
656 source "arch/m68k/Kconfig.debug"
658 source "security/Kconfig"
660 source "crypto/Kconfig"