2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "Linux Kernel Configuration"
13 The ARM series is a line of low-power-consumption RISC chip designs
14 licensed by ARM Ltd and targeted at embedded applications and
15 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
16 manufactured, but legacy ARM-based PC hardware remains popular in
17 Europe. There is an ARM Linux project with a web page at
18 <http://www.arm.linux.org.uk/>.
31 The Extended Industry Standard Architecture (EISA) bus was
32 developed as an open alternative to the IBM MicroChannel bus.
34 The EISA bus provided some of the features of the IBM MicroChannel
35 bus while maintaining backward compatibility with cards made for
36 the older ISA bus. The EISA bus saw limited use between 1988 and
37 1995 when it was made obsolete by the PCI bus.
39 Say Y here if you are building a kernel for an EISA-based machine.
49 MicroChannel Architecture is found in some IBM PS/2 machines and
50 laptops. It is a bus system similar to PCI or ISA. See
51 <file:Documentation/mca.txt> (and especially the web page given
52 there) before attempting to build an MCA bus kernel.
54 config GENERIC_HARDIRQS
58 config TRACE_IRQFLAGS_SUPPORT
62 config HARDIRQS_SW_RESEND
66 config GENERIC_IRQ_PROBE
70 config RWSEM_GENERIC_SPINLOCK
74 config RWSEM_XCHGADD_ALGORITHM
77 config GENERIC_HWEIGHT
81 config GENERIC_CALIBRATE_DELAY
85 config GENERIC_BUST_SPINLOCK
88 config ARCH_MAY_HAVE_PC_FDC
91 config GENERIC_ISA_DMA
102 default 0xffff0000 if MMU
103 default DRAM_BASE if REMAP_VECTORS_TO_RAM
106 The base address of exception vectors.
108 source "init/Kconfig"
113 prompt "ARM system type"
114 default ARCH_VERSATILE
117 bool "Agilent AAEC-2000 based"
120 This enables support for systems based on the Agilent AAEC-2000
122 config ARCH_INTEGRATOR
123 bool "ARM Ltd. Integrator family"
127 Support for ARM's Integrator platform.
130 bool "ARM Ltd. RealView family"
134 This enables support for ARM Ltd RealView boards.
136 config ARCH_VERSATILE
137 bool "ARM Ltd. Versatile family"
142 This enables support for ARM Ltd Versatile board.
147 This enables support for systems based on the Atmel AT91RM9200
148 and AT91SAM9xxx processors.
151 bool "Cirrus CL-PS7500FE"
155 Support for the Cirrus Logic PS7500FE system-on-a-chip.
158 bool "Cirrus Logic CLPS711x/EP721x-based"
160 Support for Cirrus Logic 711x/721x based boards.
165 select FOOTBRIDGE_ADDIN
167 Support for Intel's EBSA285 companion chip.
173 This is an evaluation board for the StrongARM processor available
174 from Digital. It has limited hardware on-board, including an
175 Ethernet interface, two PCMCIA sockets, two serial ports and a
183 This enables support for the Cirrus EP93xx series of CPUs.
185 config ARCH_FOOTBRIDGE
189 Support for systems based on the DC21285 companion chip
190 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
193 bool "Hilscher NetX based"
196 This enables support for systems based on the Hilscher NetX Soc
199 bool "Hynix HMS720x-based"
202 This enables support for systems based on the Hynix HMS720x
207 Support for Motorola's i.MX family of processors (MX1, MXL).
215 Support for Intel's 80219 and IOP32X (XScale) family of
224 Support for Intel's IOP33X (XScale) family of processors.
230 Support for Intel's IXP4XX (XScale) family of processors.
233 bool "IXP2400/2800-based"
237 Support for Intel's IXP2400/2800 (XScale) family of processors.
244 Support for Intel's IXP23xx (XScale) family of processors.
250 Say Y here if you intend to run this kernel on a LinkUp Systems
251 L7200 Software Development Board which uses an ARM720T processor.
252 Information on this board can be obtained at:
254 <http://www.linkupsys.com/>
256 If you have any questions or comments about the Linux kernel port
257 to this board, send e-mail to <sjhill@cotw.com>.
260 bool "Philips Nexperia PNX4008 Mobile"
262 This enables support for Philips PNX4008 mobile platform.
269 Support for Intel's PXA2XX processor line.
276 select ARCH_MAY_HAVE_PC_FDC
279 On the Acorn Risc-PC, Linux can support the internal IDE disk and
280 CD-ROM interface, serial and parallel port, and the floppy drive.
285 select ARCH_DISCONTIGMEM_ENABLE
288 Support for StrongARM 11x0 based boards.
291 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442"
293 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
294 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
295 the Samsung SMDK2410 development board (and derivatives).
303 Support for the StrongARM based Digital DNARD machine, also known
304 as "Shark" (<http://www.shark-linux.de/shark.html>).
309 Say Y here for systems based on one of the Sharp LH7A40X
310 System on a Chip processors. These CPUs include an ARM922T
311 core with a wide array of integrated devices for
312 hand-held and low-power applications.
317 Support for TI's OMAP platform (OMAP1 and OMAP2).
321 source "arch/arm/mach-clps711x/Kconfig"
323 source "arch/arm/mach-ep93xx/Kconfig"
325 source "arch/arm/mach-footbridge/Kconfig"
327 source "arch/arm/mach-integrator/Kconfig"
329 source "arch/arm/mach-iop32x/Kconfig"
331 source "arch/arm/mach-iop33x/Kconfig"
333 source "arch/arm/mach-ixp4xx/Kconfig"
335 source "arch/arm/mach-ixp2000/Kconfig"
337 source "arch/arm/mach-ixp23xx/Kconfig"
339 source "arch/arm/mach-pxa/Kconfig"
341 source "arch/arm/mach-sa1100/Kconfig"
343 source "arch/arm/plat-omap/Kconfig"
345 source "arch/arm/mach-omap1/Kconfig"
347 source "arch/arm/mach-omap2/Kconfig"
349 source "arch/arm/mach-s3c2410/Kconfig"
351 source "arch/arm/mach-lh7a40x/Kconfig"
353 source "arch/arm/mach-imx/Kconfig"
355 source "arch/arm/mach-h720x/Kconfig"
357 source "arch/arm/mach-versatile/Kconfig"
359 source "arch/arm/mach-aaec2000/Kconfig"
361 source "arch/arm/mach-realview/Kconfig"
363 source "arch/arm/mach-at91rm9200/Kconfig"
365 source "arch/arm/mach-netx/Kconfig"
367 # Definitions to make life easier
374 source arch/arm/mm/Kconfig
376 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
379 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
383 source "arch/arm/Kconfig-nommu"
388 source "arch/arm/common/Kconfig"
390 config FORCE_MAX_ZONEORDER
403 Find out whether you have ISA slots on your motherboard. ISA is the
404 name of a bus system, i.e. the way the CPU talks to the other stuff
405 inside your box. Other bus systems are PCI, EISA, MicroChannel
406 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
407 newer boards don't support it. If you have ISA, say Y, otherwise N.
409 # Select ISA DMA controller support
414 # Select ISA DMA interface
419 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
421 Find out whether you have a PCI motherboard. PCI is the name of a
422 bus system, i.e. the way the CPU talks to the other stuff inside
423 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
424 VESA. If you have PCI, say Y, otherwise N.
426 The PCI-HOWTO, available from
427 <http://www.tldp.org/docs.html#howto>, contains valuable
428 information about which PCI hardware does work under Linux and which
431 # Select the host bridge type
432 config PCI_HOST_VIA82C505
434 depends on PCI && ARCH_SHARK
437 source "drivers/pci/Kconfig"
439 source "drivers/pcmcia/Kconfig"
443 menu "Kernel Features"
446 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
447 depends on EXPERIMENTAL && REALVIEW_MPCORE
449 This enables support for systems with more than one CPU. If you have
450 a system with only one CPU, like most personal computers, say N. If
451 you have a system with more than one CPU, say Y.
453 If you say N here, the kernel will run on single and multiprocessor
454 machines, but will use only one CPU of a multiprocessor machine. If
455 you say Y here, the kernel will run on many, but not all, single
456 processor machines. On a single processor machine, the kernel will
457 run faster if you say N here.
459 See also the <file:Documentation/smp.txt>,
460 <file:Documentation/i386/IO-APIC.txt>,
461 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
462 <http://www.linuxdoc.org/docs.html#howto>.
464 If you don't know what to do here, say N.
467 int "Maximum number of CPUs (2-32)"
473 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
474 depends on SMP && HOTPLUG && EXPERIMENTAL
476 Say Y here to experiment with turning CPUs off and on. CPUs
477 can be controlled through /sys/devices/system/cpu.
480 bool "Use local timer interrupts"
481 depends on SMP && REALVIEW_MPCORE
484 Enable support for local timers on SMP platforms, rather then the
485 legacy IPI broadcast method. Local timers allows the system
486 accounting to be spread across the timer interval, preventing a
487 "thundering herd" at every timer tick.
490 bool "Preemptible Kernel (EXPERIMENTAL)"
491 depends on EXPERIMENTAL
493 This option reduces the latency of the kernel when reacting to
494 real-time or interactive events by allowing a low priority process to
495 be preempted even if it is in kernel mode executing a system call.
496 This allows applications to run more reliably even when the system is
499 Say Y here if you are building a kernel for a desktop, embedded
500 or real-time system. Say N if you are unsure.
503 bool "Dynamic tick timer"
505 Select this option if you want to disable continuous timer ticks
506 and have them programmed to occur as required. This option saves
507 power as the system can remain in idle state for longer.
509 By default dynamic tick is disabled during the boot, and can be
510 manually enabled with:
512 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
514 Alternatively, if you want dynamic tick automatically enabled
515 during boot, pass "dyntick=enable" via the kernel command string.
517 Please note that dynamic tick may affect the accuracy of
518 timekeeping on some platforms depending on the implementation.
519 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
520 to have accurate timekeeping with dynamic tick.
524 default 128 if ARCH_L7200
525 default 200 if ARCH_EBSA110 || ARCH_S3C2410
526 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
530 bool "Use the ARM EABI to compile the kernel"
532 This option allows for the kernel to be compiled using the latest
533 ARM ABI (aka EABI). This is only useful if you are using a user
534 space environment that is also compiled with EABI.
536 Since there are major incompatibilities between the legacy ABI and
537 EABI, especially with regard to structure member alignment, this
538 option also changes the kernel syscall calling convention to
539 disambiguate both ABIs and allow for backward compatibility support
540 (selected with CONFIG_OABI_COMPAT).
542 To use this you need GCC version 4.0.0 or later.
545 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
546 depends on AEABI && EXPERIMENTAL
549 This option preserves the old syscall interface along with the
550 new (ARM EABI) one. It also provides a compatibility layer to
551 intercept syscalls that have structure arguments which layout
552 in memory differs between the legacy ABI and the new ARM EABI
553 (only for non "thumb" binaries). This option adds a tiny
554 overhead to all syscalls and produces a slightly larger kernel.
555 If you know you'll be using only pure EABI user space then you
556 can say N here. If this option is not selected and you attempt
557 to execute a legacy ABI binary then the result will be
558 UNPREDICTABLE (in fact it can be predicted that it won't work
559 at all). If in doubt say Y.
561 config ARCH_DISCONTIGMEM_ENABLE
563 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
565 Say Y to support efficient handling of discontiguous physical memory,
566 for architectures which are either NUMA (Non-Uniform Memory Access)
567 or have huge holes in the physical address space for other reasons.
568 See <file:Documentation/vm/numa> for more.
572 default "4" if ARCH_LH7A40X
574 depends on NEED_MULTIPLE_NODES
579 bool "Timer and CPU usage LEDs"
580 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
581 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
582 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
583 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
584 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
585 ARCH_AT91RM9200 || MACH_TRIZEPS4
587 If you say Y here, the LEDs on your machine will be used
588 to provide useful information about your current system status.
590 If you are compiling a kernel for a NetWinder or EBSA-285, you will
591 be able to select which LEDs are active using the options below. If
592 you are compiling a kernel for the EBSA-110 or the LART however, the
593 red LED will simply flash regularly to indicate that the system is
594 still functional. It is safe to say Y here if you have a CATS
595 system, but the driver will do nothing.
598 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
599 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
601 default y if ARCH_EBSA110
603 If you say Y here, one of the system LEDs (the green one on the
604 NetWinder, the amber one on the EBSA285, or the red one on the LART)
605 will flash regularly to indicate that the system is still
606 operational. This is mainly useful to kernel hackers who are
607 debugging unstable kernels.
609 The LART uses the same LED for both Timer LED and CPU usage LED
610 functions. You may choose to use both, but the Timer LED function
611 will overrule the CPU usage LED.
614 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
615 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
618 If you say Y here, the red LED will be used to give a good real
619 time indication of CPU usage, by lighting whenever the idle task
620 is not currently executing.
622 The LART uses the same LED for both Timer LED and CPU usage LED
623 functions. You may choose to use both, but the Timer LED function
624 will overrule the CPU usage LED.
626 config ALIGNMENT_TRAP
628 default y if !ARCH_EBSA110
630 ARM processors can not fetch/store information which is not
631 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
632 address divisible by 4. On 32-bit ARM processors, these non-aligned
633 fetch/store instructions will be emulated in software if you say
634 here, which has a severe performance impact. This is necessary for
635 correct operation of some network protocols. With an IP-only
636 configuration it is safe to say N, otherwise say Y.
642 # Compressed boot loader in ROM. Yes, we really want to ask about
643 # TEXT and BSS so we preserve their values in the config files.
644 config ZBOOT_ROM_TEXT
645 hex "Compressed ROM boot loader base address"
648 The physical address at which the ROM-able zImage is to be
649 placed in the target. Platforms which normally make use of
650 ROM-able zImage formats normally set this to a suitable
651 value in their defconfig file.
653 If ZBOOT_ROM is not enabled, this has no effect.
656 hex "Compressed ROM boot loader BSS address"
659 The base address of an area of read/write memory in the target
660 for the ROM-able zImage which must be available while the
661 decompressor is running. It must be large enough to hold the
662 entire decompressed kernel plus an additional 128 KiB.
663 Platforms which normally make use of ROM-able zImage formats
664 normally set this to a suitable value in their defconfig file.
666 If ZBOOT_ROM is not enabled, this has no effect.
669 bool "Compressed boot loader in ROM/flash"
670 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
672 Say Y here if you intend to execute your compressed kernel image
673 (zImage) directly from ROM or flash. If unsure, say N.
676 string "Default kernel command string"
679 On some architectures (EBSA110 and CATS), there is currently no way
680 for the boot loader to pass arguments to the kernel. For these
681 architectures, you should supply some command-line options at build
682 time by entering them here. As a minimum, you should specify the
683 memory size and the root device (e.g., mem=64M root=/dev/nfs).
686 bool "Kernel Execute-In-Place from ROM"
687 depends on !ZBOOT_ROM
689 Execute-In-Place allows the kernel to run from non-volatile storage
690 directly addressable by the CPU, such as NOR flash. This saves RAM
691 space since the text section of the kernel is not loaded from flash
692 to RAM. Read-write sections, such as the data section and stack,
693 are still copied to RAM. The XIP kernel is not compressed since
694 it has to run directly from flash, so it will take more space to
695 store it. The flash address used to link the kernel object files,
696 and for storing it, is configuration dependent. Therefore, if you
697 say Y here, you must know the proper physical address where to
698 store the kernel image depending on your own flash memory usage.
700 Also note that the make target becomes "make xipImage" rather than
701 "make zImage" or "make Image". The final kernel binary to put in
702 ROM memory will be arch/arm/boot/xipImage.
707 hex "XIP Kernel Physical Location"
708 depends on XIP_KERNEL
711 This is the physical address in your flash memory the kernel will
712 be linked for and stored to. This address is dependent on your
717 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP)
719 menu "CPU Frequency scaling"
721 source "drivers/cpufreq/Kconfig"
723 config CPU_FREQ_SA1100
725 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
728 config CPU_FREQ_SA1110
730 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
733 config CPU_FREQ_INTEGRATOR
734 tristate "CPUfreq driver for ARM Integrator CPUs"
735 depends on ARCH_INTEGRATOR && CPU_FREQ
738 This enables the CPUfreq driver for ARM Integrator CPUs.
740 For details, take a look at <file:Documentation/cpu-freq>.
748 menu "Floating point emulation"
750 comment "At least one emulation must be selected"
753 bool "NWFPE math emulation"
754 depends on !AEABI || OABI_COMPAT
756 Say Y to include the NWFPE floating point emulator in the kernel.
757 This is necessary to run most binaries. Linux does not currently
758 support floating point hardware so you need to say Y here even if
759 your machine has an FPA or floating point co-processor podule.
761 You may say N here if you are going to load the Acorn FPEmulator
765 bool "Support extended precision"
768 Say Y to include 80-bit support in the kernel floating-point
769 emulator. Otherwise, only 32 and 64-bit support is compiled in.
770 Note that gcc does not generate 80-bit operations by default,
771 so in most cases this option only enlarges the size of the
772 floating point emulator without any good reason.
774 You almost surely want to say N here.
777 bool "FastFPE math emulation (EXPERIMENTAL)"
778 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
780 Say Y here to include the FAST floating point emulator in the kernel.
781 This is an experimental much faster emulator which now also has full
782 precision for the mantissa. It does not support any exceptions.
783 It is very simple, and approximately 3-6 times faster than NWFPE.
785 It should be sufficient for most programs. It may be not suitable
786 for scientific calculations, but you have to check this for yourself.
787 If you do not feel you need a faster FP emulation you should better
791 bool "VFP-format floating point maths"
792 depends on CPU_V6 || CPU_ARM926T
794 Say Y to include VFP support code in the kernel. This is needed
795 if your hardware includes a VFP unit.
797 Please see <file:Documentation/arm/VFP/release-notes.txt> for
798 release notes and additional status information.
800 Say N if your target does not have VFP hardware.
804 menu "Userspace binary formats"
806 source "fs/Kconfig.binfmt"
809 tristate "RISC OS personality"
812 Say Y here to include the kernel code necessary if you want to run
813 Acorn RISC OS/Arthur binaries under Linux. This code is still very
814 experimental; if this sounds frightening, say N and sleep in peace.
815 You can also say M here to compile this support as a module (which
816 will be called arthur).
820 menu "Power management options"
822 source "kernel/power/Kconfig"
825 tristate "Advanced Power Management Emulation"
827 APM is a BIOS specification for saving power using several different
828 techniques. This is mostly useful for battery powered laptops with
829 APM compliant BIOSes. If you say Y here, the system time will be
830 reset after a RESUME operation, the /proc/apm device will provide
831 battery status information, and user-space programs will receive
832 notification of APM "events" (e.g. battery status change).
834 In order to use APM, you will need supporting software. For location
835 and more information, read <file:Documentation/pm.txt> and the
836 Battery Powered Linux mini-HOWTO, available from
837 <http://www.tldp.org/docs.html#howto>.
839 This driver does not spin down disk drives (see the hdparm(8)
840 manpage ("man 8 hdparm") for that), and it doesn't turn off
841 VESA-compliant "green" monitors.
843 Generally, if you don't have a battery in your machine, there isn't
844 much point in using this driver and you should say N. If you get
845 random kernel OOPSes or reboots that don't seem to be related to
846 anything, try disabling/enabling this option (or disabling/enabling
853 menu "Device Drivers"
855 source "drivers/base/Kconfig"
857 source "drivers/connector/Kconfig"
860 source "drivers/mtd/Kconfig"
863 source "drivers/parport/Kconfig"
865 source "drivers/pnp/Kconfig"
867 source "drivers/block/Kconfig"
869 source "drivers/acorn/block/Kconfig"
871 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
872 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
873 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
875 source "drivers/ide/Kconfig"
878 source "drivers/scsi/Kconfig"
880 source "drivers/md/Kconfig"
882 source "drivers/message/fusion/Kconfig"
884 source "drivers/ieee1394/Kconfig"
886 source "drivers/message/i2o/Kconfig"
888 source "drivers/net/Kconfig"
890 source "drivers/isdn/Kconfig"
892 # input before char - char/joystick depends on it. As does USB.
894 source "drivers/input/Kconfig"
896 source "drivers/char/Kconfig"
898 source "drivers/i2c/Kconfig"
900 source "drivers/spi/Kconfig"
902 source "drivers/w1/Kconfig"
904 source "drivers/hwmon/Kconfig"
906 #source "drivers/l3/Kconfig"
908 source "drivers/misc/Kconfig"
910 source "drivers/mfd/Kconfig"
912 source "drivers/leds/Kconfig"
914 source "drivers/media/Kconfig"
916 source "drivers/video/Kconfig"
918 source "sound/Kconfig"
920 source "drivers/usb/Kconfig"
922 source "drivers/mmc/Kconfig"
924 source "drivers/rtc/Kconfig"
930 source "arch/arm/oprofile/Kconfig"
932 source "arch/arm/Kconfig.debug"
934 source "security/Kconfig"
936 source "crypto/Kconfig"