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 RWSEM_GENERIC_SPINLOCK
54 config RWSEM_XCHGADD_ALGORITHM
57 config GENERIC_HWEIGHT
61 config GENERIC_CALIBRATE_DELAY
65 config GENERIC_BUST_SPINLOCK
68 config ARCH_MAY_HAVE_PC_FDC
71 config GENERIC_ISA_DMA
82 default 0xffff0000 if MMU
83 default DRAM_BASE if REMAP_VECTORS_TO_RAM
86 The base address of exception vectors.
93 prompt "ARM system type"
94 default ARCH_VERSATILE
97 bool "Cirrus-CL-PS7500FE"
101 Support for the Cirrus Logic PS7500FE system-on-a-chip.
104 bool "CLPS711x/EP721x-based"
106 Support for Cirrus Logic 711x/721x based boards.
111 select FOOTBRIDGE_ADDIN
113 Support for Intel's EBSA285 companion chip.
119 This is an evaluation board for the StrongARM processor available
120 from Digital. It has limited hardware on-board, including an
121 Ethernet interface, two PCMCIA sockets, two serial ports and a
129 This enables support for the Cirrus EP93xx series of CPUs.
131 config ARCH_FOOTBRIDGE
135 Support for systems based on the DC21285 companion chip
136 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
138 config ARCH_INTEGRATOR
143 Support for ARM's Integrator platform.
149 Support for Intel's IOP3XX (XScale) family of processors.
154 Support for Intel's IXP4XX (XScale) family of processors.
157 bool "IXP2400/2800-based"
160 Support for Intel's IXP2400/2800 (XScale) family of processors.
166 Support for Intel's IXP23xx (XScale) family of processors.
172 Say Y here if you intend to run this kernel on a LinkUp Systems
173 L7200 Software Development Board which uses an ARM720T processor.
174 Information on this board can be obtained at:
176 <http://www.linkupsys.com/>
178 If you have any questions or comments about the Linux kernel port
179 to this board, send e-mail to <sjhill@cotw.com>.
185 Support for Intel's PXA2XX processor line.
192 select ARCH_MAY_HAVE_PC_FDC
195 On the Acorn Risc-PC, Linux can support the internal IDE disk and
196 CD-ROM interface, serial and parallel port, and the floppy drive.
201 select ARCH_DISCONTIGMEM_ENABLE
204 Support for StrongARM 11x0 based boards.
207 bool "Samsung S3C2410"
209 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
210 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
211 the Samsung SMDK2410 development board (and derivatives).
219 Support for the StrongARM based Digital DNARD machine, also known
220 as "Shark" (<http://www.shark-linux.de/shark.html>).
225 Say Y here for systems based on one of the Sharp LH7A40X
226 System on a Chip processors. These CPUs include an ARM922T
227 core with a wide array of integrated devices for
228 hand-held and low-power applications.
233 Support for TI's OMAP platform (OMAP1 and OMAP2).
235 config ARCH_VERSATILE
241 This enables support for ARM Ltd Versatile board.
248 This enables support for ARM Ltd RealView boards.
253 Support for Motorola's i.MX family of processors (MX1, MXL).
256 bool "Hynix-HMS720x-based"
259 This enables support for systems based on the Hynix HMS720x
262 bool "Agilent AAEC-2000 based"
265 This enables support for systems based on the Agilent AAEC-2000
267 config ARCH_AT91RM9200
270 Say Y here if you intend to run this kernel on an Atmel
271 AT91RM9200-based board.
274 bool "Philips Nexperia PNX4008 Mobile"
276 This enables support for Philips PNX4008 mobile platform.
280 source "arch/arm/mach-clps711x/Kconfig"
282 source "arch/arm/mach-ep93xx/Kconfig"
284 source "arch/arm/mach-footbridge/Kconfig"
286 source "arch/arm/mach-integrator/Kconfig"
288 source "arch/arm/mach-iop3xx/Kconfig"
290 source "arch/arm/mach-ixp4xx/Kconfig"
292 source "arch/arm/mach-ixp2000/Kconfig"
294 source "arch/arm/mach-ixp23xx/Kconfig"
296 source "arch/arm/mach-pxa/Kconfig"
298 source "arch/arm/mach-sa1100/Kconfig"
300 source "arch/arm/plat-omap/Kconfig"
302 source "arch/arm/mach-omap1/Kconfig"
304 source "arch/arm/mach-omap2/Kconfig"
306 source "arch/arm/mach-s3c2410/Kconfig"
308 source "arch/arm/mach-lh7a40x/Kconfig"
310 source "arch/arm/mach-imx/Kconfig"
312 source "arch/arm/mach-h720x/Kconfig"
314 source "arch/arm/mach-versatile/Kconfig"
316 source "arch/arm/mach-aaec2000/Kconfig"
318 source "arch/arm/mach-realview/Kconfig"
320 source "arch/arm/mach-at91rm9200/Kconfig"
322 # Definitions to make life easier
326 source arch/arm/mm/Kconfig
328 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
331 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
336 source "arch/arm/common/Kconfig"
338 config FORCE_MAX_ZONEORDER
351 Find out whether you have ISA slots on your motherboard. ISA is the
352 name of a bus system, i.e. the way the CPU talks to the other stuff
353 inside your box. Other bus systems are PCI, EISA, MicroChannel
354 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
355 newer boards don't support it. If you have ISA, say Y, otherwise N.
357 # Select ISA DMA controller support
362 # Select ISA DMA interface
367 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
369 Find out whether you have a PCI motherboard. PCI is the name of a
370 bus system, i.e. the way the CPU talks to the other stuff inside
371 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
372 VESA. If you have PCI, say Y, otherwise N.
374 The PCI-HOWTO, available from
375 <http://www.tldp.org/docs.html#howto>, contains valuable
376 information about which PCI hardware does work under Linux and which
379 # Select the host bridge type
380 config PCI_HOST_VIA82C505
382 depends on PCI && ARCH_SHARK
385 source "drivers/pci/Kconfig"
387 source "drivers/pcmcia/Kconfig"
391 menu "Kernel Features"
394 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
395 depends on EXPERIMENTAL && REALVIEW_MPCORE
397 This enables support for systems with more than one CPU. If you have
398 a system with only one CPU, like most personal computers, say N. If
399 you have a system with more than one CPU, say Y.
401 If you say N here, the kernel will run on single and multiprocessor
402 machines, but will use only one CPU of a multiprocessor machine. If
403 you say Y here, the kernel will run on many, but not all, single
404 processor machines. On a single processor machine, the kernel will
405 run faster if you say N here.
407 See also the <file:Documentation/smp.txt>,
408 <file:Documentation/i386/IO-APIC.txt>,
409 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
410 <http://www.linuxdoc.org/docs.html#howto>.
412 If you don't know what to do here, say N.
415 int "Maximum number of CPUs (2-32)"
421 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
422 depends on SMP && HOTPLUG && EXPERIMENTAL
424 Say Y here to experiment with turning CPUs off and on. CPUs
425 can be controlled through /sys/devices/system/cpu.
428 bool "Use local timer interrupts"
429 depends on SMP && REALVIEW_MPCORE
432 Enable support for local timers on SMP platforms, rather then the
433 legacy IPI broadcast method. Local timers allows the system
434 accounting to be spread across the timer interval, preventing a
435 "thundering herd" at every timer tick.
438 bool "Preemptible Kernel (EXPERIMENTAL)"
439 depends on EXPERIMENTAL
441 This option reduces the latency of the kernel when reacting to
442 real-time or interactive events by allowing a low priority process to
443 be preempted even if it is in kernel mode executing a system call.
444 This allows applications to run more reliably even when the system is
447 Say Y here if you are building a kernel for a desktop, embedded
448 or real-time system. Say N if you are unsure.
451 bool "Dynamic tick timer"
453 Select this option if you want to disable continuous timer ticks
454 and have them programmed to occur as required. This option saves
455 power as the system can remain in idle state for longer.
457 By default dynamic tick is disabled during the boot, and can be
458 manually enabled with:
460 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
462 Alternatively, if you want dynamic tick automatically enabled
463 during boot, pass "dyntick=enable" via the kernel command string.
465 Please note that dynamic tick may affect the accuracy of
466 timekeeping on some platforms depending on the implementation.
467 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
468 to have accurate timekeeping with dynamic tick.
472 default 128 if ARCH_L7200
473 default 200 if ARCH_EBSA110 || ARCH_S3C2410
474 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
478 bool "Use the ARM EABI to compile the kernel"
480 This option allows for the kernel to be compiled using the latest
481 ARM ABI (aka EABI). This is only useful if you are using a user
482 space environment that is also compiled with EABI.
484 Since there are major incompatibilities between the legacy ABI and
485 EABI, especially with regard to structure member alignment, this
486 option also changes the kernel syscall calling convention to
487 disambiguate both ABIs and allow for backward compatibility support
488 (selected with CONFIG_OABI_COMPAT).
490 To use this you need GCC version 4.0.0 or later.
493 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
494 depends on AEABI && EXPERIMENTAL
497 This option preserves the old syscall interface along with the
498 new (ARM EABI) one. It also provides a compatibility layer to
499 intercept syscalls that have structure arguments which layout
500 in memory differs between the legacy ABI and the new ARM EABI
501 (only for non "thumb" binaries). This option adds a tiny
502 overhead to all syscalls and produces a slightly larger kernel.
503 If you know you'll be using only pure EABI user space then you
504 can say N here. If this option is not selected and you attempt
505 to execute a legacy ABI binary then the result will be
506 UNPREDICTABLE (in fact it can be predicted that it won't work
507 at all). If in doubt say Y.
509 config ARCH_DISCONTIGMEM_ENABLE
511 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
513 Say Y to support efficient handling of discontiguous physical memory,
514 for architectures which are either NUMA (Non-Uniform Memory Access)
515 or have huge holes in the physical address space for other reasons.
516 See <file:Documentation/vm/numa> for more.
520 default "4" if ARCH_LH7A40X
522 depends on NEED_MULTIPLE_NODES
527 bool "Timer and CPU usage LEDs"
528 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
529 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
530 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
531 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
532 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
535 If you say Y here, the LEDs on your machine will be used
536 to provide useful information about your current system status.
538 If you are compiling a kernel for a NetWinder or EBSA-285, you will
539 be able to select which LEDs are active using the options below. If
540 you are compiling a kernel for the EBSA-110 or the LART however, the
541 red LED will simply flash regularly to indicate that the system is
542 still functional. It is safe to say Y here if you have a CATS
543 system, but the driver will do nothing.
546 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
547 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
549 default y if ARCH_EBSA110
551 If you say Y here, one of the system LEDs (the green one on the
552 NetWinder, the amber one on the EBSA285, or the red one on the LART)
553 will flash regularly to indicate that the system is still
554 operational. This is mainly useful to kernel hackers who are
555 debugging unstable kernels.
557 The LART uses the same LED for both Timer LED and CPU usage LED
558 functions. You may choose to use both, but the Timer LED function
559 will overrule the CPU usage LED.
562 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
563 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
566 If you say Y here, the red LED will be used to give a good real
567 time indication of CPU usage, by lighting whenever the idle task
568 is not currently executing.
570 The LART uses the same LED for both Timer LED and CPU usage LED
571 functions. You may choose to use both, but the Timer LED function
572 will overrule the CPU usage LED.
574 config ALIGNMENT_TRAP
576 default y if !ARCH_EBSA110
578 ARM processors can not fetch/store information which is not
579 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
580 address divisible by 4. On 32-bit ARM processors, these non-aligned
581 fetch/store instructions will be emulated in software if you say
582 here, which has a severe performance impact. This is necessary for
583 correct operation of some network protocols. With an IP-only
584 configuration it is safe to say N, otherwise say Y.
590 # Compressed boot loader in ROM. Yes, we really want to ask about
591 # TEXT and BSS so we preserve their values in the config files.
592 config ZBOOT_ROM_TEXT
593 hex "Compressed ROM boot loader base address"
596 The physical address at which the ROM-able zImage is to be
597 placed in the target. Platforms which normally make use of
598 ROM-able zImage formats normally set this to a suitable
599 value in their defconfig file.
601 If ZBOOT_ROM is not enabled, this has no effect.
604 hex "Compressed ROM boot loader BSS address"
607 The base address of 64KiB of read/write memory in the target
608 for the ROM-able zImage, which must be available while the
609 decompressor is running. Platforms which normally make use of
610 ROM-able zImage formats normally set this to a suitable
611 value in their defconfig file.
613 If ZBOOT_ROM is not enabled, this has no effect.
616 bool "Compressed boot loader in ROM/flash"
617 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
619 Say Y here if you intend to execute your compressed kernel image
620 (zImage) directly from ROM or flash. If unsure, say N.
623 string "Default kernel command string"
626 On some architectures (EBSA110 and CATS), there is currently no way
627 for the boot loader to pass arguments to the kernel. For these
628 architectures, you should supply some command-line options at build
629 time by entering them here. As a minimum, you should specify the
630 memory size and the root device (e.g., mem=64M root=/dev/nfs).
633 bool "Kernel Execute-In-Place from ROM"
634 depends on !ZBOOT_ROM
636 Execute-In-Place allows the kernel to run from non-volatile storage
637 directly addressable by the CPU, such as NOR flash. This saves RAM
638 space since the text section of the kernel is not loaded from flash
639 to RAM. Read-write sections, such as the data section and stack,
640 are still copied to RAM. The XIP kernel is not compressed since
641 it has to run directly from flash, so it will take more space to
642 store it. The flash address used to link the kernel object files,
643 and for storing it, is configuration dependent. Therefore, if you
644 say Y here, you must know the proper physical address where to
645 store the kernel image depending on your own flash memory usage.
647 Also note that the make target becomes "make xipImage" rather than
648 "make zImage" or "make Image". The final kernel binary to put in
649 ROM memory will be arch/arm/boot/xipImage.
654 hex "XIP Kernel Physical Location"
655 depends on XIP_KERNEL
658 This is the physical address in your flash memory the kernel will
659 be linked for and stored to. This address is dependent on your
664 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
666 menu "CPU Frequency scaling"
668 source "drivers/cpufreq/Kconfig"
670 config CPU_FREQ_SA1100
672 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
675 config CPU_FREQ_SA1110
677 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
680 config CPU_FREQ_INTEGRATOR
681 tristate "CPUfreq driver for ARM Integrator CPUs"
682 depends on ARCH_INTEGRATOR && CPU_FREQ
685 This enables the CPUfreq driver for ARM Integrator CPUs.
687 For details, take a look at <file:Documentation/cpu-freq>.
695 menu "Floating point emulation"
697 comment "At least one emulation must be selected"
700 bool "NWFPE math emulation"
701 depends on !AEABI || OABI_COMPAT
703 Say Y to include the NWFPE floating point emulator in the kernel.
704 This is necessary to run most binaries. Linux does not currently
705 support floating point hardware so you need to say Y here even if
706 your machine has an FPA or floating point co-processor podule.
708 You may say N here if you are going to load the Acorn FPEmulator
712 bool "Support extended precision"
715 Say Y to include 80-bit support in the kernel floating-point
716 emulator. Otherwise, only 32 and 64-bit support is compiled in.
717 Note that gcc does not generate 80-bit operations by default,
718 so in most cases this option only enlarges the size of the
719 floating point emulator without any good reason.
721 You almost surely want to say N here.
724 bool "FastFPE math emulation (EXPERIMENTAL)"
725 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
727 Say Y here to include the FAST floating point emulator in the kernel.
728 This is an experimental much faster emulator which now also has full
729 precision for the mantissa. It does not support any exceptions.
730 It is very simple, and approximately 3-6 times faster than NWFPE.
732 It should be sufficient for most programs. It may be not suitable
733 for scientific calculations, but you have to check this for yourself.
734 If you do not feel you need a faster FP emulation you should better
738 bool "VFP-format floating point maths"
739 depends on CPU_V6 || CPU_ARM926T
741 Say Y to include VFP support code in the kernel. This is needed
742 if your hardware includes a VFP unit.
744 Please see <file:Documentation/arm/VFP/release-notes.txt> for
745 release notes and additional status information.
747 Say N if your target does not have VFP hardware.
751 menu "Userspace binary formats"
753 source "fs/Kconfig.binfmt"
756 tristate "RISC OS personality"
759 Say Y here to include the kernel code necessary if you want to run
760 Acorn RISC OS/Arthur binaries under Linux. This code is still very
761 experimental; if this sounds frightening, say N and sleep in peace.
762 You can also say M here to compile this support as a module (which
763 will be called arthur).
767 menu "Power management options"
769 source "kernel/power/Kconfig"
772 tristate "Advanced Power Management Emulation"
774 APM is a BIOS specification for saving power using several different
775 techniques. This is mostly useful for battery powered laptops with
776 APM compliant BIOSes. If you say Y here, the system time will be
777 reset after a RESUME operation, the /proc/apm device will provide
778 battery status information, and user-space programs will receive
779 notification of APM "events" (e.g. battery status change).
781 In order to use APM, you will need supporting software. For location
782 and more information, read <file:Documentation/pm.txt> and the
783 Battery Powered Linux mini-HOWTO, available from
784 <http://www.tldp.org/docs.html#howto>.
786 This driver does not spin down disk drives (see the hdparm(8)
787 manpage ("man 8 hdparm") for that), and it doesn't turn off
788 VESA-compliant "green" monitors.
790 Generally, if you don't have a battery in your machine, there isn't
791 much point in using this driver and you should say N. If you get
792 random kernel OOPSes or reboots that don't seem to be related to
793 anything, try disabling/enabling this option (or disabling/enabling
800 menu "Device Drivers"
802 source "drivers/base/Kconfig"
804 source "drivers/connector/Kconfig"
807 source "drivers/mtd/Kconfig"
810 source "drivers/parport/Kconfig"
812 source "drivers/pnp/Kconfig"
814 source "drivers/block/Kconfig"
816 source "drivers/acorn/block/Kconfig"
818 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
819 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
820 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
822 source "drivers/ide/Kconfig"
825 source "drivers/scsi/Kconfig"
827 source "drivers/md/Kconfig"
829 source "drivers/message/fusion/Kconfig"
831 source "drivers/ieee1394/Kconfig"
833 source "drivers/message/i2o/Kconfig"
835 source "drivers/net/Kconfig"
837 source "drivers/isdn/Kconfig"
839 # input before char - char/joystick depends on it. As does USB.
841 source "drivers/input/Kconfig"
843 source "drivers/char/Kconfig"
845 source "drivers/i2c/Kconfig"
847 source "drivers/spi/Kconfig"
849 source "drivers/w1/Kconfig"
851 source "drivers/hwmon/Kconfig"
853 #source "drivers/l3/Kconfig"
855 source "drivers/misc/Kconfig"
857 source "drivers/mfd/Kconfig"
859 source "drivers/leds/Kconfig"
861 source "drivers/media/Kconfig"
863 source "drivers/video/Kconfig"
865 source "sound/Kconfig"
867 source "drivers/usb/Kconfig"
869 source "drivers/mmc/Kconfig"
871 source "drivers/rtc/Kconfig"
877 source "arch/arm/oprofile/Kconfig"
879 source "arch/arm/Kconfig.debug"
881 source "security/Kconfig"
883 source "crypto/Kconfig"