2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "Linux Kernel Configuration"
12 select SYS_SUPPORTS_APM_EMULATION
14 The ARM series is a line of low-power-consumption RISC chip designs
15 licensed by ARM Ltd and targeted at embedded applications and
16 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
17 manufactured, but legacy ARM-based PC hardware remains popular in
18 Europe. There is an ARM Linux project with a web page at
19 <http://www.arm.linux.org.uk/>.
21 config SYS_SUPPORTS_APM_EMULATION
39 The Extended Industry Standard Architecture (EISA) bus was
40 developed as an open alternative to the IBM MicroChannel bus.
42 The EISA bus provided some of the features of the IBM MicroChannel
43 bus while maintaining backward compatibility with cards made for
44 the older ISA bus. The EISA bus saw limited use between 1988 and
45 1995 when it was made obsolete by the PCI bus.
47 Say Y here if you are building a kernel for an EISA-based machine.
57 MicroChannel Architecture is found in some IBM PS/2 machines and
58 laptops. It is a bus system similar to PCI or ISA. See
59 <file:Documentation/mca.txt> (and especially the web page given
60 there) before attempting to build an MCA bus kernel.
62 config GENERIC_HARDIRQS
66 config TRACE_IRQFLAGS_SUPPORT
70 config HARDIRQS_SW_RESEND
74 config GENERIC_IRQ_PROBE
78 config RWSEM_GENERIC_SPINLOCK
82 config RWSEM_XCHGADD_ALGORITHM
85 config ARCH_HAS_ILOG2_U32
89 config ARCH_HAS_ILOG2_U64
93 config GENERIC_HWEIGHT
97 config GENERIC_CALIBRATE_DELAY
101 config GENERIC_BUST_SPINLOCK
104 config ARCH_MAY_HAVE_PC_FDC
111 config GENERIC_ISA_DMA
122 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
123 default DRAM_BASE if REMAP_VECTORS_TO_RAM
126 The base address of exception vectors.
128 source "init/Kconfig"
133 prompt "ARM system type"
134 default ARCH_VERSATILE
137 bool "Agilent AAEC-2000 based"
140 This enables support for systems based on the Agilent AAEC-2000
142 config ARCH_INTEGRATOR
143 bool "ARM Ltd. Integrator family"
147 Support for ARM's Integrator platform.
150 bool "ARM Ltd. RealView family"
154 This enables support for ARM Ltd RealView boards.
156 config ARCH_VERSATILE
157 bool "ARM Ltd. Versatile family"
162 This enables support for ARM Ltd Versatile board.
167 This enables support for systems based on the Atmel AT91RM9200
168 and AT91SAM9xxx processors.
171 bool "Cirrus CL-PS7500FE"
175 Support for the Cirrus Logic PS7500FE system-on-a-chip.
178 bool "Cirrus Logic CLPS711x/EP721x-based"
180 Support for Cirrus Logic 711x/721x based boards.
185 select FOOTBRIDGE_ADDIN
187 Support for Intel's EBSA285 companion chip.
193 This is an evaluation board for the StrongARM processor available
194 from Digital. It has limited hardware on-board, including an
195 Ethernet interface, two PCMCIA sockets, two serial ports and a
203 This enables support for the Cirrus EP93xx series of CPUs.
205 config ARCH_FOOTBRIDGE
209 Support for systems based on the DC21285 companion chip
210 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
213 bool "Hilscher NetX based"
216 This enables support for systems based on the Hilscher NetX Soc
219 bool "Hynix HMS720x-based"
222 This enables support for systems based on the Hynix HMS720x
227 Support for Motorola's i.MX family of processors (MX1, MXL).
235 Support for Intel's 80219 and IOP32X (XScale) family of
244 Support for Intel's IOP33X (XScale) family of processors.
250 Support for Intel's IOP13XX (XScale) family of processors.
257 Support for Intel's IXP4XX (XScale) family of processors.
260 bool "IXP2400/2800-based"
264 Support for Intel's IXP2400/2800 (XScale) family of processors.
271 Support for Intel's IXP23xx (XScale) family of processors.
277 Say Y here if you intend to run this kernel on a LinkUp Systems
278 L7200 Software Development Board which uses an ARM720T processor.
279 Information on this board can be obtained at:
281 <http://www.linkupsys.com/>
283 If you have any questions or comments about the Linux kernel port
284 to this board, send e-mail to <sjhill@cotw.com>.
287 bool "Philips Nexperia PNX4008 Mobile"
289 This enables support for Philips PNX4008 mobile platform.
296 Support for Intel's PXA2XX processor line.
303 select ARCH_MAY_HAVE_PC_FDC
307 On the Acorn Risc-PC, Linux can support the internal IDE disk and
308 CD-ROM interface, serial and parallel port, and the floppy drive.
313 select ARCH_DISCONTIGMEM_ENABLE
316 Support for StrongARM 11x0 based boards.
319 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442"
321 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
322 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
323 the Samsung SMDK2410 development board (and derivatives).
331 Support for the StrongARM based Digital DNARD machine, also known
332 as "Shark" (<http://www.shark-linux.de/shark.html>).
337 Say Y here for systems based on one of the Sharp LH7A40X
338 System on a Chip processors. These CPUs include an ARM922T
339 core with a wide array of integrated devices for
340 hand-held and low-power applications.
345 Support for TI's OMAP platform (OMAP1 and OMAP2).
349 source "arch/arm/mach-clps711x/Kconfig"
351 source "arch/arm/mach-ep93xx/Kconfig"
353 source "arch/arm/mach-footbridge/Kconfig"
355 source "arch/arm/mach-integrator/Kconfig"
357 source "arch/arm/mach-iop32x/Kconfig"
359 source "arch/arm/mach-iop33x/Kconfig"
361 source "arch/arm/mach-iop13xx/Kconfig"
363 source "arch/arm/mach-ixp4xx/Kconfig"
365 source "arch/arm/mach-ixp2000/Kconfig"
367 source "arch/arm/mach-ixp23xx/Kconfig"
369 source "arch/arm/mach-pxa/Kconfig"
371 source "arch/arm/mach-sa1100/Kconfig"
373 source "arch/arm/plat-omap/Kconfig"
375 source "arch/arm/mach-omap1/Kconfig"
377 source "arch/arm/mach-omap2/Kconfig"
379 source "arch/arm/mach-s3c2410/Kconfig"
381 source "arch/arm/mach-lh7a40x/Kconfig"
383 source "arch/arm/mach-imx/Kconfig"
385 source "arch/arm/mach-h720x/Kconfig"
387 source "arch/arm/mach-versatile/Kconfig"
389 source "arch/arm/mach-aaec2000/Kconfig"
391 source "arch/arm/mach-realview/Kconfig"
393 source "arch/arm/mach-at91rm9200/Kconfig"
395 source "arch/arm/mach-netx/Kconfig"
397 # Definitions to make life easier
404 source arch/arm/mm/Kconfig
407 bool "Enable iWMMXt support"
408 depends CPU_XSCALE || CPU_XSC3
411 Enable support for iWMMXt context switching at run time if
412 running on a CPU that supports it.
414 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
417 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
421 source "arch/arm/Kconfig-nommu"
426 source "arch/arm/common/Kconfig"
428 config FORCE_MAX_ZONEORDER
441 Find out whether you have ISA slots on your motherboard. ISA is the
442 name of a bus system, i.e. the way the CPU talks to the other stuff
443 inside your box. Other bus systems are PCI, EISA, MicroChannel
444 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
445 newer boards don't support it. If you have ISA, say Y, otherwise N.
447 # Select ISA DMA controller support
452 # Select ISA DMA interface
457 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
459 Find out whether you have a PCI motherboard. PCI is the name of a
460 bus system, i.e. the way the CPU talks to the other stuff inside
461 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
462 VESA. If you have PCI, say Y, otherwise N.
464 The PCI-HOWTO, available from
465 <http://www.tldp.org/docs.html#howto>, contains valuable
466 information about which PCI hardware does work under Linux and which
469 # Select the host bridge type
470 config PCI_HOST_VIA82C505
472 depends on PCI && ARCH_SHARK
475 source "drivers/pci/Kconfig"
477 source "drivers/pcmcia/Kconfig"
481 menu "Kernel Features"
484 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
485 depends on EXPERIMENTAL && REALVIEW_MPCORE
487 This enables support for systems with more than one CPU. If you have
488 a system with only one CPU, like most personal computers, say N. If
489 you have a system with more than one CPU, say Y.
491 If you say N here, the kernel will run on single and multiprocessor
492 machines, but will use only one CPU of a multiprocessor machine. If
493 you say Y here, the kernel will run on many, but not all, single
494 processor machines. On a single processor machine, the kernel will
495 run faster if you say N here.
497 See also the <file:Documentation/smp.txt>,
498 <file:Documentation/i386/IO-APIC.txt>,
499 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
500 <http://www.linuxdoc.org/docs.html#howto>.
502 If you don't know what to do here, say N.
505 int "Maximum number of CPUs (2-32)"
511 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
512 depends on SMP && HOTPLUG && EXPERIMENTAL
514 Say Y here to experiment with turning CPUs off and on. CPUs
515 can be controlled through /sys/devices/system/cpu.
518 bool "Use local timer interrupts"
519 depends on SMP && REALVIEW_MPCORE
522 Enable support for local timers on SMP platforms, rather then the
523 legacy IPI broadcast method. Local timers allows the system
524 accounting to be spread across the timer interval, preventing a
525 "thundering herd" at every timer tick.
528 bool "Preemptible Kernel (EXPERIMENTAL)"
529 depends on EXPERIMENTAL
531 This option reduces the latency of the kernel when reacting to
532 real-time or interactive events by allowing a low priority process to
533 be preempted even if it is in kernel mode executing a system call.
534 This allows applications to run more reliably even when the system is
537 Say Y here if you are building a kernel for a desktop, embedded
538 or real-time system. Say N if you are unsure.
541 bool "Dynamic tick timer"
543 Select this option if you want to disable continuous timer ticks
544 and have them programmed to occur as required. This option saves
545 power as the system can remain in idle state for longer.
547 By default dynamic tick is disabled during the boot, and can be
548 manually enabled with:
550 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
552 Alternatively, if you want dynamic tick automatically enabled
553 during boot, pass "dyntick=enable" via the kernel command string.
555 Please note that dynamic tick may affect the accuracy of
556 timekeeping on some platforms depending on the implementation.
557 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
558 to have accurate timekeeping with dynamic tick.
562 default 128 if ARCH_L7200
563 default 200 if ARCH_EBSA110 || ARCH_S3C2410
564 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
568 bool "Use the ARM EABI to compile the kernel"
570 This option allows for the kernel to be compiled using the latest
571 ARM ABI (aka EABI). This is only useful if you are using a user
572 space environment that is also compiled with EABI.
574 Since there are major incompatibilities between the legacy ABI and
575 EABI, especially with regard to structure member alignment, this
576 option also changes the kernel syscall calling convention to
577 disambiguate both ABIs and allow for backward compatibility support
578 (selected with CONFIG_OABI_COMPAT).
580 To use this you need GCC version 4.0.0 or later.
583 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
584 depends on AEABI && EXPERIMENTAL
587 This option preserves the old syscall interface along with the
588 new (ARM EABI) one. It also provides a compatibility layer to
589 intercept syscalls that have structure arguments which layout
590 in memory differs between the legacy ABI and the new ARM EABI
591 (only for non "thumb" binaries). This option adds a tiny
592 overhead to all syscalls and produces a slightly larger kernel.
593 If you know you'll be using only pure EABI user space then you
594 can say N here. If this option is not selected and you attempt
595 to execute a legacy ABI binary then the result will be
596 UNPREDICTABLE (in fact it can be predicted that it won't work
597 at all). If in doubt say Y.
599 config ARCH_DISCONTIGMEM_ENABLE
601 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
603 Say Y to support efficient handling of discontiguous physical memory,
604 for architectures which are either NUMA (Non-Uniform Memory Access)
605 or have huge holes in the physical address space for other reasons.
606 See <file:Documentation/vm/numa> for more.
610 default "4" if ARCH_LH7A40X
612 depends on NEED_MULTIPLE_NODES
617 bool "Timer and CPU usage LEDs"
618 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
619 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
620 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
621 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
622 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
623 ARCH_AT91 || MACH_TRIZEPS4
625 If you say Y here, the LEDs on your machine will be used
626 to provide useful information about your current system status.
628 If you are compiling a kernel for a NetWinder or EBSA-285, you will
629 be able to select which LEDs are active using the options below. If
630 you are compiling a kernel for the EBSA-110 or the LART however, the
631 red LED will simply flash regularly to indicate that the system is
632 still functional. It is safe to say Y here if you have a CATS
633 system, but the driver will do nothing.
636 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
637 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
639 default y if ARCH_EBSA110
641 If you say Y here, one of the system LEDs (the green one on the
642 NetWinder, the amber one on the EBSA285, or the red one on the LART)
643 will flash regularly to indicate that the system is still
644 operational. This is mainly useful to kernel hackers who are
645 debugging unstable kernels.
647 The LART uses the same LED for both Timer LED and CPU usage LED
648 functions. You may choose to use both, but the Timer LED function
649 will overrule the CPU usage LED.
652 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
653 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
656 If you say Y here, the red LED will be used to give a good real
657 time indication of CPU usage, by lighting whenever the idle task
658 is not currently executing.
660 The LART uses the same LED for both Timer LED and CPU usage LED
661 functions. You may choose to use both, but the Timer LED function
662 will overrule the CPU usage LED.
664 config ALIGNMENT_TRAP
666 depends on CPU_CP15_MMU
667 default y if !ARCH_EBSA110
669 ARM processors cannot fetch/store information which is not
670 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
671 address divisible by 4. On 32-bit ARM processors, these non-aligned
672 fetch/store instructions will be emulated in software if you say
673 here, which has a severe performance impact. This is necessary for
674 correct operation of some network protocols. With an IP-only
675 configuration it is safe to say N, otherwise say Y.
681 # Compressed boot loader in ROM. Yes, we really want to ask about
682 # TEXT and BSS so we preserve their values in the config files.
683 config ZBOOT_ROM_TEXT
684 hex "Compressed ROM boot loader base address"
687 The physical address at which the ROM-able zImage is to be
688 placed in the target. Platforms which normally make use of
689 ROM-able zImage formats normally set this to a suitable
690 value in their defconfig file.
692 If ZBOOT_ROM is not enabled, this has no effect.
695 hex "Compressed ROM boot loader BSS address"
698 The base address of an area of read/write memory in the target
699 for the ROM-able zImage which must be available while the
700 decompressor is running. It must be large enough to hold the
701 entire decompressed kernel plus an additional 128 KiB.
702 Platforms which normally make use of ROM-able zImage formats
703 normally set this to a suitable value in their defconfig file.
705 If ZBOOT_ROM is not enabled, this has no effect.
708 bool "Compressed boot loader in ROM/flash"
709 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
711 Say Y here if you intend to execute your compressed kernel image
712 (zImage) directly from ROM or flash. If unsure, say N.
715 string "Default kernel command string"
718 On some architectures (EBSA110 and CATS), there is currently no way
719 for the boot loader to pass arguments to the kernel. For these
720 architectures, you should supply some command-line options at build
721 time by entering them here. As a minimum, you should specify the
722 memory size and the root device (e.g., mem=64M root=/dev/nfs).
725 bool "Kernel Execute-In-Place from ROM"
726 depends on !ZBOOT_ROM
728 Execute-In-Place allows the kernel to run from non-volatile storage
729 directly addressable by the CPU, such as NOR flash. This saves RAM
730 space since the text section of the kernel is not loaded from flash
731 to RAM. Read-write sections, such as the data section and stack,
732 are still copied to RAM. The XIP kernel is not compressed since
733 it has to run directly from flash, so it will take more space to
734 store it. The flash address used to link the kernel object files,
735 and for storing it, is configuration dependent. Therefore, if you
736 say Y here, you must know the proper physical address where to
737 store the kernel image depending on your own flash memory usage.
739 Also note that the make target becomes "make xipImage" rather than
740 "make zImage" or "make Image". The final kernel binary to put in
741 ROM memory will be arch/arm/boot/xipImage.
746 hex "XIP Kernel Physical Location"
747 depends on XIP_KERNEL
750 This is the physical address in your flash memory the kernel will
751 be linked for and stored to. This address is dependent on your
756 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
758 menu "CPU Frequency scaling"
760 source "drivers/cpufreq/Kconfig"
762 config CPU_FREQ_SA1100
764 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
767 config CPU_FREQ_SA1110
769 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
772 config CPU_FREQ_INTEGRATOR
773 tristate "CPUfreq driver for ARM Integrator CPUs"
774 depends on ARCH_INTEGRATOR && CPU_FREQ
777 This enables the CPUfreq driver for ARM Integrator CPUs.
779 For details, take a look at <file:Documentation/cpu-freq>.
784 tristate "CPUfreq driver for i.MX CPUs"
785 depends on ARCH_IMX && CPU_FREQ
788 This enables the CPUfreq driver for i.MX CPUs.
796 menu "Floating point emulation"
798 comment "At least one emulation must be selected"
801 bool "NWFPE math emulation"
802 depends on !AEABI || OABI_COMPAT
804 Say Y to include the NWFPE floating point emulator in the kernel.
805 This is necessary to run most binaries. Linux does not currently
806 support floating point hardware so you need to say Y here even if
807 your machine has an FPA or floating point co-processor podule.
809 You may say N here if you are going to load the Acorn FPEmulator
813 bool "Support extended precision"
816 Say Y to include 80-bit support in the kernel floating-point
817 emulator. Otherwise, only 32 and 64-bit support is compiled in.
818 Note that gcc does not generate 80-bit operations by default,
819 so in most cases this option only enlarges the size of the
820 floating point emulator without any good reason.
822 You almost surely want to say N here.
825 bool "FastFPE math emulation (EXPERIMENTAL)"
826 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
828 Say Y here to include the FAST floating point emulator in the kernel.
829 This is an experimental much faster emulator which now also has full
830 precision for the mantissa. It does not support any exceptions.
831 It is very simple, and approximately 3-6 times faster than NWFPE.
833 It should be sufficient for most programs. It may be not suitable
834 for scientific calculations, but you have to check this for yourself.
835 If you do not feel you need a faster FP emulation you should better
839 bool "VFP-format floating point maths"
840 depends on CPU_V6 || CPU_ARM926T
842 Say Y to include VFP support code in the kernel. This is needed
843 if your hardware includes a VFP unit.
845 Please see <file:Documentation/arm/VFP/release-notes.txt> for
846 release notes and additional status information.
848 Say N if your target does not have VFP hardware.
852 menu "Userspace binary formats"
854 source "fs/Kconfig.binfmt"
857 tristate "RISC OS personality"
860 Say Y here to include the kernel code necessary if you want to run
861 Acorn RISC OS/Arthur binaries under Linux. This code is still very
862 experimental; if this sounds frightening, say N and sleep in peace.
863 You can also say M here to compile this support as a module (which
864 will be called arthur).
868 menu "Power management options"
870 source "kernel/power/Kconfig"
876 menu "Device Drivers"
878 source "drivers/base/Kconfig"
880 source "drivers/connector/Kconfig"
882 if ALIGNMENT_TRAP || !CPU_CP15_MMU
883 source "drivers/mtd/Kconfig"
886 source "drivers/parport/Kconfig"
888 source "drivers/pnp/Kconfig"
890 source "drivers/block/Kconfig"
892 source "drivers/acorn/block/Kconfig"
894 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
895 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
896 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
898 source "drivers/ide/Kconfig"
901 source "drivers/scsi/Kconfig"
903 source "drivers/ata/Kconfig"
905 source "drivers/md/Kconfig"
907 source "drivers/message/fusion/Kconfig"
909 source "drivers/ieee1394/Kconfig"
911 source "drivers/message/i2o/Kconfig"
913 source "drivers/net/Kconfig"
915 source "drivers/isdn/Kconfig"
917 # input before char - char/joystick depends on it. As does USB.
919 source "drivers/input/Kconfig"
921 source "drivers/char/Kconfig"
923 source "drivers/i2c/Kconfig"
925 source "drivers/spi/Kconfig"
927 source "drivers/w1/Kconfig"
929 source "drivers/hwmon/Kconfig"
931 #source "drivers/l3/Kconfig"
933 source "drivers/misc/Kconfig"
935 source "drivers/mfd/Kconfig"
937 source "drivers/leds/Kconfig"
939 source "drivers/media/Kconfig"
941 source "drivers/video/Kconfig"
943 source "sound/Kconfig"
945 source "drivers/hid/Kconfig"
947 source "drivers/usb/Kconfig"
949 source "drivers/mmc/Kconfig"
951 source "drivers/rtc/Kconfig"
957 source "arch/arm/oprofile/Kconfig"
959 source "arch/arm/Kconfig.debug"
961 source "security/Kconfig"
963 source "crypto/Kconfig"