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 TRACE_IRQFLAGS_SUPPORT
58 config HARDIRQS_SW_RESEND
62 config GENERIC_IRQ_PROBE
66 config RWSEM_GENERIC_SPINLOCK
70 config RWSEM_XCHGADD_ALGORITHM
73 config GENERIC_HWEIGHT
77 config GENERIC_CALIBRATE_DELAY
81 config GENERIC_BUST_SPINLOCK
84 config ARCH_MAY_HAVE_PC_FDC
87 config GENERIC_ISA_DMA
98 default 0xffff0000 if MMU
99 default DRAM_BASE if REMAP_VECTORS_TO_RAM
102 The base address of exception vectors.
104 source "init/Kconfig"
109 prompt "ARM system type"
110 default ARCH_VERSATILE
113 bool "Agilent AAEC-2000 based"
116 This enables support for systems based on the Agilent AAEC-2000
118 config ARCH_INTEGRATOR
119 bool "ARM Ltd. Integrator family"
123 Support for ARM's Integrator platform.
126 bool "ARM Ltd. RealView family"
130 This enables support for ARM Ltd RealView boards.
132 config ARCH_VERSATILE
133 bool "ARM Ltd. Versatile family"
138 This enables support for ARM Ltd Versatile board.
143 This enables support for systems based on the Atmel AT91RM9200
144 and AT91SAM9xxx processors.
147 bool "Cirrus CL-PS7500FE"
151 Support for the Cirrus Logic PS7500FE system-on-a-chip.
154 bool "Cirrus Logic CLPS711x/EP721x-based"
156 Support for Cirrus Logic 711x/721x based boards.
161 select FOOTBRIDGE_ADDIN
163 Support for Intel's EBSA285 companion chip.
169 This is an evaluation board for the StrongARM processor available
170 from Digital. It has limited hardware on-board, including an
171 Ethernet interface, two PCMCIA sockets, two serial ports and a
179 This enables support for the Cirrus EP93xx series of CPUs.
181 config ARCH_FOOTBRIDGE
185 Support for systems based on the DC21285 companion chip
186 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
189 bool "Hilscher NetX based"
192 This enables support for systems based on the Hilscher NetX Soc
195 bool "Hynix HMS720x-based"
198 This enables support for systems based on the Hynix HMS720x
203 Support for Motorola's i.MX family of processors (MX1, MXL).
211 Support for Intel's 80219 and IOP32X (XScale) family of
220 Support for Intel's IOP33X (XScale) family of processors.
226 Support for Intel's IXP4XX (XScale) family of processors.
229 bool "IXP2400/2800-based"
233 Support for Intel's IXP2400/2800 (XScale) family of processors.
240 Support for Intel's IXP23xx (XScale) family of processors.
246 Say Y here if you intend to run this kernel on a LinkUp Systems
247 L7200 Software Development Board which uses an ARM720T processor.
248 Information on this board can be obtained at:
250 <http://www.linkupsys.com/>
252 If you have any questions or comments about the Linux kernel port
253 to this board, send e-mail to <sjhill@cotw.com>.
256 bool "Philips Nexperia PNX4008 Mobile"
258 This enables support for Philips PNX4008 mobile platform.
265 Support for Intel's PXA2XX processor line.
272 select ARCH_MAY_HAVE_PC_FDC
275 On the Acorn Risc-PC, Linux can support the internal IDE disk and
276 CD-ROM interface, serial and parallel port, and the floppy drive.
281 select ARCH_DISCONTIGMEM_ENABLE
284 Support for StrongARM 11x0 based boards.
287 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442"
289 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
290 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
291 the Samsung SMDK2410 development board (and derivatives).
299 Support for the StrongARM based Digital DNARD machine, also known
300 as "Shark" (<http://www.shark-linux.de/shark.html>).
305 Say Y here for systems based on one of the Sharp LH7A40X
306 System on a Chip processors. These CPUs include an ARM922T
307 core with a wide array of integrated devices for
308 hand-held and low-power applications.
313 Support for TI's OMAP platform (OMAP1 and OMAP2).
317 source "arch/arm/mach-clps711x/Kconfig"
319 source "arch/arm/mach-ep93xx/Kconfig"
321 source "arch/arm/mach-footbridge/Kconfig"
323 source "arch/arm/mach-integrator/Kconfig"
325 source "arch/arm/mach-iop32x/Kconfig"
327 source "arch/arm/mach-iop33x/Kconfig"
329 source "arch/arm/mach-ixp4xx/Kconfig"
331 source "arch/arm/mach-ixp2000/Kconfig"
333 source "arch/arm/mach-ixp23xx/Kconfig"
335 source "arch/arm/mach-pxa/Kconfig"
337 source "arch/arm/mach-sa1100/Kconfig"
339 source "arch/arm/plat-omap/Kconfig"
341 source "arch/arm/mach-omap1/Kconfig"
343 source "arch/arm/mach-omap2/Kconfig"
345 source "arch/arm/mach-s3c2410/Kconfig"
347 source "arch/arm/mach-lh7a40x/Kconfig"
349 source "arch/arm/mach-imx/Kconfig"
351 source "arch/arm/mach-h720x/Kconfig"
353 source "arch/arm/mach-versatile/Kconfig"
355 source "arch/arm/mach-aaec2000/Kconfig"
357 source "arch/arm/mach-realview/Kconfig"
359 source "arch/arm/mach-at91rm9200/Kconfig"
361 source "arch/arm/mach-netx/Kconfig"
363 # Definitions to make life easier
370 source arch/arm/mm/Kconfig
372 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
375 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
379 source "arch/arm/Kconfig-nommu"
384 source "arch/arm/common/Kconfig"
386 config FORCE_MAX_ZONEORDER
399 Find out whether you have ISA slots on your motherboard. ISA is the
400 name of a bus system, i.e. the way the CPU talks to the other stuff
401 inside your box. Other bus systems are PCI, EISA, MicroChannel
402 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
403 newer boards don't support it. If you have ISA, say Y, otherwise N.
405 # Select ISA DMA controller support
410 # Select ISA DMA interface
415 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
417 Find out whether you have a PCI motherboard. PCI is the name of a
418 bus system, i.e. the way the CPU talks to the other stuff inside
419 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
420 VESA. If you have PCI, say Y, otherwise N.
422 The PCI-HOWTO, available from
423 <http://www.tldp.org/docs.html#howto>, contains valuable
424 information about which PCI hardware does work under Linux and which
427 # Select the host bridge type
428 config PCI_HOST_VIA82C505
430 depends on PCI && ARCH_SHARK
433 source "drivers/pci/Kconfig"
435 source "drivers/pcmcia/Kconfig"
439 menu "Kernel Features"
442 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
443 depends on EXPERIMENTAL && REALVIEW_MPCORE
445 This enables support for systems with more than one CPU. If you have
446 a system with only one CPU, like most personal computers, say N. If
447 you have a system with more than one CPU, say Y.
449 If you say N here, the kernel will run on single and multiprocessor
450 machines, but will use only one CPU of a multiprocessor machine. If
451 you say Y here, the kernel will run on many, but not all, single
452 processor machines. On a single processor machine, the kernel will
453 run faster if you say N here.
455 See also the <file:Documentation/smp.txt>,
456 <file:Documentation/i386/IO-APIC.txt>,
457 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
458 <http://www.linuxdoc.org/docs.html#howto>.
460 If you don't know what to do here, say N.
463 int "Maximum number of CPUs (2-32)"
469 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
470 depends on SMP && HOTPLUG && EXPERIMENTAL
472 Say Y here to experiment with turning CPUs off and on. CPUs
473 can be controlled through /sys/devices/system/cpu.
476 bool "Use local timer interrupts"
477 depends on SMP && REALVIEW_MPCORE
480 Enable support for local timers on SMP platforms, rather then the
481 legacy IPI broadcast method. Local timers allows the system
482 accounting to be spread across the timer interval, preventing a
483 "thundering herd" at every timer tick.
486 bool "Preemptible Kernel (EXPERIMENTAL)"
487 depends on EXPERIMENTAL
489 This option reduces the latency of the kernel when reacting to
490 real-time or interactive events by allowing a low priority process to
491 be preempted even if it is in kernel mode executing a system call.
492 This allows applications to run more reliably even when the system is
495 Say Y here if you are building a kernel for a desktop, embedded
496 or real-time system. Say N if you are unsure.
499 bool "Dynamic tick timer"
501 Select this option if you want to disable continuous timer ticks
502 and have them programmed to occur as required. This option saves
503 power as the system can remain in idle state for longer.
505 By default dynamic tick is disabled during the boot, and can be
506 manually enabled with:
508 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
510 Alternatively, if you want dynamic tick automatically enabled
511 during boot, pass "dyntick=enable" via the kernel command string.
513 Please note that dynamic tick may affect the accuracy of
514 timekeeping on some platforms depending on the implementation.
515 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
516 to have accurate timekeeping with dynamic tick.
520 default 128 if ARCH_L7200
521 default 200 if ARCH_EBSA110 || ARCH_S3C2410
522 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
526 bool "Use the ARM EABI to compile the kernel"
528 This option allows for the kernel to be compiled using the latest
529 ARM ABI (aka EABI). This is only useful if you are using a user
530 space environment that is also compiled with EABI.
532 Since there are major incompatibilities between the legacy ABI and
533 EABI, especially with regard to structure member alignment, this
534 option also changes the kernel syscall calling convention to
535 disambiguate both ABIs and allow for backward compatibility support
536 (selected with CONFIG_OABI_COMPAT).
538 To use this you need GCC version 4.0.0 or later.
541 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
542 depends on AEABI && EXPERIMENTAL
545 This option preserves the old syscall interface along with the
546 new (ARM EABI) one. It also provides a compatibility layer to
547 intercept syscalls that have structure arguments which layout
548 in memory differs between the legacy ABI and the new ARM EABI
549 (only for non "thumb" binaries). This option adds a tiny
550 overhead to all syscalls and produces a slightly larger kernel.
551 If you know you'll be using only pure EABI user space then you
552 can say N here. If this option is not selected and you attempt
553 to execute a legacy ABI binary then the result will be
554 UNPREDICTABLE (in fact it can be predicted that it won't work
555 at all). If in doubt say Y.
557 config ARCH_DISCONTIGMEM_ENABLE
559 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
561 Say Y to support efficient handling of discontiguous physical memory,
562 for architectures which are either NUMA (Non-Uniform Memory Access)
563 or have huge holes in the physical address space for other reasons.
564 See <file:Documentation/vm/numa> for more.
568 default "4" if ARCH_LH7A40X
570 depends on NEED_MULTIPLE_NODES
575 bool "Timer and CPU usage LEDs"
576 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
577 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
578 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
579 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
580 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
581 ARCH_AT91RM9200 || MACH_TRIZEPS4
583 If you say Y here, the LEDs on your machine will be used
584 to provide useful information about your current system status.
586 If you are compiling a kernel for a NetWinder or EBSA-285, you will
587 be able to select which LEDs are active using the options below. If
588 you are compiling a kernel for the EBSA-110 or the LART however, the
589 red LED will simply flash regularly to indicate that the system is
590 still functional. It is safe to say Y here if you have a CATS
591 system, but the driver will do nothing.
594 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
595 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
597 default y if ARCH_EBSA110
599 If you say Y here, one of the system LEDs (the green one on the
600 NetWinder, the amber one on the EBSA285, or the red one on the LART)
601 will flash regularly to indicate that the system is still
602 operational. This is mainly useful to kernel hackers who are
603 debugging unstable kernels.
605 The LART uses the same LED for both Timer LED and CPU usage LED
606 functions. You may choose to use both, but the Timer LED function
607 will overrule the CPU usage LED.
610 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
611 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
614 If you say Y here, the red LED will be used to give a good real
615 time indication of CPU usage, by lighting whenever the idle task
616 is not currently executing.
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.
622 config ALIGNMENT_TRAP
624 default y if !ARCH_EBSA110
626 ARM processors can not fetch/store information which is not
627 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
628 address divisible by 4. On 32-bit ARM processors, these non-aligned
629 fetch/store instructions will be emulated in software if you say
630 here, which has a severe performance impact. This is necessary for
631 correct operation of some network protocols. With an IP-only
632 configuration it is safe to say N, otherwise say Y.
638 # Compressed boot loader in ROM. Yes, we really want to ask about
639 # TEXT and BSS so we preserve their values in the config files.
640 config ZBOOT_ROM_TEXT
641 hex "Compressed ROM boot loader base address"
644 The physical address at which the ROM-able zImage is to be
645 placed in the target. Platforms which normally make use of
646 ROM-able zImage formats normally set this to a suitable
647 value in their defconfig file.
649 If ZBOOT_ROM is not enabled, this has no effect.
652 hex "Compressed ROM boot loader BSS address"
655 The base address of 64KiB of read/write memory in the target
656 for the ROM-able zImage, which must be available while the
657 decompressor is running. Platforms which normally make use of
658 ROM-able zImage formats normally set this to a suitable
659 value in their defconfig file.
661 If ZBOOT_ROM is not enabled, this has no effect.
664 bool "Compressed boot loader in ROM/flash"
665 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
667 Say Y here if you intend to execute your compressed kernel image
668 (zImage) directly from ROM or flash. If unsure, say N.
671 string "Default kernel command string"
674 On some architectures (EBSA110 and CATS), there is currently no way
675 for the boot loader to pass arguments to the kernel. For these
676 architectures, you should supply some command-line options at build
677 time by entering them here. As a minimum, you should specify the
678 memory size and the root device (e.g., mem=64M root=/dev/nfs).
681 bool "Kernel Execute-In-Place from ROM"
682 depends on !ZBOOT_ROM
684 Execute-In-Place allows the kernel to run from non-volatile storage
685 directly addressable by the CPU, such as NOR flash. This saves RAM
686 space since the text section of the kernel is not loaded from flash
687 to RAM. Read-write sections, such as the data section and stack,
688 are still copied to RAM. The XIP kernel is not compressed since
689 it has to run directly from flash, so it will take more space to
690 store it. The flash address used to link the kernel object files,
691 and for storing it, is configuration dependent. Therefore, if you
692 say Y here, you must know the proper physical address where to
693 store the kernel image depending on your own flash memory usage.
695 Also note that the make target becomes "make xipImage" rather than
696 "make zImage" or "make Image". The final kernel binary to put in
697 ROM memory will be arch/arm/boot/xipImage.
702 hex "XIP Kernel Physical Location"
703 depends on XIP_KERNEL
706 This is the physical address in your flash memory the kernel will
707 be linked for and stored to. This address is dependent on your
712 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP)
714 menu "CPU Frequency scaling"
716 source "drivers/cpufreq/Kconfig"
718 config CPU_FREQ_SA1100
720 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
723 config CPU_FREQ_SA1110
725 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
728 config CPU_FREQ_INTEGRATOR
729 tristate "CPUfreq driver for ARM Integrator CPUs"
730 depends on ARCH_INTEGRATOR && CPU_FREQ
733 This enables the CPUfreq driver for ARM Integrator CPUs.
735 For details, take a look at <file:Documentation/cpu-freq>.
743 menu "Floating point emulation"
745 comment "At least one emulation must be selected"
748 bool "NWFPE math emulation"
749 depends on !AEABI || OABI_COMPAT
751 Say Y to include the NWFPE floating point emulator in the kernel.
752 This is necessary to run most binaries. Linux does not currently
753 support floating point hardware so you need to say Y here even if
754 your machine has an FPA or floating point co-processor podule.
756 You may say N here if you are going to load the Acorn FPEmulator
760 bool "Support extended precision"
763 Say Y to include 80-bit support in the kernel floating-point
764 emulator. Otherwise, only 32 and 64-bit support is compiled in.
765 Note that gcc does not generate 80-bit operations by default,
766 so in most cases this option only enlarges the size of the
767 floating point emulator without any good reason.
769 You almost surely want to say N here.
772 bool "FastFPE math emulation (EXPERIMENTAL)"
773 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
775 Say Y here to include the FAST floating point emulator in the kernel.
776 This is an experimental much faster emulator which now also has full
777 precision for the mantissa. It does not support any exceptions.
778 It is very simple, and approximately 3-6 times faster than NWFPE.
780 It should be sufficient for most programs. It may be not suitable
781 for scientific calculations, but you have to check this for yourself.
782 If you do not feel you need a faster FP emulation you should better
786 bool "VFP-format floating point maths"
787 depends on CPU_V6 || CPU_ARM926T
789 Say Y to include VFP support code in the kernel. This is needed
790 if your hardware includes a VFP unit.
792 Please see <file:Documentation/arm/VFP/release-notes.txt> for
793 release notes and additional status information.
795 Say N if your target does not have VFP hardware.
799 menu "Userspace binary formats"
801 source "fs/Kconfig.binfmt"
804 tristate "RISC OS personality"
807 Say Y here to include the kernel code necessary if you want to run
808 Acorn RISC OS/Arthur binaries under Linux. This code is still very
809 experimental; if this sounds frightening, say N and sleep in peace.
810 You can also say M here to compile this support as a module (which
811 will be called arthur).
815 menu "Power management options"
817 source "kernel/power/Kconfig"
820 tristate "Advanced Power Management Emulation"
822 APM is a BIOS specification for saving power using several different
823 techniques. This is mostly useful for battery powered laptops with
824 APM compliant BIOSes. If you say Y here, the system time will be
825 reset after a RESUME operation, the /proc/apm device will provide
826 battery status information, and user-space programs will receive
827 notification of APM "events" (e.g. battery status change).
829 In order to use APM, you will need supporting software. For location
830 and more information, read <file:Documentation/pm.txt> and the
831 Battery Powered Linux mini-HOWTO, available from
832 <http://www.tldp.org/docs.html#howto>.
834 This driver does not spin down disk drives (see the hdparm(8)
835 manpage ("man 8 hdparm") for that), and it doesn't turn off
836 VESA-compliant "green" monitors.
838 Generally, if you don't have a battery in your machine, there isn't
839 much point in using this driver and you should say N. If you get
840 random kernel OOPSes or reboots that don't seem to be related to
841 anything, try disabling/enabling this option (or disabling/enabling
848 menu "Device Drivers"
850 source "drivers/base/Kconfig"
852 source "drivers/connector/Kconfig"
855 source "drivers/mtd/Kconfig"
858 source "drivers/parport/Kconfig"
860 source "drivers/pnp/Kconfig"
862 source "drivers/block/Kconfig"
864 source "drivers/acorn/block/Kconfig"
866 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
867 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
868 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
870 source "drivers/ide/Kconfig"
873 source "drivers/scsi/Kconfig"
875 source "drivers/md/Kconfig"
877 source "drivers/message/fusion/Kconfig"
879 source "drivers/ieee1394/Kconfig"
881 source "drivers/message/i2o/Kconfig"
883 source "drivers/net/Kconfig"
885 source "drivers/isdn/Kconfig"
887 # input before char - char/joystick depends on it. As does USB.
889 source "drivers/input/Kconfig"
891 source "drivers/char/Kconfig"
893 source "drivers/i2c/Kconfig"
895 source "drivers/spi/Kconfig"
897 source "drivers/w1/Kconfig"
899 source "drivers/hwmon/Kconfig"
901 #source "drivers/l3/Kconfig"
903 source "drivers/misc/Kconfig"
905 source "drivers/mfd/Kconfig"
907 source "drivers/leds/Kconfig"
909 source "drivers/media/Kconfig"
911 source "drivers/video/Kconfig"
913 source "sound/Kconfig"
915 source "drivers/usb/Kconfig"
917 source "drivers/mmc/Kconfig"
919 source "drivers/rtc/Kconfig"
925 source "arch/arm/oprofile/Kconfig"
927 source "arch/arm/Kconfig.debug"
929 source "security/Kconfig"
931 source "crypto/Kconfig"