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).
210 Support for Intel's IOP3XX (XScale) family of processors.
216 Support for Intel's IXP4XX (XScale) family of processors.
219 bool "IXP2400/2800-based"
223 Support for Intel's IXP2400/2800 (XScale) family of processors.
230 Support for Intel's IXP23xx (XScale) family of processors.
236 Say Y here if you intend to run this kernel on a LinkUp Systems
237 L7200 Software Development Board which uses an ARM720T processor.
238 Information on this board can be obtained at:
240 <http://www.linkupsys.com/>
242 If you have any questions or comments about the Linux kernel port
243 to this board, send e-mail to <sjhill@cotw.com>.
246 bool "Philips Nexperia PNX4008 Mobile"
248 This enables support for Philips PNX4008 mobile platform.
255 Support for Intel's PXA2XX processor line.
262 select ARCH_MAY_HAVE_PC_FDC
265 On the Acorn Risc-PC, Linux can support the internal IDE disk and
266 CD-ROM interface, serial and parallel port, and the floppy drive.
271 select ARCH_DISCONTIGMEM_ENABLE
274 Support for StrongARM 11x0 based boards.
277 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442"
279 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
280 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
281 the Samsung SMDK2410 development board (and derivatives).
289 Support for the StrongARM based Digital DNARD machine, also known
290 as "Shark" (<http://www.shark-linux.de/shark.html>).
295 Say Y here for systems based on one of the Sharp LH7A40X
296 System on a Chip processors. These CPUs include an ARM922T
297 core with a wide array of integrated devices for
298 hand-held and low-power applications.
303 Support for TI's OMAP platform (OMAP1 and OMAP2).
307 source "arch/arm/mach-clps711x/Kconfig"
309 source "arch/arm/mach-ep93xx/Kconfig"
311 source "arch/arm/mach-footbridge/Kconfig"
313 source "arch/arm/mach-integrator/Kconfig"
315 source "arch/arm/mach-iop3xx/Kconfig"
317 source "arch/arm/mach-ixp4xx/Kconfig"
319 source "arch/arm/mach-ixp2000/Kconfig"
321 source "arch/arm/mach-ixp23xx/Kconfig"
323 source "arch/arm/mach-pxa/Kconfig"
325 source "arch/arm/mach-sa1100/Kconfig"
327 source "arch/arm/plat-omap/Kconfig"
329 source "arch/arm/mach-omap1/Kconfig"
331 source "arch/arm/mach-omap2/Kconfig"
333 source "arch/arm/mach-s3c2410/Kconfig"
335 source "arch/arm/mach-lh7a40x/Kconfig"
337 source "arch/arm/mach-imx/Kconfig"
339 source "arch/arm/mach-h720x/Kconfig"
341 source "arch/arm/mach-versatile/Kconfig"
343 source "arch/arm/mach-aaec2000/Kconfig"
345 source "arch/arm/mach-realview/Kconfig"
347 source "arch/arm/mach-at91rm9200/Kconfig"
349 source "arch/arm/mach-netx/Kconfig"
351 # Definitions to make life easier
355 source arch/arm/mm/Kconfig
357 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
360 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
364 source "arch/arm/Kconfig-nommu"
369 source "arch/arm/common/Kconfig"
371 config FORCE_MAX_ZONEORDER
384 Find out whether you have ISA slots on your motherboard. ISA is the
385 name of a bus system, i.e. the way the CPU talks to the other stuff
386 inside your box. Other bus systems are PCI, EISA, MicroChannel
387 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
388 newer boards don't support it. If you have ISA, say Y, otherwise N.
390 # Select ISA DMA controller support
395 # Select ISA DMA interface
400 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
402 Find out whether you have a PCI motherboard. PCI is the name of a
403 bus system, i.e. the way the CPU talks to the other stuff inside
404 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
405 VESA. If you have PCI, say Y, otherwise N.
407 The PCI-HOWTO, available from
408 <http://www.tldp.org/docs.html#howto>, contains valuable
409 information about which PCI hardware does work under Linux and which
412 # Select the host bridge type
413 config PCI_HOST_VIA82C505
415 depends on PCI && ARCH_SHARK
418 source "drivers/pci/Kconfig"
420 source "drivers/pcmcia/Kconfig"
424 menu "Kernel Features"
427 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
428 depends on EXPERIMENTAL && REALVIEW_MPCORE
430 This enables support for systems with more than one CPU. If you have
431 a system with only one CPU, like most personal computers, say N. If
432 you have a system with more than one CPU, say Y.
434 If you say N here, the kernel will run on single and multiprocessor
435 machines, but will use only one CPU of a multiprocessor machine. If
436 you say Y here, the kernel will run on many, but not all, single
437 processor machines. On a single processor machine, the kernel will
438 run faster if you say N here.
440 See also the <file:Documentation/smp.txt>,
441 <file:Documentation/i386/IO-APIC.txt>,
442 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
443 <http://www.linuxdoc.org/docs.html#howto>.
445 If you don't know what to do here, say N.
448 int "Maximum number of CPUs (2-32)"
454 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
455 depends on SMP && HOTPLUG && EXPERIMENTAL
457 Say Y here to experiment with turning CPUs off and on. CPUs
458 can be controlled through /sys/devices/system/cpu.
461 bool "Use local timer interrupts"
462 depends on SMP && REALVIEW_MPCORE
465 Enable support for local timers on SMP platforms, rather then the
466 legacy IPI broadcast method. Local timers allows the system
467 accounting to be spread across the timer interval, preventing a
468 "thundering herd" at every timer tick.
471 bool "Preemptible Kernel (EXPERIMENTAL)"
472 depends on EXPERIMENTAL
474 This option reduces the latency of the kernel when reacting to
475 real-time or interactive events by allowing a low priority process to
476 be preempted even if it is in kernel mode executing a system call.
477 This allows applications to run more reliably even when the system is
480 Say Y here if you are building a kernel for a desktop, embedded
481 or real-time system. Say N if you are unsure.
484 bool "Dynamic tick timer"
486 Select this option if you want to disable continuous timer ticks
487 and have them programmed to occur as required. This option saves
488 power as the system can remain in idle state for longer.
490 By default dynamic tick is disabled during the boot, and can be
491 manually enabled with:
493 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
495 Alternatively, if you want dynamic tick automatically enabled
496 during boot, pass "dyntick=enable" via the kernel command string.
498 Please note that dynamic tick may affect the accuracy of
499 timekeeping on some platforms depending on the implementation.
500 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
501 to have accurate timekeeping with dynamic tick.
505 default 128 if ARCH_L7200
506 default 200 if ARCH_EBSA110 || ARCH_S3C2410
507 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
511 bool "Use the ARM EABI to compile the kernel"
513 This option allows for the kernel to be compiled using the latest
514 ARM ABI (aka EABI). This is only useful if you are using a user
515 space environment that is also compiled with EABI.
517 Since there are major incompatibilities between the legacy ABI and
518 EABI, especially with regard to structure member alignment, this
519 option also changes the kernel syscall calling convention to
520 disambiguate both ABIs and allow for backward compatibility support
521 (selected with CONFIG_OABI_COMPAT).
523 To use this you need GCC version 4.0.0 or later.
526 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
527 depends on AEABI && EXPERIMENTAL
530 This option preserves the old syscall interface along with the
531 new (ARM EABI) one. It also provides a compatibility layer to
532 intercept syscalls that have structure arguments which layout
533 in memory differs between the legacy ABI and the new ARM EABI
534 (only for non "thumb" binaries). This option adds a tiny
535 overhead to all syscalls and produces a slightly larger kernel.
536 If you know you'll be using only pure EABI user space then you
537 can say N here. If this option is not selected and you attempt
538 to execute a legacy ABI binary then the result will be
539 UNPREDICTABLE (in fact it can be predicted that it won't work
540 at all). If in doubt say Y.
542 config ARCH_DISCONTIGMEM_ENABLE
544 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
546 Say Y to support efficient handling of discontiguous physical memory,
547 for architectures which are either NUMA (Non-Uniform Memory Access)
548 or have huge holes in the physical address space for other reasons.
549 See <file:Documentation/vm/numa> for more.
553 default "4" if ARCH_LH7A40X
555 depends on NEED_MULTIPLE_NODES
560 bool "Timer and CPU usage LEDs"
561 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
562 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
563 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
564 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
565 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
566 ARCH_AT91RM9200 || MACH_TRIZEPS4
568 If you say Y here, the LEDs on your machine will be used
569 to provide useful information about your current system status.
571 If you are compiling a kernel for a NetWinder or EBSA-285, you will
572 be able to select which LEDs are active using the options below. If
573 you are compiling a kernel for the EBSA-110 or the LART however, the
574 red LED will simply flash regularly to indicate that the system is
575 still functional. It is safe to say Y here if you have a CATS
576 system, but the driver will do nothing.
579 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
580 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
582 default y if ARCH_EBSA110
584 If you say Y here, one of the system LEDs (the green one on the
585 NetWinder, the amber one on the EBSA285, or the red one on the LART)
586 will flash regularly to indicate that the system is still
587 operational. This is mainly useful to kernel hackers who are
588 debugging unstable kernels.
590 The LART uses the same LED for both Timer LED and CPU usage LED
591 functions. You may choose to use both, but the Timer LED function
592 will overrule the CPU usage LED.
595 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
596 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
599 If you say Y here, the red LED will be used to give a good real
600 time indication of CPU usage, by lighting whenever the idle task
601 is not currently executing.
603 The LART uses the same LED for both Timer LED and CPU usage LED
604 functions. You may choose to use both, but the Timer LED function
605 will overrule the CPU usage LED.
607 config ALIGNMENT_TRAP
609 default y if !ARCH_EBSA110
611 ARM processors can not fetch/store information which is not
612 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
613 address divisible by 4. On 32-bit ARM processors, these non-aligned
614 fetch/store instructions will be emulated in software if you say
615 here, which has a severe performance impact. This is necessary for
616 correct operation of some network protocols. With an IP-only
617 configuration it is safe to say N, otherwise say Y.
623 # Compressed boot loader in ROM. Yes, we really want to ask about
624 # TEXT and BSS so we preserve their values in the config files.
625 config ZBOOT_ROM_TEXT
626 hex "Compressed ROM boot loader base address"
629 The physical address at which the ROM-able zImage is to be
630 placed in the target. Platforms which normally make use of
631 ROM-able zImage formats normally set this to a suitable
632 value in their defconfig file.
634 If ZBOOT_ROM is not enabled, this has no effect.
637 hex "Compressed ROM boot loader BSS address"
640 The base address of 64KiB of read/write memory in the target
641 for the ROM-able zImage, which must be available while the
642 decompressor is running. Platforms which normally make use of
643 ROM-able zImage formats normally set this to a suitable
644 value in their defconfig file.
646 If ZBOOT_ROM is not enabled, this has no effect.
649 bool "Compressed boot loader in ROM/flash"
650 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
652 Say Y here if you intend to execute your compressed kernel image
653 (zImage) directly from ROM or flash. If unsure, say N.
656 string "Default kernel command string"
659 On some architectures (EBSA110 and CATS), there is currently no way
660 for the boot loader to pass arguments to the kernel. For these
661 architectures, you should supply some command-line options at build
662 time by entering them here. As a minimum, you should specify the
663 memory size and the root device (e.g., mem=64M root=/dev/nfs).
666 bool "Kernel Execute-In-Place from ROM"
667 depends on !ZBOOT_ROM
669 Execute-In-Place allows the kernel to run from non-volatile storage
670 directly addressable by the CPU, such as NOR flash. This saves RAM
671 space since the text section of the kernel is not loaded from flash
672 to RAM. Read-write sections, such as the data section and stack,
673 are still copied to RAM. The XIP kernel is not compressed since
674 it has to run directly from flash, so it will take more space to
675 store it. The flash address used to link the kernel object files,
676 and for storing it, is configuration dependent. Therefore, if you
677 say Y here, you must know the proper physical address where to
678 store the kernel image depending on your own flash memory usage.
680 Also note that the make target becomes "make xipImage" rather than
681 "make zImage" or "make Image". The final kernel binary to put in
682 ROM memory will be arch/arm/boot/xipImage.
687 hex "XIP Kernel Physical Location"
688 depends on XIP_KERNEL
691 This is the physical address in your flash memory the kernel will
692 be linked for and stored to. This address is dependent on your
697 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP)
699 menu "CPU Frequency scaling"
701 source "drivers/cpufreq/Kconfig"
703 config CPU_FREQ_SA1100
705 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
708 config CPU_FREQ_SA1110
710 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
713 config CPU_FREQ_INTEGRATOR
714 tristate "CPUfreq driver for ARM Integrator CPUs"
715 depends on ARCH_INTEGRATOR && CPU_FREQ
718 This enables the CPUfreq driver for ARM Integrator CPUs.
720 For details, take a look at <file:Documentation/cpu-freq>.
728 menu "Floating point emulation"
730 comment "At least one emulation must be selected"
733 bool "NWFPE math emulation"
734 depends on !AEABI || OABI_COMPAT
736 Say Y to include the NWFPE floating point emulator in the kernel.
737 This is necessary to run most binaries. Linux does not currently
738 support floating point hardware so you need to say Y here even if
739 your machine has an FPA or floating point co-processor podule.
741 You may say N here if you are going to load the Acorn FPEmulator
745 bool "Support extended precision"
748 Say Y to include 80-bit support in the kernel floating-point
749 emulator. Otherwise, only 32 and 64-bit support is compiled in.
750 Note that gcc does not generate 80-bit operations by default,
751 so in most cases this option only enlarges the size of the
752 floating point emulator without any good reason.
754 You almost surely want to say N here.
757 bool "FastFPE math emulation (EXPERIMENTAL)"
758 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
760 Say Y here to include the FAST floating point emulator in the kernel.
761 This is an experimental much faster emulator which now also has full
762 precision for the mantissa. It does not support any exceptions.
763 It is very simple, and approximately 3-6 times faster than NWFPE.
765 It should be sufficient for most programs. It may be not suitable
766 for scientific calculations, but you have to check this for yourself.
767 If you do not feel you need a faster FP emulation you should better
771 bool "VFP-format floating point maths"
772 depends on CPU_V6 || CPU_ARM926T
774 Say Y to include VFP support code in the kernel. This is needed
775 if your hardware includes a VFP unit.
777 Please see <file:Documentation/arm/VFP/release-notes.txt> for
778 release notes and additional status information.
780 Say N if your target does not have VFP hardware.
784 menu "Userspace binary formats"
786 source "fs/Kconfig.binfmt"
789 tristate "RISC OS personality"
792 Say Y here to include the kernel code necessary if you want to run
793 Acorn RISC OS/Arthur binaries under Linux. This code is still very
794 experimental; if this sounds frightening, say N and sleep in peace.
795 You can also say M here to compile this support as a module (which
796 will be called arthur).
800 menu "Power management options"
802 source "kernel/power/Kconfig"
805 tristate "Advanced Power Management Emulation"
807 APM is a BIOS specification for saving power using several different
808 techniques. This is mostly useful for battery powered laptops with
809 APM compliant BIOSes. If you say Y here, the system time will be
810 reset after a RESUME operation, the /proc/apm device will provide
811 battery status information, and user-space programs will receive
812 notification of APM "events" (e.g. battery status change).
814 In order to use APM, you will need supporting software. For location
815 and more information, read <file:Documentation/pm.txt> and the
816 Battery Powered Linux mini-HOWTO, available from
817 <http://www.tldp.org/docs.html#howto>.
819 This driver does not spin down disk drives (see the hdparm(8)
820 manpage ("man 8 hdparm") for that), and it doesn't turn off
821 VESA-compliant "green" monitors.
823 Generally, if you don't have a battery in your machine, there isn't
824 much point in using this driver and you should say N. If you get
825 random kernel OOPSes or reboots that don't seem to be related to
826 anything, try disabling/enabling this option (or disabling/enabling
833 menu "Device Drivers"
835 source "drivers/base/Kconfig"
837 source "drivers/connector/Kconfig"
840 source "drivers/mtd/Kconfig"
843 source "drivers/parport/Kconfig"
845 source "drivers/pnp/Kconfig"
847 source "drivers/block/Kconfig"
849 source "drivers/acorn/block/Kconfig"
851 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
852 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
853 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
855 source "drivers/ide/Kconfig"
858 source "drivers/scsi/Kconfig"
860 source "drivers/md/Kconfig"
862 source "drivers/message/fusion/Kconfig"
864 source "drivers/ieee1394/Kconfig"
866 source "drivers/message/i2o/Kconfig"
868 source "drivers/net/Kconfig"
870 source "drivers/isdn/Kconfig"
872 # input before char - char/joystick depends on it. As does USB.
874 source "drivers/input/Kconfig"
876 source "drivers/char/Kconfig"
878 source "drivers/i2c/Kconfig"
880 source "drivers/spi/Kconfig"
882 source "drivers/w1/Kconfig"
884 source "drivers/hwmon/Kconfig"
886 #source "drivers/l3/Kconfig"
888 source "drivers/misc/Kconfig"
890 source "drivers/mfd/Kconfig"
892 source "drivers/leds/Kconfig"
894 source "drivers/media/Kconfig"
896 source "drivers/video/Kconfig"
898 source "sound/Kconfig"
900 source "drivers/usb/Kconfig"
902 source "drivers/mmc/Kconfig"
904 source "drivers/rtc/Kconfig"
910 source "arch/arm/oprofile/Kconfig"
912 source "arch/arm/Kconfig.debug"
914 source "security/Kconfig"
916 source "crypto/Kconfig"