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
40 config ARCH_MAY_HAVE_PC_FDC
42 depends on Q40 || (BROKEN && SUN3X)
48 mainmenu "Linux/68k Kernel Configuration"
52 menu "Platform dependent setup"
57 The Extended Industry Standard Architecture (EISA) bus was
58 developed as an open alternative to the IBM MicroChannel bus.
60 The EISA bus provided some of the features of the IBM MicroChannel
61 bus while maintaining backward compatibility with cards made for
62 the older ISA bus. The EISA bus saw limited use between 1988 and
63 1995 when it was made obsolete by the PCI bus.
65 Say Y here if you are building a kernel for an EISA-based machine.
72 MicroChannel Architecture is found in some IBM PS/2 machines and
73 laptops. It is a bus system similar to PCI or ISA. See
74 <file:Documentation/mca.txt> (and especially the web page given
75 there) before attempting to build an MCA bus kernel.
80 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
81 computer. These are credit-card size devices such as network cards,
82 modems or hard drives often used with laptops computers. There are
83 actually two varieties of these cards: the older 16 bit PCMCIA cards
84 and the newer 32 bit CardBus cards. If you want to use CardBus
85 cards, you need to say Y here and also to "CardBus support" below.
87 To use your PC-cards, you will need supporting software from David
88 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
89 for location). Please also read the PCMCIA-HOWTO, available from
90 <http://www.tldp.org/docs.html#howto>.
92 To compile this driver as modules, choose M here: the
93 modules will be called pcmcia_core and ds.
98 select MMU_SUN3 if MMU
100 This option enables support for the Sun 3 series of workstations
101 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
102 that all other hardware types must be disabled, as Sun 3 kernels
103 are incompatible with all other m68k targets (including Sun 3x!).
105 If you don't want to compile a kernel exclusively for a Sun 3, say N.
111 This option enables support for the Amiga series of computers. If
112 you plan to use this kernel on an Amiga, say Y here and browse the
113 material available in <file:Documentation/m68k>; otherwise say N.
119 This option enables support for the 68000-based Atari series of
120 computers (including the TT, Falcon and Medusa). If you plan to use
121 this kernel on an Atari, say Y here and browse the material
122 available in <file:Documentation/m68k>; otherwise say N.
126 depends on ATARI && BROKEN
128 This option enables support for the Hades Atari clone. If you plan
129 to use this kernel on a Hades, say Y here; otherwise say N.
136 Find out whether you have a PCI motherboard. PCI is the name of a
137 bus system, i.e. the way the CPU talks to the other stuff inside
138 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
139 VESA. If you have PCI, say Y, otherwise N.
141 The PCI-HOWTO, available from
142 <http://www.tldp.org/docs.html#howto>, contains valuable
143 information about which PCI hardware does work under Linux and which
147 bool "Macintosh support"
150 This option enables support for the Apple Macintosh series of
151 computers (yes, there is experimental support now, at least for part
154 Say N unless you're willing to code the remaining necessary support.
168 bool "Apollo support"
171 Say Y here if you want to run Linux on an MC680x0-based Apollo
172 Domain workstation such as the DN3500.
175 bool "VME (Motorola and BVM) support"
178 Say Y here if you want to build a kernel for a 680x0 based VME
179 board. Boards currently supported include Motorola boards MVME147,
180 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
181 BVME6000 boards from BVM Ltd are also supported.
184 bool "MVME147 support"
187 Say Y to include support for early Motorola VME boards. This will
188 build a kernel which can run on MVME147 single-board computers. 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 "MVME162, 166 and 167 support"
196 Say Y to include support for Motorola VME boards. This will build a
197 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
198 MVME177 boards. If you select this option you will have to select
199 the appropriate drivers for SCSI, Ethernet and serial ports later
203 bool "BVME4000 and BVME6000 support"
206 Say Y to include support for VME boards from BVM Ltd. This will
207 build a kernel which can run on BVME4000 and BVME6000 boards. If
208 you select this option you will have to select the appropriate
209 drivers for SCSI, Ethernet and serial ports later on.
212 bool "HP9000/300 and HP9000/400 support"
215 This option enables support for the HP9000/300 and HP9000/400 series
216 of workstations. Support for these machines is still somewhat
217 experimental. If you plan to try to use the kernel on such a machine
219 Everybody else says N.
222 bool "DIO bus support"
226 Say Y here to enable support for the "DIO" expansion bus used in
227 HP300 machines. If you are using such a system you almost certainly
235 This option enables support for the Sun 3x series of workstations.
236 Be warned that this support is very experimental.
237 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
238 General Linux information on the Sun 3x series (now discontinued)
239 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
241 If you don't want to compile a kernel for a Sun 3x, say N.
244 bool "Q40/Q60 support"
247 The Q40 is a Motorola 68040-based successor to the Sinclair QL
248 manufactured in Germany. There is an official Q40 home page at
249 <http://www.q40.de/>. This option enables support for the Q40 and
250 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
253 comment "Processor type"
258 If you anticipate running this kernel on a computer with a MC68020
259 processor, say Y. Otherwise, say N. Note that the 68020 requires a
260 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
261 Sun 3, which provides its own version.
267 If you anticipate running this kernel on a computer with a MC68030
268 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
269 work, as it does not include an MMU (Memory Management Unit).
275 If you anticipate running this kernel on a computer with a MC68LC040
276 or MC68040 processor, say Y. Otherwise, say N. Note that an
277 MC68EC040 will not work, as it does not include an MMU (Memory
284 If you anticipate running this kernel on a computer with a MC68060
285 processor, say Y. Otherwise, say N.
289 depends on MMU && !MMU_SUN3
296 bool "Math emulation support (EXPERIMENTAL)"
297 depends on EXPERIMENTAL
299 At some point in the future, this will cause floating-point math
300 instructions to be emulated by the kernel on machines that lack a
301 floating-point math coprocessor. Thrill-seekers and chronically
302 sleep-deprived psychotic hacker types can say Y now, everyone else
303 should probably wait a while.
305 config M68KFPU_EMU_EXTRAPREC
306 bool "Math emulation extra precision"
307 depends on M68KFPU_EMU
309 The fpu uses normally a few bit more during calculations for
310 correct rounding, the emulator can (often) do the same but this
311 extra calculation can cost quite some time, so you can disable
312 it here. The emulator will then "only" calculate with a 64 bit
313 mantissa and round slightly incorrect, what is more then enough
316 config M68KFPU_EMU_ONLY
317 bool "Math emulation only kernel"
318 depends on M68KFPU_EMU
320 This option prevents any floating-point instructions from being
321 compiled into the kernel, thereby the kernel doesn't save any
322 floating point context anymore during task switches, so this
323 kernel will only be usable on machines without a floating-point
324 math coprocessor. This makes the kernel a bit faster as no tests
325 needs to be executed whether a floating-point instruction in the
326 kernel should be executed or not.
329 bool "Advanced configuration options"
331 This gives you access to some advanced options for the CPU. The
332 defaults should be fine for most users, but these options may make
333 it possible for you to improve performance somewhat if you know what
336 Note that the answer to this question won't directly affect the
337 kernel: saying N will just cause the configurator to skip all
338 the questions about these options.
340 Most users should say N to this question.
343 bool "Use read-modify-write instructions"
346 This allows to use certain instructions that work with indivisible
347 read-modify-write bus cycles. While this is faster than the
348 workaround of disabling interrupts, it can conflict with DMA
349 ( = direct memory access) on many Amiga systems, and it is also said
350 to destabilize other machines. It is very likely that this will
351 cause serious problems on any Amiga or Atari Medusa if set. The only
352 configuration where it should work are 68030-based Ataris, where it
353 apparently improves performance. But you've been warned! Unless you
354 really know what you are doing, say N. Try Y only if you're quite
357 config SINGLE_MEMORY_CHUNK
358 bool "Use one physical chunk of memory only"
359 depends on ADVANCED && !SUN3
361 Ignore all but the first contiguous chunk of physical memory for VM
362 purposes. This will save a few bytes kernel size and may speed up
363 some operations. Say N if not sure.
365 config 060_WRITETHROUGH
366 bool "Use write-through caching for 68060 supervisor accesses"
367 depends on ADVANCED && M68060
369 The 68060 generally uses copyback caching of recently accessed data.
370 Copyback caching means that memory writes will be held in an on-chip
371 cache and only written back to memory some time later. Saying Y
372 here will force supervisor (kernel) accesses to use writethrough
373 caching. Writethrough caching means that data is written to memory
374 straight away, so that cache and memory data always agree.
375 Writethrough caching is less efficient, but is needed for some
376 drivers on 68060 based systems where the 68060 bus snooping signal
377 is hardwired on. The 53c710 SCSI driver is known to suffer from
386 source "fs/Kconfig.binfmt"
389 bool "Amiga Zorro (AutoConfig) bus support"
392 This enables support for the Zorro bus in the Amiga. If you have
393 expansion cards in your Amiga that conform to the Amiga
394 AutoConfig(tm) specification, say Y, otherwise N. Note that even
395 expansion cards that do not fit in the Zorro slots but fit in e.g.
396 the CPU slot may fall in this category, so you have to say Y to let
400 bool "Amiga 1200/600 PCMCIA support (EXPERIMENTAL)"
401 depends on AMIGA && EXPERIMENTAL
403 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
404 600. If you intend to use pcmcia cards say Y; otherwise say N.
407 bool "ST-RAM statistics in /proc"
410 Say Y here to report ST-RAM usage statistics in /proc/stram.
412 config ATARI_KBD_CORE
416 bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || MAC ||Q40
417 default y if !AMIGA && !APOLLO && !ATARI && !MAC && !Q40 && HP300
419 Use the power-on LED on your machine as a load meter. The exact
420 behavior is platform-dependent, but normally the flash frequency is
421 a hyperbolic function of the 5-minute load average.
423 # We have a dedicated heartbeat LED. :-)
425 bool "/proc/hardware support"
427 Say Y here to support the /proc/hardware file, which gives you
428 access to information about the machine you're running on,
429 including the model, CPU, MMU, clock speed, BogoMIPS rating,
434 depends on Q40 || AMIGA_PCMCIA || GG2
437 Find out whether you have ISA slots on your motherboard. ISA is the
438 name of a bus system, i.e. the way the CPU talks to the other stuff
439 inside your box. Other bus systems are PCI, EISA, MicroChannel
440 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
441 newer boards don't support it. If you have ISA, say Y, otherwise N.
443 config GENERIC_ISA_DMA
445 depends on Q40 || AMIGA_PCMCIA || GG2
452 source "drivers/pci/Kconfig"
454 source "drivers/zorro/Kconfig"
460 source "drivers/Kconfig"
462 menu "Character devices"
465 tristate "Atari MFP serial support"
468 If you like to use the MFP serial ports ("Modem1", "Serial1") under
469 Linux, say Y. The driver equally supports all kinds of MFP serial
470 ports and automatically detects whether Serial1 is available.
472 To compile this driver as a module, choose M here.
474 Note for Falcon users: You also have an MFP port, it's just not
475 wired to the outside... But you could use the port under Linux.
478 tristate "Atari SCC serial support"
481 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
482 LAN) and like to use them under Linux, say Y. All built-in SCC's are
483 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
484 two connectors for channel A (Serial2 and LAN), they are visible as
485 two separate devices.
487 To compile this driver as a module, choose M here.
490 bool "Atari SCC serial DMA support"
493 This enables DMA support for receiving data on channel A of the SCC.
494 If you have a TT you may say Y here and read
495 drivers/char/atari_SCC.README. All other users should say N here,
496 because only the TT has SCC-DMA, even if your machine keeps claiming
500 tristate "Atari MIDI serial support"
503 If you want to use your Atari's MIDI port in Linux, say Y.
505 To compile this driver as a module, choose M here.
508 tristate "Atari DSP56k support (EXPERIMENTAL)"
509 depends on ATARI && EXPERIMENTAL
511 If you want to be able to use the DSP56001 in Falcons, say Y. This
512 driver is still experimental, and if you don't know what it is, or
513 if you don't have this processor, just say N.
515 To compile this driver as a module, choose M here.
517 config AMIGA_BUILTIN_SERIAL
518 tristate "Amiga builtin serial support"
521 If you want to use your Amiga's built-in serial port in Linux,
524 To compile this driver as a module, choose M here.
526 config WHIPPET_SERIAL
527 tristate "Hisoft Whippet PCMCIA serial support"
528 depends on AMIGA_PCMCIA
530 HiSoft has a web page at <http://www.hisoft.co.uk/>, but there
531 is no listing for the Whippet in their Amiga section.
533 config MULTIFACE_III_TTY
534 tristate "Multiface Card III serial support"
537 If you want to use a Multiface III card's serial port in Linux,
540 To compile this driver as a module, choose M here.
543 tristate "GVP IO-Extender support"
544 depends on PARPORT=n && ZORRO
546 If you want to use a GVP IO-Extender serial card in Linux, say Y.
550 tristate "GVP IO-Extender parallel printer support"
553 Say Y to enable driving a printer from the parallel port on your
554 GVP IO-Extender card, N otherwise.
557 tristate "GVP IO-Extender PLIP support"
560 Say Y to enable doing IP over the parallel port on your GVP
561 IO-Extender card, N otherwise.
564 tristate "Macintosh serial support"
569 depends on INPUT_ADBHID
572 config MAC_ADBKEYCODES
573 bool "Support for ADB raw keycodes"
574 depends on INPUT_ADBHID
576 This provides support for sending raw ADB keycodes to console
577 devices. This is the default up to 2.4.0, but in future this may be
578 phased out in favor of generic Linux keycodes. If you say Y here,
579 you can dynamically switch via the
580 /proc/sys/dev/mac_hid/keyboard_sends_linux_keycodes
581 sysctl and with the "keyboard_sends_linux_keycodes=" kernel
584 If unsure, say Y here.
587 bool "Support for ADB keyboard (old driver)"
588 depends on MAC && !INPUT_ADBHID
590 This option allows you to use an ADB keyboard attached to your
591 machine. Note that this disables any other (ie. PS/2) keyboard
592 support, even if your machine is physically capable of using both at
595 If you use an ADB keyboard (4 pin connector), say Y here.
596 If you use a PS/2 keyboard (6 pin connector), say N here.
599 tristate "HP DCA serial support"
600 depends on DIO && SERIAL_8250
602 If you want to use the internal "DCA" serial ports on an HP300
606 tristate "HP APCI serial support"
607 depends on HP300 && SERIAL_8250 && EXPERIMENTAL
609 If you want to use the internal "APCI" serial ports on an HP400
613 bool "SCC support for MVME147 serial ports"
616 This is the driver for the serial ports on the Motorola MVME147
617 boards. Everyone using one of these boards should say Y here.
620 bool "CD2401 support for MVME166/7 serial ports"
623 This is the driver for the serial ports on the Motorola MVME166,
624 167, and 172 boards. Everyone using one of these boards should say
628 bool "SCC support for MVME162 serial ports"
631 This is the driver for the serial ports on the Motorola MVME162 and
632 172 boards. Everyone using one of these boards should say Y here.
635 bool "SCC support for BVME6000 serial ports"
638 This is the driver for the serial ports on the BVME4000 and BVME6000
639 boards from BVM Ltd. Everyone using one of these boards should say
643 bool "Support for DN serial port (dummy)"
646 config SERIAL_CONSOLE
647 bool "Support for serial port console"
648 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)
650 If you say Y here, it will be possible to use a serial port as the
651 system console (the system console is the device which receives all
652 kernel messages and warnings and which allows logins in single user
653 mode). This could be useful if some terminal or printer is connected
656 Even if you say Y here, the currently visible virtual console
657 (/dev/tty0) will still be used as the system console by default, but
658 you can alter that using a kernel command line option such as
659 "console=ttyS1". (Try "man bootparam" or see the documentation of
660 your boot loader (lilo or loadlin) about how to pass options to the
661 kernel at boot time.)
663 If you don't have a VGA card installed and you say Y here, the
664 kernel will automatically use the first serial line, /dev/ttyS0, as
673 source "arch/m68k/Kconfig.debug"
675 source "security/Kconfig"
677 source "crypto/Kconfig"