2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "Linux Kernel Configuration"
12 The ARM series is a line of low-power-consumption RISC chip designs
13 licensed by ARM ltd and targeted at embedded applications and
14 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
15 manufactured, but legacy ARM-based PC hardware remains popular in
16 Europe. There is an ARM Linux project with a web page at
17 <http://www.arm.linux.org.uk/>.
26 The Extended Industry Standard Architecture (EISA) bus was
27 developed as an open alternative to the IBM MicroChannel bus.
29 The EISA bus provided some of the features of the IBM MicroChannel
30 bus while maintaining backward compatibility with cards made for
31 the older ISA bus. The EISA bus saw limited use between 1988 and
32 1995 when it was made obsolete by the PCI bus.
34 Say Y here if you are building a kernel for an EISA-based machine.
44 MicroChannel Architecture is found in some IBM PS/2 machines and
45 laptops. It is a bus system similar to PCI or ISA. See
46 <file:Documentation/mca.txt> (and especially the web page given
47 there) before attempting to build an MCA bus kernel.
53 config RWSEM_GENERIC_SPINLOCK
57 config RWSEM_XCHGADD_ALGORITHM
60 config GENERIC_CALIBRATE_DELAY
64 config GENERIC_BUST_SPINLOCK
67 config ARCH_MAY_HAVE_PC_FDC
70 config GENERIC_ISA_DMA
81 prompt "ARM system type"
85 bool "Cirrus-CL-PS7500FE"
90 bool "CLPS711x/EP721x-based"
95 select FOOTBRIDGE_ADDIN
101 This is an evaluation board for the StrongARM processor available
102 from Digital. It has limited hardware on-board, including an onboard
103 Ethernet interface, two PCMCIA sockets, two serial ports and a
109 This enables support for Altera's Excalibur XA10 development board.
110 If you would like to build your kernel to run on one of these boards
111 then you must say 'Y' here. Otherwise say 'N'
113 config ARCH_FOOTBRIDGE
117 config ARCH_INTEGRATOR
132 bool "IXP2400/2800-based"
139 Say Y here if you intend to run this kernel on a LinkUp Systems
140 L7200 Software Development Board which uses an ARM720T processor.
141 Information on this board can be obtained at:
143 <http://www.linkupsys.com/>
145 If you have any questions or comments about the Linux kernel port
146 to this board, send e-mail to <sjhill@cotw.com>.
156 select ARCH_MAY_HAVE_PC_FDC
158 On the Acorn Risc-PC, Linux can support the internal IDE disk and
159 CD-ROM interface, serial and parallel port, and the floppy drive.
164 select ARCH_DISCONTIGMEM_ENABLE
167 bool "Samsung S3C2410"
169 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
170 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
171 the Samsung SMDK2410 development board (and derviatives).
182 Say Y here for systems based on one of the Sharp LH7A40X
183 System on a Chip processors. These CPUs include an ARM922T
184 core with a wide array of integrated devices for
185 hand-held and low-power applications.
190 config ARCH_VERSATILE
195 This enables support for ARM Ltd Versatile board.
201 bool "Hynix-HMS720x-based"
203 This enables support for systems based on the Hynix HMS720x
206 bool "Agilent AAEC-2000 based"
209 This enables support for systems based on the Agilent AAEC-2000
213 source "arch/arm/mach-clps711x/Kconfig"
215 source "arch/arm/mach-epxa10db/Kconfig"
217 source "arch/arm/mach-footbridge/Kconfig"
219 source "arch/arm/mach-integrator/Kconfig"
221 source "arch/arm/mach-iop3xx/Kconfig"
223 source "arch/arm/mach-ixp4xx/Kconfig"
225 source "arch/arm/mach-ixp2000/Kconfig"
227 source "arch/arm/mach-pxa/Kconfig"
229 source "arch/arm/mach-sa1100/Kconfig"
231 source "arch/arm/plat-omap/Kconfig"
233 source "arch/arm/mach-omap1/Kconfig"
235 source "arch/arm/mach-s3c2410/Kconfig"
237 source "arch/arm/mach-lh7a40x/Kconfig"
239 source "arch/arm/mach-imx/Kconfig"
241 source "arch/arm/mach-h720x/Kconfig"
243 source "arch/arm/mach-versatile/Kconfig"
245 source "arch/arm/mach-aaec2000/Kconfig"
247 # Definitions to make life easier
251 source arch/arm/mm/Kconfig
253 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
256 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
261 source "arch/arm/common/Kconfig"
263 config FORCE_MAX_ZONEORDER
276 Find out whether you have ISA slots on your motherboard. ISA is the
277 name of a bus system, i.e. the way the CPU talks to the other stuff
278 inside your box. Other bus systems are PCI, EISA, MicroChannel
279 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
280 newer boards don't support it. If you have ISA, say Y, otherwise N.
290 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
292 Find out whether you have a PCI motherboard. PCI is the name of a
293 bus system, i.e. the way the CPU talks to the other stuff inside
294 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
295 VESA. If you have PCI, say Y, otherwise N.
297 The PCI-HOWTO, available from
298 <http://www.tldp.org/docs.html#howto>, contains valuable
299 information about which PCI hardware does work under Linux and which
302 # Select the host bridge type
303 config PCI_HOST_VIA82C505
305 depends on PCI && ARCH_SHARK
308 source "drivers/pci/Kconfig"
310 source "drivers/pcmcia/Kconfig"
314 menu "Kernel Features"
317 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
318 depends on EXPERIMENTAL && BROKEN #&& n
320 This enables support for systems with more than one CPU. If you have
321 a system with only one CPU, like most personal computers, say N. If
322 you have a system with more than one CPU, say Y.
324 If you say N here, the kernel will run on single and multiprocessor
325 machines, but will use only one CPU of a multiprocessor machine. If
326 you say Y here, the kernel will run on many, but not all, single
327 processor machines. On a single processor machine, the kernel will
328 run faster if you say N here.
330 See also the <file:Documentation/smp.txt>,
331 <file:Documentation/i386/IO-APIC.txt>,
332 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
333 <http://www.linuxdoc.org/docs.html#howto>.
335 If you don't know what to do here, say N.
338 int "Maximum number of CPUs (2-32)"
344 bool "Preemptible Kernel (EXPERIMENTAL)"
345 depends on EXPERIMENTAL
347 This option reduces the latency of the kernel when reacting to
348 real-time or interactive events by allowing a low priority process to
349 be preempted even if it is in kernel mode executing a system call.
350 This allows applications to run more reliably even when the system is
353 Say Y here if you are building a kernel for a desktop, embedded
354 or real-time system. Say N if you are unsure.
357 bool "Dynamic tick timer"
359 Select this option if you want to disable continuous timer ticks
360 and have them programmed to occur as required. This option saves
361 power as the system can remain in idle state for longer.
363 By default dynamic tick is disabled during the boot, and can be
364 manually enabled with:
366 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
368 Alternatively, if you want dynamic tick automatically enabled
369 during boot, pass "dyntick=enable" via the kernel command string.
371 Please note that dynamic tick may affect the accuracy of
372 timekeeping on some platforms depending on the implementation.
373 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
374 to have accurate timekeeping with dynamic tick.
376 config ARCH_DISCONTIGMEM_ENABLE
378 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
380 Say Y to support efficient handling of discontiguous physical memory,
381 for architectures which are either NUMA (Non-Uniform Memory Access)
382 or have huge holes in the physical address space for other reasons.
383 See <file:Documentation/vm/numa> for more.
388 bool "Timer and CPU usage LEDs"
389 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
390 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
391 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
392 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
393 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE
395 If you say Y here, the LEDs on your machine will be used
396 to provide useful information about your current system status.
398 If you are compiling a kernel for a NetWinder or EBSA-285, you will
399 be able to select which LEDs are active using the options below. If
400 you are compiling a kernel for the EBSA-110 or the LART however, the
401 red LED will simply flash regularly to indicate that the system is
402 still functional. It is safe to say Y here if you have a CATS
403 system, but the driver will do nothing.
406 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
407 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
409 default y if ARCH_EBSA110
411 If you say Y here, one of the system LEDs (the green one on the
412 NetWinder, the amber one on the EBSA285, or the red one on the LART)
413 will flash regularly to indicate that the system is still
414 operational. This is mainly useful to kernel hackers who are
415 debugging unstable kernels.
417 The LART uses the same LED for both Timer LED and CPU usage LED
418 functions. You may choose to use both, but the Timer LED function
419 will overrule the CPU usage LED.
422 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
423 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
426 If you say Y here, the red LED will be used to give a good real
427 time indication of CPU usage, by lighting whenever the idle task
428 is not currently executing.
430 The LART uses the same LED for both Timer LED and CPU usage LED
431 functions. You may choose to use both, but the Timer LED function
432 will overrule the CPU usage LED.
434 config ALIGNMENT_TRAP
436 default y if !ARCH_EBSA110
438 ARM processors can not fetch/store information which is not
439 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
440 address divisible by 4. On 32-bit ARM processors, these non-aligned
441 fetch/store instructions will be emulated in software if you say
442 here, which has a severe performance impact. This is necessary for
443 correct operation of some network protocols. With an IP-only
444 configuration it is safe to say N, otherwise say Y.
450 # Compressed boot loader in ROM. Yes, we really want to ask about
451 # TEXT and BSS so we preserve their values in the config files.
452 config ZBOOT_ROM_TEXT
453 hex "Compressed ROM boot loader base address"
456 The physical address at which the ROM-able zImage is to be
457 placed in the target. Platforms which normally make use of
458 ROM-able zImage formats normally set this to a suitable
459 value in their defconfig file.
461 If ZBOOT_ROM is not enabled, this has no effect.
464 hex "Compressed ROM boot loader BSS address"
467 The base address of 64KiB of read/write memory in the target
468 for the ROM-able zImage, which must be available while the
469 decompressor is running. Platforms which normally make use of
470 ROM-able zImage formats normally set this to a suitable
471 value in their defconfig file.
473 If ZBOOT_ROM is not enabled, this has no effect.
476 bool "Compressed boot loader in ROM/flash"
477 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
479 Say Y here if you intend to execute your compressed kernel image
480 (zImage) directly from ROM or flash. If unsure, say N.
483 string "Default kernel command string"
486 On some architectures (EBSA110 and CATS), there is currently no way
487 for the boot loader to pass arguments to the kernel. For these
488 architectures, you should supply some command-line options at build
489 time by entering them here. As a minimum, you should specify the
490 memory size and the root device (e.g., mem=64M root=/dev/nfs).
493 bool "Kernel Execute-In-Place from ROM"
494 depends on !ZBOOT_ROM
496 Execute-In-Place allows the kernel to run from non-volatile storage
497 directly addressable by the CPU, such as NOR flash. This saves RAM
498 space since the text section of the kernel is not loaded from flash
499 to RAM. Read-write sections, such as the data section and stack,
500 are still copied to RAM. The XIP kernel is not compressed since
501 it has to run directly from flash, so it will take more space to
502 store it. The flash address used to link the kernel object files,
503 and for storing it, is configuration dependent. Therefore, if you
504 say Y here, you must know the proper physical address where to
505 store the kernel image depending on your own flash memory usage.
507 Also note that the make target becomes "make xipImage" rather than
508 "make zImage" or "make Image". The final kernel binary to put in
509 ROM memory will be arch/arm/boot/xipImage.
514 hex "XIP Kernel Physical Location"
515 depends on XIP_KERNEL
518 This is the physical address in your flash memory the kernel will
519 be linked for and stored to. This address is dependent on your
524 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
526 menu "CPU Frequency scaling"
528 source "drivers/cpufreq/Kconfig"
530 config CPU_FREQ_SA1100
532 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
535 config CPU_FREQ_SA1110
537 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
540 config CPU_FREQ_INTEGRATOR
541 tristate "CPUfreq driver for ARM Integrator CPUs"
542 depends on ARCH_INTEGRATOR && CPU_FREQ
545 This enables the CPUfreq driver for ARM Integrator CPUs.
547 For details, take a look at <file:Documentation/cpu-freq>.
555 menu "Floating point emulation"
557 comment "At least one emulation must be selected"
560 bool "NWFPE math emulation"
562 Say Y to include the NWFPE floating point emulator in the kernel.
563 This is necessary to run most binaries. Linux does not currently
564 support floating point hardware so you need to say Y here even if
565 your machine has an FPA or floating point co-processor podule.
567 You may say N here if you are going to load the Acorn FPEmulator
571 bool "Support extended precision"
572 depends on FPE_NWFPE && !CPU_BIG_ENDIAN
574 Say Y to include 80-bit support in the kernel floating-point
575 emulator. Otherwise, only 32 and 64-bit support is compiled in.
576 Note that gcc does not generate 80-bit operations by default,
577 so in most cases this option only enlarges the size of the
578 floating point emulator without any good reason.
580 You almost surely want to say N here.
583 bool "FastFPE math emulation (EXPERIMENTAL)"
584 depends on !CPU_32v3 && EXPERIMENTAL
586 Say Y here to include the FAST floating point emulator in the kernel.
587 This is an experimental much faster emulator which now also has full
588 precision for the mantissa. It does not support any exceptions.
589 It is very simple, and approximately 3-6 times faster than NWFPE.
591 It should be sufficient for most programs. It may be not suitable
592 for scientific calculations, but you have to check this for yourself.
593 If you do not feel you need a faster FP emulation you should better
597 bool "VFP-format floating point maths"
598 depends on CPU_V6 || CPU_ARM926T
600 Say Y to include VFP support code in the kernel. This is needed
601 if your hardware includes a VFP unit.
603 Please see <file:Documentation/arm/VFP/release-notes.txt> for
604 release notes and additional status information.
606 Say N if your target does not have VFP hardware.
610 menu "Userspace binary formats"
612 source "fs/Kconfig.binfmt"
615 tristate "RISC OS personality"
617 Say Y here to include the kernel code necessary if you want to run
618 Acorn RISC OS/Arthur binaries under Linux. This code is still very
619 experimental; if this sounds frightening, say N and sleep in peace.
620 You can also say M here to compile this support as a module (which
621 will be called arthur).
625 menu "Power management options"
628 bool "Power Management support"
630 "Power Management" means that parts of your computer are shut
631 off or put into a power conserving "sleep" mode if they are not
632 being used. There are two competing standards for doing this: APM
633 and ACPI. If you want to use either one, say Y here and then also
634 to the requisite support below.
636 Power Management is most important for battery powered laptop
637 computers; if you have a laptop, check out the Linux Laptop home
638 page on the WWW at <http://www.linux-on-laptops.com/> or
639 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>
640 and the Battery Powered Linux mini-HOWTO, available from
641 <http://www.tldp.org/docs.html#howto>.
644 tristate "Advanced Power Management Emulation"
647 APM is a BIOS specification for saving power using several different
648 techniques. This is mostly useful for battery powered laptops with
649 APM compliant BIOSes. If you say Y here, the system time will be
650 reset after a RESUME operation, the /proc/apm device will provide
651 battery status information, and user-space programs will receive
652 notification of APM "events" (e.g. battery status change).
654 In order to use APM, you will need supporting software. For location
655 and more information, read <file:Documentation/pm.txt> and the
656 Battery Powered Linux mini-HOWTO, available from
657 <http://www.tldp.org/docs.html#howto>.
659 This driver does not spin down disk drives (see the hdparm(8)
660 manpage ("man 8 hdparm") for that), and it doesn't turn off
661 VESA-compliant "green" monitors.
663 Generally, if you don't have a battery in your machine, there isn't
664 much point in using this driver and you should say N. If you get
665 random kernel OOPSes or reboots that don't seem to be related to
666 anything, try disabling/enabling this option (or disabling/enabling
673 menu "Device Drivers"
675 source "drivers/base/Kconfig"
678 source "drivers/mtd/Kconfig"
681 source "drivers/parport/Kconfig"
683 source "drivers/pnp/Kconfig"
685 source "drivers/block/Kconfig"
687 source "drivers/acorn/block/Kconfig"
689 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
690 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
691 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
693 source "drivers/ide/Kconfig"
696 source "drivers/scsi/Kconfig"
698 source "drivers/md/Kconfig"
700 source "drivers/message/fusion/Kconfig"
702 source "drivers/ieee1394/Kconfig"
704 source "drivers/message/i2o/Kconfig"
706 source "drivers/net/Kconfig"
708 source "drivers/isdn/Kconfig"
710 # input before char - char/joystick depends on it. As does USB.
712 source "drivers/input/Kconfig"
714 source "drivers/char/Kconfig"
716 source "drivers/i2c/Kconfig"
718 source "drivers/hwmon/Kconfig"
720 #source "drivers/l3/Kconfig"
722 source "drivers/misc/Kconfig"
724 source "drivers/mfd/Kconfig"
726 source "drivers/media/Kconfig"
728 source "drivers/video/Kconfig"
730 source "sound/Kconfig"
732 source "drivers/usb/Kconfig"
734 source "drivers/mmc/Kconfig"
740 source "arch/arm/oprofile/Kconfig"
742 source "arch/arm/Kconfig.debug"
744 source "security/Kconfig"
746 source "crypto/Kconfig"