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_HWEIGHT
60 config GENERIC_CALIBRATE_DELAY
64 config GENERIC_BUST_SPINLOCK
67 config ARCH_MAY_HAVE_PC_FDC
70 config GENERIC_ISA_DMA
84 prompt "ARM system type"
85 default ARCH_VERSATILE
88 bool "Cirrus-CL-PS7500FE"
92 Support for the Cirrus Logic PS7500FE system-on-a-chip.
95 bool "CLPS711x/EP721x-based"
97 Support for Cirrus Logic 711x/721x based boards.
102 select FOOTBRIDGE_ADDIN
104 Support for Intel's EBSA285 companion chip.
110 This is an evaluation board for the StrongARM processor available
111 from Digital. It has limited hardware on-board, including an
112 Ethernet interface, two PCMCIA sockets, two serial ports and a
120 This enables support for the Cirrus EP93xx series of CPUs.
122 config ARCH_FOOTBRIDGE
126 Support for systems based on the DC21285 companion chip
127 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
129 config ARCH_INTEGRATOR
134 Support for ARM's Integrator platform.
140 Support for Intel's IOP3XX (XScale) family of processors.
147 Support for Intel's IXP4XX (XScale) family of processors.
150 bool "IXP2400/2800-based"
153 Support for Intel's IXP2400/2800 (XScale) family of processors.
159 Say Y here if you intend to run this kernel on a LinkUp Systems
160 L7200 Software Development Board which uses an ARM720T processor.
161 Information on this board can be obtained at:
163 <http://www.linkupsys.com/>
165 If you have any questions or comments about the Linux kernel port
166 to this board, send e-mail to <sjhill@cotw.com>.
172 Support for Intel's PXA2XX processor line.
179 select ARCH_MAY_HAVE_PC_FDC
182 On the Acorn Risc-PC, Linux can support the internal IDE disk and
183 CD-ROM interface, serial and parallel port, and the floppy drive.
188 select ARCH_DISCONTIGMEM_ENABLE
191 Support for StrongARM 11x0 based boards.
194 bool "Samsung S3C2410"
196 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
197 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
198 the Samsung SMDK2410 development board (and derivatives).
206 Support for the StrongARM based Digital DNARD machine, also known
207 as "Shark" (<http://www.shark-linux.de/shark.html>).
212 Say Y here for systems based on one of the Sharp LH7A40X
213 System on a Chip processors. These CPUs include an ARM922T
214 core with a wide array of integrated devices for
215 hand-held and low-power applications.
220 Support for TI's OMAP platform (OMAP1 and OMAP2).
222 config ARCH_VERSATILE
228 This enables support for ARM Ltd Versatile board.
235 This enables support for ARM Ltd RealView boards.
240 Support for Motorola's i.MX family of processors (MX1, MXL).
243 bool "Hynix-HMS720x-based"
246 This enables support for systems based on the Hynix HMS720x
249 bool "Agilent AAEC-2000 based"
252 This enables support for systems based on the Agilent AAEC-2000
254 config ARCH_AT91RM9200
257 Say Y here if you intend to run this kernel on an Atmel
258 AT91RM9200-based board.
262 source "arch/arm/mach-clps711x/Kconfig"
264 source "arch/arm/mach-ep93xx/Kconfig"
266 source "arch/arm/mach-footbridge/Kconfig"
268 source "arch/arm/mach-integrator/Kconfig"
270 source "arch/arm/mach-iop3xx/Kconfig"
272 source "arch/arm/mach-ixp4xx/Kconfig"
274 source "arch/arm/mach-ixp2000/Kconfig"
276 source "arch/arm/mach-pxa/Kconfig"
278 source "arch/arm/mach-sa1100/Kconfig"
280 source "arch/arm/plat-omap/Kconfig"
282 source "arch/arm/mach-omap1/Kconfig"
284 source "arch/arm/mach-omap2/Kconfig"
286 source "arch/arm/mach-s3c2410/Kconfig"
288 source "arch/arm/mach-lh7a40x/Kconfig"
290 source "arch/arm/mach-imx/Kconfig"
292 source "arch/arm/mach-h720x/Kconfig"
294 source "arch/arm/mach-versatile/Kconfig"
296 source "arch/arm/mach-aaec2000/Kconfig"
298 source "arch/arm/mach-realview/Kconfig"
300 source "arch/arm/mach-at91rm9200/Kconfig"
302 # Definitions to make life easier
306 source arch/arm/mm/Kconfig
308 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
311 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
316 source "arch/arm/common/Kconfig"
318 config FORCE_MAX_ZONEORDER
331 Find out whether you have ISA slots on your motherboard. ISA is the
332 name of a bus system, i.e. the way the CPU talks to the other stuff
333 inside your box. Other bus systems are PCI, EISA, MicroChannel
334 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
335 newer boards don't support it. If you have ISA, say Y, otherwise N.
337 # Select ISA DMA controller support
342 # Select ISA DMA interface
347 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
349 Find out whether you have a PCI motherboard. PCI is the name of a
350 bus system, i.e. the way the CPU talks to the other stuff inside
351 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
352 VESA. If you have PCI, say Y, otherwise N.
354 The PCI-HOWTO, available from
355 <http://www.tldp.org/docs.html#howto>, contains valuable
356 information about which PCI hardware does work under Linux and which
359 # Select the host bridge type
360 config PCI_HOST_VIA82C505
362 depends on PCI && ARCH_SHARK
365 source "drivers/pci/Kconfig"
367 source "drivers/pcmcia/Kconfig"
371 menu "Kernel Features"
374 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
375 depends on EXPERIMENTAL && REALVIEW_MPCORE
377 This enables support for systems with more than one CPU. If you have
378 a system with only one CPU, like most personal computers, say N. If
379 you have a system with more than one CPU, say Y.
381 If you say N here, the kernel will run on single and multiprocessor
382 machines, but will use only one CPU of a multiprocessor machine. If
383 you say Y here, the kernel will run on many, but not all, single
384 processor machines. On a single processor machine, the kernel will
385 run faster if you say N here.
387 See also the <file:Documentation/smp.txt>,
388 <file:Documentation/i386/IO-APIC.txt>,
389 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
390 <http://www.linuxdoc.org/docs.html#howto>.
392 If you don't know what to do here, say N.
395 int "Maximum number of CPUs (2-32)"
401 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
402 depends on SMP && HOTPLUG && EXPERIMENTAL
404 Say Y here to experiment with turning CPUs off and on. CPUs
405 can be controlled through /sys/devices/system/cpu.
408 bool "Use local timer interrupts"
409 depends on SMP && REALVIEW_MPCORE
412 Enable support for local timers on SMP platforms, rather then the
413 legacy IPI broadcast method. Local timers allows the system
414 accounting to be spread across the timer interval, preventing a
415 "thundering herd" at every timer tick.
418 bool "Preemptible Kernel (EXPERIMENTAL)"
419 depends on EXPERIMENTAL
421 This option reduces the latency of the kernel when reacting to
422 real-time or interactive events by allowing a low priority process to
423 be preempted even if it is in kernel mode executing a system call.
424 This allows applications to run more reliably even when the system is
427 Say Y here if you are building a kernel for a desktop, embedded
428 or real-time system. Say N if you are unsure.
431 bool "Dynamic tick timer"
433 Select this option if you want to disable continuous timer ticks
434 and have them programmed to occur as required. This option saves
435 power as the system can remain in idle state for longer.
437 By default dynamic tick is disabled during the boot, and can be
438 manually enabled with:
440 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
442 Alternatively, if you want dynamic tick automatically enabled
443 during boot, pass "dyntick=enable" via the kernel command string.
445 Please note that dynamic tick may affect the accuracy of
446 timekeeping on some platforms depending on the implementation.
447 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
448 to have accurate timekeeping with dynamic tick.
452 default 128 if ARCH_L7200
453 default 200 if ARCH_EBSA110 || ARCH_S3C2410
454 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
458 bool "Use the ARM EABI to compile the kernel"
460 This option allows for the kernel to be compiled using the latest
461 ARM ABI (aka EABI). This is only useful if you are using a user
462 space environment that is also compiled with EABI.
464 Since there are major incompatibilities between the legacy ABI and
465 EABI, especially with regard to structure member alignment, this
466 option also changes the kernel syscall calling convention to
467 disambiguate both ABIs and allow for backward compatibility support
468 (selected with CONFIG_OABI_COMPAT).
470 To use this you need GCC version 4.0.0 or later.
473 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
474 depends on AEABI && EXPERIMENTAL
477 This option preserves the old syscall interface along with the
478 new (ARM EABI) one. It also provides a compatibility layer to
479 intercept syscalls that have structure arguments which layout
480 in memory differs between the legacy ABI and the new ARM EABI
481 (only for non "thumb" binaries). This option adds a tiny
482 overhead to all syscalls and produces a slightly larger kernel.
483 If you know you'll be using only pure EABI user space then you
484 can say N here. If this option is not selected and you attempt
485 to execute a legacy ABI binary then the result will be
486 UNPREDICTABLE (in fact it can be predicted that it won't work
487 at all). If in doubt say Y.
489 config ARCH_DISCONTIGMEM_ENABLE
491 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
493 Say Y to support efficient handling of discontiguous physical memory,
494 for architectures which are either NUMA (Non-Uniform Memory Access)
495 or have huge holes in the physical address space for other reasons.
496 See <file:Documentation/vm/numa> for more.
501 bool "Timer and CPU usage LEDs"
502 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
503 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
504 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
505 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
506 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
509 If you say Y here, the LEDs on your machine will be used
510 to provide useful information about your current system status.
512 If you are compiling a kernel for a NetWinder or EBSA-285, you will
513 be able to select which LEDs are active using the options below. If
514 you are compiling a kernel for the EBSA-110 or the LART however, the
515 red LED will simply flash regularly to indicate that the system is
516 still functional. It is safe to say Y here if you have a CATS
517 system, but the driver will do nothing.
520 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
521 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
523 default y if ARCH_EBSA110
525 If you say Y here, one of the system LEDs (the green one on the
526 NetWinder, the amber one on the EBSA285, or the red one on the LART)
527 will flash regularly to indicate that the system is still
528 operational. This is mainly useful to kernel hackers who are
529 debugging unstable kernels.
531 The LART uses the same LED for both Timer LED and CPU usage LED
532 functions. You may choose to use both, but the Timer LED function
533 will overrule the CPU usage LED.
536 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
537 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
540 If you say Y here, the red LED will be used to give a good real
541 time indication of CPU usage, by lighting whenever the idle task
542 is not currently executing.
544 The LART uses the same LED for both Timer LED and CPU usage LED
545 functions. You may choose to use both, but the Timer LED function
546 will overrule the CPU usage LED.
548 config ALIGNMENT_TRAP
550 default y if !ARCH_EBSA110
552 ARM processors can not fetch/store information which is not
553 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
554 address divisible by 4. On 32-bit ARM processors, these non-aligned
555 fetch/store instructions will be emulated in software if you say
556 here, which has a severe performance impact. This is necessary for
557 correct operation of some network protocols. With an IP-only
558 configuration it is safe to say N, otherwise say Y.
564 # Compressed boot loader in ROM. Yes, we really want to ask about
565 # TEXT and BSS so we preserve their values in the config files.
566 config ZBOOT_ROM_TEXT
567 hex "Compressed ROM boot loader base address"
570 The physical address at which the ROM-able zImage is to be
571 placed in the target. Platforms which normally make use of
572 ROM-able zImage formats normally set this to a suitable
573 value in their defconfig file.
575 If ZBOOT_ROM is not enabled, this has no effect.
578 hex "Compressed ROM boot loader BSS address"
581 The base address of 64KiB of read/write memory in the target
582 for the ROM-able zImage, which must be available while the
583 decompressor is running. Platforms which normally make use of
584 ROM-able zImage formats normally set this to a suitable
585 value in their defconfig file.
587 If ZBOOT_ROM is not enabled, this has no effect.
590 bool "Compressed boot loader in ROM/flash"
591 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
593 Say Y here if you intend to execute your compressed kernel image
594 (zImage) directly from ROM or flash. If unsure, say N.
597 string "Default kernel command string"
600 On some architectures (EBSA110 and CATS), there is currently no way
601 for the boot loader to pass arguments to the kernel. For these
602 architectures, you should supply some command-line options at build
603 time by entering them here. As a minimum, you should specify the
604 memory size and the root device (e.g., mem=64M root=/dev/nfs).
607 bool "Kernel Execute-In-Place from ROM"
608 depends on !ZBOOT_ROM
610 Execute-In-Place allows the kernel to run from non-volatile storage
611 directly addressable by the CPU, such as NOR flash. This saves RAM
612 space since the text section of the kernel is not loaded from flash
613 to RAM. Read-write sections, such as the data section and stack,
614 are still copied to RAM. The XIP kernel is not compressed since
615 it has to run directly from flash, so it will take more space to
616 store it. The flash address used to link the kernel object files,
617 and for storing it, is configuration dependent. Therefore, if you
618 say Y here, you must know the proper physical address where to
619 store the kernel image depending on your own flash memory usage.
621 Also note that the make target becomes "make xipImage" rather than
622 "make zImage" or "make Image". The final kernel binary to put in
623 ROM memory will be arch/arm/boot/xipImage.
628 hex "XIP Kernel Physical Location"
629 depends on XIP_KERNEL
632 This is the physical address in your flash memory the kernel will
633 be linked for and stored to. This address is dependent on your
638 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
640 menu "CPU Frequency scaling"
642 source "drivers/cpufreq/Kconfig"
644 config CPU_FREQ_SA1100
646 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
649 config CPU_FREQ_SA1110
651 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
654 config CPU_FREQ_INTEGRATOR
655 tristate "CPUfreq driver for ARM Integrator CPUs"
656 depends on ARCH_INTEGRATOR && CPU_FREQ
659 This enables the CPUfreq driver for ARM Integrator CPUs.
661 For details, take a look at <file:Documentation/cpu-freq>.
669 menu "Floating point emulation"
671 comment "At least one emulation must be selected"
674 bool "NWFPE math emulation"
675 depends on !AEABI || OABI_COMPAT
677 Say Y to include the NWFPE floating point emulator in the kernel.
678 This is necessary to run most binaries. Linux does not currently
679 support floating point hardware so you need to say Y here even if
680 your machine has an FPA or floating point co-processor podule.
682 You may say N here if you are going to load the Acorn FPEmulator
686 bool "Support extended precision"
689 Say Y to include 80-bit support in the kernel floating-point
690 emulator. Otherwise, only 32 and 64-bit support is compiled in.
691 Note that gcc does not generate 80-bit operations by default,
692 so in most cases this option only enlarges the size of the
693 floating point emulator without any good reason.
695 You almost surely want to say N here.
698 bool "FastFPE math emulation (EXPERIMENTAL)"
699 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
701 Say Y here to include the FAST floating point emulator in the kernel.
702 This is an experimental much faster emulator which now also has full
703 precision for the mantissa. It does not support any exceptions.
704 It is very simple, and approximately 3-6 times faster than NWFPE.
706 It should be sufficient for most programs. It may be not suitable
707 for scientific calculations, but you have to check this for yourself.
708 If you do not feel you need a faster FP emulation you should better
712 bool "VFP-format floating point maths"
713 depends on CPU_V6 || CPU_ARM926T
715 Say Y to include VFP support code in the kernel. This is needed
716 if your hardware includes a VFP unit.
718 Please see <file:Documentation/arm/VFP/release-notes.txt> for
719 release notes and additional status information.
721 Say N if your target does not have VFP hardware.
725 menu "Userspace binary formats"
727 source "fs/Kconfig.binfmt"
730 tristate "RISC OS personality"
733 Say Y here to include the kernel code necessary if you want to run
734 Acorn RISC OS/Arthur binaries under Linux. This code is still very
735 experimental; if this sounds frightening, say N and sleep in peace.
736 You can also say M here to compile this support as a module (which
737 will be called arthur).
741 menu "Power management options"
743 source "kernel/power/Kconfig"
746 tristate "Advanced Power Management Emulation"
748 APM is a BIOS specification for saving power using several different
749 techniques. This is mostly useful for battery powered laptops with
750 APM compliant BIOSes. If you say Y here, the system time will be
751 reset after a RESUME operation, the /proc/apm device will provide
752 battery status information, and user-space programs will receive
753 notification of APM "events" (e.g. battery status change).
755 In order to use APM, you will need supporting software. For location
756 and more information, read <file:Documentation/pm.txt> and the
757 Battery Powered Linux mini-HOWTO, available from
758 <http://www.tldp.org/docs.html#howto>.
760 This driver does not spin down disk drives (see the hdparm(8)
761 manpage ("man 8 hdparm") for that), and it doesn't turn off
762 VESA-compliant "green" monitors.
764 Generally, if you don't have a battery in your machine, there isn't
765 much point in using this driver and you should say N. If you get
766 random kernel OOPSes or reboots that don't seem to be related to
767 anything, try disabling/enabling this option (or disabling/enabling
774 menu "Device Drivers"
776 source "drivers/base/Kconfig"
778 source "drivers/connector/Kconfig"
781 source "drivers/mtd/Kconfig"
784 source "drivers/parport/Kconfig"
786 source "drivers/pnp/Kconfig"
788 source "drivers/block/Kconfig"
790 source "drivers/acorn/block/Kconfig"
792 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
793 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
794 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
795 source "drivers/ide/Kconfig"
798 source "drivers/scsi/Kconfig"
800 source "drivers/md/Kconfig"
802 source "drivers/message/fusion/Kconfig"
804 source "drivers/ieee1394/Kconfig"
806 source "drivers/message/i2o/Kconfig"
808 source "drivers/net/Kconfig"
810 source "drivers/isdn/Kconfig"
812 # input before char - char/joystick depends on it. As does USB.
814 source "drivers/input/Kconfig"
816 source "drivers/char/Kconfig"
818 source "drivers/i2c/Kconfig"
820 source "drivers/spi/Kconfig"
822 source "drivers/w1/Kconfig"
824 source "drivers/hwmon/Kconfig"
826 #source "drivers/l3/Kconfig"
828 source "drivers/misc/Kconfig"
830 source "drivers/mfd/Kconfig"
832 source "drivers/media/Kconfig"
834 source "drivers/video/Kconfig"
836 source "sound/Kconfig"
838 source "drivers/usb/Kconfig"
840 source "drivers/mmc/Kconfig"
846 source "arch/arm/oprofile/Kconfig"
848 source "arch/arm/Kconfig.debug"
850 source "security/Kconfig"
852 source "crypto/Kconfig"