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 || CPU_HIGH_VECTOR
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.
231 Support for Intel's IXP4XX (XScale) family of processors.
234 bool "IXP2400/2800-based"
238 Support for Intel's IXP2400/2800 (XScale) family of processors.
245 Support for Intel's IXP23xx (XScale) family of processors.
251 Say Y here if you intend to run this kernel on a LinkUp Systems
252 L7200 Software Development Board which uses an ARM720T processor.
253 Information on this board can be obtained at:
255 <http://www.linkupsys.com/>
257 If you have any questions or comments about the Linux kernel port
258 to this board, send e-mail to <sjhill@cotw.com>.
261 bool "Philips Nexperia PNX4008 Mobile"
263 This enables support for Philips PNX4008 mobile platform.
270 Support for Intel's PXA2XX processor line.
277 select ARCH_MAY_HAVE_PC_FDC
280 On the Acorn Risc-PC, Linux can support the internal IDE disk and
281 CD-ROM interface, serial and parallel port, and the floppy drive.
286 select ARCH_DISCONTIGMEM_ENABLE
289 Support for StrongARM 11x0 based boards.
292 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442"
294 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
295 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
296 the Samsung SMDK2410 development board (and derivatives).
304 Support for the StrongARM based Digital DNARD machine, also known
305 as "Shark" (<http://www.shark-linux.de/shark.html>).
310 Say Y here for systems based on one of the Sharp LH7A40X
311 System on a Chip processors. These CPUs include an ARM922T
312 core with a wide array of integrated devices for
313 hand-held and low-power applications.
318 Support for TI's OMAP platform (OMAP1 and OMAP2).
322 source "arch/arm/mach-clps711x/Kconfig"
324 source "arch/arm/mach-ep93xx/Kconfig"
326 source "arch/arm/mach-footbridge/Kconfig"
328 source "arch/arm/mach-integrator/Kconfig"
330 source "arch/arm/mach-iop32x/Kconfig"
332 source "arch/arm/mach-iop33x/Kconfig"
334 source "arch/arm/mach-ixp4xx/Kconfig"
336 source "arch/arm/mach-ixp2000/Kconfig"
338 source "arch/arm/mach-ixp23xx/Kconfig"
340 source "arch/arm/mach-pxa/Kconfig"
342 source "arch/arm/mach-sa1100/Kconfig"
344 source "arch/arm/plat-omap/Kconfig"
346 source "arch/arm/mach-omap1/Kconfig"
348 source "arch/arm/mach-omap2/Kconfig"
350 source "arch/arm/mach-s3c2410/Kconfig"
352 source "arch/arm/mach-lh7a40x/Kconfig"
354 source "arch/arm/mach-imx/Kconfig"
356 source "arch/arm/mach-h720x/Kconfig"
358 source "arch/arm/mach-versatile/Kconfig"
360 source "arch/arm/mach-aaec2000/Kconfig"
362 source "arch/arm/mach-realview/Kconfig"
364 source "arch/arm/mach-at91rm9200/Kconfig"
366 source "arch/arm/mach-netx/Kconfig"
368 # Definitions to make life easier
375 source arch/arm/mm/Kconfig
378 bool "Enable iWMMXt support"
379 depends CPU_XSCALE || CPU_XSC3
382 Enable support for iWMMXt context switching at run time if
383 running on a CPU that supports it.
385 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
388 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
392 source "arch/arm/Kconfig-nommu"
397 source "arch/arm/common/Kconfig"
399 config FORCE_MAX_ZONEORDER
412 Find out whether you have ISA slots on your motherboard. ISA is the
413 name of a bus system, i.e. the way the CPU talks to the other stuff
414 inside your box. Other bus systems are PCI, EISA, MicroChannel
415 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
416 newer boards don't support it. If you have ISA, say Y, otherwise N.
418 # Select ISA DMA controller support
423 # Select ISA DMA interface
428 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
430 Find out whether you have a PCI motherboard. PCI is the name of a
431 bus system, i.e. the way the CPU talks to the other stuff inside
432 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
433 VESA. If you have PCI, say Y, otherwise N.
435 The PCI-HOWTO, available from
436 <http://www.tldp.org/docs.html#howto>, contains valuable
437 information about which PCI hardware does work under Linux and which
440 # Select the host bridge type
441 config PCI_HOST_VIA82C505
443 depends on PCI && ARCH_SHARK
446 source "drivers/pci/Kconfig"
448 source "drivers/pcmcia/Kconfig"
452 menu "Kernel Features"
455 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
456 depends on EXPERIMENTAL && REALVIEW_MPCORE
458 This enables support for systems with more than one CPU. If you have
459 a system with only one CPU, like most personal computers, say N. If
460 you have a system with more than one CPU, say Y.
462 If you say N here, the kernel will run on single and multiprocessor
463 machines, but will use only one CPU of a multiprocessor machine. If
464 you say Y here, the kernel will run on many, but not all, single
465 processor machines. On a single processor machine, the kernel will
466 run faster if you say N here.
468 See also the <file:Documentation/smp.txt>,
469 <file:Documentation/i386/IO-APIC.txt>,
470 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
471 <http://www.linuxdoc.org/docs.html#howto>.
473 If you don't know what to do here, say N.
476 int "Maximum number of CPUs (2-32)"
482 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
483 depends on SMP && HOTPLUG && EXPERIMENTAL
485 Say Y here to experiment with turning CPUs off and on. CPUs
486 can be controlled through /sys/devices/system/cpu.
489 bool "Use local timer interrupts"
490 depends on SMP && REALVIEW_MPCORE
493 Enable support for local timers on SMP platforms, rather then the
494 legacy IPI broadcast method. Local timers allows the system
495 accounting to be spread across the timer interval, preventing a
496 "thundering herd" at every timer tick.
499 bool "Preemptible Kernel (EXPERIMENTAL)"
500 depends on EXPERIMENTAL
502 This option reduces the latency of the kernel when reacting to
503 real-time or interactive events by allowing a low priority process to
504 be preempted even if it is in kernel mode executing a system call.
505 This allows applications to run more reliably even when the system is
508 Say Y here if you are building a kernel for a desktop, embedded
509 or real-time system. Say N if you are unsure.
512 bool "Dynamic tick timer"
514 Select this option if you want to disable continuous timer ticks
515 and have them programmed to occur as required. This option saves
516 power as the system can remain in idle state for longer.
518 By default dynamic tick is disabled during the boot, and can be
519 manually enabled with:
521 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
523 Alternatively, if you want dynamic tick automatically enabled
524 during boot, pass "dyntick=enable" via the kernel command string.
526 Please note that dynamic tick may affect the accuracy of
527 timekeeping on some platforms depending on the implementation.
528 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
529 to have accurate timekeeping with dynamic tick.
533 default 128 if ARCH_L7200
534 default 200 if ARCH_EBSA110 || ARCH_S3C2410
535 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
539 bool "Use the ARM EABI to compile the kernel"
541 This option allows for the kernel to be compiled using the latest
542 ARM ABI (aka EABI). This is only useful if you are using a user
543 space environment that is also compiled with EABI.
545 Since there are major incompatibilities between the legacy ABI and
546 EABI, especially with regard to structure member alignment, this
547 option also changes the kernel syscall calling convention to
548 disambiguate both ABIs and allow for backward compatibility support
549 (selected with CONFIG_OABI_COMPAT).
551 To use this you need GCC version 4.0.0 or later.
554 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
555 depends on AEABI && EXPERIMENTAL
558 This option preserves the old syscall interface along with the
559 new (ARM EABI) one. It also provides a compatibility layer to
560 intercept syscalls that have structure arguments which layout
561 in memory differs between the legacy ABI and the new ARM EABI
562 (only for non "thumb" binaries). This option adds a tiny
563 overhead to all syscalls and produces a slightly larger kernel.
564 If you know you'll be using only pure EABI user space then you
565 can say N here. If this option is not selected and you attempt
566 to execute a legacy ABI binary then the result will be
567 UNPREDICTABLE (in fact it can be predicted that it won't work
568 at all). If in doubt say Y.
570 config ARCH_DISCONTIGMEM_ENABLE
572 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
574 Say Y to support efficient handling of discontiguous physical memory,
575 for architectures which are either NUMA (Non-Uniform Memory Access)
576 or have huge holes in the physical address space for other reasons.
577 See <file:Documentation/vm/numa> for more.
581 default "4" if ARCH_LH7A40X
583 depends on NEED_MULTIPLE_NODES
588 bool "Timer and CPU usage LEDs"
589 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
590 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
591 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
592 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
593 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
594 ARCH_AT91RM9200 || MACH_TRIZEPS4
596 If you say Y here, the LEDs on your machine will be used
597 to provide useful information about your current system status.
599 If you are compiling a kernel for a NetWinder or EBSA-285, you will
600 be able to select which LEDs are active using the options below. If
601 you are compiling a kernel for the EBSA-110 or the LART however, the
602 red LED will simply flash regularly to indicate that the system is
603 still functional. It is safe to say Y here if you have a CATS
604 system, but the driver will do nothing.
607 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
608 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
610 default y if ARCH_EBSA110
612 If you say Y here, one of the system LEDs (the green one on the
613 NetWinder, the amber one on the EBSA285, or the red one on the LART)
614 will flash regularly to indicate that the system is still
615 operational. This is mainly useful to kernel hackers who are
616 debugging unstable kernels.
618 The LART uses the same LED for both Timer LED and CPU usage LED
619 functions. You may choose to use both, but the Timer LED function
620 will overrule the CPU usage LED.
623 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
624 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
627 If you say Y here, the red LED will be used to give a good real
628 time indication of CPU usage, by lighting whenever the idle task
629 is not currently executing.
631 The LART uses the same LED for both Timer LED and CPU usage LED
632 functions. You may choose to use both, but the Timer LED function
633 will overrule the CPU usage LED.
635 config ALIGNMENT_TRAP
637 depends on CPU_CP15_MMU
638 default y if !ARCH_EBSA110
640 ARM processors cannot fetch/store information which is not
641 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
642 address divisible by 4. On 32-bit ARM processors, these non-aligned
643 fetch/store instructions will be emulated in software if you say
644 here, which has a severe performance impact. This is necessary for
645 correct operation of some network protocols. With an IP-only
646 configuration it is safe to say N, otherwise say Y.
652 # Compressed boot loader in ROM. Yes, we really want to ask about
653 # TEXT and BSS so we preserve their values in the config files.
654 config ZBOOT_ROM_TEXT
655 hex "Compressed ROM boot loader base address"
658 The physical address at which the ROM-able zImage is to be
659 placed in the target. Platforms which normally make use of
660 ROM-able zImage formats normally set this to a suitable
661 value in their defconfig file.
663 If ZBOOT_ROM is not enabled, this has no effect.
666 hex "Compressed ROM boot loader BSS address"
669 The base address of an area of read/write memory in the target
670 for the ROM-able zImage which must be available while the
671 decompressor is running. It must be large enough to hold the
672 entire decompressed kernel plus an additional 128 KiB.
673 Platforms which normally make use of ROM-able zImage formats
674 normally set this to a suitable value in their defconfig file.
676 If ZBOOT_ROM is not enabled, this has no effect.
679 bool "Compressed boot loader in ROM/flash"
680 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
682 Say Y here if you intend to execute your compressed kernel image
683 (zImage) directly from ROM or flash. If unsure, say N.
686 string "Default kernel command string"
689 On some architectures (EBSA110 and CATS), there is currently no way
690 for the boot loader to pass arguments to the kernel. For these
691 architectures, you should supply some command-line options at build
692 time by entering them here. As a minimum, you should specify the
693 memory size and the root device (e.g., mem=64M root=/dev/nfs).
696 bool "Kernel Execute-In-Place from ROM"
697 depends on !ZBOOT_ROM
699 Execute-In-Place allows the kernel to run from non-volatile storage
700 directly addressable by the CPU, such as NOR flash. This saves RAM
701 space since the text section of the kernel is not loaded from flash
702 to RAM. Read-write sections, such as the data section and stack,
703 are still copied to RAM. The XIP kernel is not compressed since
704 it has to run directly from flash, so it will take more space to
705 store it. The flash address used to link the kernel object files,
706 and for storing it, is configuration dependent. Therefore, if you
707 say Y here, you must know the proper physical address where to
708 store the kernel image depending on your own flash memory usage.
710 Also note that the make target becomes "make xipImage" rather than
711 "make zImage" or "make Image". The final kernel binary to put in
712 ROM memory will be arch/arm/boot/xipImage.
717 hex "XIP Kernel Physical Location"
718 depends on XIP_KERNEL
721 This is the physical address in your flash memory the kernel will
722 be linked for and stored to. This address is dependent on your
727 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP)
729 menu "CPU Frequency scaling"
731 source "drivers/cpufreq/Kconfig"
733 config CPU_FREQ_SA1100
735 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
738 config CPU_FREQ_SA1110
740 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
743 config CPU_FREQ_INTEGRATOR
744 tristate "CPUfreq driver for ARM Integrator CPUs"
745 depends on ARCH_INTEGRATOR && CPU_FREQ
748 This enables the CPUfreq driver for ARM Integrator CPUs.
750 For details, take a look at <file:Documentation/cpu-freq>.
758 menu "Floating point emulation"
760 comment "At least one emulation must be selected"
763 bool "NWFPE math emulation"
764 depends on !AEABI || OABI_COMPAT
766 Say Y to include the NWFPE floating point emulator in the kernel.
767 This is necessary to run most binaries. Linux does not currently
768 support floating point hardware so you need to say Y here even if
769 your machine has an FPA or floating point co-processor podule.
771 You may say N here if you are going to load the Acorn FPEmulator
775 bool "Support extended precision"
778 Say Y to include 80-bit support in the kernel floating-point
779 emulator. Otherwise, only 32 and 64-bit support is compiled in.
780 Note that gcc does not generate 80-bit operations by default,
781 so in most cases this option only enlarges the size of the
782 floating point emulator without any good reason.
784 You almost surely want to say N here.
787 bool "FastFPE math emulation (EXPERIMENTAL)"
788 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
790 Say Y here to include the FAST floating point emulator in the kernel.
791 This is an experimental much faster emulator which now also has full
792 precision for the mantissa. It does not support any exceptions.
793 It is very simple, and approximately 3-6 times faster than NWFPE.
795 It should be sufficient for most programs. It may be not suitable
796 for scientific calculations, but you have to check this for yourself.
797 If you do not feel you need a faster FP emulation you should better
801 bool "VFP-format floating point maths"
802 depends on CPU_V6 || CPU_ARM926T
804 Say Y to include VFP support code in the kernel. This is needed
805 if your hardware includes a VFP unit.
807 Please see <file:Documentation/arm/VFP/release-notes.txt> for
808 release notes and additional status information.
810 Say N if your target does not have VFP hardware.
814 menu "Userspace binary formats"
816 source "fs/Kconfig.binfmt"
819 tristate "RISC OS personality"
822 Say Y here to include the kernel code necessary if you want to run
823 Acorn RISC OS/Arthur binaries under Linux. This code is still very
824 experimental; if this sounds frightening, say N and sleep in peace.
825 You can also say M here to compile this support as a module (which
826 will be called arthur).
830 menu "Power management options"
832 source "kernel/power/Kconfig"
835 tristate "Advanced Power Management Emulation"
837 APM is a BIOS specification for saving power using several different
838 techniques. This is mostly useful for battery powered laptops with
839 APM compliant BIOSes. If you say Y here, the system time will be
840 reset after a RESUME operation, the /proc/apm device will provide
841 battery status information, and user-space programs will receive
842 notification of APM "events" (e.g. battery status change).
844 In order to use APM, you will need supporting software. For location
845 and more information, read <file:Documentation/pm.txt> and the
846 Battery Powered Linux mini-HOWTO, available from
847 <http://www.tldp.org/docs.html#howto>.
849 This driver does not spin down disk drives (see the hdparm(8)
850 manpage ("man 8 hdparm") for that), and it doesn't turn off
851 VESA-compliant "green" monitors.
853 Generally, if you don't have a battery in your machine, there isn't
854 much point in using this driver and you should say N. If you get
855 random kernel OOPSes or reboots that don't seem to be related to
856 anything, try disabling/enabling this option (or disabling/enabling
863 menu "Device Drivers"
865 source "drivers/base/Kconfig"
867 source "drivers/connector/Kconfig"
869 if ALIGNMENT_TRAP || !CPU_CP15_MMU
870 source "drivers/mtd/Kconfig"
873 source "drivers/parport/Kconfig"
875 source "drivers/pnp/Kconfig"
877 source "drivers/block/Kconfig"
879 source "drivers/acorn/block/Kconfig"
881 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
882 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
883 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
885 source "drivers/ide/Kconfig"
888 source "drivers/scsi/Kconfig"
890 source "drivers/ata/Kconfig"
892 source "drivers/md/Kconfig"
894 source "drivers/message/fusion/Kconfig"
896 source "drivers/ieee1394/Kconfig"
898 source "drivers/message/i2o/Kconfig"
900 source "drivers/net/Kconfig"
902 source "drivers/isdn/Kconfig"
904 # input before char - char/joystick depends on it. As does USB.
906 source "drivers/input/Kconfig"
908 source "drivers/char/Kconfig"
910 source "drivers/i2c/Kconfig"
912 source "drivers/spi/Kconfig"
914 source "drivers/w1/Kconfig"
916 source "drivers/hwmon/Kconfig"
918 #source "drivers/l3/Kconfig"
920 source "drivers/misc/Kconfig"
922 source "drivers/mfd/Kconfig"
924 source "drivers/leds/Kconfig"
926 source "drivers/media/Kconfig"
928 source "drivers/video/Kconfig"
930 source "sound/Kconfig"
932 source "drivers/usb/Kconfig"
934 source "drivers/mmc/Kconfig"
936 source "drivers/rtc/Kconfig"
942 source "arch/arm/oprofile/Kconfig"
944 source "arch/arm/Kconfig.debug"
946 source "security/Kconfig"
948 source "crypto/Kconfig"