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 "Agilent AAEC-2000 based"
100 This enables support for systems based on the Agilent AAEC-2000
102 config ARCH_INTEGRATOR
103 bool "ARM Ltd. Integrator family"
107 Support for ARM's Integrator platform.
110 bool "ARM Ltd. RealView family"
114 This enables support for ARM Ltd RealView boards.
116 config ARCH_VERSATILE
117 bool "ARM Ltd. Versatile family"
122 This enables support for ARM Ltd Versatile board.
127 This enables support for systems based on the Atmel AT91RM9200
128 and AT91SAM9xxx processors.
131 bool "Cirrus CL-PS7500FE"
135 Support for the Cirrus Logic PS7500FE system-on-a-chip.
138 bool "Cirrus Logic CLPS711x/EP721x-based"
140 Support for Cirrus Logic 711x/721x based boards.
145 select FOOTBRIDGE_ADDIN
147 Support for Intel's EBSA285 companion chip.
153 This is an evaluation board for the StrongARM processor available
154 from Digital. It has limited hardware on-board, including an
155 Ethernet interface, two PCMCIA sockets, two serial ports and a
163 This enables support for the Cirrus EP93xx series of CPUs.
165 config ARCH_FOOTBRIDGE
169 Support for systems based on the DC21285 companion chip
170 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
173 bool "Hilscher NetX based"
176 This enables support for systems based on the Hilscher NetX Soc
179 bool "Hynix HMS720x-based"
182 This enables support for systems based on the Hynix HMS720x
187 Support for Motorola's i.MX family of processors (MX1, MXL).
194 Support for Intel's IOP3XX (XScale) family of processors.
200 Support for Intel's IXP4XX (XScale) family of processors.
203 bool "IXP2400/2800-based"
207 Support for Intel's IXP2400/2800 (XScale) family of processors.
214 Support for Intel's IXP23xx (XScale) family of processors.
220 Say Y here if you intend to run this kernel on a LinkUp Systems
221 L7200 Software Development Board which uses an ARM720T processor.
222 Information on this board can be obtained at:
224 <http://www.linkupsys.com/>
226 If you have any questions or comments about the Linux kernel port
227 to this board, send e-mail to <sjhill@cotw.com>.
230 bool "Philips Nexperia PNX4008 Mobile"
232 This enables support for Philips PNX4008 mobile platform.
239 Support for Intel's PXA2XX processor line.
246 select ARCH_MAY_HAVE_PC_FDC
249 On the Acorn Risc-PC, Linux can support the internal IDE disk and
250 CD-ROM interface, serial and parallel port, and the floppy drive.
255 select ARCH_DISCONTIGMEM_ENABLE
258 Support for StrongARM 11x0 based boards.
261 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442"
263 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
264 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
265 the Samsung SMDK2410 development board (and derivatives).
273 Support for the StrongARM based Digital DNARD machine, also known
274 as "Shark" (<http://www.shark-linux.de/shark.html>).
279 Say Y here for systems based on one of the Sharp LH7A40X
280 System on a Chip processors. These CPUs include an ARM922T
281 core with a wide array of integrated devices for
282 hand-held and low-power applications.
287 Support for TI's OMAP platform (OMAP1 and OMAP2).
291 source "arch/arm/mach-clps711x/Kconfig"
293 source "arch/arm/mach-ep93xx/Kconfig"
295 source "arch/arm/mach-footbridge/Kconfig"
297 source "arch/arm/mach-integrator/Kconfig"
299 source "arch/arm/mach-iop3xx/Kconfig"
301 source "arch/arm/mach-ixp4xx/Kconfig"
303 source "arch/arm/mach-ixp2000/Kconfig"
305 source "arch/arm/mach-ixp23xx/Kconfig"
307 source "arch/arm/mach-pxa/Kconfig"
309 source "arch/arm/mach-sa1100/Kconfig"
311 source "arch/arm/plat-omap/Kconfig"
313 source "arch/arm/mach-omap1/Kconfig"
315 source "arch/arm/mach-omap2/Kconfig"
317 source "arch/arm/mach-s3c2410/Kconfig"
319 source "arch/arm/mach-lh7a40x/Kconfig"
321 source "arch/arm/mach-imx/Kconfig"
323 source "arch/arm/mach-h720x/Kconfig"
325 source "arch/arm/mach-versatile/Kconfig"
327 source "arch/arm/mach-aaec2000/Kconfig"
329 source "arch/arm/mach-realview/Kconfig"
331 source "arch/arm/mach-at91rm9200/Kconfig"
333 source "arch/arm/mach-netx/Kconfig"
335 # Definitions to make life easier
339 source arch/arm/mm/Kconfig
341 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
344 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
348 source "arch/arm/Kconfig-nommu"
353 source "arch/arm/common/Kconfig"
355 config FORCE_MAX_ZONEORDER
368 Find out whether you have ISA slots on your motherboard. ISA is the
369 name of a bus system, i.e. the way the CPU talks to the other stuff
370 inside your box. Other bus systems are PCI, EISA, MicroChannel
371 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
372 newer boards don't support it. If you have ISA, say Y, otherwise N.
374 # Select ISA DMA controller support
379 # Select ISA DMA interface
384 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
386 Find out whether you have a PCI motherboard. PCI is the name of a
387 bus system, i.e. the way the CPU talks to the other stuff inside
388 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
389 VESA. If you have PCI, say Y, otherwise N.
391 The PCI-HOWTO, available from
392 <http://www.tldp.org/docs.html#howto>, contains valuable
393 information about which PCI hardware does work under Linux and which
396 # Select the host bridge type
397 config PCI_HOST_VIA82C505
399 depends on PCI && ARCH_SHARK
402 source "drivers/pci/Kconfig"
404 source "drivers/pcmcia/Kconfig"
408 menu "Kernel Features"
411 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
412 depends on EXPERIMENTAL && REALVIEW_MPCORE
414 This enables support for systems with more than one CPU. If you have
415 a system with only one CPU, like most personal computers, say N. If
416 you have a system with more than one CPU, say Y.
418 If you say N here, the kernel will run on single and multiprocessor
419 machines, but will use only one CPU of a multiprocessor machine. If
420 you say Y here, the kernel will run on many, but not all, single
421 processor machines. On a single processor machine, the kernel will
422 run faster if you say N here.
424 See also the <file:Documentation/smp.txt>,
425 <file:Documentation/i386/IO-APIC.txt>,
426 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
427 <http://www.linuxdoc.org/docs.html#howto>.
429 If you don't know what to do here, say N.
432 int "Maximum number of CPUs (2-32)"
438 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
439 depends on SMP && HOTPLUG && EXPERIMENTAL
441 Say Y here to experiment with turning CPUs off and on. CPUs
442 can be controlled through /sys/devices/system/cpu.
445 bool "Use local timer interrupts"
446 depends on SMP && REALVIEW_MPCORE
449 Enable support for local timers on SMP platforms, rather then the
450 legacy IPI broadcast method. Local timers allows the system
451 accounting to be spread across the timer interval, preventing a
452 "thundering herd" at every timer tick.
455 bool "Preemptible Kernel (EXPERIMENTAL)"
456 depends on EXPERIMENTAL
458 This option reduces the latency of the kernel when reacting to
459 real-time or interactive events by allowing a low priority process to
460 be preempted even if it is in kernel mode executing a system call.
461 This allows applications to run more reliably even when the system is
464 Say Y here if you are building a kernel for a desktop, embedded
465 or real-time system. Say N if you are unsure.
468 bool "Dynamic tick timer"
470 Select this option if you want to disable continuous timer ticks
471 and have them programmed to occur as required. This option saves
472 power as the system can remain in idle state for longer.
474 By default dynamic tick is disabled during the boot, and can be
475 manually enabled with:
477 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
479 Alternatively, if you want dynamic tick automatically enabled
480 during boot, pass "dyntick=enable" via the kernel command string.
482 Please note that dynamic tick may affect the accuracy of
483 timekeeping on some platforms depending on the implementation.
484 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
485 to have accurate timekeeping with dynamic tick.
489 default 128 if ARCH_L7200
490 default 200 if ARCH_EBSA110 || ARCH_S3C2410
491 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
495 bool "Use the ARM EABI to compile the kernel"
497 This option allows for the kernel to be compiled using the latest
498 ARM ABI (aka EABI). This is only useful if you are using a user
499 space environment that is also compiled with EABI.
501 Since there are major incompatibilities between the legacy ABI and
502 EABI, especially with regard to structure member alignment, this
503 option also changes the kernel syscall calling convention to
504 disambiguate both ABIs and allow for backward compatibility support
505 (selected with CONFIG_OABI_COMPAT).
507 To use this you need GCC version 4.0.0 or later.
510 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
511 depends on AEABI && EXPERIMENTAL
514 This option preserves the old syscall interface along with the
515 new (ARM EABI) one. It also provides a compatibility layer to
516 intercept syscalls that have structure arguments which layout
517 in memory differs between the legacy ABI and the new ARM EABI
518 (only for non "thumb" binaries). This option adds a tiny
519 overhead to all syscalls and produces a slightly larger kernel.
520 If you know you'll be using only pure EABI user space then you
521 can say N here. If this option is not selected and you attempt
522 to execute a legacy ABI binary then the result will be
523 UNPREDICTABLE (in fact it can be predicted that it won't work
524 at all). If in doubt say Y.
526 config ARCH_DISCONTIGMEM_ENABLE
528 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
530 Say Y to support efficient handling of discontiguous physical memory,
531 for architectures which are either NUMA (Non-Uniform Memory Access)
532 or have huge holes in the physical address space for other reasons.
533 See <file:Documentation/vm/numa> for more.
537 default "4" if ARCH_LH7A40X
539 depends on NEED_MULTIPLE_NODES
544 bool "Timer and CPU usage LEDs"
545 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
546 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
547 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
548 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
549 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
550 ARCH_AT91RM9200 || MACH_TRIZEPS4
552 If you say Y here, the LEDs on your machine will be used
553 to provide useful information about your current system status.
555 If you are compiling a kernel for a NetWinder or EBSA-285, you will
556 be able to select which LEDs are active using the options below. If
557 you are compiling a kernel for the EBSA-110 or the LART however, the
558 red LED will simply flash regularly to indicate that the system is
559 still functional. It is safe to say Y here if you have a CATS
560 system, but the driver will do nothing.
563 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
564 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
566 default y if ARCH_EBSA110
568 If you say Y here, one of the system LEDs (the green one on the
569 NetWinder, the amber one on the EBSA285, or the red one on the LART)
570 will flash regularly to indicate that the system is still
571 operational. This is mainly useful to kernel hackers who are
572 debugging unstable kernels.
574 The LART uses the same LED for both Timer LED and CPU usage LED
575 functions. You may choose to use both, but the Timer LED function
576 will overrule the CPU usage LED.
579 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
580 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
583 If you say Y here, the red LED will be used to give a good real
584 time indication of CPU usage, by lighting whenever the idle task
585 is not currently executing.
587 The LART uses the same LED for both Timer LED and CPU usage LED
588 functions. You may choose to use both, but the Timer LED function
589 will overrule the CPU usage LED.
591 config ALIGNMENT_TRAP
593 default y if !ARCH_EBSA110
595 ARM processors can not fetch/store information which is not
596 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
597 address divisible by 4. On 32-bit ARM processors, these non-aligned
598 fetch/store instructions will be emulated in software if you say
599 here, which has a severe performance impact. This is necessary for
600 correct operation of some network protocols. With an IP-only
601 configuration it is safe to say N, otherwise say Y.
607 # Compressed boot loader in ROM. Yes, we really want to ask about
608 # TEXT and BSS so we preserve their values in the config files.
609 config ZBOOT_ROM_TEXT
610 hex "Compressed ROM boot loader base address"
613 The physical address at which the ROM-able zImage is to be
614 placed in the target. Platforms which normally make use of
615 ROM-able zImage formats normally set this to a suitable
616 value in their defconfig file.
618 If ZBOOT_ROM is not enabled, this has no effect.
621 hex "Compressed ROM boot loader BSS address"
624 The base address of 64KiB of read/write memory in the target
625 for the ROM-able zImage, which must be available while the
626 decompressor is running. 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 bool "Compressed boot loader in ROM/flash"
634 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
636 Say Y here if you intend to execute your compressed kernel image
637 (zImage) directly from ROM or flash. If unsure, say N.
640 string "Default kernel command string"
643 On some architectures (EBSA110 and CATS), there is currently no way
644 for the boot loader to pass arguments to the kernel. For these
645 architectures, you should supply some command-line options at build
646 time by entering them here. As a minimum, you should specify the
647 memory size and the root device (e.g., mem=64M root=/dev/nfs).
650 bool "Kernel Execute-In-Place from ROM"
651 depends on !ZBOOT_ROM
653 Execute-In-Place allows the kernel to run from non-volatile storage
654 directly addressable by the CPU, such as NOR flash. This saves RAM
655 space since the text section of the kernel is not loaded from flash
656 to RAM. Read-write sections, such as the data section and stack,
657 are still copied to RAM. The XIP kernel is not compressed since
658 it has to run directly from flash, so it will take more space to
659 store it. The flash address used to link the kernel object files,
660 and for storing it, is configuration dependent. Therefore, if you
661 say Y here, you must know the proper physical address where to
662 store the kernel image depending on your own flash memory usage.
664 Also note that the make target becomes "make xipImage" rather than
665 "make zImage" or "make Image". The final kernel binary to put in
666 ROM memory will be arch/arm/boot/xipImage.
671 hex "XIP Kernel Physical Location"
672 depends on XIP_KERNEL
675 This is the physical address in your flash memory the kernel will
676 be linked for and stored to. This address is dependent on your
681 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP)
683 menu "CPU Frequency scaling"
685 source "drivers/cpufreq/Kconfig"
687 config CPU_FREQ_SA1100
689 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
692 config CPU_FREQ_SA1110
694 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
697 config CPU_FREQ_INTEGRATOR
698 tristate "CPUfreq driver for ARM Integrator CPUs"
699 depends on ARCH_INTEGRATOR && CPU_FREQ
702 This enables the CPUfreq driver for ARM Integrator CPUs.
704 For details, take a look at <file:Documentation/cpu-freq>.
712 menu "Floating point emulation"
714 comment "At least one emulation must be selected"
717 bool "NWFPE math emulation"
718 depends on !AEABI || OABI_COMPAT
720 Say Y to include the NWFPE floating point emulator in the kernel.
721 This is necessary to run most binaries. Linux does not currently
722 support floating point hardware so you need to say Y here even if
723 your machine has an FPA or floating point co-processor podule.
725 You may say N here if you are going to load the Acorn FPEmulator
729 bool "Support extended precision"
732 Say Y to include 80-bit support in the kernel floating-point
733 emulator. Otherwise, only 32 and 64-bit support is compiled in.
734 Note that gcc does not generate 80-bit operations by default,
735 so in most cases this option only enlarges the size of the
736 floating point emulator without any good reason.
738 You almost surely want to say N here.
741 bool "FastFPE math emulation (EXPERIMENTAL)"
742 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
744 Say Y here to include the FAST floating point emulator in the kernel.
745 This is an experimental much faster emulator which now also has full
746 precision for the mantissa. It does not support any exceptions.
747 It is very simple, and approximately 3-6 times faster than NWFPE.
749 It should be sufficient for most programs. It may be not suitable
750 for scientific calculations, but you have to check this for yourself.
751 If you do not feel you need a faster FP emulation you should better
755 bool "VFP-format floating point maths"
756 depends on CPU_V6 || CPU_ARM926T
758 Say Y to include VFP support code in the kernel. This is needed
759 if your hardware includes a VFP unit.
761 Please see <file:Documentation/arm/VFP/release-notes.txt> for
762 release notes and additional status information.
764 Say N if your target does not have VFP hardware.
768 menu "Userspace binary formats"
770 source "fs/Kconfig.binfmt"
773 tristate "RISC OS personality"
776 Say Y here to include the kernel code necessary if you want to run
777 Acorn RISC OS/Arthur binaries under Linux. This code is still very
778 experimental; if this sounds frightening, say N and sleep in peace.
779 You can also say M here to compile this support as a module (which
780 will be called arthur).
784 menu "Power management options"
786 source "kernel/power/Kconfig"
789 tristate "Advanced Power Management Emulation"
791 APM is a BIOS specification for saving power using several different
792 techniques. This is mostly useful for battery powered laptops with
793 APM compliant BIOSes. If you say Y here, the system time will be
794 reset after a RESUME operation, the /proc/apm device will provide
795 battery status information, and user-space programs will receive
796 notification of APM "events" (e.g. battery status change).
798 In order to use APM, you will need supporting software. For location
799 and more information, read <file:Documentation/pm.txt> and the
800 Battery Powered Linux mini-HOWTO, available from
801 <http://www.tldp.org/docs.html#howto>.
803 This driver does not spin down disk drives (see the hdparm(8)
804 manpage ("man 8 hdparm") for that), and it doesn't turn off
805 VESA-compliant "green" monitors.
807 Generally, if you don't have a battery in your machine, there isn't
808 much point in using this driver and you should say N. If you get
809 random kernel OOPSes or reboots that don't seem to be related to
810 anything, try disabling/enabling this option (or disabling/enabling
817 menu "Device Drivers"
819 source "drivers/base/Kconfig"
821 source "drivers/connector/Kconfig"
824 source "drivers/mtd/Kconfig"
827 source "drivers/parport/Kconfig"
829 source "drivers/pnp/Kconfig"
831 source "drivers/block/Kconfig"
833 source "drivers/acorn/block/Kconfig"
835 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
836 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
837 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
839 source "drivers/ide/Kconfig"
842 source "drivers/scsi/Kconfig"
844 source "drivers/md/Kconfig"
846 source "drivers/message/fusion/Kconfig"
848 source "drivers/ieee1394/Kconfig"
850 source "drivers/message/i2o/Kconfig"
852 source "drivers/net/Kconfig"
854 source "drivers/isdn/Kconfig"
856 # input before char - char/joystick depends on it. As does USB.
858 source "drivers/input/Kconfig"
860 source "drivers/char/Kconfig"
862 source "drivers/i2c/Kconfig"
864 source "drivers/spi/Kconfig"
866 source "drivers/w1/Kconfig"
868 source "drivers/hwmon/Kconfig"
870 #source "drivers/l3/Kconfig"
872 source "drivers/misc/Kconfig"
874 source "drivers/mfd/Kconfig"
876 source "drivers/leds/Kconfig"
878 source "drivers/media/Kconfig"
880 source "drivers/video/Kconfig"
882 source "sound/Kconfig"
884 source "drivers/usb/Kconfig"
886 source "drivers/mmc/Kconfig"
888 source "drivers/rtc/Kconfig"
894 source "arch/arm/oprofile/Kconfig"
896 source "arch/arm/Kconfig.debug"
898 source "security/Kconfig"
900 source "crypto/Kconfig"