2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "Linux Kernel Configuration"
12 select SYS_SUPPORTS_APM_EMULATION
14 The ARM series is a line of low-power-consumption RISC chip designs
15 licensed by ARM Ltd and targeted at embedded applications and
16 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
17 manufactured, but legacy ARM-based PC hardware remains popular in
18 Europe. There is an ARM Linux project with a web page at
19 <http://www.arm.linux.org.uk/>.
21 config SYS_SUPPORTS_APM_EMULATION
35 The Extended Industry Standard Architecture (EISA) bus was
36 developed as an open alternative to the IBM MicroChannel bus.
38 The EISA bus provided some of the features of the IBM MicroChannel
39 bus while maintaining backward compatibility with cards made for
40 the older ISA bus. The EISA bus saw limited use between 1988 and
41 1995 when it was made obsolete by the PCI bus.
43 Say Y here if you are building a kernel for an EISA-based machine.
53 MicroChannel Architecture is found in some IBM PS/2 machines and
54 laptops. It is a bus system similar to PCI or ISA. See
55 <file:Documentation/mca.txt> (and especially the web page given
56 there) before attempting to build an MCA bus kernel.
58 config GENERIC_HARDIRQS
62 config TRACE_IRQFLAGS_SUPPORT
66 config HARDIRQS_SW_RESEND
70 config GENERIC_IRQ_PROBE
74 config RWSEM_GENERIC_SPINLOCK
78 config RWSEM_XCHGADD_ALGORITHM
81 config ARCH_HAS_ILOG2_U32
85 config ARCH_HAS_ILOG2_U64
89 config GENERIC_HWEIGHT
93 config GENERIC_CALIBRATE_DELAY
97 config GENERIC_BUST_SPINLOCK
100 config ARCH_MAY_HAVE_PC_FDC
107 config GENERIC_ISA_DMA
118 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
119 default DRAM_BASE if REMAP_VECTORS_TO_RAM
122 The base address of exception vectors.
124 source "init/Kconfig"
129 prompt "ARM system type"
130 default ARCH_VERSATILE
133 bool "Agilent AAEC-2000 based"
136 This enables support for systems based on the Agilent AAEC-2000
138 config ARCH_INTEGRATOR
139 bool "ARM Ltd. Integrator family"
143 Support for ARM's Integrator platform.
146 bool "ARM Ltd. RealView family"
150 This enables support for ARM Ltd RealView boards.
152 config ARCH_VERSATILE
153 bool "ARM Ltd. Versatile family"
158 This enables support for ARM Ltd Versatile board.
163 This enables support for systems based on the Atmel AT91RM9200
164 and AT91SAM9xxx processors.
167 bool "Cirrus CL-PS7500FE"
171 Support for the Cirrus Logic PS7500FE system-on-a-chip.
174 bool "Cirrus Logic CLPS711x/EP721x-based"
176 Support for Cirrus Logic 711x/721x based boards.
181 select FOOTBRIDGE_ADDIN
183 Support for Intel's EBSA285 companion chip.
189 This is an evaluation board for the StrongARM processor available
190 from Digital. It has limited hardware on-board, including an
191 Ethernet interface, two PCMCIA sockets, two serial ports and a
199 This enables support for the Cirrus EP93xx series of CPUs.
201 config ARCH_FOOTBRIDGE
205 Support for systems based on the DC21285 companion chip
206 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
209 bool "Hilscher NetX based"
212 This enables support for systems based on the Hilscher NetX Soc
215 bool "Hynix HMS720x-based"
218 This enables support for systems based on the Hynix HMS720x
223 Support for Motorola's i.MX family of processors (MX1, MXL).
231 Support for Intel's 80219 and IOP32X (XScale) family of
240 Support for Intel's IOP33X (XScale) family of processors.
246 Support for Intel's IOP13XX (XScale) family of processors.
253 Support for Intel's IXP4XX (XScale) family of processors.
256 bool "IXP2400/2800-based"
260 Support for Intel's IXP2400/2800 (XScale) family of processors.
267 Support for Intel's IXP23xx (XScale) family of processors.
273 Say Y here if you intend to run this kernel on a LinkUp Systems
274 L7200 Software Development Board which uses an ARM720T processor.
275 Information on this board can be obtained at:
277 <http://www.linkupsys.com/>
279 If you have any questions or comments about the Linux kernel port
280 to this board, send e-mail to <sjhill@cotw.com>.
283 bool "Philips Nexperia PNX4008 Mobile"
285 This enables support for Philips PNX4008 mobile platform.
292 Support for Intel's PXA2XX processor line.
299 select ARCH_MAY_HAVE_PC_FDC
302 On the Acorn Risc-PC, Linux can support the internal IDE disk and
303 CD-ROM interface, serial and parallel port, and the floppy drive.
308 select ARCH_DISCONTIGMEM_ENABLE
311 Support for StrongARM 11x0 based boards.
314 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442"
316 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
317 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
318 the Samsung SMDK2410 development board (and derivatives).
326 Support for the StrongARM based Digital DNARD machine, also known
327 as "Shark" (<http://www.shark-linux.de/shark.html>).
332 Say Y here for systems based on one of the Sharp LH7A40X
333 System on a Chip processors. These CPUs include an ARM922T
334 core with a wide array of integrated devices for
335 hand-held and low-power applications.
340 Support for TI's OMAP platform (OMAP1 and OMAP2).
344 source "arch/arm/mach-clps711x/Kconfig"
346 source "arch/arm/mach-ep93xx/Kconfig"
348 source "arch/arm/mach-footbridge/Kconfig"
350 source "arch/arm/mach-integrator/Kconfig"
352 source "arch/arm/mach-iop32x/Kconfig"
354 source "arch/arm/mach-iop33x/Kconfig"
356 source "arch/arm/mach-iop13xx/Kconfig"
358 source "arch/arm/mach-ixp4xx/Kconfig"
360 source "arch/arm/mach-ixp2000/Kconfig"
362 source "arch/arm/mach-ixp23xx/Kconfig"
364 source "arch/arm/mach-pxa/Kconfig"
366 source "arch/arm/mach-sa1100/Kconfig"
368 source "arch/arm/plat-omap/Kconfig"
370 source "arch/arm/mach-omap1/Kconfig"
372 source "arch/arm/mach-omap2/Kconfig"
374 source "arch/arm/mach-s3c2410/Kconfig"
376 source "arch/arm/mach-lh7a40x/Kconfig"
378 source "arch/arm/mach-imx/Kconfig"
380 source "arch/arm/mach-h720x/Kconfig"
382 source "arch/arm/mach-versatile/Kconfig"
384 source "arch/arm/mach-aaec2000/Kconfig"
386 source "arch/arm/mach-realview/Kconfig"
388 source "arch/arm/mach-at91rm9200/Kconfig"
390 source "arch/arm/mach-netx/Kconfig"
392 # Definitions to make life easier
399 source arch/arm/mm/Kconfig
402 bool "Enable iWMMXt support"
403 depends CPU_XSCALE || CPU_XSC3
406 Enable support for iWMMXt context switching at run time if
407 running on a CPU that supports it.
409 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
412 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
416 source "arch/arm/Kconfig-nommu"
421 source "arch/arm/common/Kconfig"
423 config FORCE_MAX_ZONEORDER
436 Find out whether you have ISA slots on your motherboard. ISA is the
437 name of a bus system, i.e. the way the CPU talks to the other stuff
438 inside your box. Other bus systems are PCI, EISA, MicroChannel
439 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
440 newer boards don't support it. If you have ISA, say Y, otherwise N.
442 # Select ISA DMA controller support
447 # Select ISA DMA interface
452 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
454 Find out whether you have a PCI motherboard. PCI is the name of a
455 bus system, i.e. the way the CPU talks to the other stuff inside
456 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
457 VESA. If you have PCI, say Y, otherwise N.
459 The PCI-HOWTO, available from
460 <http://www.tldp.org/docs.html#howto>, contains valuable
461 information about which PCI hardware does work under Linux and which
464 # Select the host bridge type
465 config PCI_HOST_VIA82C505
467 depends on PCI && ARCH_SHARK
470 source "drivers/pci/Kconfig"
472 source "drivers/pcmcia/Kconfig"
476 menu "Kernel Features"
479 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
480 depends on EXPERIMENTAL && REALVIEW_MPCORE
482 This enables support for systems with more than one CPU. If you have
483 a system with only one CPU, like most personal computers, say N. If
484 you have a system with more than one CPU, say Y.
486 If you say N here, the kernel will run on single and multiprocessor
487 machines, but will use only one CPU of a multiprocessor machine. If
488 you say Y here, the kernel will run on many, but not all, single
489 processor machines. On a single processor machine, the kernel will
490 run faster if you say N here.
492 See also the <file:Documentation/smp.txt>,
493 <file:Documentation/i386/IO-APIC.txt>,
494 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
495 <http://www.linuxdoc.org/docs.html#howto>.
497 If you don't know what to do here, say N.
500 int "Maximum number of CPUs (2-32)"
506 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
507 depends on SMP && HOTPLUG && EXPERIMENTAL
509 Say Y here to experiment with turning CPUs off and on. CPUs
510 can be controlled through /sys/devices/system/cpu.
513 bool "Use local timer interrupts"
514 depends on SMP && REALVIEW_MPCORE
517 Enable support for local timers on SMP platforms, rather then the
518 legacy IPI broadcast method. Local timers allows the system
519 accounting to be spread across the timer interval, preventing a
520 "thundering herd" at every timer tick.
523 bool "Preemptible Kernel (EXPERIMENTAL)"
524 depends on EXPERIMENTAL
526 This option reduces the latency of the kernel when reacting to
527 real-time or interactive events by allowing a low priority process to
528 be preempted even if it is in kernel mode executing a system call.
529 This allows applications to run more reliably even when the system is
532 Say Y here if you are building a kernel for a desktop, embedded
533 or real-time system. Say N if you are unsure.
536 bool "Dynamic tick timer"
538 Select this option if you want to disable continuous timer ticks
539 and have them programmed to occur as required. This option saves
540 power as the system can remain in idle state for longer.
542 By default dynamic tick is disabled during the boot, and can be
543 manually enabled with:
545 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
547 Alternatively, if you want dynamic tick automatically enabled
548 during boot, pass "dyntick=enable" via the kernel command string.
550 Please note that dynamic tick may affect the accuracy of
551 timekeeping on some platforms depending on the implementation.
552 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
553 to have accurate timekeeping with dynamic tick.
557 default 128 if ARCH_L7200
558 default 200 if ARCH_EBSA110 || ARCH_S3C2410
559 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
563 bool "Use the ARM EABI to compile the kernel"
565 This option allows for the kernel to be compiled using the latest
566 ARM ABI (aka EABI). This is only useful if you are using a user
567 space environment that is also compiled with EABI.
569 Since there are major incompatibilities between the legacy ABI and
570 EABI, especially with regard to structure member alignment, this
571 option also changes the kernel syscall calling convention to
572 disambiguate both ABIs and allow for backward compatibility support
573 (selected with CONFIG_OABI_COMPAT).
575 To use this you need GCC version 4.0.0 or later.
578 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
579 depends on AEABI && EXPERIMENTAL
582 This option preserves the old syscall interface along with the
583 new (ARM EABI) one. It also provides a compatibility layer to
584 intercept syscalls that have structure arguments which layout
585 in memory differs between the legacy ABI and the new ARM EABI
586 (only for non "thumb" binaries). This option adds a tiny
587 overhead to all syscalls and produces a slightly larger kernel.
588 If you know you'll be using only pure EABI user space then you
589 can say N here. If this option is not selected and you attempt
590 to execute a legacy ABI binary then the result will be
591 UNPREDICTABLE (in fact it can be predicted that it won't work
592 at all). If in doubt say Y.
594 config ARCH_DISCONTIGMEM_ENABLE
596 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
598 Say Y to support efficient handling of discontiguous physical memory,
599 for architectures which are either NUMA (Non-Uniform Memory Access)
600 or have huge holes in the physical address space for other reasons.
601 See <file:Documentation/vm/numa> for more.
605 default "4" if ARCH_LH7A40X
607 depends on NEED_MULTIPLE_NODES
612 bool "Timer and CPU usage LEDs"
613 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
614 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
615 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
616 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
617 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
618 ARCH_AT91 || MACH_TRIZEPS4
620 If you say Y here, the LEDs on your machine will be used
621 to provide useful information about your current system status.
623 If you are compiling a kernel for a NetWinder or EBSA-285, you will
624 be able to select which LEDs are active using the options below. If
625 you are compiling a kernel for the EBSA-110 or the LART however, the
626 red LED will simply flash regularly to indicate that the system is
627 still functional. It is safe to say Y here if you have a CATS
628 system, but the driver will do nothing.
631 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
632 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
634 default y if ARCH_EBSA110
636 If you say Y here, one of the system LEDs (the green one on the
637 NetWinder, the amber one on the EBSA285, or the red one on the LART)
638 will flash regularly to indicate that the system is still
639 operational. This is mainly useful to kernel hackers who are
640 debugging unstable kernels.
642 The LART uses the same LED for both Timer LED and CPU usage LED
643 functions. You may choose to use both, but the Timer LED function
644 will overrule the CPU usage LED.
647 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
648 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
651 If you say Y here, the red LED will be used to give a good real
652 time indication of CPU usage, by lighting whenever the idle task
653 is not currently executing.
655 The LART uses the same LED for both Timer LED and CPU usage LED
656 functions. You may choose to use both, but the Timer LED function
657 will overrule the CPU usage LED.
659 config ALIGNMENT_TRAP
661 depends on CPU_CP15_MMU
662 default y if !ARCH_EBSA110
664 ARM processors cannot fetch/store information which is not
665 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
666 address divisible by 4. On 32-bit ARM processors, these non-aligned
667 fetch/store instructions will be emulated in software if you say
668 here, which has a severe performance impact. This is necessary for
669 correct operation of some network protocols. With an IP-only
670 configuration it is safe to say N, otherwise say Y.
676 # Compressed boot loader in ROM. Yes, we really want to ask about
677 # TEXT and BSS so we preserve their values in the config files.
678 config ZBOOT_ROM_TEXT
679 hex "Compressed ROM boot loader base address"
682 The physical address at which the ROM-able zImage is to be
683 placed in the target. Platforms which normally make use of
684 ROM-able zImage formats normally set this to a suitable
685 value in their defconfig file.
687 If ZBOOT_ROM is not enabled, this has no effect.
690 hex "Compressed ROM boot loader BSS address"
693 The base address of an area of read/write memory in the target
694 for the ROM-able zImage which must be available while the
695 decompressor is running. It must be large enough to hold the
696 entire decompressed kernel plus an additional 128 KiB.
697 Platforms which normally make use of ROM-able zImage formats
698 normally set this to a suitable value in their defconfig file.
700 If ZBOOT_ROM is not enabled, this has no effect.
703 bool "Compressed boot loader in ROM/flash"
704 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
706 Say Y here if you intend to execute your compressed kernel image
707 (zImage) directly from ROM or flash. If unsure, say N.
710 string "Default kernel command string"
713 On some architectures (EBSA110 and CATS), there is currently no way
714 for the boot loader to pass arguments to the kernel. For these
715 architectures, you should supply some command-line options at build
716 time by entering them here. As a minimum, you should specify the
717 memory size and the root device (e.g., mem=64M root=/dev/nfs).
720 bool "Kernel Execute-In-Place from ROM"
721 depends on !ZBOOT_ROM
723 Execute-In-Place allows the kernel to run from non-volatile storage
724 directly addressable by the CPU, such as NOR flash. This saves RAM
725 space since the text section of the kernel is not loaded from flash
726 to RAM. Read-write sections, such as the data section and stack,
727 are still copied to RAM. The XIP kernel is not compressed since
728 it has to run directly from flash, so it will take more space to
729 store it. The flash address used to link the kernel object files,
730 and for storing it, is configuration dependent. Therefore, if you
731 say Y here, you must know the proper physical address where to
732 store the kernel image depending on your own flash memory usage.
734 Also note that the make target becomes "make xipImage" rather than
735 "make zImage" or "make Image". The final kernel binary to put in
736 ROM memory will be arch/arm/boot/xipImage.
741 hex "XIP Kernel Physical Location"
742 depends on XIP_KERNEL
745 This is the physical address in your flash memory the kernel will
746 be linked for and stored to. This address is dependent on your
751 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
753 menu "CPU Frequency scaling"
755 source "drivers/cpufreq/Kconfig"
757 config CPU_FREQ_SA1100
759 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
762 config CPU_FREQ_SA1110
764 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
767 config CPU_FREQ_INTEGRATOR
768 tristate "CPUfreq driver for ARM Integrator CPUs"
769 depends on ARCH_INTEGRATOR && CPU_FREQ
772 This enables the CPUfreq driver for ARM Integrator CPUs.
774 For details, take a look at <file:Documentation/cpu-freq>.
779 tristate "CPUfreq driver for i.MX CPUs"
780 depends on ARCH_IMX && CPU_FREQ
783 This enables the CPUfreq driver for i.MX CPUs.
791 menu "Floating point emulation"
793 comment "At least one emulation must be selected"
796 bool "NWFPE math emulation"
797 depends on !AEABI || OABI_COMPAT
799 Say Y to include the NWFPE floating point emulator in the kernel.
800 This is necessary to run most binaries. Linux does not currently
801 support floating point hardware so you need to say Y here even if
802 your machine has an FPA or floating point co-processor podule.
804 You may say N here if you are going to load the Acorn FPEmulator
808 bool "Support extended precision"
811 Say Y to include 80-bit support in the kernel floating-point
812 emulator. Otherwise, only 32 and 64-bit support is compiled in.
813 Note that gcc does not generate 80-bit operations by default,
814 so in most cases this option only enlarges the size of the
815 floating point emulator without any good reason.
817 You almost surely want to say N here.
820 bool "FastFPE math emulation (EXPERIMENTAL)"
821 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
823 Say Y here to include the FAST floating point emulator in the kernel.
824 This is an experimental much faster emulator which now also has full
825 precision for the mantissa. It does not support any exceptions.
826 It is very simple, and approximately 3-6 times faster than NWFPE.
828 It should be sufficient for most programs. It may be not suitable
829 for scientific calculations, but you have to check this for yourself.
830 If you do not feel you need a faster FP emulation you should better
834 bool "VFP-format floating point maths"
835 depends on CPU_V6 || CPU_ARM926T
837 Say Y to include VFP support code in the kernel. This is needed
838 if your hardware includes a VFP unit.
840 Please see <file:Documentation/arm/VFP/release-notes.txt> for
841 release notes and additional status information.
843 Say N if your target does not have VFP hardware.
847 menu "Userspace binary formats"
849 source "fs/Kconfig.binfmt"
852 tristate "RISC OS personality"
855 Say Y here to include the kernel code necessary if you want to run
856 Acorn RISC OS/Arthur binaries under Linux. This code is still very
857 experimental; if this sounds frightening, say N and sleep in peace.
858 You can also say M here to compile this support as a module (which
859 will be called arthur).
863 menu "Power management options"
865 source "kernel/power/Kconfig"
871 menu "Device Drivers"
873 source "drivers/base/Kconfig"
875 source "drivers/connector/Kconfig"
877 if ALIGNMENT_TRAP || !CPU_CP15_MMU
878 source "drivers/mtd/Kconfig"
881 source "drivers/parport/Kconfig"
883 source "drivers/pnp/Kconfig"
885 source "drivers/block/Kconfig"
887 source "drivers/acorn/block/Kconfig"
889 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
890 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
891 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
893 source "drivers/ide/Kconfig"
896 source "drivers/scsi/Kconfig"
898 source "drivers/ata/Kconfig"
900 source "drivers/md/Kconfig"
902 source "drivers/message/fusion/Kconfig"
904 source "drivers/ieee1394/Kconfig"
906 source "drivers/message/i2o/Kconfig"
908 source "drivers/net/Kconfig"
910 source "drivers/isdn/Kconfig"
912 # input before char - char/joystick depends on it. As does USB.
914 source "drivers/input/Kconfig"
916 source "drivers/char/Kconfig"
918 source "drivers/i2c/Kconfig"
920 source "drivers/spi/Kconfig"
922 source "drivers/w1/Kconfig"
924 source "drivers/hwmon/Kconfig"
926 #source "drivers/l3/Kconfig"
928 source "drivers/misc/Kconfig"
930 source "drivers/mfd/Kconfig"
932 source "drivers/leds/Kconfig"
934 source "drivers/media/Kconfig"
936 source "drivers/video/Kconfig"
938 source "sound/Kconfig"
940 source "drivers/hid/Kconfig"
942 source "drivers/usb/Kconfig"
944 source "drivers/mmc/Kconfig"
946 source "drivers/rtc/Kconfig"
952 source "arch/arm/oprofile/Kconfig"
954 source "arch/arm/Kconfig.debug"
956 source "security/Kconfig"
958 source "crypto/Kconfig"