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
85 prompt "ARM system type"
86 default ARCH_VERSATILE
89 bool "Cirrus-CL-PS7500FE"
93 Support for the Cirrus Logic PS7500FE system-on-a-chip.
96 bool "CLPS711x/EP721x-based"
98 Support for Cirrus Logic 711x/721x based boards.
103 select FOOTBRIDGE_ADDIN
105 Support for Intel's EBSA285 companion chip.
111 This is an evaluation board for the StrongARM processor available
112 from Digital. It has limited hardware on-board, including an
113 Ethernet interface, two PCMCIA sockets, two serial ports and a
121 This enables support for the Cirrus EP93xx series of CPUs.
123 config ARCH_FOOTBRIDGE
127 Support for systems based on the DC21285 companion chip
128 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
130 config ARCH_INTEGRATOR
135 Support for ARM's Integrator platform.
141 Support for Intel's IOP3XX (XScale) family of processors.
148 Support for Intel's IXP4XX (XScale) family of processors.
151 bool "IXP2400/2800-based"
154 Support for Intel's IXP2400/2800 (XScale) family of processors.
160 Say Y here if you intend to run this kernel on a LinkUp Systems
161 L7200 Software Development Board which uses an ARM720T processor.
162 Information on this board can be obtained at:
164 <http://www.linkupsys.com/>
166 If you have any questions or comments about the Linux kernel port
167 to this board, send e-mail to <sjhill@cotw.com>.
173 Support for Intel's PXA2XX processor line.
180 select ARCH_MAY_HAVE_PC_FDC
183 On the Acorn Risc-PC, Linux can support the internal IDE disk and
184 CD-ROM interface, serial and parallel port, and the floppy drive.
189 select ARCH_DISCONTIGMEM_ENABLE
192 Support for StrongARM 11x0 based boards.
195 bool "Samsung S3C2410"
197 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
198 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
199 the Samsung SMDK2410 development board (and derivatives).
207 Support for the StrongARM based Digital DNARD machine, also known
208 as "Shark" (<http://www.shark-linux.de/shark.html>).
213 Say Y here for systems based on one of the Sharp LH7A40X
214 System on a Chip processors. These CPUs include an ARM922T
215 core with a wide array of integrated devices for
216 hand-held and low-power applications.
221 Support for TI's OMAP platform (OMAP1 and OMAP2).
223 config ARCH_VERSATILE
229 This enables support for ARM Ltd Versatile board.
236 This enables support for ARM Ltd RealView boards.
241 Support for Motorola's i.MX family of processors (MX1, MXL).
244 bool "Hynix-HMS720x-based"
247 This enables support for systems based on the Hynix HMS720x
250 bool "Agilent AAEC-2000 based"
253 This enables support for systems based on the Agilent AAEC-2000
255 config ARCH_AT91RM9200
258 Say Y here if you intend to run this kernel on an Atmel
259 AT91RM9200-based board.
263 source "arch/arm/mach-clps711x/Kconfig"
265 source "arch/arm/mach-ep93xx/Kconfig"
267 source "arch/arm/mach-footbridge/Kconfig"
269 source "arch/arm/mach-integrator/Kconfig"
271 source "arch/arm/mach-iop3xx/Kconfig"
273 source "arch/arm/mach-ixp4xx/Kconfig"
275 source "arch/arm/mach-ixp2000/Kconfig"
277 source "arch/arm/mach-pxa/Kconfig"
279 source "arch/arm/mach-sa1100/Kconfig"
281 source "arch/arm/plat-omap/Kconfig"
283 source "arch/arm/mach-omap1/Kconfig"
285 source "arch/arm/mach-omap2/Kconfig"
287 source "arch/arm/mach-s3c2410/Kconfig"
289 source "arch/arm/mach-lh7a40x/Kconfig"
291 source "arch/arm/mach-imx/Kconfig"
293 source "arch/arm/mach-h720x/Kconfig"
295 source "arch/arm/mach-versatile/Kconfig"
297 source "arch/arm/mach-aaec2000/Kconfig"
299 source "arch/arm/mach-realview/Kconfig"
301 source "arch/arm/mach-at91rm9200/Kconfig"
303 # Definitions to make life easier
307 source arch/arm/mm/Kconfig
309 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
312 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
317 source "arch/arm/common/Kconfig"
319 config FORCE_MAX_ZONEORDER
332 Find out whether you have ISA slots on your motherboard. ISA is the
333 name of a bus system, i.e. the way the CPU talks to the other stuff
334 inside your box. Other bus systems are PCI, EISA, MicroChannel
335 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
336 newer boards don't support it. If you have ISA, say Y, otherwise N.
338 # Select ISA DMA controller support
343 # Select ISA DMA interface
348 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
350 Find out whether you have a PCI motherboard. PCI is the name of a
351 bus system, i.e. the way the CPU talks to the other stuff inside
352 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
353 VESA. If you have PCI, say Y, otherwise N.
355 The PCI-HOWTO, available from
356 <http://www.tldp.org/docs.html#howto>, contains valuable
357 information about which PCI hardware does work under Linux and which
360 # Select the host bridge type
361 config PCI_HOST_VIA82C505
363 depends on PCI && ARCH_SHARK
366 source "drivers/pci/Kconfig"
368 source "drivers/pcmcia/Kconfig"
372 menu "Kernel Features"
375 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
376 depends on EXPERIMENTAL && REALVIEW_MPCORE
378 This enables support for systems with more than one CPU. If you have
379 a system with only one CPU, like most personal computers, say N. If
380 you have a system with more than one CPU, say Y.
382 If you say N here, the kernel will run on single and multiprocessor
383 machines, but will use only one CPU of a multiprocessor machine. If
384 you say Y here, the kernel will run on many, but not all, single
385 processor machines. On a single processor machine, the kernel will
386 run faster if you say N here.
388 See also the <file:Documentation/smp.txt>,
389 <file:Documentation/i386/IO-APIC.txt>,
390 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
391 <http://www.linuxdoc.org/docs.html#howto>.
393 If you don't know what to do here, say N.
396 int "Maximum number of CPUs (2-32)"
402 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
403 depends on SMP && HOTPLUG && EXPERIMENTAL
405 Say Y here to experiment with turning CPUs off and on. CPUs
406 can be controlled through /sys/devices/system/cpu.
409 bool "Use local timer interrupts"
410 depends on SMP && REALVIEW_MPCORE
413 Enable support for local timers on SMP platforms, rather then the
414 legacy IPI broadcast method. Local timers allows the system
415 accounting to be spread across the timer interval, preventing a
416 "thundering herd" at every timer tick.
419 bool "Preemptible Kernel (EXPERIMENTAL)"
420 depends on EXPERIMENTAL
422 This option reduces the latency of the kernel when reacting to
423 real-time or interactive events by allowing a low priority process to
424 be preempted even if it is in kernel mode executing a system call.
425 This allows applications to run more reliably even when the system is
428 Say Y here if you are building a kernel for a desktop, embedded
429 or real-time system. Say N if you are unsure.
432 bool "Dynamic tick timer"
434 Select this option if you want to disable continuous timer ticks
435 and have them programmed to occur as required. This option saves
436 power as the system can remain in idle state for longer.
438 By default dynamic tick is disabled during the boot, and can be
439 manually enabled with:
441 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
443 Alternatively, if you want dynamic tick automatically enabled
444 during boot, pass "dyntick=enable" via the kernel command string.
446 Please note that dynamic tick may affect the accuracy of
447 timekeeping on some platforms depending on the implementation.
448 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
449 to have accurate timekeeping with dynamic tick.
453 default 128 if ARCH_L7200
454 default 200 if ARCH_EBSA110 || ARCH_S3C2410
455 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
459 bool "Use the ARM EABI to compile the kernel"
461 This option allows for the kernel to be compiled using the latest
462 ARM ABI (aka EABI). This is only useful if you are using a user
463 space environment that is also compiled with EABI.
465 Since there are major incompatibilities between the legacy ABI and
466 EABI, especially with regard to structure member alignment, this
467 option also changes the kernel syscall calling convention to
468 disambiguate both ABIs and allow for backward compatibility support
469 (selected with CONFIG_OABI_COMPAT).
471 To use this you need GCC version 4.0.0 or later.
474 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
475 depends on AEABI && EXPERIMENTAL
478 This option preserves the old syscall interface along with the
479 new (ARM EABI) one. It also provides a compatibility layer to
480 intercept syscalls that have structure arguments which layout
481 in memory differs between the legacy ABI and the new ARM EABI
482 (only for non "thumb" binaries). This option adds a tiny
483 overhead to all syscalls and produces a slightly larger kernel.
484 If you know you'll be using only pure EABI user space then you
485 can say N here. If this option is not selected and you attempt
486 to execute a legacy ABI binary then the result will be
487 UNPREDICTABLE (in fact it can be predicted that it won't work
488 at all). If in doubt say Y.
490 config ARCH_DISCONTIGMEM_ENABLE
492 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
494 Say Y to support efficient handling of discontiguous physical memory,
495 for architectures which are either NUMA (Non-Uniform Memory Access)
496 or have huge holes in the physical address space for other reasons.
497 See <file:Documentation/vm/numa> for more.
502 bool "Timer and CPU usage LEDs"
503 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
504 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
505 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
506 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
507 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
510 If you say Y here, the LEDs on your machine will be used
511 to provide useful information about your current system status.
513 If you are compiling a kernel for a NetWinder or EBSA-285, you will
514 be able to select which LEDs are active using the options below. If
515 you are compiling a kernel for the EBSA-110 or the LART however, the
516 red LED will simply flash regularly to indicate that the system is
517 still functional. It is safe to say Y here if you have a CATS
518 system, but the driver will do nothing.
521 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
522 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
524 default y if ARCH_EBSA110
526 If you say Y here, one of the system LEDs (the green one on the
527 NetWinder, the amber one on the EBSA285, or the red one on the LART)
528 will flash regularly to indicate that the system is still
529 operational. This is mainly useful to kernel hackers who are
530 debugging unstable kernels.
532 The LART uses the same LED for both Timer LED and CPU usage LED
533 functions. You may choose to use both, but the Timer LED function
534 will overrule the CPU usage LED.
537 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
538 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
541 If you say Y here, the red LED will be used to give a good real
542 time indication of CPU usage, by lighting whenever the idle task
543 is not currently executing.
545 The LART uses the same LED for both Timer LED and CPU usage LED
546 functions. You may choose to use both, but the Timer LED function
547 will overrule the CPU usage LED.
549 config ALIGNMENT_TRAP
551 default y if !ARCH_EBSA110
553 ARM processors can not fetch/store information which is not
554 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
555 address divisible by 4. On 32-bit ARM processors, these non-aligned
556 fetch/store instructions will be emulated in software if you say
557 here, which has a severe performance impact. This is necessary for
558 correct operation of some network protocols. With an IP-only
559 configuration it is safe to say N, otherwise say Y.
565 # Compressed boot loader in ROM. Yes, we really want to ask about
566 # TEXT and BSS so we preserve their values in the config files.
567 config ZBOOT_ROM_TEXT
568 hex "Compressed ROM boot loader base address"
571 The physical address at which the ROM-able zImage is to be
572 placed in the target. Platforms which normally make use of
573 ROM-able zImage formats normally set this to a suitable
574 value in their defconfig file.
576 If ZBOOT_ROM is not enabled, this has no effect.
579 hex "Compressed ROM boot loader BSS address"
582 The base address of 64KiB of read/write memory in the target
583 for the ROM-able zImage, which must be available while the
584 decompressor is running. Platforms which normally make use of
585 ROM-able zImage formats normally set this to a suitable
586 value in their defconfig file.
588 If ZBOOT_ROM is not enabled, this has no effect.
591 bool "Compressed boot loader in ROM/flash"
592 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
594 Say Y here if you intend to execute your compressed kernel image
595 (zImage) directly from ROM or flash. If unsure, say N.
598 string "Default kernel command string"
601 On some architectures (EBSA110 and CATS), there is currently no way
602 for the boot loader to pass arguments to the kernel. For these
603 architectures, you should supply some command-line options at build
604 time by entering them here. As a minimum, you should specify the
605 memory size and the root device (e.g., mem=64M root=/dev/nfs).
608 bool "Kernel Execute-In-Place from ROM"
609 depends on !ZBOOT_ROM
611 Execute-In-Place allows the kernel to run from non-volatile storage
612 directly addressable by the CPU, such as NOR flash. This saves RAM
613 space since the text section of the kernel is not loaded from flash
614 to RAM. Read-write sections, such as the data section and stack,
615 are still copied to RAM. The XIP kernel is not compressed since
616 it has to run directly from flash, so it will take more space to
617 store it. The flash address used to link the kernel object files,
618 and for storing it, is configuration dependent. Therefore, if you
619 say Y here, you must know the proper physical address where to
620 store the kernel image depending on your own flash memory usage.
622 Also note that the make target becomes "make xipImage" rather than
623 "make zImage" or "make Image". The final kernel binary to put in
624 ROM memory will be arch/arm/boot/xipImage.
629 hex "XIP Kernel Physical Location"
630 depends on XIP_KERNEL
633 This is the physical address in your flash memory the kernel will
634 be linked for and stored to. This address is dependent on your
639 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
641 menu "CPU Frequency scaling"
643 source "drivers/cpufreq/Kconfig"
645 config CPU_FREQ_SA1100
647 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
650 config CPU_FREQ_SA1110
652 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
655 config CPU_FREQ_INTEGRATOR
656 tristate "CPUfreq driver for ARM Integrator CPUs"
657 depends on ARCH_INTEGRATOR && CPU_FREQ
660 This enables the CPUfreq driver for ARM Integrator CPUs.
662 For details, take a look at <file:Documentation/cpu-freq>.
670 menu "Floating point emulation"
672 comment "At least one emulation must be selected"
675 bool "NWFPE math emulation"
676 depends on !AEABI || OABI_COMPAT
678 Say Y to include the NWFPE floating point emulator in the kernel.
679 This is necessary to run most binaries. Linux does not currently
680 support floating point hardware so you need to say Y here even if
681 your machine has an FPA or floating point co-processor podule.
683 You may say N here if you are going to load the Acorn FPEmulator
687 bool "Support extended precision"
690 Say Y to include 80-bit support in the kernel floating-point
691 emulator. Otherwise, only 32 and 64-bit support is compiled in.
692 Note that gcc does not generate 80-bit operations by default,
693 so in most cases this option only enlarges the size of the
694 floating point emulator without any good reason.
696 You almost surely want to say N here.
699 bool "FastFPE math emulation (EXPERIMENTAL)"
700 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
702 Say Y here to include the FAST floating point emulator in the kernel.
703 This is an experimental much faster emulator which now also has full
704 precision for the mantissa. It does not support any exceptions.
705 It is very simple, and approximately 3-6 times faster than NWFPE.
707 It should be sufficient for most programs. It may be not suitable
708 for scientific calculations, but you have to check this for yourself.
709 If you do not feel you need a faster FP emulation you should better
713 bool "VFP-format floating point maths"
714 depends on CPU_V6 || CPU_ARM926T
716 Say Y to include VFP support code in the kernel. This is needed
717 if your hardware includes a VFP unit.
719 Please see <file:Documentation/arm/VFP/release-notes.txt> for
720 release notes and additional status information.
722 Say N if your target does not have VFP hardware.
726 menu "Userspace binary formats"
728 source "fs/Kconfig.binfmt"
731 tristate "RISC OS personality"
734 Say Y here to include the kernel code necessary if you want to run
735 Acorn RISC OS/Arthur binaries under Linux. This code is still very
736 experimental; if this sounds frightening, say N and sleep in peace.
737 You can also say M here to compile this support as a module (which
738 will be called arthur).
742 menu "Power management options"
744 source "kernel/power/Kconfig"
747 tristate "Advanced Power Management Emulation"
749 APM is a BIOS specification for saving power using several different
750 techniques. This is mostly useful for battery powered laptops with
751 APM compliant BIOSes. If you say Y here, the system time will be
752 reset after a RESUME operation, the /proc/apm device will provide
753 battery status information, and user-space programs will receive
754 notification of APM "events" (e.g. battery status change).
756 In order to use APM, you will need supporting software. For location
757 and more information, read <file:Documentation/pm.txt> and the
758 Battery Powered Linux mini-HOWTO, available from
759 <http://www.tldp.org/docs.html#howto>.
761 This driver does not spin down disk drives (see the hdparm(8)
762 manpage ("man 8 hdparm") for that), and it doesn't turn off
763 VESA-compliant "green" monitors.
765 Generally, if you don't have a battery in your machine, there isn't
766 much point in using this driver and you should say N. If you get
767 random kernel OOPSes or reboots that don't seem to be related to
768 anything, try disabling/enabling this option (or disabling/enabling
775 menu "Device Drivers"
777 source "drivers/base/Kconfig"
779 source "drivers/connector/Kconfig"
782 source "drivers/mtd/Kconfig"
785 source "drivers/parport/Kconfig"
787 source "drivers/pnp/Kconfig"
789 source "drivers/block/Kconfig"
791 source "drivers/acorn/block/Kconfig"
793 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
794 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
795 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
796 source "drivers/ide/Kconfig"
799 source "drivers/scsi/Kconfig"
801 source "drivers/md/Kconfig"
803 source "drivers/message/fusion/Kconfig"
805 source "drivers/ieee1394/Kconfig"
807 source "drivers/message/i2o/Kconfig"
809 source "drivers/net/Kconfig"
811 source "drivers/isdn/Kconfig"
813 # input before char - char/joystick depends on it. As does USB.
815 source "drivers/input/Kconfig"
817 source "drivers/char/Kconfig"
819 source "drivers/i2c/Kconfig"
821 source "drivers/spi/Kconfig"
823 source "drivers/w1/Kconfig"
825 source "drivers/hwmon/Kconfig"
827 #source "drivers/l3/Kconfig"
829 source "drivers/misc/Kconfig"
831 source "drivers/mfd/Kconfig"
833 source "drivers/media/Kconfig"
835 source "drivers/video/Kconfig"
837 source "sound/Kconfig"
839 source "drivers/usb/Kconfig"
841 source "drivers/mmc/Kconfig"
843 source "drivers/rtc/Kconfig"
849 source "arch/arm/oprofile/Kconfig"
851 source "arch/arm/Kconfig.debug"
853 source "security/Kconfig"
855 source "crypto/Kconfig"