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/>.
27 The Extended Industry Standard Architecture (EISA) bus was
28 developed as an open alternative to the IBM MicroChannel bus.
30 The EISA bus provided some of the features of the IBM MicroChannel
31 bus while maintaining backward compatibility with cards made for
32 the older ISA bus. The EISA bus saw limited use between 1988 and
33 1995 when it was made obsolete by the PCI bus.
35 Say Y here if you are building a kernel for an EISA-based machine.
45 MicroChannel Architecture is found in some IBM PS/2 machines and
46 laptops. It is a bus system similar to PCI or ISA. See
47 <file:Documentation/mca.txt> (and especially the web page given
48 there) before attempting to build an MCA bus kernel.
50 config GENERIC_HARDIRQS
54 config HARDIRQS_SW_RESEND
58 config GENERIC_IRQ_PROBE
62 config RWSEM_GENERIC_SPINLOCK
66 config RWSEM_XCHGADD_ALGORITHM
69 config GENERIC_HWEIGHT
73 config GENERIC_CALIBRATE_DELAY
77 config GENERIC_BUST_SPINLOCK
80 config ARCH_MAY_HAVE_PC_FDC
83 config GENERIC_ISA_DMA
94 default 0xffff0000 if MMU
95 default DRAM_BASE if REMAP_VECTORS_TO_RAM
98 The base address of exception vectors.
100 source "init/Kconfig"
105 prompt "ARM system type"
106 default ARCH_VERSATILE
109 bool "Agilent AAEC-2000 based"
112 This enables support for systems based on the Agilent AAEC-2000
114 config ARCH_INTEGRATOR
115 bool "ARM Ltd. Integrator family"
119 Support for ARM's Integrator platform.
122 bool "ARM Ltd. RealView family"
126 This enables support for ARM Ltd RealView boards.
128 config ARCH_VERSATILE
129 bool "ARM Ltd. Versatile family"
134 This enables support for ARM Ltd Versatile board.
139 This enables support for systems based on the Atmel AT91RM9200
140 and AT91SAM9xxx processors.
143 bool "Cirrus CL-PS7500FE"
147 Support for the Cirrus Logic PS7500FE system-on-a-chip.
150 bool "Cirrus Logic CLPS711x/EP721x-based"
152 Support for Cirrus Logic 711x/721x based boards.
157 select FOOTBRIDGE_ADDIN
159 Support for Intel's EBSA285 companion chip.
165 This is an evaluation board for the StrongARM processor available
166 from Digital. It has limited hardware on-board, including an
167 Ethernet interface, two PCMCIA sockets, two serial ports and a
175 This enables support for the Cirrus EP93xx series of CPUs.
177 config ARCH_FOOTBRIDGE
181 Support for systems based on the DC21285 companion chip
182 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
185 bool "Hilscher NetX based"
188 This enables support for systems based on the Hilscher NetX Soc
191 bool "Hynix HMS720x-based"
194 This enables support for systems based on the Hynix HMS720x
199 Support for Motorola's i.MX family of processors (MX1, MXL).
206 Support for Intel's IOP3XX (XScale) family of processors.
212 Support for Intel's IXP4XX (XScale) family of processors.
215 bool "IXP2400/2800-based"
219 Support for Intel's IXP2400/2800 (XScale) family of processors.
226 Support for Intel's IXP23xx (XScale) family of processors.
232 Say Y here if you intend to run this kernel on a LinkUp Systems
233 L7200 Software Development Board which uses an ARM720T processor.
234 Information on this board can be obtained at:
236 <http://www.linkupsys.com/>
238 If you have any questions or comments about the Linux kernel port
239 to this board, send e-mail to <sjhill@cotw.com>.
242 bool "Philips Nexperia PNX4008 Mobile"
244 This enables support for Philips PNX4008 mobile platform.
251 Support for Intel's PXA2XX processor line.
258 select ARCH_MAY_HAVE_PC_FDC
261 On the Acorn Risc-PC, Linux can support the internal IDE disk and
262 CD-ROM interface, serial and parallel port, and the floppy drive.
267 select ARCH_DISCONTIGMEM_ENABLE
270 Support for StrongARM 11x0 based boards.
273 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442"
275 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
276 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
277 the Samsung SMDK2410 development board (and derivatives).
285 Support for the StrongARM based Digital DNARD machine, also known
286 as "Shark" (<http://www.shark-linux.de/shark.html>).
291 Say Y here for systems based on one of the Sharp LH7A40X
292 System on a Chip processors. These CPUs include an ARM922T
293 core with a wide array of integrated devices for
294 hand-held and low-power applications.
299 Support for TI's OMAP platform (OMAP1 and OMAP2).
303 source "arch/arm/mach-clps711x/Kconfig"
305 source "arch/arm/mach-ep93xx/Kconfig"
307 source "arch/arm/mach-footbridge/Kconfig"
309 source "arch/arm/mach-integrator/Kconfig"
311 source "arch/arm/mach-iop3xx/Kconfig"
313 source "arch/arm/mach-ixp4xx/Kconfig"
315 source "arch/arm/mach-ixp2000/Kconfig"
317 source "arch/arm/mach-ixp23xx/Kconfig"
319 source "arch/arm/mach-pxa/Kconfig"
321 source "arch/arm/mach-sa1100/Kconfig"
323 source "arch/arm/plat-omap/Kconfig"
325 source "arch/arm/mach-omap1/Kconfig"
327 source "arch/arm/mach-omap2/Kconfig"
329 source "arch/arm/mach-s3c2410/Kconfig"
331 source "arch/arm/mach-lh7a40x/Kconfig"
333 source "arch/arm/mach-imx/Kconfig"
335 source "arch/arm/mach-h720x/Kconfig"
337 source "arch/arm/mach-versatile/Kconfig"
339 source "arch/arm/mach-aaec2000/Kconfig"
341 source "arch/arm/mach-realview/Kconfig"
343 source "arch/arm/mach-at91rm9200/Kconfig"
345 source "arch/arm/mach-netx/Kconfig"
347 # Definitions to make life easier
351 source arch/arm/mm/Kconfig
353 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
356 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
360 source "arch/arm/Kconfig-nommu"
365 source "arch/arm/common/Kconfig"
367 config FORCE_MAX_ZONEORDER
380 Find out whether you have ISA slots on your motherboard. ISA is the
381 name of a bus system, i.e. the way the CPU talks to the other stuff
382 inside your box. Other bus systems are PCI, EISA, MicroChannel
383 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
384 newer boards don't support it. If you have ISA, say Y, otherwise N.
386 # Select ISA DMA controller support
391 # Select ISA DMA interface
396 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
398 Find out whether you have a PCI motherboard. PCI is the name of a
399 bus system, i.e. the way the CPU talks to the other stuff inside
400 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
401 VESA. If you have PCI, say Y, otherwise N.
403 The PCI-HOWTO, available from
404 <http://www.tldp.org/docs.html#howto>, contains valuable
405 information about which PCI hardware does work under Linux and which
408 # Select the host bridge type
409 config PCI_HOST_VIA82C505
411 depends on PCI && ARCH_SHARK
414 source "drivers/pci/Kconfig"
416 source "drivers/pcmcia/Kconfig"
420 menu "Kernel Features"
423 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
424 depends on EXPERIMENTAL && REALVIEW_MPCORE
426 This enables support for systems with more than one CPU. If you have
427 a system with only one CPU, like most personal computers, say N. If
428 you have a system with more than one CPU, say Y.
430 If you say N here, the kernel will run on single and multiprocessor
431 machines, but will use only one CPU of a multiprocessor machine. If
432 you say Y here, the kernel will run on many, but not all, single
433 processor machines. On a single processor machine, the kernel will
434 run faster if you say N here.
436 See also the <file:Documentation/smp.txt>,
437 <file:Documentation/i386/IO-APIC.txt>,
438 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
439 <http://www.linuxdoc.org/docs.html#howto>.
441 If you don't know what to do here, say N.
444 int "Maximum number of CPUs (2-32)"
450 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
451 depends on SMP && HOTPLUG && EXPERIMENTAL
453 Say Y here to experiment with turning CPUs off and on. CPUs
454 can be controlled through /sys/devices/system/cpu.
457 bool "Use local timer interrupts"
458 depends on SMP && REALVIEW_MPCORE
461 Enable support for local timers on SMP platforms, rather then the
462 legacy IPI broadcast method. Local timers allows the system
463 accounting to be spread across the timer interval, preventing a
464 "thundering herd" at every timer tick.
467 bool "Preemptible Kernel (EXPERIMENTAL)"
468 depends on EXPERIMENTAL
470 This option reduces the latency of the kernel when reacting to
471 real-time or interactive events by allowing a low priority process to
472 be preempted even if it is in kernel mode executing a system call.
473 This allows applications to run more reliably even when the system is
476 Say Y here if you are building a kernel for a desktop, embedded
477 or real-time system. Say N if you are unsure.
480 bool "Dynamic tick timer"
482 Select this option if you want to disable continuous timer ticks
483 and have them programmed to occur as required. This option saves
484 power as the system can remain in idle state for longer.
486 By default dynamic tick is disabled during the boot, and can be
487 manually enabled with:
489 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
491 Alternatively, if you want dynamic tick automatically enabled
492 during boot, pass "dyntick=enable" via the kernel command string.
494 Please note that dynamic tick may affect the accuracy of
495 timekeeping on some platforms depending on the implementation.
496 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
497 to have accurate timekeeping with dynamic tick.
501 default 128 if ARCH_L7200
502 default 200 if ARCH_EBSA110 || ARCH_S3C2410
503 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
507 bool "Use the ARM EABI to compile the kernel"
509 This option allows for the kernel to be compiled using the latest
510 ARM ABI (aka EABI). This is only useful if you are using a user
511 space environment that is also compiled with EABI.
513 Since there are major incompatibilities between the legacy ABI and
514 EABI, especially with regard to structure member alignment, this
515 option also changes the kernel syscall calling convention to
516 disambiguate both ABIs and allow for backward compatibility support
517 (selected with CONFIG_OABI_COMPAT).
519 To use this you need GCC version 4.0.0 or later.
522 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
523 depends on AEABI && EXPERIMENTAL
526 This option preserves the old syscall interface along with the
527 new (ARM EABI) one. It also provides a compatibility layer to
528 intercept syscalls that have structure arguments which layout
529 in memory differs between the legacy ABI and the new ARM EABI
530 (only for non "thumb" binaries). This option adds a tiny
531 overhead to all syscalls and produces a slightly larger kernel.
532 If you know you'll be using only pure EABI user space then you
533 can say N here. If this option is not selected and you attempt
534 to execute a legacy ABI binary then the result will be
535 UNPREDICTABLE (in fact it can be predicted that it won't work
536 at all). If in doubt say Y.
538 config ARCH_DISCONTIGMEM_ENABLE
540 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
542 Say Y to support efficient handling of discontiguous physical memory,
543 for architectures which are either NUMA (Non-Uniform Memory Access)
544 or have huge holes in the physical address space for other reasons.
545 See <file:Documentation/vm/numa> for more.
549 default "4" if ARCH_LH7A40X
551 depends on NEED_MULTIPLE_NODES
556 bool "Timer and CPU usage LEDs"
557 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
558 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
559 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
560 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
561 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
562 ARCH_AT91RM9200 || MACH_TRIZEPS4
564 If you say Y here, the LEDs on your machine will be used
565 to provide useful information about your current system status.
567 If you are compiling a kernel for a NetWinder or EBSA-285, you will
568 be able to select which LEDs are active using the options below. If
569 you are compiling a kernel for the EBSA-110 or the LART however, the
570 red LED will simply flash regularly to indicate that the system is
571 still functional. It is safe to say Y here if you have a CATS
572 system, but the driver will do nothing.
575 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
576 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
578 default y if ARCH_EBSA110
580 If you say Y here, one of the system LEDs (the green one on the
581 NetWinder, the amber one on the EBSA285, or the red one on the LART)
582 will flash regularly to indicate that the system is still
583 operational. This is mainly useful to kernel hackers who are
584 debugging unstable kernels.
586 The LART uses the same LED for both Timer LED and CPU usage LED
587 functions. You may choose to use both, but the Timer LED function
588 will overrule the CPU usage LED.
591 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
592 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
595 If you say Y here, the red LED will be used to give a good real
596 time indication of CPU usage, by lighting whenever the idle task
597 is not currently executing.
599 The LART uses the same LED for both Timer LED and CPU usage LED
600 functions. You may choose to use both, but the Timer LED function
601 will overrule the CPU usage LED.
603 config ALIGNMENT_TRAP
605 default y if !ARCH_EBSA110
607 ARM processors can not fetch/store information which is not
608 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
609 address divisible by 4. On 32-bit ARM processors, these non-aligned
610 fetch/store instructions will be emulated in software if you say
611 here, which has a severe performance impact. This is necessary for
612 correct operation of some network protocols. With an IP-only
613 configuration it is safe to say N, otherwise say Y.
619 # Compressed boot loader in ROM. Yes, we really want to ask about
620 # TEXT and BSS so we preserve their values in the config files.
621 config ZBOOT_ROM_TEXT
622 hex "Compressed ROM boot loader base address"
625 The physical address at which the ROM-able zImage is to be
626 placed in the target. Platforms which normally make use of
627 ROM-able zImage formats normally set this to a suitable
628 value in their defconfig file.
630 If ZBOOT_ROM is not enabled, this has no effect.
633 hex "Compressed ROM boot loader BSS address"
636 The base address of 64KiB of read/write memory in the target
637 for the ROM-able zImage, which must be available while the
638 decompressor is running. Platforms which normally make use of
639 ROM-able zImage formats normally set this to a suitable
640 value in their defconfig file.
642 If ZBOOT_ROM is not enabled, this has no effect.
645 bool "Compressed boot loader in ROM/flash"
646 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
648 Say Y here if you intend to execute your compressed kernel image
649 (zImage) directly from ROM or flash. If unsure, say N.
652 string "Default kernel command string"
655 On some architectures (EBSA110 and CATS), there is currently no way
656 for the boot loader to pass arguments to the kernel. For these
657 architectures, you should supply some command-line options at build
658 time by entering them here. As a minimum, you should specify the
659 memory size and the root device (e.g., mem=64M root=/dev/nfs).
662 bool "Kernel Execute-In-Place from ROM"
663 depends on !ZBOOT_ROM
665 Execute-In-Place allows the kernel to run from non-volatile storage
666 directly addressable by the CPU, such as NOR flash. This saves RAM
667 space since the text section of the kernel is not loaded from flash
668 to RAM. Read-write sections, such as the data section and stack,
669 are still copied to RAM. The XIP kernel is not compressed since
670 it has to run directly from flash, so it will take more space to
671 store it. The flash address used to link the kernel object files,
672 and for storing it, is configuration dependent. Therefore, if you
673 say Y here, you must know the proper physical address where to
674 store the kernel image depending on your own flash memory usage.
676 Also note that the make target becomes "make xipImage" rather than
677 "make zImage" or "make Image". The final kernel binary to put in
678 ROM memory will be arch/arm/boot/xipImage.
683 hex "XIP Kernel Physical Location"
684 depends on XIP_KERNEL
687 This is the physical address in your flash memory the kernel will
688 be linked for and stored to. This address is dependent on your
693 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP)
695 menu "CPU Frequency scaling"
697 source "drivers/cpufreq/Kconfig"
699 config CPU_FREQ_SA1100
701 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
704 config CPU_FREQ_SA1110
706 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
709 config CPU_FREQ_INTEGRATOR
710 tristate "CPUfreq driver for ARM Integrator CPUs"
711 depends on ARCH_INTEGRATOR && CPU_FREQ
714 This enables the CPUfreq driver for ARM Integrator CPUs.
716 For details, take a look at <file:Documentation/cpu-freq>.
724 menu "Floating point emulation"
726 comment "At least one emulation must be selected"
729 bool "NWFPE math emulation"
730 depends on !AEABI || OABI_COMPAT
732 Say Y to include the NWFPE floating point emulator in the kernel.
733 This is necessary to run most binaries. Linux does not currently
734 support floating point hardware so you need to say Y here even if
735 your machine has an FPA or floating point co-processor podule.
737 You may say N here if you are going to load the Acorn FPEmulator
741 bool "Support extended precision"
744 Say Y to include 80-bit support in the kernel floating-point
745 emulator. Otherwise, only 32 and 64-bit support is compiled in.
746 Note that gcc does not generate 80-bit operations by default,
747 so in most cases this option only enlarges the size of the
748 floating point emulator without any good reason.
750 You almost surely want to say N here.
753 bool "FastFPE math emulation (EXPERIMENTAL)"
754 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
756 Say Y here to include the FAST floating point emulator in the kernel.
757 This is an experimental much faster emulator which now also has full
758 precision for the mantissa. It does not support any exceptions.
759 It is very simple, and approximately 3-6 times faster than NWFPE.
761 It should be sufficient for most programs. It may be not suitable
762 for scientific calculations, but you have to check this for yourself.
763 If you do not feel you need a faster FP emulation you should better
767 bool "VFP-format floating point maths"
768 depends on CPU_V6 || CPU_ARM926T
770 Say Y to include VFP support code in the kernel. This is needed
771 if your hardware includes a VFP unit.
773 Please see <file:Documentation/arm/VFP/release-notes.txt> for
774 release notes and additional status information.
776 Say N if your target does not have VFP hardware.
780 menu "Userspace binary formats"
782 source "fs/Kconfig.binfmt"
785 tristate "RISC OS personality"
788 Say Y here to include the kernel code necessary if you want to run
789 Acorn RISC OS/Arthur binaries under Linux. This code is still very
790 experimental; if this sounds frightening, say N and sleep in peace.
791 You can also say M here to compile this support as a module (which
792 will be called arthur).
796 menu "Power management options"
798 source "kernel/power/Kconfig"
801 tristate "Advanced Power Management Emulation"
803 APM is a BIOS specification for saving power using several different
804 techniques. This is mostly useful for battery powered laptops with
805 APM compliant BIOSes. If you say Y here, the system time will be
806 reset after a RESUME operation, the /proc/apm device will provide
807 battery status information, and user-space programs will receive
808 notification of APM "events" (e.g. battery status change).
810 In order to use APM, you will need supporting software. For location
811 and more information, read <file:Documentation/pm.txt> and the
812 Battery Powered Linux mini-HOWTO, available from
813 <http://www.tldp.org/docs.html#howto>.
815 This driver does not spin down disk drives (see the hdparm(8)
816 manpage ("man 8 hdparm") for that), and it doesn't turn off
817 VESA-compliant "green" monitors.
819 Generally, if you don't have a battery in your machine, there isn't
820 much point in using this driver and you should say N. If you get
821 random kernel OOPSes or reboots that don't seem to be related to
822 anything, try disabling/enabling this option (or disabling/enabling
829 menu "Device Drivers"
831 source "drivers/base/Kconfig"
833 source "drivers/connector/Kconfig"
836 source "drivers/mtd/Kconfig"
839 source "drivers/parport/Kconfig"
841 source "drivers/pnp/Kconfig"
843 source "drivers/block/Kconfig"
845 source "drivers/acorn/block/Kconfig"
847 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
848 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
849 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
851 source "drivers/ide/Kconfig"
854 source "drivers/scsi/Kconfig"
856 source "drivers/md/Kconfig"
858 source "drivers/message/fusion/Kconfig"
860 source "drivers/ieee1394/Kconfig"
862 source "drivers/message/i2o/Kconfig"
864 source "drivers/net/Kconfig"
866 source "drivers/isdn/Kconfig"
868 # input before char - char/joystick depends on it. As does USB.
870 source "drivers/input/Kconfig"
872 source "drivers/char/Kconfig"
874 source "drivers/i2c/Kconfig"
876 source "drivers/spi/Kconfig"
878 source "drivers/w1/Kconfig"
880 source "drivers/hwmon/Kconfig"
882 #source "drivers/l3/Kconfig"
884 source "drivers/misc/Kconfig"
886 source "drivers/mfd/Kconfig"
888 source "drivers/leds/Kconfig"
890 source "drivers/media/Kconfig"
892 source "drivers/video/Kconfig"
894 source "sound/Kconfig"
896 source "drivers/usb/Kconfig"
898 source "drivers/mmc/Kconfig"
900 source "drivers/rtc/Kconfig"
906 source "arch/arm/oprofile/Kconfig"
908 source "arch/arm/Kconfig.debug"
910 source "security/Kconfig"
912 source "crypto/Kconfig"