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.
230 Support for Intel's IOP13XX (XScale) family of processors.
237 Support for Intel's IXP4XX (XScale) family of processors.
240 bool "IXP2400/2800-based"
244 Support for Intel's IXP2400/2800 (XScale) family of processors.
251 Support for Intel's IXP23xx (XScale) family of processors.
257 Say Y here if you intend to run this kernel on a LinkUp Systems
258 L7200 Software Development Board which uses an ARM720T processor.
259 Information on this board can be obtained at:
261 <http://www.linkupsys.com/>
263 If you have any questions or comments about the Linux kernel port
264 to this board, send e-mail to <sjhill@cotw.com>.
267 bool "Philips Nexperia PNX4008 Mobile"
269 This enables support for Philips PNX4008 mobile platform.
276 Support for Intel's PXA2XX processor line.
283 select ARCH_MAY_HAVE_PC_FDC
286 On the Acorn Risc-PC, Linux can support the internal IDE disk and
287 CD-ROM interface, serial and parallel port, and the floppy drive.
292 select ARCH_DISCONTIGMEM_ENABLE
295 Support for StrongARM 11x0 based boards.
298 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442"
300 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
301 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
302 the Samsung SMDK2410 development board (and derivatives).
310 Support for the StrongARM based Digital DNARD machine, also known
311 as "Shark" (<http://www.shark-linux.de/shark.html>).
316 Say Y here for systems based on one of the Sharp LH7A40X
317 System on a Chip processors. These CPUs include an ARM922T
318 core with a wide array of integrated devices for
319 hand-held and low-power applications.
324 Support for TI's OMAP platform (OMAP1 and OMAP2).
328 source "arch/arm/mach-clps711x/Kconfig"
330 source "arch/arm/mach-ep93xx/Kconfig"
332 source "arch/arm/mach-footbridge/Kconfig"
334 source "arch/arm/mach-integrator/Kconfig"
336 source "arch/arm/mach-iop32x/Kconfig"
338 source "arch/arm/mach-iop33x/Kconfig"
340 source "arch/arm/mach-iop13xx/Kconfig"
342 source "arch/arm/mach-ixp4xx/Kconfig"
344 source "arch/arm/mach-ixp2000/Kconfig"
346 source "arch/arm/mach-ixp23xx/Kconfig"
348 source "arch/arm/mach-pxa/Kconfig"
350 source "arch/arm/mach-sa1100/Kconfig"
352 source "arch/arm/plat-omap/Kconfig"
354 source "arch/arm/mach-omap1/Kconfig"
356 source "arch/arm/mach-omap2/Kconfig"
358 source "arch/arm/mach-s3c2410/Kconfig"
360 source "arch/arm/mach-lh7a40x/Kconfig"
362 source "arch/arm/mach-imx/Kconfig"
364 source "arch/arm/mach-h720x/Kconfig"
366 source "arch/arm/mach-versatile/Kconfig"
368 source "arch/arm/mach-aaec2000/Kconfig"
370 source "arch/arm/mach-realview/Kconfig"
372 source "arch/arm/mach-at91rm9200/Kconfig"
374 source "arch/arm/mach-netx/Kconfig"
376 # Definitions to make life easier
383 source arch/arm/mm/Kconfig
386 bool "Enable iWMMXt support"
387 depends CPU_XSCALE || CPU_XSC3
390 Enable support for iWMMXt context switching at run time if
391 running on a CPU that supports it.
393 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
396 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
400 source "arch/arm/Kconfig-nommu"
405 source "arch/arm/common/Kconfig"
407 config FORCE_MAX_ZONEORDER
420 Find out whether you have ISA slots on your motherboard. ISA is the
421 name of a bus system, i.e. the way the CPU talks to the other stuff
422 inside your box. Other bus systems are PCI, EISA, MicroChannel
423 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
424 newer boards don't support it. If you have ISA, say Y, otherwise N.
426 # Select ISA DMA controller support
431 # Select ISA DMA interface
436 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
438 Find out whether you have a PCI motherboard. PCI is the name of a
439 bus system, i.e. the way the CPU talks to the other stuff inside
440 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
441 VESA. If you have PCI, say Y, otherwise N.
443 The PCI-HOWTO, available from
444 <http://www.tldp.org/docs.html#howto>, contains valuable
445 information about which PCI hardware does work under Linux and which
448 # Select the host bridge type
449 config PCI_HOST_VIA82C505
451 depends on PCI && ARCH_SHARK
454 source "drivers/pci/Kconfig"
456 source "drivers/pcmcia/Kconfig"
460 menu "Kernel Features"
463 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
464 depends on EXPERIMENTAL && REALVIEW_MPCORE
466 This enables support for systems with more than one CPU. If you have
467 a system with only one CPU, like most personal computers, say N. If
468 you have a system with more than one CPU, say Y.
470 If you say N here, the kernel will run on single and multiprocessor
471 machines, but will use only one CPU of a multiprocessor machine. If
472 you say Y here, the kernel will run on many, but not all, single
473 processor machines. On a single processor machine, the kernel will
474 run faster if you say N here.
476 See also the <file:Documentation/smp.txt>,
477 <file:Documentation/i386/IO-APIC.txt>,
478 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
479 <http://www.linuxdoc.org/docs.html#howto>.
481 If you don't know what to do here, say N.
484 int "Maximum number of CPUs (2-32)"
490 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
491 depends on SMP && HOTPLUG && EXPERIMENTAL
493 Say Y here to experiment with turning CPUs off and on. CPUs
494 can be controlled through /sys/devices/system/cpu.
497 bool "Use local timer interrupts"
498 depends on SMP && REALVIEW_MPCORE
501 Enable support for local timers on SMP platforms, rather then the
502 legacy IPI broadcast method. Local timers allows the system
503 accounting to be spread across the timer interval, preventing a
504 "thundering herd" at every timer tick.
507 bool "Preemptible Kernel (EXPERIMENTAL)"
508 depends on EXPERIMENTAL
510 This option reduces the latency of the kernel when reacting to
511 real-time or interactive events by allowing a low priority process to
512 be preempted even if it is in kernel mode executing a system call.
513 This allows applications to run more reliably even when the system is
516 Say Y here if you are building a kernel for a desktop, embedded
517 or real-time system. Say N if you are unsure.
520 bool "Dynamic tick timer"
522 Select this option if you want to disable continuous timer ticks
523 and have them programmed to occur as required. This option saves
524 power as the system can remain in idle state for longer.
526 By default dynamic tick is disabled during the boot, and can be
527 manually enabled with:
529 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
531 Alternatively, if you want dynamic tick automatically enabled
532 during boot, pass "dyntick=enable" via the kernel command string.
534 Please note that dynamic tick may affect the accuracy of
535 timekeeping on some platforms depending on the implementation.
536 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
537 to have accurate timekeeping with dynamic tick.
541 default 128 if ARCH_L7200
542 default 200 if ARCH_EBSA110 || ARCH_S3C2410
543 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
547 bool "Use the ARM EABI to compile the kernel"
549 This option allows for the kernel to be compiled using the latest
550 ARM ABI (aka EABI). This is only useful if you are using a user
551 space environment that is also compiled with EABI.
553 Since there are major incompatibilities between the legacy ABI and
554 EABI, especially with regard to structure member alignment, this
555 option also changes the kernel syscall calling convention to
556 disambiguate both ABIs and allow for backward compatibility support
557 (selected with CONFIG_OABI_COMPAT).
559 To use this you need GCC version 4.0.0 or later.
562 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
563 depends on AEABI && EXPERIMENTAL
566 This option preserves the old syscall interface along with the
567 new (ARM EABI) one. It also provides a compatibility layer to
568 intercept syscalls that have structure arguments which layout
569 in memory differs between the legacy ABI and the new ARM EABI
570 (only for non "thumb" binaries). This option adds a tiny
571 overhead to all syscalls and produces a slightly larger kernel.
572 If you know you'll be using only pure EABI user space then you
573 can say N here. If this option is not selected and you attempt
574 to execute a legacy ABI binary then the result will be
575 UNPREDICTABLE (in fact it can be predicted that it won't work
576 at all). If in doubt say Y.
578 config ARCH_DISCONTIGMEM_ENABLE
580 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
582 Say Y to support efficient handling of discontiguous physical memory,
583 for architectures which are either NUMA (Non-Uniform Memory Access)
584 or have huge holes in the physical address space for other reasons.
585 See <file:Documentation/vm/numa> for more.
589 default "4" if ARCH_LH7A40X
591 depends on NEED_MULTIPLE_NODES
596 bool "Timer and CPU usage LEDs"
597 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
598 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
599 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
600 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
601 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
602 ARCH_AT91 || MACH_TRIZEPS4
604 If you say Y here, the LEDs on your machine will be used
605 to provide useful information about your current system status.
607 If you are compiling a kernel for a NetWinder or EBSA-285, you will
608 be able to select which LEDs are active using the options below. If
609 you are compiling a kernel for the EBSA-110 or the LART however, the
610 red LED will simply flash regularly to indicate that the system is
611 still functional. It is safe to say Y here if you have a CATS
612 system, but the driver will do nothing.
615 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
616 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
618 default y if ARCH_EBSA110
620 If you say Y here, one of the system LEDs (the green one on the
621 NetWinder, the amber one on the EBSA285, or the red one on the LART)
622 will flash regularly to indicate that the system is still
623 operational. This is mainly useful to kernel hackers who are
624 debugging unstable kernels.
626 The LART uses the same LED for both Timer LED and CPU usage LED
627 functions. You may choose to use both, but the Timer LED function
628 will overrule the CPU usage LED.
631 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
632 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
635 If you say Y here, the red LED will be used to give a good real
636 time indication of CPU usage, by lighting whenever the idle task
637 is not currently executing.
639 The LART uses the same LED for both Timer LED and CPU usage LED
640 functions. You may choose to use both, but the Timer LED function
641 will overrule the CPU usage LED.
643 config ALIGNMENT_TRAP
645 depends on CPU_CP15_MMU
646 default y if !ARCH_EBSA110
648 ARM processors cannot fetch/store information which is not
649 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
650 address divisible by 4. On 32-bit ARM processors, these non-aligned
651 fetch/store instructions will be emulated in software if you say
652 here, which has a severe performance impact. This is necessary for
653 correct operation of some network protocols. With an IP-only
654 configuration it is safe to say N, otherwise say Y.
660 # Compressed boot loader in ROM. Yes, we really want to ask about
661 # TEXT and BSS so we preserve their values in the config files.
662 config ZBOOT_ROM_TEXT
663 hex "Compressed ROM boot loader base address"
666 The physical address at which the ROM-able zImage is to be
667 placed in the target. Platforms which normally make use of
668 ROM-able zImage formats normally set this to a suitable
669 value in their defconfig file.
671 If ZBOOT_ROM is not enabled, this has no effect.
674 hex "Compressed ROM boot loader BSS address"
677 The base address of an area of read/write memory in the target
678 for the ROM-able zImage which must be available while the
679 decompressor is running. It must be large enough to hold the
680 entire decompressed kernel plus an additional 128 KiB.
681 Platforms which normally make use of ROM-able zImage formats
682 normally set this to a suitable value in their defconfig file.
684 If ZBOOT_ROM is not enabled, this has no effect.
687 bool "Compressed boot loader in ROM/flash"
688 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
690 Say Y here if you intend to execute your compressed kernel image
691 (zImage) directly from ROM or flash. If unsure, say N.
694 string "Default kernel command string"
697 On some architectures (EBSA110 and CATS), there is currently no way
698 for the boot loader to pass arguments to the kernel. For these
699 architectures, you should supply some command-line options at build
700 time by entering them here. As a minimum, you should specify the
701 memory size and the root device (e.g., mem=64M root=/dev/nfs).
704 bool "Kernel Execute-In-Place from ROM"
705 depends on !ZBOOT_ROM
707 Execute-In-Place allows the kernel to run from non-volatile storage
708 directly addressable by the CPU, such as NOR flash. This saves RAM
709 space since the text section of the kernel is not loaded from flash
710 to RAM. Read-write sections, such as the data section and stack,
711 are still copied to RAM. The XIP kernel is not compressed since
712 it has to run directly from flash, so it will take more space to
713 store it. The flash address used to link the kernel object files,
714 and for storing it, is configuration dependent. Therefore, if you
715 say Y here, you must know the proper physical address where to
716 store the kernel image depending on your own flash memory usage.
718 Also note that the make target becomes "make xipImage" rather than
719 "make zImage" or "make Image". The final kernel binary to put in
720 ROM memory will be arch/arm/boot/xipImage.
725 hex "XIP Kernel Physical Location"
726 depends on XIP_KERNEL
729 This is the physical address in your flash memory the kernel will
730 be linked for and stored to. This address is dependent on your
735 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP)
737 menu "CPU Frequency scaling"
739 source "drivers/cpufreq/Kconfig"
741 config CPU_FREQ_SA1100
743 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
746 config CPU_FREQ_SA1110
748 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
751 config CPU_FREQ_INTEGRATOR
752 tristate "CPUfreq driver for ARM Integrator CPUs"
753 depends on ARCH_INTEGRATOR && CPU_FREQ
756 This enables the CPUfreq driver for ARM Integrator CPUs.
758 For details, take a look at <file:Documentation/cpu-freq>.
766 menu "Floating point emulation"
768 comment "At least one emulation must be selected"
771 bool "NWFPE math emulation"
772 depends on !AEABI || OABI_COMPAT
774 Say Y to include the NWFPE floating point emulator in the kernel.
775 This is necessary to run most binaries. Linux does not currently
776 support floating point hardware so you need to say Y here even if
777 your machine has an FPA or floating point co-processor podule.
779 You may say N here if you are going to load the Acorn FPEmulator
783 bool "Support extended precision"
786 Say Y to include 80-bit support in the kernel floating-point
787 emulator. Otherwise, only 32 and 64-bit support is compiled in.
788 Note that gcc does not generate 80-bit operations by default,
789 so in most cases this option only enlarges the size of the
790 floating point emulator without any good reason.
792 You almost surely want to say N here.
795 bool "FastFPE math emulation (EXPERIMENTAL)"
796 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
798 Say Y here to include the FAST floating point emulator in the kernel.
799 This is an experimental much faster emulator which now also has full
800 precision for the mantissa. It does not support any exceptions.
801 It is very simple, and approximately 3-6 times faster than NWFPE.
803 It should be sufficient for most programs. It may be not suitable
804 for scientific calculations, but you have to check this for yourself.
805 If you do not feel you need a faster FP emulation you should better
809 bool "VFP-format floating point maths"
810 depends on CPU_V6 || CPU_ARM926T
812 Say Y to include VFP support code in the kernel. This is needed
813 if your hardware includes a VFP unit.
815 Please see <file:Documentation/arm/VFP/release-notes.txt> for
816 release notes and additional status information.
818 Say N if your target does not have VFP hardware.
822 menu "Userspace binary formats"
824 source "fs/Kconfig.binfmt"
827 tristate "RISC OS personality"
830 Say Y here to include the kernel code necessary if you want to run
831 Acorn RISC OS/Arthur binaries under Linux. This code is still very
832 experimental; if this sounds frightening, say N and sleep in peace.
833 You can also say M here to compile this support as a module (which
834 will be called arthur).
838 menu "Power management options"
840 source "kernel/power/Kconfig"
843 tristate "Advanced Power Management Emulation"
845 APM is a BIOS specification for saving power using several different
846 techniques. This is mostly useful for battery powered laptops with
847 APM compliant BIOSes. If you say Y here, the system time will be
848 reset after a RESUME operation, the /proc/apm device will provide
849 battery status information, and user-space programs will receive
850 notification of APM "events" (e.g. battery status change).
852 In order to use APM, you will need supporting software. For location
853 and more information, read <file:Documentation/pm.txt> and the
854 Battery Powered Linux mini-HOWTO, available from
855 <http://www.tldp.org/docs.html#howto>.
857 This driver does not spin down disk drives (see the hdparm(8)
858 manpage ("man 8 hdparm") for that), and it doesn't turn off
859 VESA-compliant "green" monitors.
861 Generally, if you don't have a battery in your machine, there isn't
862 much point in using this driver and you should say N. If you get
863 random kernel OOPSes or reboots that don't seem to be related to
864 anything, try disabling/enabling this option (or disabling/enabling
871 menu "Device Drivers"
873 source "drivers/base/Kconfig"
875 source "drivers/connector/Kconfig"
877 if ALIGNMENT_TRAP || !CPU_CP15_MMU
878 source "drivers/mtd/Kconfig"
881 source "drivers/parport/Kconfig"
883 source "drivers/pnp/Kconfig"
885 source "drivers/block/Kconfig"
887 source "drivers/acorn/block/Kconfig"
889 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
890 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
891 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
893 source "drivers/ide/Kconfig"
896 source "drivers/scsi/Kconfig"
898 source "drivers/ata/Kconfig"
900 source "drivers/md/Kconfig"
902 source "drivers/message/fusion/Kconfig"
904 source "drivers/ieee1394/Kconfig"
906 source "drivers/message/i2o/Kconfig"
908 source "drivers/net/Kconfig"
910 source "drivers/isdn/Kconfig"
912 # input before char - char/joystick depends on it. As does USB.
914 source "drivers/input/Kconfig"
916 source "drivers/char/Kconfig"
918 source "drivers/i2c/Kconfig"
920 source "drivers/spi/Kconfig"
922 source "drivers/w1/Kconfig"
924 source "drivers/hwmon/Kconfig"
926 #source "drivers/l3/Kconfig"
928 source "drivers/misc/Kconfig"
930 source "drivers/mfd/Kconfig"
932 source "drivers/leds/Kconfig"
934 source "drivers/media/Kconfig"
936 source "drivers/video/Kconfig"
938 source "sound/Kconfig"
940 source "drivers/usb/Kconfig"
942 source "drivers/mmc/Kconfig"
944 source "drivers/rtc/Kconfig"
950 source "arch/arm/oprofile/Kconfig"
952 source "arch/arm/Kconfig.debug"
954 source "security/Kconfig"
956 source "crypto/Kconfig"