2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
15 config RWSEM_GENERIC_SPINLOCK
19 config RWSEM_XCHGADD_ALGORITHM
22 config ARCH_HAS_ILOG2_U32
26 config ARCH_HAS_ILOG2_U64
30 config GENERIC_HWEIGHT
34 config GENERIC_CALIBRATE_DELAY
46 config ARCH_MAY_HAVE_PC_FDC
48 depends on BROKEN && (Q40 || SUN3X)
61 mainmenu "Linux/68k Kernel Configuration"
65 menu "Platform dependent setup"
70 The Extended Industry Standard Architecture (EISA) bus was
71 developed as an open alternative to the IBM MicroChannel bus.
73 The EISA bus provided some of the features of the IBM MicroChannel
74 bus while maintaining backward compatibility with cards made for
75 the older ISA bus. The EISA bus saw limited use between 1988 and
76 1995 when it was made obsolete by the PCI bus.
78 Say Y here if you are building a kernel for an EISA-based machine.
85 MicroChannel Architecture is found in some IBM PS/2 machines and
86 laptops. It is a bus system similar to PCI or ISA. See
87 <file:Documentation/mca.txt> (and especially the web page given
88 there) before attempting to build an MCA bus kernel.
93 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
94 computer. These are credit-card size devices such as network cards,
95 modems or hard drives often used with laptops computers. There are
96 actually two varieties of these cards: the older 16 bit PCMCIA cards
97 and the newer 32 bit CardBus cards. If you want to use CardBus
98 cards, you need to say Y here and also to "CardBus support" below.
100 To use your PC-cards, you will need supporting software from David
101 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
102 for location). Please also read the PCMCIA-HOWTO, available from
103 <http://www.tldp.org/docs.html#howto>.
105 To compile this driver as modules, choose M here: the
106 modules will be called pcmcia_core and ds.
110 select MMU_MOTOROLA if MMU
112 This option enables support for the Amiga series of computers. If
113 you plan to use this kernel on an Amiga, say Y here and browse the
114 material available in <file:Documentation/m68k>; otherwise say N.
118 select MMU_MOTOROLA if MMU
120 This option enables support for the 68000-based Atari series of
121 computers (including the TT, Falcon and Medusa). If you plan to use
122 this kernel on an Atari, say Y here and browse the material
123 available in <file:Documentation/m68k>; otherwise say N.
130 bool "Macintosh support"
131 select MMU_MOTOROLA if MMU
133 This option enables support for the Apple Macintosh series of
134 computers (yes, there is experimental support now, at least for part
137 Say N unless you're willing to code the remaining necessary support.
151 bool "Apollo support"
152 select MMU_MOTOROLA if MMU
154 Say Y here if you want to run Linux on an MC680x0-based Apollo
155 Domain workstation such as the DN3500.
158 bool "VME (Motorola and BVM) support"
159 select MMU_MOTOROLA if MMU
161 Say Y here if you want to build a kernel for a 680x0 based VME
162 board. Boards currently supported include Motorola boards MVME147,
163 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
164 BVME6000 boards from BVM Ltd are also supported.
167 bool "MVME147 support"
170 Say Y to include support for early Motorola VME boards. This will
171 build a kernel which can run on MVME147 single-board computers. If
172 you select this option you will have to select the appropriate
173 drivers for SCSI, Ethernet and serial ports later on.
176 bool "MVME162, 166 and 167 support"
179 Say Y to include support for Motorola VME boards. This will build a
180 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
181 MVME177 boards. If you select this option you will have to select
182 the appropriate drivers for SCSI, Ethernet and serial ports later
186 bool "BVME4000 and BVME6000 support"
189 Say Y to include support for VME boards from BVM Ltd. This will
190 build a kernel which can run on BVME4000 and BVME6000 boards. 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 "HP9000/300 and HP9000/400 support"
196 select MMU_MOTOROLA if MMU
198 This option enables support for the HP9000/300 and HP9000/400 series
199 of workstations. Support for these machines is still somewhat
200 experimental. If you plan to try to use the kernel on such a machine
202 Everybody else says N.
205 bool "DIO bus support"
209 Say Y here to enable support for the "DIO" expansion bus used in
210 HP300 machines. If you are using such a system you almost certainly
215 select MMU_MOTOROLA if MMU
218 This option enables support for the Sun 3x series of workstations.
219 Be warned that this support is very experimental.
220 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
221 General Linux information on the Sun 3x series (now discontinued)
222 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
224 If you don't want to compile a kernel for a Sun 3x, say N.
227 bool "Q40/Q60 support"
228 select MMU_MOTOROLA if MMU
230 The Q40 is a Motorola 68040-based successor to the Sinclair QL
231 manufactured in Germany. There is an official Q40 home page at
232 <http://www.q40.de/>. This option enables support for the Q40 and
233 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
238 depends on !MMU_MOTOROLA
239 select MMU_SUN3 if MMU
242 This option enables support for the Sun 3 series of workstations
243 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
244 that all other hardware types must be disabled, as Sun 3 kernels
245 are incompatible with all other m68k targets (including Sun 3x!).
247 If you don't want to compile a kernel exclusively for a Sun 3, say N.
249 comment "Processor type"
254 If you anticipate running this kernel on a computer with a MC68020
255 processor, say Y. Otherwise, say N. Note that the 68020 requires a
256 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
257 Sun 3, which provides its own version.
263 If you anticipate running this kernel on a computer with a MC68030
264 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
265 work, as it does not include an MMU (Memory Management Unit).
271 If you anticipate running this kernel on a computer with a MC68LC040
272 or MC68040 processor, say Y. Otherwise, say N. Note that an
273 MC68EC040 will not work, as it does not include an MMU (Memory
280 If you anticipate running this kernel on a computer with a MC68060
281 processor, say Y. Otherwise, say N.
285 depends on MMU && !MMU_SUN3
289 depends on MMU && !MMU_MOTOROLA
292 bool "Math emulation support (EXPERIMENTAL)"
293 depends on EXPERIMENTAL
295 At some point in the future, this will cause floating-point math
296 instructions to be emulated by the kernel on machines that lack a
297 floating-point math coprocessor. Thrill-seekers and chronically
298 sleep-deprived psychotic hacker types can say Y now, everyone else
299 should probably wait a while.
301 config M68KFPU_EMU_EXTRAPREC
302 bool "Math emulation extra precision"
303 depends on M68KFPU_EMU
305 The fpu uses normally a few bit more during calculations for
306 correct rounding, the emulator can (often) do the same but this
307 extra calculation can cost quite some time, so you can disable
308 it here. The emulator will then "only" calculate with a 64 bit
309 mantissa and round slightly incorrect, what is more then enough
312 config M68KFPU_EMU_ONLY
313 bool "Math emulation only kernel"
314 depends on M68KFPU_EMU
316 This option prevents any floating-point instructions from being
317 compiled into the kernel, thereby the kernel doesn't save any
318 floating point context anymore during task switches, so this
319 kernel will only be usable on machines without a floating-point
320 math coprocessor. This makes the kernel a bit faster as no tests
321 needs to be executed whether a floating-point instruction in the
322 kernel should be executed or not.
325 bool "Advanced configuration options"
327 This gives you access to some advanced options for the CPU. The
328 defaults should be fine for most users, but these options may make
329 it possible for you to improve performance somewhat if you know what
332 Note that the answer to this question won't directly affect the
333 kernel: saying N will just cause the configurator to skip all
334 the questions about these options.
336 Most users should say N to this question.
339 bool "Use read-modify-write instructions"
342 This allows to use certain instructions that work with indivisible
343 read-modify-write bus cycles. While this is faster than the
344 workaround of disabling interrupts, it can conflict with DMA
345 ( = direct memory access) on many Amiga systems, and it is also said
346 to destabilize other machines. It is very likely that this will
347 cause serious problems on any Amiga or Atari Medusa if set. The only
348 configuration where it should work are 68030-based Ataris, where it
349 apparently improves performance. But you've been warned! Unless you
350 really know what you are doing, say N. Try Y only if you're quite
353 config SINGLE_MEMORY_CHUNK
354 bool "Use one physical chunk of memory only" if ADVANCED && !SUN3
356 select NEED_MULTIPLE_NODES
358 Ignore all but the first contiguous chunk of physical memory for VM
359 purposes. This will save a few bytes kernel size and may speed up
360 some operations. Say N if not sure.
362 config 060_WRITETHROUGH
363 bool "Use write-through caching for 68060 supervisor accesses"
364 depends on ADVANCED && M68060
366 The 68060 generally uses copyback caching of recently accessed data.
367 Copyback caching means that memory writes will be held in an on-chip
368 cache and only written back to memory some time later. Saying Y
369 here will force supervisor (kernel) accesses to use writethrough
370 caching. Writethrough caching means that data is written to memory
371 straight away, so that cache and memory data always agree.
372 Writethrough caching is less efficient, but is needed for some
373 drivers on 68060 based systems where the 68060 bus snooping signal
374 is hardwired on. The 53c710 SCSI driver is known to suffer from
377 config ARCH_DISCONTIGMEM_ENABLE
378 def_bool !SINGLE_MEMORY_CHUNK
383 depends on !SINGLE_MEMORY_CHUNK
391 source "fs/Kconfig.binfmt"
394 bool "Amiga Zorro (AutoConfig) bus support"
397 This enables support for the Zorro bus in the Amiga. If you have
398 expansion cards in your Amiga that conform to the Amiga
399 AutoConfig(tm) specification, say Y, otherwise N. Note that even
400 expansion cards that do not fit in the Zorro slots but fit in e.g.
401 the CPU slot may fall in this category, so you have to say Y to let
405 bool "Amiga 1200/600 PCMCIA support (EXPERIMENTAL)"
406 depends on AMIGA && EXPERIMENTAL
408 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
409 600. If you intend to use pcmcia cards say Y; otherwise say N.
412 bool "ST-RAM statistics in /proc"
415 Say Y here to report ST-RAM usage statistics in /proc/stram.
418 bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || MAC ||Q40
419 default y if !AMIGA && !APOLLO && !ATARI && !MAC && !Q40 && HP300
421 Use the power-on LED on your machine as a load meter. The exact
422 behavior is platform-dependent, but normally the flash frequency is
423 a hyperbolic function of the 5-minute load average.
425 # We have a dedicated heartbeat LED. :-)
427 bool "/proc/hardware support"
429 Say Y here to support the /proc/hardware file, which gives you
430 access to information about the machine you're running on,
431 including the model, CPU, MMU, clock speed, BogoMIPS rating,
436 depends on Q40 || AMIGA_PCMCIA || GG2
439 Find out whether you have ISA slots on your motherboard. ISA is the
440 name of a bus system, i.e. the way the CPU talks to the other stuff
441 inside your box. Other bus systems are PCI, EISA, MicroChannel
442 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
443 newer boards don't support it. If you have ISA, say Y, otherwise N.
445 config GENERIC_ISA_DMA
447 depends on Q40 || AMIGA_PCMCIA || GG2
454 source "drivers/pci/Kconfig"
456 source "drivers/zorro/Kconfig"
462 source "drivers/Kconfig"
464 menu "Character devices"
467 tristate "Atari MFP serial support"
470 If you like to use the MFP serial ports ("Modem1", "Serial1") under
471 Linux, say Y. The driver equally supports all kinds of MFP serial
472 ports and automatically detects whether Serial1 is available.
474 To compile this driver as a module, choose M here.
476 Note for Falcon users: You also have an MFP port, it's just not
477 wired to the outside... But you could use the port under Linux.
480 tristate "Atari MIDI serial support"
483 If you want to use your Atari's MIDI port in Linux, say Y.
485 To compile this driver as a module, choose M here.
488 tristate "Atari DSP56k support (EXPERIMENTAL)"
489 depends on ATARI && EXPERIMENTAL
491 If you want to be able to use the DSP56001 in Falcons, say Y. This
492 driver is still experimental, and if you don't know what it is, or
493 if you don't have this processor, just say N.
495 To compile this driver as a module, choose M here.
497 config AMIGA_BUILTIN_SERIAL
498 tristate "Amiga builtin serial support"
501 If you want to use your Amiga's built-in serial port in Linux,
504 To compile this driver as a module, choose M here.
506 config MULTIFACE_III_TTY
507 tristate "Multiface Card III serial support"
510 If you want to use a Multiface III card's serial port in Linux,
513 To compile this driver as a module, choose M here.
516 tristate "GVP IO-Extender support"
517 depends on PARPORT=n && ZORRO
519 If you want to use a GVP IO-Extender serial card in Linux, say Y.
523 tristate "GVP IO-Extender parallel printer support"
526 Say Y to enable driving a printer from the parallel port on your
527 GVP IO-Extender card, N otherwise.
530 tristate "GVP IO-Extender PLIP support"
533 Say Y to enable doing IP over the parallel port on your GVP
534 IO-Extender card, N otherwise.
537 tristate "Macintosh serial support"
542 depends on INPUT_ADBHID
546 tristate "HP DCA serial support"
547 depends on DIO && SERIAL_8250
549 If you want to use the internal "DCA" serial ports on an HP300
553 tristate "HP APCI serial support"
554 depends on HP300 && SERIAL_8250 && EXPERIMENTAL
556 If you want to use the internal "APCI" serial ports on an HP400
560 bool "SCC support for MVME147 serial ports"
563 This is the driver for the serial ports on the Motorola MVME147
564 boards. Everyone using one of these boards should say Y here.
567 bool "CD2401 support for MVME166/7 serial ports"
570 This is the driver for the serial ports on the Motorola MVME166,
571 167, and 172 boards. Everyone using one of these boards should say
575 bool "SCC support for MVME162 serial ports"
578 This is the driver for the serial ports on the Motorola MVME162 and
579 172 boards. Everyone using one of these boards should say Y here.
582 bool "SCC support for BVME6000 serial ports"
585 This is the driver for the serial ports on the BVME4000 and BVME6000
586 boards from BVM Ltd. Everyone using one of these boards should say
590 bool "Support for DN serial port (dummy)"
593 config SERIAL_CONSOLE
594 bool "Support for serial port console"
595 depends on (AMIGA || ATARI || MAC || SUN3 || SUN3X || VME || APOLLO) && (ATARI_MFPSER=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)
597 If you say Y here, it will be possible to use a serial port as the
598 system console (the system console is the device which receives all
599 kernel messages and warnings and which allows logins in single user
600 mode). This could be useful if some terminal or printer is connected
603 Even if you say Y here, the currently visible virtual console
604 (/dev/tty0) will still be used as the system console by default, but
605 you can alter that using a kernel command line option such as
606 "console=ttyS1". (Try "man bootparam" or see the documentation of
607 your boot loader (lilo or loadlin) about how to pass options to the
608 kernel at boot time.)
610 If you don't have a VGA card installed and you say Y here, the
611 kernel will automatically use the first serial line, /dev/ttyS0, as
620 source "arch/m68k/Kconfig.debug"
622 source "security/Kconfig"
624 source "crypto/Kconfig"