2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "Linux Kernel Configuration"
12 The ARM series is a line of low-power-consumption RISC chip designs
13 licensed by ARM Ltd and targeted at embedded applications and
14 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
15 manufactured, but legacy ARM-based PC hardware remains popular in
16 Europe. There is an ARM Linux project with a web page at
17 <http://www.arm.linux.org.uk/>.
26 The Extended Industry Standard Architecture (EISA) bus was
27 developed as an open alternative to the IBM MicroChannel bus.
29 The EISA bus provided some of the features of the IBM MicroChannel
30 bus while maintaining backward compatibility with cards made for
31 the older ISA bus. The EISA bus saw limited use between 1988 and
32 1995 when it was made obsolete by the PCI bus.
34 Say Y here if you are building a kernel for an EISA-based machine.
44 MicroChannel Architecture is found in some IBM PS/2 machines and
45 laptops. It is a bus system similar to PCI or ISA. See
46 <file:Documentation/mca.txt> (and especially the web page given
47 there) before attempting to build an MCA bus kernel.
49 config RWSEM_GENERIC_SPINLOCK
53 config RWSEM_XCHGADD_ALGORITHM
56 config GENERIC_CALIBRATE_DELAY
60 config GENERIC_BUST_SPINLOCK
63 config ARCH_MAY_HAVE_PC_FDC
66 config GENERIC_ISA_DMA
80 prompt "ARM system type"
81 default ARCH_VERSATILE
84 bool "Cirrus-CL-PS7500FE"
88 Support for the Cirrus Logic PS7500FE system-on-a-chip.
91 bool "CLPS711x/EP721x-based"
93 Support for Cirrus Logic 711x/721x based boards.
98 select FOOTBRIDGE_ADDIN
100 Support for Intel's EBSA285 companion chip.
106 This is an evaluation board for the StrongARM processor available
107 from Digital. It has limited hardware on-board, including an
108 Ethernet interface, two PCMCIA sockets, two serial ports and a
116 This enables support for the Cirrus EP93xx series of CPUs.
118 config ARCH_FOOTBRIDGE
122 Support for systems based on the DC21285 companion chip
123 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
125 config ARCH_INTEGRATOR
130 Support for ARM's Integrator platform.
136 Support for Intel's IOP3XX (XScale) family of processors.
143 Support for Intel's IXP4XX (XScale) family of processors.
146 bool "IXP2400/2800-based"
149 Support for Intel's IXP2400/2800 (XScale) family of processors.
155 Support for Intel's IXP23xx (XScale) family of processors.
161 Say Y here if you intend to run this kernel on a LinkUp Systems
162 L7200 Software Development Board which uses an ARM720T processor.
163 Information on this board can be obtained at:
165 <http://www.linkupsys.com/>
167 If you have any questions or comments about the Linux kernel port
168 to this board, send e-mail to <sjhill@cotw.com>.
174 Support for Intel's PXA2XX processor line.
181 select ARCH_MAY_HAVE_PC_FDC
184 On the Acorn Risc-PC, Linux can support the internal IDE disk and
185 CD-ROM interface, serial and parallel port, and the floppy drive.
190 select ARCH_DISCONTIGMEM_ENABLE
193 Support for StrongARM 11x0 based boards.
196 bool "Samsung S3C2410"
198 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
199 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
200 the Samsung SMDK2410 development board (and derivatives).
208 Support for the StrongARM based Digital DNARD machine, also known
209 as "Shark" (<http://www.shark-linux.de/shark.html>).
214 Say Y here for systems based on one of the Sharp LH7A40X
215 System on a Chip processors. These CPUs include an ARM922T
216 core with a wide array of integrated devices for
217 hand-held and low-power applications.
222 Support for TI's OMAP platform (OMAP1 and OMAP2).
224 config ARCH_VERSATILE
230 This enables support for ARM Ltd Versatile board.
237 This enables support for ARM Ltd RealView boards.
242 Support for Motorola's i.MX family of processors (MX1, MXL).
245 bool "Hynix-HMS720x-based"
248 This enables support for systems based on the Hynix HMS720x
251 bool "Agilent AAEC-2000 based"
254 This enables support for systems based on the Agilent AAEC-2000
256 config ARCH_AT91RM9200
259 Say Y here if you intend to run this kernel on an Atmel
260 AT91RM9200-based board.
264 source "arch/arm/mach-clps711x/Kconfig"
266 source "arch/arm/mach-ep93xx/Kconfig"
268 source "arch/arm/mach-footbridge/Kconfig"
270 source "arch/arm/mach-integrator/Kconfig"
272 source "arch/arm/mach-iop3xx/Kconfig"
274 source "arch/arm/mach-ixp4xx/Kconfig"
276 source "arch/arm/mach-ixp2000/Kconfig"
278 source "arch/arm/mach-ixp23xx/Kconfig"
280 source "arch/arm/mach-pxa/Kconfig"
282 source "arch/arm/mach-sa1100/Kconfig"
284 source "arch/arm/plat-omap/Kconfig"
286 source "arch/arm/mach-omap1/Kconfig"
288 source "arch/arm/mach-omap2/Kconfig"
290 source "arch/arm/mach-s3c2410/Kconfig"
292 source "arch/arm/mach-lh7a40x/Kconfig"
294 source "arch/arm/mach-imx/Kconfig"
296 source "arch/arm/mach-h720x/Kconfig"
298 source "arch/arm/mach-versatile/Kconfig"
300 source "arch/arm/mach-aaec2000/Kconfig"
302 source "arch/arm/mach-realview/Kconfig"
304 source "arch/arm/mach-at91rm9200/Kconfig"
306 # Definitions to make life easier
310 source arch/arm/mm/Kconfig
312 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
315 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
320 source "arch/arm/common/Kconfig"
322 config FORCE_MAX_ZONEORDER
335 Find out whether you have ISA slots on your motherboard. ISA is the
336 name of a bus system, i.e. the way the CPU talks to the other stuff
337 inside your box. Other bus systems are PCI, EISA, MicroChannel
338 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
339 newer boards don't support it. If you have ISA, say Y, otherwise N.
341 # Select ISA DMA controller support
346 # Select ISA DMA interface
351 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
353 Find out whether you have a PCI motherboard. PCI is the name of a
354 bus system, i.e. the way the CPU talks to the other stuff inside
355 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
356 VESA. If you have PCI, say Y, otherwise N.
358 The PCI-HOWTO, available from
359 <http://www.tldp.org/docs.html#howto>, contains valuable
360 information about which PCI hardware does work under Linux and which
363 # Select the host bridge type
364 config PCI_HOST_VIA82C505
366 depends on PCI && ARCH_SHARK
369 source "drivers/pci/Kconfig"
371 source "drivers/pcmcia/Kconfig"
375 menu "Kernel Features"
378 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
379 depends on EXPERIMENTAL && REALVIEW_MPCORE
381 This enables support for systems with more than one CPU. If you have
382 a system with only one CPU, like most personal computers, say N. If
383 you have a system with more than one CPU, say Y.
385 If you say N here, the kernel will run on single and multiprocessor
386 machines, but will use only one CPU of a multiprocessor machine. If
387 you say Y here, the kernel will run on many, but not all, single
388 processor machines. On a single processor machine, the kernel will
389 run faster if you say N here.
391 See also the <file:Documentation/smp.txt>,
392 <file:Documentation/i386/IO-APIC.txt>,
393 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
394 <http://www.linuxdoc.org/docs.html#howto>.
396 If you don't know what to do here, say N.
399 int "Maximum number of CPUs (2-32)"
405 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
406 depends on SMP && HOTPLUG && EXPERIMENTAL
408 Say Y here to experiment with turning CPUs off and on. CPUs
409 can be controlled through /sys/devices/system/cpu.
412 bool "Use local timer interrupts"
413 depends on SMP && REALVIEW_MPCORE
416 Enable support for local timers on SMP platforms, rather then the
417 legacy IPI broadcast method. Local timers allows the system
418 accounting to be spread across the timer interval, preventing a
419 "thundering herd" at every timer tick.
422 bool "Preemptible Kernel (EXPERIMENTAL)"
423 depends on EXPERIMENTAL
425 This option reduces the latency of the kernel when reacting to
426 real-time or interactive events by allowing a low priority process to
427 be preempted even if it is in kernel mode executing a system call.
428 This allows applications to run more reliably even when the system is
431 Say Y here if you are building a kernel for a desktop, embedded
432 or real-time system. Say N if you are unsure.
435 bool "Dynamic tick timer"
437 Select this option if you want to disable continuous timer ticks
438 and have them programmed to occur as required. This option saves
439 power as the system can remain in idle state for longer.
441 By default dynamic tick is disabled during the boot, and can be
442 manually enabled with:
444 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
446 Alternatively, if you want dynamic tick automatically enabled
447 during boot, pass "dyntick=enable" via the kernel command string.
449 Please note that dynamic tick may affect the accuracy of
450 timekeeping on some platforms depending on the implementation.
451 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
452 to have accurate timekeeping with dynamic tick.
456 default 128 if ARCH_L7200
457 default 200 if ARCH_EBSA110 || ARCH_S3C2410
458 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
462 bool "Use the ARM EABI to compile the kernel"
464 This option allows for the kernel to be compiled using the latest
465 ARM ABI (aka EABI). This is only useful if you are using a user
466 space environment that is also compiled with EABI.
468 Since there are major incompatibilities between the legacy ABI and
469 EABI, especially with regard to structure member alignment, this
470 option also changes the kernel syscall calling convention to
471 disambiguate both ABIs and allow for backward compatibility support
472 (selected with CONFIG_OABI_COMPAT).
474 To use this you need GCC version 4.0.0 or later.
477 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
478 depends on AEABI && EXPERIMENTAL
481 This option preserves the old syscall interface along with the
482 new (ARM EABI) one. It also provides a compatibility layer to
483 intercept syscalls that have structure arguments which layout
484 in memory differs between the legacy ABI and the new ARM EABI
485 (only for non "thumb" binaries). This option adds a tiny
486 overhead to all syscalls and produces a slightly larger kernel.
487 If you know you'll be using only pure EABI user space then you
488 can say N here. If this option is not selected and you attempt
489 to execute a legacy ABI binary then the result will be
490 UNPREDICTABLE (in fact it can be predicted that it won't work
491 at all). If in doubt say Y.
493 config ARCH_DISCONTIGMEM_ENABLE
495 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
497 Say Y to support efficient handling of discontiguous physical memory,
498 for architectures which are either NUMA (Non-Uniform Memory Access)
499 or have huge holes in the physical address space for other reasons.
500 See <file:Documentation/vm/numa> for more.
505 bool "Timer and CPU usage LEDs"
506 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
507 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
508 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
509 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
510 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
513 If you say Y here, the LEDs on your machine will be used
514 to provide useful information about your current system status.
516 If you are compiling a kernel for a NetWinder or EBSA-285, you will
517 be able to select which LEDs are active using the options below. If
518 you are compiling a kernel for the EBSA-110 or the LART however, the
519 red LED will simply flash regularly to indicate that the system is
520 still functional. It is safe to say Y here if you have a CATS
521 system, but the driver will do nothing.
524 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
525 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
527 default y if ARCH_EBSA110
529 If you say Y here, one of the system LEDs (the green one on the
530 NetWinder, the amber one on the EBSA285, or the red one on the LART)
531 will flash regularly to indicate that the system is still
532 operational. This is mainly useful to kernel hackers who are
533 debugging unstable kernels.
535 The LART uses the same LED for both Timer LED and CPU usage LED
536 functions. You may choose to use both, but the Timer LED function
537 will overrule the CPU usage LED.
540 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
541 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
544 If you say Y here, the red LED will be used to give a good real
545 time indication of CPU usage, by lighting whenever the idle task
546 is not currently executing.
548 The LART uses the same LED for both Timer LED and CPU usage LED
549 functions. You may choose to use both, but the Timer LED function
550 will overrule the CPU usage LED.
552 config ALIGNMENT_TRAP
554 default y if !ARCH_EBSA110
556 ARM processors can not fetch/store information which is not
557 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
558 address divisible by 4. On 32-bit ARM processors, these non-aligned
559 fetch/store instructions will be emulated in software if you say
560 here, which has a severe performance impact. This is necessary for
561 correct operation of some network protocols. With an IP-only
562 configuration it is safe to say N, otherwise say Y.
568 # Compressed boot loader in ROM. Yes, we really want to ask about
569 # TEXT and BSS so we preserve their values in the config files.
570 config ZBOOT_ROM_TEXT
571 hex "Compressed ROM boot loader base address"
574 The physical address at which the ROM-able zImage is to be
575 placed in the target. Platforms which normally make use of
576 ROM-able zImage formats normally set this to a suitable
577 value in their defconfig file.
579 If ZBOOT_ROM is not enabled, this has no effect.
582 hex "Compressed ROM boot loader BSS address"
585 The base address of 64KiB of read/write memory in the target
586 for the ROM-able zImage, which must be available while the
587 decompressor is running. Platforms which normally make use of
588 ROM-able zImage formats normally set this to a suitable
589 value in their defconfig file.
591 If ZBOOT_ROM is not enabled, this has no effect.
594 bool "Compressed boot loader in ROM/flash"
595 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
597 Say Y here if you intend to execute your compressed kernel image
598 (zImage) directly from ROM or flash. If unsure, say N.
601 string "Default kernel command string"
604 On some architectures (EBSA110 and CATS), there is currently no way
605 for the boot loader to pass arguments to the kernel. For these
606 architectures, you should supply some command-line options at build
607 time by entering them here. As a minimum, you should specify the
608 memory size and the root device (e.g., mem=64M root=/dev/nfs).
611 bool "Kernel Execute-In-Place from ROM"
612 depends on !ZBOOT_ROM
614 Execute-In-Place allows the kernel to run from non-volatile storage
615 directly addressable by the CPU, such as NOR flash. This saves RAM
616 space since the text section of the kernel is not loaded from flash
617 to RAM. Read-write sections, such as the data section and stack,
618 are still copied to RAM. The XIP kernel is not compressed since
619 it has to run directly from flash, so it will take more space to
620 store it. The flash address used to link the kernel object files,
621 and for storing it, is configuration dependent. Therefore, if you
622 say Y here, you must know the proper physical address where to
623 store the kernel image depending on your own flash memory usage.
625 Also note that the make target becomes "make xipImage" rather than
626 "make zImage" or "make Image". The final kernel binary to put in
627 ROM memory will be arch/arm/boot/xipImage.
632 hex "XIP Kernel Physical Location"
633 depends on XIP_KERNEL
636 This is the physical address in your flash memory the kernel will
637 be linked for and stored to. This address is dependent on your
642 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
644 menu "CPU Frequency scaling"
646 source "drivers/cpufreq/Kconfig"
648 config CPU_FREQ_SA1100
650 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
653 config CPU_FREQ_SA1110
655 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
658 config CPU_FREQ_INTEGRATOR
659 tristate "CPUfreq driver for ARM Integrator CPUs"
660 depends on ARCH_INTEGRATOR && CPU_FREQ
663 This enables the CPUfreq driver for ARM Integrator CPUs.
665 For details, take a look at <file:Documentation/cpu-freq>.
673 menu "Floating point emulation"
675 comment "At least one emulation must be selected"
678 bool "NWFPE math emulation"
679 depends on !AEABI || OABI_COMPAT
681 Say Y to include the NWFPE floating point emulator in the kernel.
682 This is necessary to run most binaries. Linux does not currently
683 support floating point hardware so you need to say Y here even if
684 your machine has an FPA or floating point co-processor podule.
686 You may say N here if you are going to load the Acorn FPEmulator
690 bool "Support extended precision"
693 Say Y to include 80-bit support in the kernel floating-point
694 emulator. Otherwise, only 32 and 64-bit support is compiled in.
695 Note that gcc does not generate 80-bit operations by default,
696 so in most cases this option only enlarges the size of the
697 floating point emulator without any good reason.
699 You almost surely want to say N here.
702 bool "FastFPE math emulation (EXPERIMENTAL)"
703 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
705 Say Y here to include the FAST floating point emulator in the kernel.
706 This is an experimental much faster emulator which now also has full
707 precision for the mantissa. It does not support any exceptions.
708 It is very simple, and approximately 3-6 times faster than NWFPE.
710 It should be sufficient for most programs. It may be not suitable
711 for scientific calculations, but you have to check this for yourself.
712 If you do not feel you need a faster FP emulation you should better
716 bool "VFP-format floating point maths"
717 depends on CPU_V6 || CPU_ARM926T
719 Say Y to include VFP support code in the kernel. This is needed
720 if your hardware includes a VFP unit.
722 Please see <file:Documentation/arm/VFP/release-notes.txt> for
723 release notes and additional status information.
725 Say N if your target does not have VFP hardware.
729 menu "Userspace binary formats"
731 source "fs/Kconfig.binfmt"
734 tristate "RISC OS personality"
737 Say Y here to include the kernel code necessary if you want to run
738 Acorn RISC OS/Arthur binaries under Linux. This code is still very
739 experimental; if this sounds frightening, say N and sleep in peace.
740 You can also say M here to compile this support as a module (which
741 will be called arthur).
745 menu "Power management options"
747 source "kernel/power/Kconfig"
750 tristate "Advanced Power Management Emulation"
752 APM is a BIOS specification for saving power using several different
753 techniques. This is mostly useful for battery powered laptops with
754 APM compliant BIOSes. If you say Y here, the system time will be
755 reset after a RESUME operation, the /proc/apm device will provide
756 battery status information, and user-space programs will receive
757 notification of APM "events" (e.g. battery status change).
759 In order to use APM, you will need supporting software. For location
760 and more information, read <file:Documentation/pm.txt> and the
761 Battery Powered Linux mini-HOWTO, available from
762 <http://www.tldp.org/docs.html#howto>.
764 This driver does not spin down disk drives (see the hdparm(8)
765 manpage ("man 8 hdparm") for that), and it doesn't turn off
766 VESA-compliant "green" monitors.
768 Generally, if you don't have a battery in your machine, there isn't
769 much point in using this driver and you should say N. If you get
770 random kernel OOPSes or reboots that don't seem to be related to
771 anything, try disabling/enabling this option (or disabling/enabling
778 menu "Device Drivers"
780 source "drivers/base/Kconfig"
782 source "drivers/connector/Kconfig"
785 source "drivers/mtd/Kconfig"
788 source "drivers/parport/Kconfig"
790 source "drivers/pnp/Kconfig"
792 source "drivers/block/Kconfig"
794 source "drivers/acorn/block/Kconfig"
796 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
797 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
798 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
800 source "drivers/ide/Kconfig"
803 source "drivers/scsi/Kconfig"
805 source "drivers/md/Kconfig"
807 source "drivers/message/fusion/Kconfig"
809 source "drivers/ieee1394/Kconfig"
811 source "drivers/message/i2o/Kconfig"
813 source "drivers/net/Kconfig"
815 source "drivers/isdn/Kconfig"
817 # input before char - char/joystick depends on it. As does USB.
819 source "drivers/input/Kconfig"
821 source "drivers/char/Kconfig"
823 source "drivers/i2c/Kconfig"
825 source "drivers/spi/Kconfig"
827 source "drivers/w1/Kconfig"
829 source "drivers/hwmon/Kconfig"
831 #source "drivers/l3/Kconfig"
833 source "drivers/misc/Kconfig"
835 source "drivers/mfd/Kconfig"
837 source "drivers/media/Kconfig"
839 source "drivers/video/Kconfig"
841 source "sound/Kconfig"
843 source "drivers/usb/Kconfig"
845 source "drivers/mmc/Kconfig"
851 source "arch/arm/oprofile/Kconfig"
853 source "arch/arm/Kconfig.debug"
855 source "security/Kconfig"
857 source "crypto/Kconfig"