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.
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
377 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
380 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
384 source "arch/arm/Kconfig-nommu"
389 source "arch/arm/common/Kconfig"
391 config FORCE_MAX_ZONEORDER
404 Find out whether you have ISA slots on your motherboard. ISA is the
405 name of a bus system, i.e. the way the CPU talks to the other stuff
406 inside your box. Other bus systems are PCI, EISA, MicroChannel
407 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
408 newer boards don't support it. If you have ISA, say Y, otherwise N.
410 # Select ISA DMA controller support
415 # Select ISA DMA interface
420 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
422 Find out whether you have a PCI motherboard. PCI is the name of a
423 bus system, i.e. the way the CPU talks to the other stuff inside
424 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
425 VESA. If you have PCI, say Y, otherwise N.
427 The PCI-HOWTO, available from
428 <http://www.tldp.org/docs.html#howto>, contains valuable
429 information about which PCI hardware does work under Linux and which
432 # Select the host bridge type
433 config PCI_HOST_VIA82C505
435 depends on PCI && ARCH_SHARK
438 source "drivers/pci/Kconfig"
440 source "drivers/pcmcia/Kconfig"
444 menu "Kernel Features"
447 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
448 depends on EXPERIMENTAL && REALVIEW_MPCORE
450 This enables support for systems with more than one CPU. If you have
451 a system with only one CPU, like most personal computers, say N. If
452 you have a system with more than one CPU, say Y.
454 If you say N here, the kernel will run on single and multiprocessor
455 machines, but will use only one CPU of a multiprocessor machine. If
456 you say Y here, the kernel will run on many, but not all, single
457 processor machines. On a single processor machine, the kernel will
458 run faster if you say N here.
460 See also the <file:Documentation/smp.txt>,
461 <file:Documentation/i386/IO-APIC.txt>,
462 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
463 <http://www.linuxdoc.org/docs.html#howto>.
465 If you don't know what to do here, say N.
468 int "Maximum number of CPUs (2-32)"
474 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
475 depends on SMP && HOTPLUG && EXPERIMENTAL
477 Say Y here to experiment with turning CPUs off and on. CPUs
478 can be controlled through /sys/devices/system/cpu.
481 bool "Use local timer interrupts"
482 depends on SMP && REALVIEW_MPCORE
485 Enable support for local timers on SMP platforms, rather then the
486 legacy IPI broadcast method. Local timers allows the system
487 accounting to be spread across the timer interval, preventing a
488 "thundering herd" at every timer tick.
491 bool "Preemptible Kernel (EXPERIMENTAL)"
492 depends on EXPERIMENTAL
494 This option reduces the latency of the kernel when reacting to
495 real-time or interactive events by allowing a low priority process to
496 be preempted even if it is in kernel mode executing a system call.
497 This allows applications to run more reliably even when the system is
500 Say Y here if you are building a kernel for a desktop, embedded
501 or real-time system. Say N if you are unsure.
504 bool "Dynamic tick timer"
506 Select this option if you want to disable continuous timer ticks
507 and have them programmed to occur as required. This option saves
508 power as the system can remain in idle state for longer.
510 By default dynamic tick is disabled during the boot, and can be
511 manually enabled with:
513 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
515 Alternatively, if you want dynamic tick automatically enabled
516 during boot, pass "dyntick=enable" via the kernel command string.
518 Please note that dynamic tick may affect the accuracy of
519 timekeeping on some platforms depending on the implementation.
520 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
521 to have accurate timekeeping with dynamic tick.
525 default 128 if ARCH_L7200
526 default 200 if ARCH_EBSA110 || ARCH_S3C2410
527 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
531 bool "Use the ARM EABI to compile the kernel"
533 This option allows for the kernel to be compiled using the latest
534 ARM ABI (aka EABI). This is only useful if you are using a user
535 space environment that is also compiled with EABI.
537 Since there are major incompatibilities between the legacy ABI and
538 EABI, especially with regard to structure member alignment, this
539 option also changes the kernel syscall calling convention to
540 disambiguate both ABIs and allow for backward compatibility support
541 (selected with CONFIG_OABI_COMPAT).
543 To use this you need GCC version 4.0.0 or later.
546 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
547 depends on AEABI && EXPERIMENTAL
550 This option preserves the old syscall interface along with the
551 new (ARM EABI) one. It also provides a compatibility layer to
552 intercept syscalls that have structure arguments which layout
553 in memory differs between the legacy ABI and the new ARM EABI
554 (only for non "thumb" binaries). This option adds a tiny
555 overhead to all syscalls and produces a slightly larger kernel.
556 If you know you'll be using only pure EABI user space then you
557 can say N here. If this option is not selected and you attempt
558 to execute a legacy ABI binary then the result will be
559 UNPREDICTABLE (in fact it can be predicted that it won't work
560 at all). If in doubt say Y.
562 config ARCH_DISCONTIGMEM_ENABLE
564 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
566 Say Y to support efficient handling of discontiguous physical memory,
567 for architectures which are either NUMA (Non-Uniform Memory Access)
568 or have huge holes in the physical address space for other reasons.
569 See <file:Documentation/vm/numa> for more.
573 default "4" if ARCH_LH7A40X
575 depends on NEED_MULTIPLE_NODES
580 bool "Timer and CPU usage LEDs"
581 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
582 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
583 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
584 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
585 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
586 ARCH_AT91RM9200 || MACH_TRIZEPS4
588 If you say Y here, the LEDs on your machine will be used
589 to provide useful information about your current system status.
591 If you are compiling a kernel for a NetWinder or EBSA-285, you will
592 be able to select which LEDs are active using the options below. If
593 you are compiling a kernel for the EBSA-110 or the LART however, the
594 red LED will simply flash regularly to indicate that the system is
595 still functional. It is safe to say Y here if you have a CATS
596 system, but the driver will do nothing.
599 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
600 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
602 default y if ARCH_EBSA110
604 If you say Y here, one of the system LEDs (the green one on the
605 NetWinder, the amber one on the EBSA285, or the red one on the LART)
606 will flash regularly to indicate that the system is still
607 operational. This is mainly useful to kernel hackers who are
608 debugging unstable kernels.
610 The LART uses the same LED for both Timer LED and CPU usage LED
611 functions. You may choose to use both, but the Timer LED function
612 will overrule the CPU usage LED.
615 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
616 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
619 If you say Y here, the red LED will be used to give a good real
620 time indication of CPU usage, by lighting whenever the idle task
621 is not currently executing.
623 The LART uses the same LED for both Timer LED and CPU usage LED
624 functions. You may choose to use both, but the Timer LED function
625 will overrule the CPU usage LED.
627 config ALIGNMENT_TRAP
629 default y if !ARCH_EBSA110
631 ARM processors can not fetch/store information which is not
632 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
633 address divisible by 4. On 32-bit ARM processors, these non-aligned
634 fetch/store instructions will be emulated in software if you say
635 here, which has a severe performance impact. This is necessary for
636 correct operation of some network protocols. With an IP-only
637 configuration it is safe to say N, otherwise say Y.
643 # Compressed boot loader in ROM. Yes, we really want to ask about
644 # TEXT and BSS so we preserve their values in the config files.
645 config ZBOOT_ROM_TEXT
646 hex "Compressed ROM boot loader base address"
649 The physical address at which the ROM-able zImage is to be
650 placed in the target. Platforms which normally make use of
651 ROM-able zImage formats normally set this to a suitable
652 value in their defconfig file.
654 If ZBOOT_ROM is not enabled, this has no effect.
657 hex "Compressed ROM boot loader BSS address"
660 The base address of an area of read/write memory in the target
661 for the ROM-able zImage which must be available while the
662 decompressor is running. It must be large enough to hold the
663 entire decompressed kernel plus an additional 128 KiB.
664 Platforms which normally make use of ROM-able zImage formats
665 normally set this to a suitable value in their defconfig file.
667 If ZBOOT_ROM is not enabled, this has no effect.
670 bool "Compressed boot loader in ROM/flash"
671 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
673 Say Y here if you intend to execute your compressed kernel image
674 (zImage) directly from ROM or flash. If unsure, say N.
677 string "Default kernel command string"
680 On some architectures (EBSA110 and CATS), there is currently no way
681 for the boot loader to pass arguments to the kernel. For these
682 architectures, you should supply some command-line options at build
683 time by entering them here. As a minimum, you should specify the
684 memory size and the root device (e.g., mem=64M root=/dev/nfs).
687 bool "Kernel Execute-In-Place from ROM"
688 depends on !ZBOOT_ROM
690 Execute-In-Place allows the kernel to run from non-volatile storage
691 directly addressable by the CPU, such as NOR flash. This saves RAM
692 space since the text section of the kernel is not loaded from flash
693 to RAM. Read-write sections, such as the data section and stack,
694 are still copied to RAM. The XIP kernel is not compressed since
695 it has to run directly from flash, so it will take more space to
696 store it. The flash address used to link the kernel object files,
697 and for storing it, is configuration dependent. Therefore, if you
698 say Y here, you must know the proper physical address where to
699 store the kernel image depending on your own flash memory usage.
701 Also note that the make target becomes "make xipImage" rather than
702 "make zImage" or "make Image". The final kernel binary to put in
703 ROM memory will be arch/arm/boot/xipImage.
708 hex "XIP Kernel Physical Location"
709 depends on XIP_KERNEL
712 This is the physical address in your flash memory the kernel will
713 be linked for and stored to. This address is dependent on your
718 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP)
720 menu "CPU Frequency scaling"
722 source "drivers/cpufreq/Kconfig"
724 config CPU_FREQ_SA1100
726 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
729 config CPU_FREQ_SA1110
731 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
734 config CPU_FREQ_INTEGRATOR
735 tristate "CPUfreq driver for ARM Integrator CPUs"
736 depends on ARCH_INTEGRATOR && CPU_FREQ
739 This enables the CPUfreq driver for ARM Integrator CPUs.
741 For details, take a look at <file:Documentation/cpu-freq>.
749 menu "Floating point emulation"
751 comment "At least one emulation must be selected"
754 bool "NWFPE math emulation"
755 depends on !AEABI || OABI_COMPAT
757 Say Y to include the NWFPE floating point emulator in the kernel.
758 This is necessary to run most binaries. Linux does not currently
759 support floating point hardware so you need to say Y here even if
760 your machine has an FPA or floating point co-processor podule.
762 You may say N here if you are going to load the Acorn FPEmulator
766 bool "Support extended precision"
769 Say Y to include 80-bit support in the kernel floating-point
770 emulator. Otherwise, only 32 and 64-bit support is compiled in.
771 Note that gcc does not generate 80-bit operations by default,
772 so in most cases this option only enlarges the size of the
773 floating point emulator without any good reason.
775 You almost surely want to say N here.
778 bool "FastFPE math emulation (EXPERIMENTAL)"
779 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
781 Say Y here to include the FAST floating point emulator in the kernel.
782 This is an experimental much faster emulator which now also has full
783 precision for the mantissa. It does not support any exceptions.
784 It is very simple, and approximately 3-6 times faster than NWFPE.
786 It should be sufficient for most programs. It may be not suitable
787 for scientific calculations, but you have to check this for yourself.
788 If you do not feel you need a faster FP emulation you should better
792 bool "VFP-format floating point maths"
793 depends on CPU_V6 || CPU_ARM926T
795 Say Y to include VFP support code in the kernel. This is needed
796 if your hardware includes a VFP unit.
798 Please see <file:Documentation/arm/VFP/release-notes.txt> for
799 release notes and additional status information.
801 Say N if your target does not have VFP hardware.
805 menu "Userspace binary formats"
807 source "fs/Kconfig.binfmt"
810 tristate "RISC OS personality"
813 Say Y here to include the kernel code necessary if you want to run
814 Acorn RISC OS/Arthur binaries under Linux. This code is still very
815 experimental; if this sounds frightening, say N and sleep in peace.
816 You can also say M here to compile this support as a module (which
817 will be called arthur).
821 menu "Power management options"
823 source "kernel/power/Kconfig"
826 tristate "Advanced Power Management Emulation"
828 APM is a BIOS specification for saving power using several different
829 techniques. This is mostly useful for battery powered laptops with
830 APM compliant BIOSes. If you say Y here, the system time will be
831 reset after a RESUME operation, the /proc/apm device will provide
832 battery status information, and user-space programs will receive
833 notification of APM "events" (e.g. battery status change).
835 In order to use APM, you will need supporting software. For location
836 and more information, read <file:Documentation/pm.txt> and the
837 Battery Powered Linux mini-HOWTO, available from
838 <http://www.tldp.org/docs.html#howto>.
840 This driver does not spin down disk drives (see the hdparm(8)
841 manpage ("man 8 hdparm") for that), and it doesn't turn off
842 VESA-compliant "green" monitors.
844 Generally, if you don't have a battery in your machine, there isn't
845 much point in using this driver and you should say N. If you get
846 random kernel OOPSes or reboots that don't seem to be related to
847 anything, try disabling/enabling this option (or disabling/enabling
854 menu "Device Drivers"
856 source "drivers/base/Kconfig"
858 source "drivers/connector/Kconfig"
861 source "drivers/mtd/Kconfig"
864 source "drivers/parport/Kconfig"
866 source "drivers/pnp/Kconfig"
868 source "drivers/block/Kconfig"
870 source "drivers/acorn/block/Kconfig"
872 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
873 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
874 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
876 source "drivers/ide/Kconfig"
879 source "drivers/scsi/Kconfig"
881 source "drivers/md/Kconfig"
883 source "drivers/message/fusion/Kconfig"
885 source "drivers/ieee1394/Kconfig"
887 source "drivers/message/i2o/Kconfig"
889 source "drivers/net/Kconfig"
891 source "drivers/isdn/Kconfig"
893 # input before char - char/joystick depends on it. As does USB.
895 source "drivers/input/Kconfig"
897 source "drivers/char/Kconfig"
899 source "drivers/i2c/Kconfig"
901 source "drivers/spi/Kconfig"
903 source "drivers/w1/Kconfig"
905 source "drivers/hwmon/Kconfig"
907 #source "drivers/l3/Kconfig"
909 source "drivers/misc/Kconfig"
911 source "drivers/mfd/Kconfig"
913 source "drivers/leds/Kconfig"
915 source "drivers/media/Kconfig"
917 source "drivers/video/Kconfig"
919 source "sound/Kconfig"
921 source "drivers/usb/Kconfig"
923 source "drivers/mmc/Kconfig"
925 source "drivers/rtc/Kconfig"
931 source "arch/arm/oprofile/Kconfig"
933 source "arch/arm/Kconfig.debug"
935 source "security/Kconfig"
937 source "crypto/Kconfig"