6 select GENERIC_ATOMIC64
12 config RWSEM_GENERIC_SPINLOCK
16 config RWSEM_XCHGADD_ALGORITHM
19 config ARCH_HAS_ILOG2_U32
22 config ARCH_HAS_ILOG2_U64
25 config GENERIC_HWEIGHT
29 config GENERIC_CALIBRATE_DELAY
41 config ARCH_MAY_HAVE_PC_FDC
43 depends on BROKEN && (Q40 || SUN3X)
56 config ARCH_USES_GETTIMEOFFSET
61 source "kernel/Kconfig.freezer"
63 menu "Platform dependent setup"
68 The Extended Industry Standard Architecture (EISA) bus was
69 developed as an open alternative to the IBM MicroChannel bus.
71 The EISA bus provided some of the features of the IBM MicroChannel
72 bus while maintaining backward compatibility with cards made for
73 the older ISA bus. The EISA bus saw limited use between 1988 and
74 1995 when it was made obsolete by the PCI bus.
76 Say Y here if you are building a kernel for an EISA-based machine.
83 MicroChannel Architecture is found in some IBM PS/2 machines and
84 laptops. It is a bus system similar to PCI or ISA. See
85 <file:Documentation/mca.txt> (and especially the web page given
86 there) before attempting to build an MCA bus kernel.
91 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
92 computer. These are credit-card size devices such as network cards,
93 modems or hard drives often used with laptops computers. There are
94 actually two varieties of these cards: the older 16 bit PCMCIA cards
95 and the newer 32 bit CardBus cards. If you want to use CardBus
96 cards, you need to say Y here and also to "CardBus support" below.
98 To use your PC-cards, you will need supporting software from David
99 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
100 for location). Please also read the PCMCIA-HOWTO, available from
101 <http://www.tldp.org/docs.html#howto>.
103 To compile this driver as modules, choose M here: the
104 modules will be called pcmcia_core and ds.
108 select MMU_MOTOROLA if MMU
110 This option enables support for the Amiga series of computers. If
111 you plan to use this kernel on an Amiga, say Y here and browse the
112 material available in <file:Documentation/m68k>; otherwise say N.
116 select MMU_MOTOROLA if MMU
118 This option enables support for the 68000-based Atari series of
119 computers (including the TT, Falcon and Medusa). If you plan to use
120 this kernel on an Atari, say Y here and browse the material
121 available in <file:Documentation/m68k>; otherwise say N.
124 bool "Macintosh support"
125 select MMU_MOTOROLA if MMU
127 This option enables support for the Apple Macintosh series of
128 computers (yes, there is experimental support now, at least for part
131 Say N unless you're willing to code the remaining necessary support.
145 bool "Apollo support"
146 select MMU_MOTOROLA if MMU
148 Say Y here if you want to run Linux on an MC680x0-based Apollo
149 Domain workstation such as the DN3500.
152 bool "VME (Motorola and BVM) support"
153 select MMU_MOTOROLA if MMU
155 Say Y here if you want to build a kernel for a 680x0 based VME
156 board. Boards currently supported include Motorola boards MVME147,
157 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
158 BVME6000 boards from BVM Ltd are also supported.
161 bool "MVME147 support"
164 Say Y to include support for early Motorola VME boards. This will
165 build a kernel which can run on MVME147 single-board computers. If
166 you select this option you will have to select the appropriate
167 drivers for SCSI, Ethernet and serial ports later on.
170 bool "MVME162, 166 and 167 support"
173 Say Y to include support for Motorola VME boards. This will build a
174 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
175 MVME177 boards. If you select this option you will have to select
176 the appropriate drivers for SCSI, Ethernet and serial ports later
180 bool "BVME4000 and BVME6000 support"
183 Say Y to include support for VME boards from BVM Ltd. This will
184 build a kernel which can run on BVME4000 and BVME6000 boards. If
185 you select this option you will have to select the appropriate
186 drivers for SCSI, Ethernet and serial ports later on.
189 bool "HP9000/300 and HP9000/400 support"
190 select MMU_MOTOROLA if MMU
192 This option enables support for the HP9000/300 and HP9000/400 series
193 of workstations. Support for these machines is still somewhat
194 experimental. If you plan to try to use the kernel on such a machine
196 Everybody else says N.
199 bool "DIO bus support"
203 Say Y here to enable support for the "DIO" expansion bus used in
204 HP300 machines. If you are using such a system you almost certainly
209 select MMU_MOTOROLA if MMU
212 This option enables support for the Sun 3x series of workstations.
213 Be warned that this support is very experimental.
214 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
215 General Linux information on the Sun 3x series (now discontinued)
216 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
218 If you don't want to compile a kernel for a Sun 3x, say N.
221 bool "Q40/Q60 support"
222 select MMU_MOTOROLA if MMU
224 The Q40 is a Motorola 68040-based successor to the Sinclair QL
225 manufactured in Germany. There is an official Q40 home page at
226 <http://www.q40.de/>. This option enables support for the Q40 and
227 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
232 depends on !MMU_MOTOROLA
233 select MMU_SUN3 if MMU
236 This option enables support for the Sun 3 series of workstations
237 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
238 that all other hardware types must be disabled, as Sun 3 kernels
239 are incompatible with all other m68k targets (including Sun 3x!).
241 If you don't want to compile a kernel exclusively for a Sun 3, say N.
244 bool "ARAnyM emulator support"
247 This option enables support for ARAnyM native features, such as
248 access to a disk image as /dev/hda.
251 tristate "NatFeat block device support"
252 depends on BLOCK && NATFEAT
254 Say Y to include support for the ARAnyM NatFeat block device
255 which allows direct access to the hard drives without using
256 the hardware emulation.
258 comment "Processor type"
263 If you anticipate running this kernel on a computer with a MC68020
264 processor, say Y. Otherwise, say N. Note that the 68020 requires a
265 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
266 Sun 3, which provides its own version.
272 If you anticipate running this kernel on a computer with a MC68030
273 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
274 work, as it does not include an MMU (Memory Management Unit).
280 If you anticipate running this kernel on a computer with a MC68LC040
281 or MC68040 processor, say Y. Otherwise, say N. Note that an
282 MC68EC040 will not work, as it does not include an MMU (Memory
289 If you anticipate running this kernel on a computer with a MC68060
290 processor, say Y. Otherwise, say N.
297 depends on MMU && !MMU_MOTOROLA
300 bool "Math emulation support (EXPERIMENTAL)"
301 depends on EXPERIMENTAL
303 At some point in the future, this will cause floating-point math
304 instructions to be emulated by the kernel on machines that lack a
305 floating-point math coprocessor. Thrill-seekers and chronically
306 sleep-deprived psychotic hacker types can say Y now, everyone else
307 should probably wait a while.
309 config M68KFPU_EMU_EXTRAPREC
310 bool "Math emulation extra precision"
311 depends on M68KFPU_EMU
313 The fpu uses normally a few bit more during calculations for
314 correct rounding, the emulator can (often) do the same but this
315 extra calculation can cost quite some time, so you can disable
316 it here. The emulator will then "only" calculate with a 64 bit
317 mantissa and round slightly incorrect, what is more than enough
320 config M68KFPU_EMU_ONLY
321 bool "Math emulation only kernel"
322 depends on M68KFPU_EMU
324 This option prevents any floating-point instructions from being
325 compiled into the kernel, thereby the kernel doesn't save any
326 floating point context anymore during task switches, so this
327 kernel will only be usable on machines without a floating-point
328 math coprocessor. This makes the kernel a bit faster as no tests
329 needs to be executed whether a floating-point instruction in the
330 kernel should be executed or not.
333 bool "Advanced configuration options"
335 This gives you access to some advanced options for the CPU. The
336 defaults should be fine for most users, but these options may make
337 it possible for you to improve performance somewhat if you know what
340 Note that the answer to this question won't directly affect the
341 kernel: saying N will just cause the configurator to skip all
342 the questions about these options.
344 Most users should say N to this question.
347 bool "Use read-modify-write instructions"
350 This allows to use certain instructions that work with indivisible
351 read-modify-write bus cycles. While this is faster than the
352 workaround of disabling interrupts, it can conflict with DMA
353 ( = direct memory access) on many Amiga systems, and it is also said
354 to destabilize other machines. It is very likely that this will
355 cause serious problems on any Amiga or Atari Medusa if set. The only
356 configuration where it should work are 68030-based Ataris, where it
357 apparently improves performance. But you've been warned! Unless you
358 really know what you are doing, say N. Try Y only if you're quite
361 config SINGLE_MEMORY_CHUNK
362 bool "Use one physical chunk of memory only" if ADVANCED && !SUN3
364 select NEED_MULTIPLE_NODES
366 Ignore all but the first contiguous chunk of physical memory for VM
367 purposes. This will save a few bytes kernel size and may speed up
368 some operations. Say N if not sure.
370 config 060_WRITETHROUGH
371 bool "Use write-through caching for 68060 supervisor accesses"
372 depends on ADVANCED && M68060
374 The 68060 generally uses copyback caching of recently accessed data.
375 Copyback caching means that memory writes will be held in an on-chip
376 cache and only written back to memory some time later. Saying Y
377 here will force supervisor (kernel) accesses to use writethrough
378 caching. Writethrough caching means that data is written to memory
379 straight away, so that cache and memory data always agree.
380 Writethrough caching is less efficient, but is needed for some
381 drivers on 68060 based systems where the 68060 bus snooping signal
382 is hardwired on. The 53c710 SCSI driver is known to suffer from
385 config ARCH_DISCONTIGMEM_ENABLE
386 def_bool !SINGLE_MEMORY_CHUNK
391 depends on !SINGLE_MEMORY_CHUNK
399 source "fs/Kconfig.binfmt"
402 bool "Amiga Zorro (AutoConfig) bus support"
405 This enables support for the Zorro bus in the Amiga. If you have
406 expansion cards in your Amiga that conform to the Amiga
407 AutoConfig(tm) specification, say Y, otherwise N. Note that even
408 expansion cards that do not fit in the Zorro slots but fit in e.g.
409 the CPU slot may fall in this category, so you have to say Y to let
413 bool "Amiga 1200/600 PCMCIA support (EXPERIMENTAL)"
414 depends on AMIGA && EXPERIMENTAL
416 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
417 600. If you intend to use pcmcia cards say Y; otherwise say N.
420 bool "ST-RAM statistics in /proc"
423 Say Y here to report ST-RAM usage statistics in /proc/stram.
426 bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || MAC ||Q40
427 default y if !AMIGA && !APOLLO && !ATARI && !MAC && !Q40 && HP300
429 Use the power-on LED on your machine as a load meter. The exact
430 behavior is platform-dependent, but normally the flash frequency is
431 a hyperbolic function of the 5-minute load average.
433 # We have a dedicated heartbeat LED. :-)
435 bool "/proc/hardware support"
437 Say Y here to support the /proc/hardware file, which gives you
438 access to information about the machine you're running on,
439 including the model, CPU, MMU, clock speed, BogoMIPS rating,
444 depends on Q40 || AMIGA_PCMCIA
447 Find out whether you have ISA slots on your motherboard. ISA is the
448 name of a bus system, i.e. the way the CPU talks to the other stuff
449 inside your box. Other bus systems are PCI, EISA, MicroChannel
450 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
451 newer boards don't support it. If you have ISA, say Y, otherwise N.
453 config GENERIC_ISA_DMA
455 depends on Q40 || AMIGA_PCMCIA
462 source "drivers/pci/Kconfig"
464 source "drivers/zorro/Kconfig"
470 source "drivers/Kconfig"
472 menu "Character devices"
475 tristate "Atari MFP serial support"
478 If you like to use the MFP serial ports ("Modem1", "Serial1") under
479 Linux, say Y. The driver equally supports all kinds of MFP serial
480 ports and automatically detects whether Serial1 is available.
482 To compile this driver as a module, choose M here.
484 Note for Falcon users: You also have an MFP port, it's just not
485 wired to the outside... But you could use the port under Linux.
488 tristate "Atari MIDI serial support"
491 If you want to use your Atari's MIDI port in Linux, say Y.
493 To compile this driver as a module, choose M here.
496 tristate "Atari DSP56k support (EXPERIMENTAL)"
497 depends on ATARI && EXPERIMENTAL
499 If you want to be able to use the DSP56001 in Falcons, say Y. This
500 driver is still experimental, and if you don't know what it is, or
501 if you don't have this processor, just say N.
503 To compile this driver as a module, choose M here.
505 config AMIGA_BUILTIN_SERIAL
506 tristate "Amiga builtin serial support"
509 If you want to use your Amiga's built-in serial port in Linux,
512 To compile this driver as a module, choose M here.
514 config MULTIFACE_III_TTY
515 tristate "Multiface Card III serial support"
518 If you want to use a Multiface III card's serial port in Linux,
521 To compile this driver as a module, choose M here.
524 tristate "GVP IO-Extender support"
525 depends on PARPORT=n && ZORRO
527 If you want to use a GVP IO-Extender serial card in Linux, say Y.
531 tristate "GVP IO-Extender parallel printer support"
534 Say Y to enable driving a printer from the parallel port on your
535 GVP IO-Extender card, N otherwise.
538 tristate "GVP IO-Extender PLIP support"
541 Say Y to enable doing IP over the parallel port on your GVP
542 IO-Extender card, N otherwise.
546 depends on INPUT_ADBHID
550 tristate "HP DCA serial support"
551 depends on DIO && SERIAL_8250
553 If you want to use the internal "DCA" serial ports on an HP300
557 tristate "HP APCI serial support"
558 depends on HP300 && SERIAL_8250 && EXPERIMENTAL
560 If you want to use the internal "APCI" serial ports on an HP400
564 bool "SCC support for MVME147 serial ports"
565 depends on MVME147 && BROKEN
567 This is the driver for the serial ports on the Motorola MVME147
568 boards. Everyone using one of these boards should say Y here.
571 bool "CD2401 support for MVME166/7 serial ports"
574 This is the driver for the serial ports on the Motorola MVME166,
575 167, and 172 boards. Everyone using one of these boards should say
579 bool "SCC support for MVME162 serial ports"
580 depends on MVME16x && BROKEN
582 This is the driver for the serial ports on the Motorola MVME162 and
583 172 boards. Everyone using one of these boards should say Y here.
586 bool "SCC support for BVME6000 serial ports"
587 depends on BVME6000 && BROKEN
589 This is the driver for the serial ports on the BVME4000 and BVME6000
590 boards from BVM Ltd. Everyone using one of these boards should say
594 bool "Support for DN serial port (dummy)"
597 config SERIAL_CONSOLE
598 bool "Support for serial port console"
599 depends on (AMIGA || ATARI || SUN3 || SUN3X || VME || APOLLO) && (ATARI_MFPSER=y || ATARI_MIDI=y || AMIGA_BUILTIN_SERIAL=y || GVPIOEXT=y || MULTIFACE_III_TTY=y || SERIAL=y || MVME147_SCC || SERIAL167 || MVME162_SCC || BVME6000_SCC || DN_SERIAL)
601 If you say Y here, it will be possible to use a serial port as the
602 system console (the system console is the device which receives all
603 kernel messages and warnings and which allows logins in single user
604 mode). This could be useful if some terminal or printer is connected
607 Even if you say Y here, the currently visible virtual console
608 (/dev/tty0) will still be used as the system console by default, but
609 you can alter that using a kernel command line option such as
610 "console=ttyS1". (Try "man bootparam" or see the documentation of
611 your boot loader (lilo or loadlin) about how to pass options to the
612 kernel at boot time.)
614 If you don't have a VGA card installed and you say Y here, the
615 kernel will automatically use the first serial line, /dev/ttyS0, as
624 source "arch/m68k/Kconfig.debug"
626 source "security/Kconfig"
628 source "crypto/Kconfig"