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
77 default 0xffff0000 if MMU
78 default DRAM_BASE if REMAP_VECTORS_TO_RAM
81 The base address of exception vectors.
88 prompt "ARM system type"
89 default ARCH_VERSATILE
92 bool "Cirrus-CL-PS7500FE"
96 Support for the Cirrus Logic PS7500FE system-on-a-chip.
99 bool "CLPS711x/EP721x-based"
101 Support for Cirrus Logic 711x/721x based boards.
106 select FOOTBRIDGE_ADDIN
108 Support for Intel's EBSA285 companion chip.
114 This is an evaluation board for the StrongARM processor available
115 from Digital. It has limited hardware on-board, including an
116 Ethernet interface, two PCMCIA sockets, two serial ports and a
124 This enables support for the Cirrus EP93xx series of CPUs.
126 config ARCH_FOOTBRIDGE
130 Support for systems based on the DC21285 companion chip
131 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
133 config ARCH_INTEGRATOR
138 Support for ARM's Integrator platform.
144 Support for Intel's IOP3XX (XScale) family of processors.
151 Support for Intel's IXP4XX (XScale) family of processors.
154 bool "IXP2400/2800-based"
157 Support for Intel's IXP2400/2800 (XScale) family of processors.
163 Support for Intel's IXP23xx (XScale) family of processors.
169 Say Y here if you intend to run this kernel on a LinkUp Systems
170 L7200 Software Development Board which uses an ARM720T processor.
171 Information on this board can be obtained at:
173 <http://www.linkupsys.com/>
175 If you have any questions or comments about the Linux kernel port
176 to this board, send e-mail to <sjhill@cotw.com>.
182 Support for Intel's PXA2XX processor line.
189 select ARCH_MAY_HAVE_PC_FDC
192 On the Acorn Risc-PC, Linux can support the internal IDE disk and
193 CD-ROM interface, serial and parallel port, and the floppy drive.
198 select ARCH_DISCONTIGMEM_ENABLE
201 Support for StrongARM 11x0 based boards.
204 bool "Samsung S3C2410"
206 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
207 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
208 the Samsung SMDK2410 development board (and derivatives).
216 Support for the StrongARM based Digital DNARD machine, also known
217 as "Shark" (<http://www.shark-linux.de/shark.html>).
222 Say Y here for systems based on one of the Sharp LH7A40X
223 System on a Chip processors. These CPUs include an ARM922T
224 core with a wide array of integrated devices for
225 hand-held and low-power applications.
230 Support for TI's OMAP platform (OMAP1 and OMAP2).
232 config ARCH_VERSATILE
238 This enables support for ARM Ltd Versatile board.
245 This enables support for ARM Ltd RealView boards.
250 Support for Motorola's i.MX family of processors (MX1, MXL).
253 bool "Hynix-HMS720x-based"
256 This enables support for systems based on the Hynix HMS720x
259 bool "Agilent AAEC-2000 based"
262 This enables support for systems based on the Agilent AAEC-2000
264 config ARCH_AT91RM9200
267 Say Y here if you intend to run this kernel on an Atmel
268 AT91RM9200-based board.
272 source "arch/arm/mach-clps711x/Kconfig"
274 source "arch/arm/mach-ep93xx/Kconfig"
276 source "arch/arm/mach-footbridge/Kconfig"
278 source "arch/arm/mach-integrator/Kconfig"
280 source "arch/arm/mach-iop3xx/Kconfig"
282 source "arch/arm/mach-ixp4xx/Kconfig"
284 source "arch/arm/mach-ixp2000/Kconfig"
286 source "arch/arm/mach-ixp23xx/Kconfig"
288 source "arch/arm/mach-pxa/Kconfig"
290 source "arch/arm/mach-sa1100/Kconfig"
292 source "arch/arm/plat-omap/Kconfig"
294 source "arch/arm/mach-omap1/Kconfig"
296 source "arch/arm/mach-omap2/Kconfig"
298 source "arch/arm/mach-s3c2410/Kconfig"
300 source "arch/arm/mach-lh7a40x/Kconfig"
302 source "arch/arm/mach-imx/Kconfig"
304 source "arch/arm/mach-h720x/Kconfig"
306 source "arch/arm/mach-versatile/Kconfig"
308 source "arch/arm/mach-aaec2000/Kconfig"
310 source "arch/arm/mach-realview/Kconfig"
312 source "arch/arm/mach-at91rm9200/Kconfig"
314 # Definitions to make life easier
318 source arch/arm/mm/Kconfig
320 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
323 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
328 source "arch/arm/common/Kconfig"
330 config FORCE_MAX_ZONEORDER
343 Find out whether you have ISA slots on your motherboard. ISA is the
344 name of a bus system, i.e. the way the CPU talks to the other stuff
345 inside your box. Other bus systems are PCI, EISA, MicroChannel
346 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
347 newer boards don't support it. If you have ISA, say Y, otherwise N.
349 # Select ISA DMA controller support
354 # Select ISA DMA interface
359 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
361 Find out whether you have a PCI motherboard. PCI is the name of a
362 bus system, i.e. the way the CPU talks to the other stuff inside
363 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
364 VESA. If you have PCI, say Y, otherwise N.
366 The PCI-HOWTO, available from
367 <http://www.tldp.org/docs.html#howto>, contains valuable
368 information about which PCI hardware does work under Linux and which
371 # Select the host bridge type
372 config PCI_HOST_VIA82C505
374 depends on PCI && ARCH_SHARK
377 source "drivers/pci/Kconfig"
379 source "drivers/pcmcia/Kconfig"
383 menu "Kernel Features"
386 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
387 depends on EXPERIMENTAL && REALVIEW_MPCORE
389 This enables support for systems with more than one CPU. If you have
390 a system with only one CPU, like most personal computers, say N. If
391 you have a system with more than one CPU, say Y.
393 If you say N here, the kernel will run on single and multiprocessor
394 machines, but will use only one CPU of a multiprocessor machine. If
395 you say Y here, the kernel will run on many, but not all, single
396 processor machines. On a single processor machine, the kernel will
397 run faster if you say N here.
399 See also the <file:Documentation/smp.txt>,
400 <file:Documentation/i386/IO-APIC.txt>,
401 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
402 <http://www.linuxdoc.org/docs.html#howto>.
404 If you don't know what to do here, say N.
407 int "Maximum number of CPUs (2-32)"
413 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
414 depends on SMP && HOTPLUG && EXPERIMENTAL
416 Say Y here to experiment with turning CPUs off and on. CPUs
417 can be controlled through /sys/devices/system/cpu.
420 bool "Use local timer interrupts"
421 depends on SMP && REALVIEW_MPCORE
424 Enable support for local timers on SMP platforms, rather then the
425 legacy IPI broadcast method. Local timers allows the system
426 accounting to be spread across the timer interval, preventing a
427 "thundering herd" at every timer tick.
430 bool "Preemptible Kernel (EXPERIMENTAL)"
431 depends on EXPERIMENTAL
433 This option reduces the latency of the kernel when reacting to
434 real-time or interactive events by allowing a low priority process to
435 be preempted even if it is in kernel mode executing a system call.
436 This allows applications to run more reliably even when the system is
439 Say Y here if you are building a kernel for a desktop, embedded
440 or real-time system. Say N if you are unsure.
443 bool "Dynamic tick timer"
445 Select this option if you want to disable continuous timer ticks
446 and have them programmed to occur as required. This option saves
447 power as the system can remain in idle state for longer.
449 By default dynamic tick is disabled during the boot, and can be
450 manually enabled with:
452 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
454 Alternatively, if you want dynamic tick automatically enabled
455 during boot, pass "dyntick=enable" via the kernel command string.
457 Please note that dynamic tick may affect the accuracy of
458 timekeeping on some platforms depending on the implementation.
459 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
460 to have accurate timekeeping with dynamic tick.
464 default 128 if ARCH_L7200
465 default 200 if ARCH_EBSA110 || ARCH_S3C2410
466 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
470 bool "Use the ARM EABI to compile the kernel"
472 This option allows for the kernel to be compiled using the latest
473 ARM ABI (aka EABI). This is only useful if you are using a user
474 space environment that is also compiled with EABI.
476 Since there are major incompatibilities between the legacy ABI and
477 EABI, especially with regard to structure member alignment, this
478 option also changes the kernel syscall calling convention to
479 disambiguate both ABIs and allow for backward compatibility support
480 (selected with CONFIG_OABI_COMPAT).
482 To use this you need GCC version 4.0.0 or later.
485 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
486 depends on AEABI && EXPERIMENTAL
489 This option preserves the old syscall interface along with the
490 new (ARM EABI) one. It also provides a compatibility layer to
491 intercept syscalls that have structure arguments which layout
492 in memory differs between the legacy ABI and the new ARM EABI
493 (only for non "thumb" binaries). This option adds a tiny
494 overhead to all syscalls and produces a slightly larger kernel.
495 If you know you'll be using only pure EABI user space then you
496 can say N here. If this option is not selected and you attempt
497 to execute a legacy ABI binary then the result will be
498 UNPREDICTABLE (in fact it can be predicted that it won't work
499 at all). If in doubt say Y.
501 config ARCH_DISCONTIGMEM_ENABLE
503 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
505 Say Y to support efficient handling of discontiguous physical memory,
506 for architectures which are either NUMA (Non-Uniform Memory Access)
507 or have huge holes in the physical address space for other reasons.
508 See <file:Documentation/vm/numa> for more.
513 bool "Timer and CPU usage LEDs"
514 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
515 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
516 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
517 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
518 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
521 If you say Y here, the LEDs on your machine will be used
522 to provide useful information about your current system status.
524 If you are compiling a kernel for a NetWinder or EBSA-285, you will
525 be able to select which LEDs are active using the options below. If
526 you are compiling a kernel for the EBSA-110 or the LART however, the
527 red LED will simply flash regularly to indicate that the system is
528 still functional. It is safe to say Y here if you have a CATS
529 system, but the driver will do nothing.
532 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
533 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
535 default y if ARCH_EBSA110
537 If you say Y here, one of the system LEDs (the green one on the
538 NetWinder, the amber one on the EBSA285, or the red one on the LART)
539 will flash regularly to indicate that the system is still
540 operational. This is mainly useful to kernel hackers who are
541 debugging unstable kernels.
543 The LART uses the same LED for both Timer LED and CPU usage LED
544 functions. You may choose to use both, but the Timer LED function
545 will overrule the CPU usage LED.
548 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
549 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
552 If you say Y here, the red LED will be used to give a good real
553 time indication of CPU usage, by lighting whenever the idle task
554 is not currently executing.
556 The LART uses the same LED for both Timer LED and CPU usage LED
557 functions. You may choose to use both, but the Timer LED function
558 will overrule the CPU usage LED.
560 config ALIGNMENT_TRAP
562 default y if !ARCH_EBSA110
564 ARM processors can not fetch/store information which is not
565 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
566 address divisible by 4. On 32-bit ARM processors, these non-aligned
567 fetch/store instructions will be emulated in software if you say
568 here, which has a severe performance impact. This is necessary for
569 correct operation of some network protocols. With an IP-only
570 configuration it is safe to say N, otherwise say Y.
576 # Compressed boot loader in ROM. Yes, we really want to ask about
577 # TEXT and BSS so we preserve their values in the config files.
578 config ZBOOT_ROM_TEXT
579 hex "Compressed ROM boot loader base address"
582 The physical address at which the ROM-able zImage is to be
583 placed in the target. 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 hex "Compressed ROM boot loader BSS address"
593 The base address of 64KiB of read/write memory in the target
594 for the ROM-able zImage, which must be available while the
595 decompressor is running. Platforms which normally make use of
596 ROM-able zImage formats normally set this to a suitable
597 value in their defconfig file.
599 If ZBOOT_ROM is not enabled, this has no effect.
602 bool "Compressed boot loader in ROM/flash"
603 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
605 Say Y here if you intend to execute your compressed kernel image
606 (zImage) directly from ROM or flash. If unsure, say N.
609 string "Default kernel command string"
612 On some architectures (EBSA110 and CATS), there is currently no way
613 for the boot loader to pass arguments to the kernel. For these
614 architectures, you should supply some command-line options at build
615 time by entering them here. As a minimum, you should specify the
616 memory size and the root device (e.g., mem=64M root=/dev/nfs).
619 bool "Kernel Execute-In-Place from ROM"
620 depends on !ZBOOT_ROM
622 Execute-In-Place allows the kernel to run from non-volatile storage
623 directly addressable by the CPU, such as NOR flash. This saves RAM
624 space since the text section of the kernel is not loaded from flash
625 to RAM. Read-write sections, such as the data section and stack,
626 are still copied to RAM. The XIP kernel is not compressed since
627 it has to run directly from flash, so it will take more space to
628 store it. The flash address used to link the kernel object files,
629 and for storing it, is configuration dependent. Therefore, if you
630 say Y here, you must know the proper physical address where to
631 store the kernel image depending on your own flash memory usage.
633 Also note that the make target becomes "make xipImage" rather than
634 "make zImage" or "make Image". The final kernel binary to put in
635 ROM memory will be arch/arm/boot/xipImage.
640 hex "XIP Kernel Physical Location"
641 depends on XIP_KERNEL
644 This is the physical address in your flash memory the kernel will
645 be linked for and stored to. This address is dependent on your
650 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
652 menu "CPU Frequency scaling"
654 source "drivers/cpufreq/Kconfig"
656 config CPU_FREQ_SA1100
658 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
661 config CPU_FREQ_SA1110
663 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
666 config CPU_FREQ_INTEGRATOR
667 tristate "CPUfreq driver for ARM Integrator CPUs"
668 depends on ARCH_INTEGRATOR && CPU_FREQ
671 This enables the CPUfreq driver for ARM Integrator CPUs.
673 For details, take a look at <file:Documentation/cpu-freq>.
681 menu "Floating point emulation"
683 comment "At least one emulation must be selected"
686 bool "NWFPE math emulation"
687 depends on !AEABI || OABI_COMPAT
689 Say Y to include the NWFPE floating point emulator in the kernel.
690 This is necessary to run most binaries. Linux does not currently
691 support floating point hardware so you need to say Y here even if
692 your machine has an FPA or floating point co-processor podule.
694 You may say N here if you are going to load the Acorn FPEmulator
698 bool "Support extended precision"
701 Say Y to include 80-bit support in the kernel floating-point
702 emulator. Otherwise, only 32 and 64-bit support is compiled in.
703 Note that gcc does not generate 80-bit operations by default,
704 so in most cases this option only enlarges the size of the
705 floating point emulator without any good reason.
707 You almost surely want to say N here.
710 bool "FastFPE math emulation (EXPERIMENTAL)"
711 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
713 Say Y here to include the FAST floating point emulator in the kernel.
714 This is an experimental much faster emulator which now also has full
715 precision for the mantissa. It does not support any exceptions.
716 It is very simple, and approximately 3-6 times faster than NWFPE.
718 It should be sufficient for most programs. It may be not suitable
719 for scientific calculations, but you have to check this for yourself.
720 If you do not feel you need a faster FP emulation you should better
724 bool "VFP-format floating point maths"
725 depends on CPU_V6 || CPU_ARM926T
727 Say Y to include VFP support code in the kernel. This is needed
728 if your hardware includes a VFP unit.
730 Please see <file:Documentation/arm/VFP/release-notes.txt> for
731 release notes and additional status information.
733 Say N if your target does not have VFP hardware.
737 menu "Userspace binary formats"
739 source "fs/Kconfig.binfmt"
742 tristate "RISC OS personality"
745 Say Y here to include the kernel code necessary if you want to run
746 Acorn RISC OS/Arthur binaries under Linux. This code is still very
747 experimental; if this sounds frightening, say N and sleep in peace.
748 You can also say M here to compile this support as a module (which
749 will be called arthur).
753 menu "Power management options"
755 source "kernel/power/Kconfig"
758 tristate "Advanced Power Management Emulation"
760 APM is a BIOS specification for saving power using several different
761 techniques. This is mostly useful for battery powered laptops with
762 APM compliant BIOSes. If you say Y here, the system time will be
763 reset after a RESUME operation, the /proc/apm device will provide
764 battery status information, and user-space programs will receive
765 notification of APM "events" (e.g. battery status change).
767 In order to use APM, you will need supporting software. For location
768 and more information, read <file:Documentation/pm.txt> and the
769 Battery Powered Linux mini-HOWTO, available from
770 <http://www.tldp.org/docs.html#howto>.
772 This driver does not spin down disk drives (see the hdparm(8)
773 manpage ("man 8 hdparm") for that), and it doesn't turn off
774 VESA-compliant "green" monitors.
776 Generally, if you don't have a battery in your machine, there isn't
777 much point in using this driver and you should say N. If you get
778 random kernel OOPSes or reboots that don't seem to be related to
779 anything, try disabling/enabling this option (or disabling/enabling
786 menu "Device Drivers"
788 source "drivers/base/Kconfig"
790 source "drivers/connector/Kconfig"
793 source "drivers/mtd/Kconfig"
796 source "drivers/parport/Kconfig"
798 source "drivers/pnp/Kconfig"
800 source "drivers/block/Kconfig"
802 source "drivers/acorn/block/Kconfig"
804 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
805 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
806 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
808 source "drivers/ide/Kconfig"
811 source "drivers/scsi/Kconfig"
813 source "drivers/md/Kconfig"
815 source "drivers/message/fusion/Kconfig"
817 source "drivers/ieee1394/Kconfig"
819 source "drivers/message/i2o/Kconfig"
821 source "drivers/net/Kconfig"
823 source "drivers/isdn/Kconfig"
825 # input before char - char/joystick depends on it. As does USB.
827 source "drivers/input/Kconfig"
829 source "drivers/char/Kconfig"
831 source "drivers/i2c/Kconfig"
833 source "drivers/spi/Kconfig"
835 source "drivers/w1/Kconfig"
837 source "drivers/hwmon/Kconfig"
839 #source "drivers/l3/Kconfig"
841 source "drivers/misc/Kconfig"
843 source "drivers/mfd/Kconfig"
845 source "drivers/media/Kconfig"
847 source "drivers/video/Kconfig"
849 source "sound/Kconfig"
851 source "drivers/usb/Kconfig"
853 source "drivers/mmc/Kconfig"
859 source "arch/arm/oprofile/Kconfig"
861 source "arch/arm/Kconfig.debug"
863 source "security/Kconfig"
865 source "crypto/Kconfig"