43
config ARCH_MAY_HAVE_PC_FDC
45
depends on BROKEN && (Q40 || SUN3X)
39
def_bool (MMU && SUN3) || (!MMU && !COLDFIRE)
46
default 1000 if CLEOPATRA
58
config ARCH_USES_GETTIMEOFFSET
61
49
source "init/Kconfig"
63
51
source "kernel/Kconfig.freezer"
54
bool "MMU-based Paged Memory Management Support"
57
Select if you want MMU-based virtualised addressing space
58
support by paged memory management. If unsure, say 'Y'.
65
60
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.
126
bool "Macintosh support"
127
select MMU_MOTOROLA if MMU
129
This option enables support for the Apple Macintosh series of
130
computers (yes, there is experimental support now, at least for part
133
Say N unless you're willing to code the remaining necessary support.
147
bool "Apollo support"
148
select MMU_MOTOROLA if MMU
150
Say Y here if you want to run Linux on an MC680x0-based Apollo
151
Domain workstation such as the DN3500.
154
bool "VME (Motorola and BVM) support"
155
select MMU_MOTOROLA if MMU
157
Say Y here if you want to build a kernel for a 680x0 based VME
158
board. Boards currently supported include Motorola boards MVME147,
159
MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
160
BVME6000 boards from BVM Ltd are also supported.
163
bool "MVME147 support"
166
Say Y to include support for early Motorola VME boards. This will
167
build a kernel which can run on MVME147 single-board computers. If
168
you select this option you will have to select the appropriate
169
drivers for SCSI, Ethernet and serial ports later on.
172
bool "MVME162, 166 and 167 support"
175
Say Y to include support for Motorola VME boards. This will build a
176
kernel which can run on MVME162, MVME166, MVME167, MVME172, and
177
MVME177 boards. If you select this option you will have to select
178
the appropriate drivers for SCSI, Ethernet and serial ports later
182
bool "BVME4000 and BVME6000 support"
185
Say Y to include support for VME boards from BVM Ltd. This will
186
build a kernel which can run on BVME4000 and BVME6000 boards. If
187
you select this option you will have to select the appropriate
188
drivers for SCSI, Ethernet and serial ports later on.
191
bool "HP9000/300 and HP9000/400 support"
192
select MMU_MOTOROLA if MMU
194
This option enables support for the HP9000/300 and HP9000/400 series
195
of workstations. Support for these machines is still somewhat
196
experimental. If you plan to try to use the kernel on such a machine
198
Everybody else says N.
201
bool "DIO bus support"
205
Say Y here to enable support for the "DIO" expansion bus used in
206
HP300 machines. If you are using such a system you almost certainly
211
select MMU_MOTOROLA if MMU
214
This option enables support for the Sun 3x series of workstations.
215
Be warned that this support is very experimental.
216
Note that Sun 3x kernels are not compatible with Sun 3 hardware.
217
General Linux information on the Sun 3x series (now discontinued)
218
is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
220
If you don't want to compile a kernel for a Sun 3x, say N.
223
bool "Q40/Q60 support"
224
select MMU_MOTOROLA if MMU
226
The Q40 is a Motorola 68040-based successor to the Sinclair QL
227
manufactured in Germany. There is an official Q40 home page at
228
<http://www.q40.de/>. This option enables support for the Q40 and
229
Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
234
depends on !MMU_MOTOROLA
235
select MMU_SUN3 if MMU
238
This option enables support for the Sun 3 series of workstations
239
(3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
240
that all other hardware types must be disabled, as Sun 3 kernels
241
are incompatible with all other m68k targets (including Sun 3x!).
243
If you don't want to compile a kernel exclusively for a Sun 3, say N.
245
comment "Processor type"
250
If you anticipate running this kernel on a computer with a MC68020
251
processor, say Y. Otherwise, say N. Note that the 68020 requires a
252
68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
253
Sun 3, which provides its own version.
259
If you anticipate running this kernel on a computer with a MC68030
260
processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
261
work, as it does not include an MMU (Memory Management Unit).
267
If you anticipate running this kernel on a computer with a MC68LC040
268
or MC68040 processor, say Y. Otherwise, say N. Note that an
269
MC68EC040 will not work, as it does not include an MMU (Memory
276
If you anticipate running this kernel on a computer with a MC68060
277
processor, say Y. Otherwise, say N.
284
depends on MMU && !MMU_MOTOROLA
287
bool "Math emulation support (EXPERIMENTAL)"
288
depends on EXPERIMENTAL
290
At some point in the future, this will cause floating-point math
291
instructions to be emulated by the kernel on machines that lack a
292
floating-point math coprocessor. Thrill-seekers and chronically
293
sleep-deprived psychotic hacker types can say Y now, everyone else
294
should probably wait a while.
296
config M68KFPU_EMU_EXTRAPREC
297
bool "Math emulation extra precision"
298
depends on M68KFPU_EMU
300
The fpu uses normally a few bit more during calculations for
301
correct rounding, the emulator can (often) do the same but this
302
extra calculation can cost quite some time, so you can disable
303
it here. The emulator will then "only" calculate with a 64 bit
304
mantissa and round slightly incorrect, what is more than enough
307
config M68KFPU_EMU_ONLY
308
bool "Math emulation only kernel"
309
depends on M68KFPU_EMU
311
This option prevents any floating-point instructions from being
312
compiled into the kernel, thereby the kernel doesn't save any
313
floating point context anymore during task switches, so this
314
kernel will only be usable on machines without a floating-point
315
math coprocessor. This makes the kernel a bit faster as no tests
316
needs to be executed whether a floating-point instruction in the
317
kernel should be executed or not.
320
bool "Advanced configuration options"
322
This gives you access to some advanced options for the CPU. The
323
defaults should be fine for most users, but these options may make
324
it possible for you to improve performance somewhat if you know what
327
Note that the answer to this question won't directly affect the
328
kernel: saying N will just cause the configurator to skip all
329
the questions about these options.
331
Most users should say N to this question.
334
bool "Use read-modify-write instructions"
337
This allows to use certain instructions that work with indivisible
338
read-modify-write bus cycles. While this is faster than the
339
workaround of disabling interrupts, it can conflict with DMA
340
( = direct memory access) on many Amiga systems, and it is also said
341
to destabilize other machines. It is very likely that this will
342
cause serious problems on any Amiga or Atari Medusa if set. The only
343
configuration where it should work are 68030-based Ataris, where it
344
apparently improves performance. But you've been warned! Unless you
345
really know what you are doing, say N. Try Y only if you're quite
348
config SINGLE_MEMORY_CHUNK
349
bool "Use one physical chunk of memory only" if ADVANCED && !SUN3
351
select NEED_MULTIPLE_NODES
353
Ignore all but the first contiguous chunk of physical memory for VM
354
purposes. This will save a few bytes kernel size and may speed up
355
some operations. Say N if not sure.
357
config 060_WRITETHROUGH
358
bool "Use write-through caching for 68060 supervisor accesses"
359
depends on ADVANCED && M68060
361
The 68060 generally uses copyback caching of recently accessed data.
362
Copyback caching means that memory writes will be held in an on-chip
363
cache and only written back to memory some time later. Saying Y
364
here will force supervisor (kernel) accesses to use writethrough
365
caching. Writethrough caching means that data is written to memory
366
straight away, so that cache and memory data always agree.
367
Writethrough caching is less efficient, but is needed for some
368
drivers on 68060 based systems where the 68060 bus snooping signal
369
is hardwired on. The 53c710 SCSI driver is known to suffer from
372
config ARCH_DISCONTIGMEM_ENABLE
373
def_bool !SINGLE_MEMORY_CHUNK
378
depends on !SINGLE_MEMORY_CHUNK
63
source arch/m68k/Kconfig.mmu
66
source arch/m68k/Kconfig.nommu
380
69
source "mm/Kconfig"
73
menu "Executable file formats"
386
75
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.
413
bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || MAC ||Q40
414
default y if !AMIGA && !APOLLO && !ATARI && !MAC && !Q40 && HP300
416
Use the power-on LED on your machine as a load meter. The exact
417
behavior is platform-dependent, but normally the flash frequency is
418
a hyperbolic function of the 5-minute load average.
420
# We have a dedicated heartbeat LED. :-)
422
bool "/proc/hardware support"
424
Say Y here to support the /proc/hardware file, which gives you
425
access to information about the machine you're running on,
426
including the model, CPU, MMU, clock speed, BogoMIPS rating,
431
depends on Q40 || AMIGA_PCMCIA
434
Find out whether you have ISA slots on your motherboard. ISA is the
435
name of a bus system, i.e. the way the CPU talks to the other stuff
436
inside your box. Other bus systems are PCI, EISA, MicroChannel
437
(MCA) or VESA. ISA is an older system, now being displaced by PCI;
438
newer boards don't support it. If you have ISA, say Y, otherwise N.
440
config GENERIC_ISA_DMA
442
depends on Q40 || AMIGA_PCMCIA
449
source "drivers/pci/Kconfig"
451
source "drivers/zorro/Kconfig"
80
menu "Power management options"
83
bool "Power Management support"
85
Support processor power management modes
455
90
source "net/Kconfig"
457
92
source "drivers/Kconfig"
459
96
menu "Character devices"
461
98
config ATARI_MFPSER