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
103 config GENERIC_ISA_DMA
114 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
115 default DRAM_BASE if REMAP_VECTORS_TO_RAM
118 The base address of exception vectors.
120 source "init/Kconfig"
125 prompt "ARM system type"
126 default ARCH_VERSATILE
129 bool "Agilent AAEC-2000 based"
132 This enables support for systems based on the Agilent AAEC-2000
134 config ARCH_INTEGRATOR
135 bool "ARM Ltd. Integrator family"
139 Support for ARM's Integrator platform.
142 bool "ARM Ltd. RealView family"
146 This enables support for ARM Ltd RealView boards.
148 config ARCH_VERSATILE
149 bool "ARM Ltd. Versatile family"
154 This enables support for ARM Ltd Versatile board.
159 This enables support for systems based on the Atmel AT91RM9200
160 and AT91SAM9xxx processors.
163 bool "Cirrus CL-PS7500FE"
167 Support for the Cirrus Logic PS7500FE system-on-a-chip.
170 bool "Cirrus Logic CLPS711x/EP721x-based"
172 Support for Cirrus Logic 711x/721x based boards.
177 select FOOTBRIDGE_ADDIN
179 Support for Intel's EBSA285 companion chip.
185 This is an evaluation board for the StrongARM processor available
186 from Digital. It has limited hardware on-board, including an
187 Ethernet interface, two PCMCIA sockets, two serial ports and a
195 This enables support for the Cirrus EP93xx series of CPUs.
197 config ARCH_FOOTBRIDGE
201 Support for systems based on the DC21285 companion chip
202 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
205 bool "Hilscher NetX based"
208 This enables support for systems based on the Hilscher NetX Soc
211 bool "Hynix HMS720x-based"
214 This enables support for systems based on the Hynix HMS720x
219 Support for Motorola's i.MX family of processors (MX1, MXL).
227 Support for Intel's 80219 and IOP32X (XScale) family of
236 Support for Intel's IOP33X (XScale) family of processors.
242 Support for Intel's IOP13XX (XScale) family of processors.
249 Support for Intel's IXP4XX (XScale) family of processors.
252 bool "IXP2400/2800-based"
256 Support for Intel's IXP2400/2800 (XScale) family of processors.
263 Support for Intel's IXP23xx (XScale) family of processors.
269 Say Y here if you intend to run this kernel on a LinkUp Systems
270 L7200 Software Development Board which uses an ARM720T processor.
271 Information on this board can be obtained at:
273 <http://www.linkupsys.com/>
275 If you have any questions or comments about the Linux kernel port
276 to this board, send e-mail to <sjhill@cotw.com>.
279 bool "Philips Nexperia PNX4008 Mobile"
281 This enables support for Philips PNX4008 mobile platform.
288 Support for Intel's PXA2XX processor line.
295 select ARCH_MAY_HAVE_PC_FDC
298 On the Acorn Risc-PC, Linux can support the internal IDE disk and
299 CD-ROM interface, serial and parallel port, and the floppy drive.
304 select ARCH_DISCONTIGMEM_ENABLE
307 Support for StrongARM 11x0 based boards.
310 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442"
312 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
313 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
314 the Samsung SMDK2410 development board (and derivatives).
322 Support for the StrongARM based Digital DNARD machine, also known
323 as "Shark" (<http://www.shark-linux.de/shark.html>).
328 Say Y here for systems based on one of the Sharp LH7A40X
329 System on a Chip processors. These CPUs include an ARM922T
330 core with a wide array of integrated devices for
331 hand-held and low-power applications.
336 Support for TI's OMAP platform (OMAP1 and OMAP2).
340 source "arch/arm/mach-clps711x/Kconfig"
342 source "arch/arm/mach-ep93xx/Kconfig"
344 source "arch/arm/mach-footbridge/Kconfig"
346 source "arch/arm/mach-integrator/Kconfig"
348 source "arch/arm/mach-iop32x/Kconfig"
350 source "arch/arm/mach-iop33x/Kconfig"
352 source "arch/arm/mach-iop13xx/Kconfig"
354 source "arch/arm/mach-ixp4xx/Kconfig"
356 source "arch/arm/mach-ixp2000/Kconfig"
358 source "arch/arm/mach-ixp23xx/Kconfig"
360 source "arch/arm/mach-pxa/Kconfig"
362 source "arch/arm/mach-sa1100/Kconfig"
364 source "arch/arm/plat-omap/Kconfig"
366 source "arch/arm/mach-omap1/Kconfig"
368 source "arch/arm/mach-omap2/Kconfig"
370 source "arch/arm/mach-s3c2410/Kconfig"
372 source "arch/arm/mach-lh7a40x/Kconfig"
374 source "arch/arm/mach-imx/Kconfig"
376 source "arch/arm/mach-h720x/Kconfig"
378 source "arch/arm/mach-versatile/Kconfig"
380 source "arch/arm/mach-aaec2000/Kconfig"
382 source "arch/arm/mach-realview/Kconfig"
384 source "arch/arm/mach-at91rm9200/Kconfig"
386 source "arch/arm/mach-netx/Kconfig"
388 # Definitions to make life easier
395 source arch/arm/mm/Kconfig
398 bool "Enable iWMMXt support"
399 depends CPU_XSCALE || CPU_XSC3
402 Enable support for iWMMXt context switching at run time if
403 running on a CPU that supports it.
405 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
408 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
412 source "arch/arm/Kconfig-nommu"
417 source "arch/arm/common/Kconfig"
419 config FORCE_MAX_ZONEORDER
432 Find out whether you have ISA slots on your motherboard. ISA is the
433 name of a bus system, i.e. the way the CPU talks to the other stuff
434 inside your box. Other bus systems are PCI, EISA, MicroChannel
435 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
436 newer boards don't support it. If you have ISA, say Y, otherwise N.
438 # Select ISA DMA controller support
443 # Select ISA DMA interface
448 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
450 Find out whether you have a PCI motherboard. PCI is the name of a
451 bus system, i.e. the way the CPU talks to the other stuff inside
452 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
453 VESA. If you have PCI, say Y, otherwise N.
455 The PCI-HOWTO, available from
456 <http://www.tldp.org/docs.html#howto>, contains valuable
457 information about which PCI hardware does work under Linux and which
460 # Select the host bridge type
461 config PCI_HOST_VIA82C505
463 depends on PCI && ARCH_SHARK
466 source "drivers/pci/Kconfig"
468 source "drivers/pcmcia/Kconfig"
472 menu "Kernel Features"
475 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
476 depends on EXPERIMENTAL && REALVIEW_MPCORE
478 This enables support for systems with more than one CPU. If you have
479 a system with only one CPU, like most personal computers, say N. If
480 you have a system with more than one CPU, say Y.
482 If you say N here, the kernel will run on single and multiprocessor
483 machines, but will use only one CPU of a multiprocessor machine. If
484 you say Y here, the kernel will run on many, but not all, single
485 processor machines. On a single processor machine, the kernel will
486 run faster if you say N here.
488 See also the <file:Documentation/smp.txt>,
489 <file:Documentation/i386/IO-APIC.txt>,
490 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
491 <http://www.linuxdoc.org/docs.html#howto>.
493 If you don't know what to do here, say N.
496 int "Maximum number of CPUs (2-32)"
502 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
503 depends on SMP && HOTPLUG && EXPERIMENTAL
505 Say Y here to experiment with turning CPUs off and on. CPUs
506 can be controlled through /sys/devices/system/cpu.
509 bool "Use local timer interrupts"
510 depends on SMP && REALVIEW_MPCORE
513 Enable support for local timers on SMP platforms, rather then the
514 legacy IPI broadcast method. Local timers allows the system
515 accounting to be spread across the timer interval, preventing a
516 "thundering herd" at every timer tick.
519 bool "Preemptible Kernel (EXPERIMENTAL)"
520 depends on EXPERIMENTAL
522 This option reduces the latency of the kernel when reacting to
523 real-time or interactive events by allowing a low priority process to
524 be preempted even if it is in kernel mode executing a system call.
525 This allows applications to run more reliably even when the system is
528 Say Y here if you are building a kernel for a desktop, embedded
529 or real-time system. Say N if you are unsure.
532 bool "Dynamic tick timer"
534 Select this option if you want to disable continuous timer ticks
535 and have them programmed to occur as required. This option saves
536 power as the system can remain in idle state for longer.
538 By default dynamic tick is disabled during the boot, and can be
539 manually enabled with:
541 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
543 Alternatively, if you want dynamic tick automatically enabled
544 during boot, pass "dyntick=enable" via the kernel command string.
546 Please note that dynamic tick may affect the accuracy of
547 timekeeping on some platforms depending on the implementation.
548 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
549 to have accurate timekeeping with dynamic tick.
553 default 128 if ARCH_L7200
554 default 200 if ARCH_EBSA110 || ARCH_S3C2410
555 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
559 bool "Use the ARM EABI to compile the kernel"
561 This option allows for the kernel to be compiled using the latest
562 ARM ABI (aka EABI). This is only useful if you are using a user
563 space environment that is also compiled with EABI.
565 Since there are major incompatibilities between the legacy ABI and
566 EABI, especially with regard to structure member alignment, this
567 option also changes the kernel syscall calling convention to
568 disambiguate both ABIs and allow for backward compatibility support
569 (selected with CONFIG_OABI_COMPAT).
571 To use this you need GCC version 4.0.0 or later.
574 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
575 depends on AEABI && EXPERIMENTAL
578 This option preserves the old syscall interface along with the
579 new (ARM EABI) one. It also provides a compatibility layer to
580 intercept syscalls that have structure arguments which layout
581 in memory differs between the legacy ABI and the new ARM EABI
582 (only for non "thumb" binaries). This option adds a tiny
583 overhead to all syscalls and produces a slightly larger kernel.
584 If you know you'll be using only pure EABI user space then you
585 can say N here. If this option is not selected and you attempt
586 to execute a legacy ABI binary then the result will be
587 UNPREDICTABLE (in fact it can be predicted that it won't work
588 at all). If in doubt say Y.
590 config ARCH_DISCONTIGMEM_ENABLE
592 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
594 Say Y to support efficient handling of discontiguous physical memory,
595 for architectures which are either NUMA (Non-Uniform Memory Access)
596 or have huge holes in the physical address space for other reasons.
597 See <file:Documentation/vm/numa> for more.
601 default "4" if ARCH_LH7A40X
603 depends on NEED_MULTIPLE_NODES
608 bool "Timer and CPU usage LEDs"
609 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
610 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
611 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
612 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
613 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
614 ARCH_AT91 || MACH_TRIZEPS4
616 If you say Y here, the LEDs on your machine will be used
617 to provide useful information about your current system status.
619 If you are compiling a kernel for a NetWinder or EBSA-285, you will
620 be able to select which LEDs are active using the options below. If
621 you are compiling a kernel for the EBSA-110 or the LART however, the
622 red LED will simply flash regularly to indicate that the system is
623 still functional. It is safe to say Y here if you have a CATS
624 system, but the driver will do nothing.
627 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
628 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
630 default y if ARCH_EBSA110
632 If you say Y here, one of the system LEDs (the green one on the
633 NetWinder, the amber one on the EBSA285, or the red one on the LART)
634 will flash regularly to indicate that the system is still
635 operational. This is mainly useful to kernel hackers who are
636 debugging unstable kernels.
638 The LART uses the same LED for both Timer LED and CPU usage LED
639 functions. You may choose to use both, but the Timer LED function
640 will overrule the CPU usage LED.
643 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
644 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
647 If you say Y here, the red LED will be used to give a good real
648 time indication of CPU usage, by lighting whenever the idle task
649 is not currently executing.
651 The LART uses the same LED for both Timer LED and CPU usage LED
652 functions. You may choose to use both, but the Timer LED function
653 will overrule the CPU usage LED.
655 config ALIGNMENT_TRAP
657 depends on CPU_CP15_MMU
658 default y if !ARCH_EBSA110
660 ARM processors cannot fetch/store information which is not
661 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
662 address divisible by 4. On 32-bit ARM processors, these non-aligned
663 fetch/store instructions will be emulated in software if you say
664 here, which has a severe performance impact. This is necessary for
665 correct operation of some network protocols. With an IP-only
666 configuration it is safe to say N, otherwise say Y.
672 # Compressed boot loader in ROM. Yes, we really want to ask about
673 # TEXT and BSS so we preserve their values in the config files.
674 config ZBOOT_ROM_TEXT
675 hex "Compressed ROM boot loader base address"
678 The physical address at which the ROM-able zImage is to be
679 placed in the target. Platforms which normally make use of
680 ROM-able zImage formats normally set this to a suitable
681 value in their defconfig file.
683 If ZBOOT_ROM is not enabled, this has no effect.
686 hex "Compressed ROM boot loader BSS address"
689 The base address of an area of read/write memory in the target
690 for the ROM-able zImage which must be available while the
691 decompressor is running. It must be large enough to hold the
692 entire decompressed kernel plus an additional 128 KiB.
693 Platforms which normally make use of ROM-able zImage formats
694 normally set this to a suitable value in their defconfig file.
696 If ZBOOT_ROM is not enabled, this has no effect.
699 bool "Compressed boot loader in ROM/flash"
700 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
702 Say Y here if you intend to execute your compressed kernel image
703 (zImage) directly from ROM or flash. If unsure, say N.
706 string "Default kernel command string"
709 On some architectures (EBSA110 and CATS), there is currently no way
710 for the boot loader to pass arguments to the kernel. For these
711 architectures, you should supply some command-line options at build
712 time by entering them here. As a minimum, you should specify the
713 memory size and the root device (e.g., mem=64M root=/dev/nfs).
716 bool "Kernel Execute-In-Place from ROM"
717 depends on !ZBOOT_ROM
719 Execute-In-Place allows the kernel to run from non-volatile storage
720 directly addressable by the CPU, such as NOR flash. This saves RAM
721 space since the text section of the kernel is not loaded from flash
722 to RAM. Read-write sections, such as the data section and stack,
723 are still copied to RAM. The XIP kernel is not compressed since
724 it has to run directly from flash, so it will take more space to
725 store it. The flash address used to link the kernel object files,
726 and for storing it, is configuration dependent. Therefore, if you
727 say Y here, you must know the proper physical address where to
728 store the kernel image depending on your own flash memory usage.
730 Also note that the make target becomes "make xipImage" rather than
731 "make zImage" or "make Image". The final kernel binary to put in
732 ROM memory will be arch/arm/boot/xipImage.
737 hex "XIP Kernel Physical Location"
738 depends on XIP_KERNEL
741 This is the physical address in your flash memory the kernel will
742 be linked for and stored to. This address is dependent on your
747 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
749 menu "CPU Frequency scaling"
751 source "drivers/cpufreq/Kconfig"
753 config CPU_FREQ_SA1100
755 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
758 config CPU_FREQ_SA1110
760 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
763 config CPU_FREQ_INTEGRATOR
764 tristate "CPUfreq driver for ARM Integrator CPUs"
765 depends on ARCH_INTEGRATOR && CPU_FREQ
768 This enables the CPUfreq driver for ARM Integrator CPUs.
770 For details, take a look at <file:Documentation/cpu-freq>.
775 tristate "CPUfreq driver for i.MX CPUs"
776 depends on ARCH_IMX && CPU_FREQ
779 This enables the CPUfreq driver for i.MX CPUs.
787 menu "Floating point emulation"
789 comment "At least one emulation must be selected"
792 bool "NWFPE math emulation"
793 depends on !AEABI || OABI_COMPAT
795 Say Y to include the NWFPE floating point emulator in the kernel.
796 This is necessary to run most binaries. Linux does not currently
797 support floating point hardware so you need to say Y here even if
798 your machine has an FPA or floating point co-processor podule.
800 You may say N here if you are going to load the Acorn FPEmulator
804 bool "Support extended precision"
807 Say Y to include 80-bit support in the kernel floating-point
808 emulator. Otherwise, only 32 and 64-bit support is compiled in.
809 Note that gcc does not generate 80-bit operations by default,
810 so in most cases this option only enlarges the size of the
811 floating point emulator without any good reason.
813 You almost surely want to say N here.
816 bool "FastFPE math emulation (EXPERIMENTAL)"
817 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
819 Say Y here to include the FAST floating point emulator in the kernel.
820 This is an experimental much faster emulator which now also has full
821 precision for the mantissa. It does not support any exceptions.
822 It is very simple, and approximately 3-6 times faster than NWFPE.
824 It should be sufficient for most programs. It may be not suitable
825 for scientific calculations, but you have to check this for yourself.
826 If you do not feel you need a faster FP emulation you should better
830 bool "VFP-format floating point maths"
831 depends on CPU_V6 || CPU_ARM926T
833 Say Y to include VFP support code in the kernel. This is needed
834 if your hardware includes a VFP unit.
836 Please see <file:Documentation/arm/VFP/release-notes.txt> for
837 release notes and additional status information.
839 Say N if your target does not have VFP hardware.
843 menu "Userspace binary formats"
845 source "fs/Kconfig.binfmt"
848 tristate "RISC OS personality"
851 Say Y here to include the kernel code necessary if you want to run
852 Acorn RISC OS/Arthur binaries under Linux. This code is still very
853 experimental; if this sounds frightening, say N and sleep in peace.
854 You can also say M here to compile this support as a module (which
855 will be called arthur).
859 menu "Power management options"
861 source "kernel/power/Kconfig"
867 menu "Device Drivers"
869 source "drivers/base/Kconfig"
871 source "drivers/connector/Kconfig"
873 if ALIGNMENT_TRAP || !CPU_CP15_MMU
874 source "drivers/mtd/Kconfig"
877 source "drivers/parport/Kconfig"
879 source "drivers/pnp/Kconfig"
881 source "drivers/block/Kconfig"
883 source "drivers/acorn/block/Kconfig"
885 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
886 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
887 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
889 source "drivers/ide/Kconfig"
892 source "drivers/scsi/Kconfig"
894 source "drivers/ata/Kconfig"
896 source "drivers/md/Kconfig"
898 source "drivers/message/fusion/Kconfig"
900 source "drivers/ieee1394/Kconfig"
902 source "drivers/message/i2o/Kconfig"
904 source "drivers/net/Kconfig"
906 source "drivers/isdn/Kconfig"
908 # input before char - char/joystick depends on it. As does USB.
910 source "drivers/input/Kconfig"
912 source "drivers/char/Kconfig"
914 source "drivers/i2c/Kconfig"
916 source "drivers/spi/Kconfig"
918 source "drivers/w1/Kconfig"
920 source "drivers/hwmon/Kconfig"
922 #source "drivers/l3/Kconfig"
924 source "drivers/misc/Kconfig"
926 source "drivers/mfd/Kconfig"
928 source "drivers/leds/Kconfig"
930 source "drivers/media/Kconfig"
932 source "drivers/video/Kconfig"
934 source "sound/Kconfig"
936 source "drivers/hid/Kconfig"
938 source "drivers/usb/Kconfig"
940 source "drivers/mmc/Kconfig"
942 source "drivers/rtc/Kconfig"
948 source "arch/arm/oprofile/Kconfig"
950 source "arch/arm/Kconfig.debug"
952 source "security/Kconfig"
954 source "crypto/Kconfig"