6 select GENERIC_ATOMIC64
12 config RWSEM_GENERIC_SPINLOCK
16 config RWSEM_XCHGADD_ALGORITHM
19 config ARCH_HAS_ILOG2_U32
23 config ARCH_HAS_ILOG2_U64
27 config GENERIC_HWEIGHT
31 config GENERIC_CALIBRATE_DELAY
43 config ARCH_MAY_HAVE_PC_FDC
45 depends on BROKEN && (Q40 || SUN3X)
61 config ARCH_USES_GETTIMEOFFSET
66 source "kernel/Kconfig.freezer"
68 menu "Platform dependent setup"
73 The Extended Industry Standard Architecture (EISA) bus was
74 developed as an open alternative to the IBM MicroChannel bus.
76 The EISA bus provided some of the features of the IBM MicroChannel
77 bus while maintaining backward compatibility with cards made for
78 the older ISA bus. The EISA bus saw limited use between 1988 and
79 1995 when it was made obsolete by the PCI bus.
81 Say Y here if you are building a kernel for an EISA-based machine.
88 MicroChannel Architecture is found in some IBM PS/2 machines and
89 laptops. It is a bus system similar to PCI or ISA. See
90 <file:Documentation/mca.txt> (and especially the web page given
91 there) before attempting to build an MCA bus kernel.
96 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
97 computer. These are credit-card size devices such as network cards,
98 modems or hard drives often used with laptops computers. There are
99 actually two varieties of these cards: the older 16 bit PCMCIA cards
100 and the newer 32 bit CardBus cards. If you want to use CardBus
101 cards, you need to say Y here and also to "CardBus support" below.
103 To use your PC-cards, you will need supporting software from David
104 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
105 for location). Please also read the PCMCIA-HOWTO, available from
106 <http://www.tldp.org/docs.html#howto>.
108 To compile this driver as modules, choose M here: the
109 modules will be called pcmcia_core and ds.
113 select MMU_MOTOROLA if MMU
115 This option enables support for the Amiga series of computers. If
116 you plan to use this kernel on an Amiga, say Y here and browse the
117 material available in <file:Documentation/m68k>; otherwise say N.
121 select MMU_MOTOROLA if MMU
123 This option enables support for the 68000-based Atari series of
124 computers (including the TT, Falcon and Medusa). If you plan to use
125 this kernel on an Atari, say Y here and browse the material
126 available in <file:Documentation/m68k>; otherwise say N.
129 bool "Macintosh support"
130 select MMU_MOTOROLA if MMU
132 This option enables support for the Apple Macintosh series of
133 computers (yes, there is experimental support now, at least for part
136 Say N unless you're willing to code the remaining necessary support.
150 bool "Apollo support"
151 select MMU_MOTOROLA if MMU
153 Say Y here if you want to run Linux on an MC680x0-based Apollo
154 Domain workstation such as the DN3500.
157 bool "VME (Motorola and BVM) support"
158 select MMU_MOTOROLA if MMU
160 Say Y here if you want to build a kernel for a 680x0 based VME
161 board. Boards currently supported include Motorola boards MVME147,
162 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
163 BVME6000 boards from BVM Ltd are also supported.
166 bool "MVME147 support"
169 Say Y to include support for early Motorola VME boards. This will
170 build a kernel which can run on MVME147 single-board computers. If
171 you select this option you will have to select the appropriate
172 drivers for SCSI, Ethernet and serial ports later on.
175 bool "MVME162, 166 and 167 support"
178 Say Y to include support for Motorola VME boards. This will build a
179 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
180 MVME177 boards. If you select this option you will have to select
181 the appropriate drivers for SCSI, Ethernet and serial ports later
185 bool "BVME4000 and BVME6000 support"
188 Say Y to include support for VME boards from BVM Ltd. This will
189 build a kernel which can run on BVME4000 and BVME6000 boards. If
190 you select this option you will have to select the appropriate
191 drivers for SCSI, Ethernet and serial ports later on.
194 bool "HP9000/300 and HP9000/400 support"
195 select MMU_MOTOROLA if MMU
197 This option enables support for the HP9000/300 and HP9000/400 series
198 of workstations. Support for these machines is still somewhat
199 experimental. If you plan to try to use the kernel on such a machine
201 Everybody else says N.
204 bool "DIO bus support"
208 Say Y here to enable support for the "DIO" expansion bus used in
209 HP300 machines. If you are using such a system you almost certainly
214 select MMU_MOTOROLA if MMU
217 This option enables support for the Sun 3x series of workstations.
218 Be warned that this support is very experimental.
219 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
220 General Linux information on the Sun 3x series (now discontinued)
221 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
223 If you don't want to compile a kernel for a Sun 3x, say N.
226 bool "Q40/Q60 support"
227 select MMU_MOTOROLA if MMU
229 The Q40 is a Motorola 68040-based successor to the Sinclair QL
230 manufactured in Germany. There is an official Q40 home page at
231 <http://www.q40.de/>. This option enables support for the Q40 and
232 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
237 depends on !MMU_MOTOROLA
238 select MMU_SUN3 if MMU
241 This option enables support for the Sun 3 series of workstations
242 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
243 that all other hardware types must be disabled, as Sun 3 kernels
244 are incompatible with all other m68k targets (including Sun 3x!).
246 If you don't want to compile a kernel exclusively for a Sun 3, say N.
248 comment "Processor type"
253 If you anticipate running this kernel on a computer with a MC68020
254 processor, say Y. Otherwise, say N. Note that the 68020 requires a
255 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
256 Sun 3, which provides its own version.
262 If you anticipate running this kernel on a computer with a MC68030
263 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
264 work, as it does not include an MMU (Memory Management Unit).
270 If you anticipate running this kernel on a computer with a MC68LC040
271 or MC68040 processor, say Y. Otherwise, say N. Note that an
272 MC68EC040 will not work, as it does not include an MMU (Memory
279 If you anticipate running this kernel on a computer with a MC68060
280 processor, say Y. Otherwise, say N.
287 depends on MMU && !MMU_MOTOROLA
290 bool "Math emulation support (EXPERIMENTAL)"
291 depends on EXPERIMENTAL
293 At some point in the future, this will cause floating-point math
294 instructions to be emulated by the kernel on machines that lack a
295 floating-point math coprocessor. Thrill-seekers and chronically
296 sleep-deprived psychotic hacker types can say Y now, everyone else
297 should probably wait a while.
299 config M68KFPU_EMU_EXTRAPREC
300 bool "Math emulation extra precision"
301 depends on M68KFPU_EMU
303 The fpu uses normally a few bit more during calculations for
304 correct rounding, the emulator can (often) do the same but this
305 extra calculation can cost quite some time, so you can disable
306 it here. The emulator will then "only" calculate with a 64 bit
307 mantissa and round slightly incorrect, what is more than enough
310 config M68KFPU_EMU_ONLY
311 bool "Math emulation only kernel"
312 depends on M68KFPU_EMU
314 This option prevents any floating-point instructions from being
315 compiled into the kernel, thereby the kernel doesn't save any
316 floating point context anymore during task switches, so this
317 kernel will only be usable on machines without a floating-point
318 math coprocessor. This makes the kernel a bit faster as no tests
319 needs to be executed whether a floating-point instruction in the
320 kernel should be executed or not.
323 bool "Advanced configuration options"
325 This gives you access to some advanced options for the CPU. The
326 defaults should be fine for most users, but these options may make
327 it possible for you to improve performance somewhat if you know what
330 Note that the answer to this question won't directly affect the
331 kernel: saying N will just cause the configurator to skip all
332 the questions about these options.
334 Most users should say N to this question.
337 bool "Use read-modify-write instructions"
340 This allows to use certain instructions that work with indivisible
341 read-modify-write bus cycles. While this is faster than the
342 workaround of disabling interrupts, it can conflict with DMA
343 ( = direct memory access) on many Amiga systems, and it is also said
344 to destabilize other machines. It is very likely that this will
345 cause serious problems on any Amiga or Atari Medusa if set. The only
346 configuration where it should work are 68030-based Ataris, where it
347 apparently improves performance. But you've been warned! Unless you
348 really know what you are doing, say N. Try Y only if you're quite
351 config SINGLE_MEMORY_CHUNK
352 bool "Use one physical chunk of memory only" if ADVANCED && !SUN3
354 select NEED_MULTIPLE_NODES
356 Ignore all but the first contiguous chunk of physical memory for VM
357 purposes. This will save a few bytes kernel size and may speed up
358 some operations. Say N if not sure.
360 config 060_WRITETHROUGH
361 bool "Use write-through caching for 68060 supervisor accesses"
362 depends on ADVANCED && M68060
364 The 68060 generally uses copyback caching of recently accessed data.
365 Copyback caching means that memory writes will be held in an on-chip
366 cache and only written back to memory some time later. Saying Y
367 here will force supervisor (kernel) accesses to use writethrough
368 caching. Writethrough caching means that data is written to memory
369 straight away, so that cache and memory data always agree.
370 Writethrough caching is less efficient, but is needed for some
371 drivers on 68060 based systems where the 68060 bus snooping signal
372 is hardwired on. The 53c710 SCSI driver is known to suffer from
375 config ARCH_DISCONTIGMEM_ENABLE
376 def_bool !SINGLE_MEMORY_CHUNK
381 depends on !SINGLE_MEMORY_CHUNK
389 source "fs/Kconfig.binfmt"
392 bool "Amiga Zorro (AutoConfig) bus support"
395 This enables support for the Zorro bus in the Amiga. If you have
396 expansion cards in your Amiga that conform to the Amiga
397 AutoConfig(tm) specification, say Y, otherwise N. Note that even
398 expansion cards that do not fit in the Zorro slots but fit in e.g.
399 the CPU slot may fall in this category, so you have to say Y to let
403 bool "Amiga 1200/600 PCMCIA support (EXPERIMENTAL)"
404 depends on AMIGA && EXPERIMENTAL
406 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
407 600. If you intend to use pcmcia cards say Y; otherwise say N.
410 bool "ST-RAM statistics in /proc"
413 Say Y here to report ST-RAM usage statistics in /proc/stram.
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 MIDI serial support"
481 If you want to use your Atari's MIDI port in Linux, say Y.
483 To compile this driver as a module, choose M here.
486 tristate "Atari DSP56k support (EXPERIMENTAL)"
487 depends on ATARI && EXPERIMENTAL
489 If you want to be able to use the DSP56001 in Falcons, say Y. This
490 driver is still experimental, and if you don't know what it is, or
491 if you don't have this processor, just say N.
493 To compile this driver as a module, choose M here.
495 config AMIGA_BUILTIN_SERIAL
496 tristate "Amiga builtin serial support"
499 If you want to use your Amiga's built-in serial port in Linux,
502 To compile this driver as a module, choose M here.
504 config MULTIFACE_III_TTY
505 tristate "Multiface Card III serial support"
508 If you want to use a Multiface III card's serial port in Linux,
511 To compile this driver as a module, choose M here.
514 tristate "GVP IO-Extender support"
515 depends on PARPORT=n && ZORRO
517 If you want to use a GVP IO-Extender serial card in Linux, say Y.
521 tristate "GVP IO-Extender parallel printer support"
524 Say Y to enable driving a printer from the parallel port on your
525 GVP IO-Extender card, N otherwise.
528 tristate "GVP IO-Extender PLIP support"
531 Say Y to enable doing IP over the parallel port on your GVP
532 IO-Extender card, N otherwise.
536 depends on INPUT_ADBHID
540 tristate "HP DCA serial support"
541 depends on DIO && SERIAL_8250
543 If you want to use the internal "DCA" serial ports on an HP300
547 tristate "HP APCI serial support"
548 depends on HP300 && SERIAL_8250 && EXPERIMENTAL
550 If you want to use the internal "APCI" serial ports on an HP400
554 bool "SCC support for MVME147 serial ports"
555 depends on MVME147 && BROKEN
557 This is the driver for the serial ports on the Motorola MVME147
558 boards. Everyone using one of these boards should say Y here.
561 bool "CD2401 support for MVME166/7 serial ports"
564 This is the driver for the serial ports on the Motorola MVME166,
565 167, and 172 boards. Everyone using one of these boards should say
569 bool "SCC support for MVME162 serial ports"
570 depends on MVME16x && BROKEN
572 This is the driver for the serial ports on the Motorola MVME162 and
573 172 boards. Everyone using one of these boards should say Y here.
576 bool "SCC support for BVME6000 serial ports"
577 depends on BVME6000 && BROKEN
579 This is the driver for the serial ports on the BVME4000 and BVME6000
580 boards from BVM Ltd. Everyone using one of these boards should say
584 bool "Support for DN serial port (dummy)"
587 config SERIAL_CONSOLE
588 bool "Support for serial port console"
589 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)
591 If you say Y here, it will be possible to use a serial port as the
592 system console (the system console is the device which receives all
593 kernel messages and warnings and which allows logins in single user
594 mode). This could be useful if some terminal or printer is connected
597 Even if you say Y here, the currently visible virtual console
598 (/dev/tty0) will still be used as the system console by default, but
599 you can alter that using a kernel command line option such as
600 "console=ttyS1". (Try "man bootparam" or see the documentation of
601 your boot loader (lilo or loadlin) about how to pass options to the
602 kernel at boot time.)
604 If you don't have a VGA card installed and you say Y here, the
605 kernel will automatically use the first serial line, /dev/ttyS0, as
614 source "arch/m68k/Kconfig.debug"
616 source "security/Kconfig"
618 source "crypto/Kconfig"