2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "Linux Kernel Configuration"
13 The ARM series is a line of low-power-consumption RISC chip designs
14 licensed by ARM Ltd and targeted at embedded applications and
15 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
16 manufactured, but legacy ARM-based PC hardware remains popular in
17 Europe. There is an ARM Linux project with a web page at
18 <http://www.arm.linux.org.uk/>.
27 The Extended Industry Standard Architecture (EISA) bus was
28 developed as an open alternative to the IBM MicroChannel bus.
30 The EISA bus provided some of the features of the IBM MicroChannel
31 bus while maintaining backward compatibility with cards made for
32 the older ISA bus. The EISA bus saw limited use between 1988 and
33 1995 when it was made obsolete by the PCI bus.
35 Say Y here if you are building a kernel for an EISA-based machine.
45 MicroChannel Architecture is found in some IBM PS/2 machines and
46 laptops. It is a bus system similar to PCI or ISA. See
47 <file:Documentation/mca.txt> (and especially the web page given
48 there) before attempting to build an MCA bus kernel.
50 config RWSEM_GENERIC_SPINLOCK
54 config RWSEM_XCHGADD_ALGORITHM
57 config GENERIC_HWEIGHT
61 config GENERIC_CALIBRATE_DELAY
65 config GENERIC_BUST_SPINLOCK
68 config ARCH_MAY_HAVE_PC_FDC
71 config GENERIC_ISA_DMA
82 default 0xffff0000 if MMU
83 default DRAM_BASE if REMAP_VECTORS_TO_RAM
86 The base address of exception vectors.
93 prompt "ARM system type"
94 default ARCH_VERSATILE
97 bool "Agilent AAEC-2000 based"
100 This enables support for systems based on the Agilent AAEC-2000
102 config ARCH_INTEGRATOR
103 bool "ARM Ltd. Integrator family"
107 Support for ARM's Integrator platform.
110 bool "ARM Ltd. RealView family"
114 This enables support for ARM Ltd RealView boards.
116 config ARCH_VERSATILE
117 bool "ARM Ltd. Versatile family"
122 This enables support for ARM Ltd Versatile board.
124 config ARCH_AT91RM9200
125 bool "Atmel AT91RM9200"
127 Say Y here if you intend to run this kernel on an Atmel
128 AT91RM9200-based board.
131 bool "Cirrus CL-PS7500FE"
135 Support for the Cirrus Logic PS7500FE system-on-a-chip.
138 bool "Cirrus Logic CLPS711x/EP721x-based"
140 Support for Cirrus Logic 711x/721x based boards.
145 select FOOTBRIDGE_ADDIN
147 Support for Intel's EBSA285 companion chip.
153 This is an evaluation board for the StrongARM processor available
154 from Digital. It has limited hardware on-board, including an
155 Ethernet interface, two PCMCIA sockets, two serial ports and a
163 This enables support for the Cirrus EP93xx series of CPUs.
165 config ARCH_FOOTBRIDGE
169 Support for systems based on the DC21285 companion chip
170 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
173 bool "Hilscher NetX based"
176 This enables support for systems based on the Hilscher NetX Soc
179 bool "Hynix HMS720x-based"
182 This enables support for systems based on the Hynix HMS720x
187 Support for Motorola's i.MX family of processors (MX1, MXL).
193 Support for Intel's IOP3XX (XScale) family of processors.
198 Support for Intel's IXP4XX (XScale) family of processors.
201 bool "IXP2400/2800-based"
204 Support for Intel's IXP2400/2800 (XScale) family of processors.
210 Support for Intel's IXP23xx (XScale) family of processors.
216 Say Y here if you intend to run this kernel on a LinkUp Systems
217 L7200 Software Development Board which uses an ARM720T processor.
218 Information on this board can be obtained at:
220 <http://www.linkupsys.com/>
222 If you have any questions or comments about the Linux kernel port
223 to this board, send e-mail to <sjhill@cotw.com>.
226 bool "Philips Nexperia PNX4008 Mobile"
228 This enables support for Philips PNX4008 mobile platform.
234 Support for Intel's PXA2XX processor line.
241 select ARCH_MAY_HAVE_PC_FDC
244 On the Acorn Risc-PC, Linux can support the internal IDE disk and
245 CD-ROM interface, serial and parallel port, and the floppy drive.
250 select ARCH_DISCONTIGMEM_ENABLE
253 Support for StrongARM 11x0 based boards.
256 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442"
258 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
259 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
260 the Samsung SMDK2410 development board (and derivatives).
268 Support for the StrongARM based Digital DNARD machine, also known
269 as "Shark" (<http://www.shark-linux.de/shark.html>).
274 Say Y here for systems based on one of the Sharp LH7A40X
275 System on a Chip processors. These CPUs include an ARM922T
276 core with a wide array of integrated devices for
277 hand-held and low-power applications.
282 Support for TI's OMAP platform (OMAP1 and OMAP2).
286 source "arch/arm/mach-clps711x/Kconfig"
288 source "arch/arm/mach-ep93xx/Kconfig"
290 source "arch/arm/mach-footbridge/Kconfig"
292 source "arch/arm/mach-integrator/Kconfig"
294 source "arch/arm/mach-iop3xx/Kconfig"
296 source "arch/arm/mach-ixp4xx/Kconfig"
298 source "arch/arm/mach-ixp2000/Kconfig"
300 source "arch/arm/mach-ixp23xx/Kconfig"
302 source "arch/arm/mach-pxa/Kconfig"
304 source "arch/arm/mach-sa1100/Kconfig"
306 source "arch/arm/plat-omap/Kconfig"
308 source "arch/arm/mach-omap1/Kconfig"
310 source "arch/arm/mach-omap2/Kconfig"
312 source "arch/arm/mach-s3c2410/Kconfig"
314 source "arch/arm/mach-lh7a40x/Kconfig"
316 source "arch/arm/mach-imx/Kconfig"
318 source "arch/arm/mach-h720x/Kconfig"
320 source "arch/arm/mach-versatile/Kconfig"
322 source "arch/arm/mach-aaec2000/Kconfig"
324 source "arch/arm/mach-realview/Kconfig"
326 source "arch/arm/mach-at91rm9200/Kconfig"
328 source "arch/arm/mach-netx/Kconfig"
330 # Definitions to make life easier
334 source arch/arm/mm/Kconfig
336 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
339 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
344 source "arch/arm/common/Kconfig"
346 config FORCE_MAX_ZONEORDER
359 Find out whether you have ISA slots on your motherboard. ISA is the
360 name of a bus system, i.e. the way the CPU talks to the other stuff
361 inside your box. Other bus systems are PCI, EISA, MicroChannel
362 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
363 newer boards don't support it. If you have ISA, say Y, otherwise N.
365 # Select ISA DMA controller support
370 # Select ISA DMA interface
375 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
377 Find out whether you have a PCI motherboard. PCI is the name of a
378 bus system, i.e. the way the CPU talks to the other stuff inside
379 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
380 VESA. If you have PCI, say Y, otherwise N.
382 The PCI-HOWTO, available from
383 <http://www.tldp.org/docs.html#howto>, contains valuable
384 information about which PCI hardware does work under Linux and which
387 # Select the host bridge type
388 config PCI_HOST_VIA82C505
390 depends on PCI && ARCH_SHARK
393 source "drivers/pci/Kconfig"
395 source "drivers/pcmcia/Kconfig"
399 menu "Kernel Features"
402 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
403 depends on EXPERIMENTAL && REALVIEW_MPCORE
405 This enables support for systems with more than one CPU. If you have
406 a system with only one CPU, like most personal computers, say N. If
407 you have a system with more than one CPU, say Y.
409 If you say N here, the kernel will run on single and multiprocessor
410 machines, but will use only one CPU of a multiprocessor machine. If
411 you say Y here, the kernel will run on many, but not all, single
412 processor machines. On a single processor machine, the kernel will
413 run faster if you say N here.
415 See also the <file:Documentation/smp.txt>,
416 <file:Documentation/i386/IO-APIC.txt>,
417 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
418 <http://www.linuxdoc.org/docs.html#howto>.
420 If you don't know what to do here, say N.
423 int "Maximum number of CPUs (2-32)"
429 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
430 depends on SMP && HOTPLUG && EXPERIMENTAL
432 Say Y here to experiment with turning CPUs off and on. CPUs
433 can be controlled through /sys/devices/system/cpu.
436 bool "Use local timer interrupts"
437 depends on SMP && REALVIEW_MPCORE
440 Enable support for local timers on SMP platforms, rather then the
441 legacy IPI broadcast method. Local timers allows the system
442 accounting to be spread across the timer interval, preventing a
443 "thundering herd" at every timer tick.
446 bool "Preemptible Kernel (EXPERIMENTAL)"
447 depends on EXPERIMENTAL
449 This option reduces the latency of the kernel when reacting to
450 real-time or interactive events by allowing a low priority process to
451 be preempted even if it is in kernel mode executing a system call.
452 This allows applications to run more reliably even when the system is
455 Say Y here if you are building a kernel for a desktop, embedded
456 or real-time system. Say N if you are unsure.
459 bool "Dynamic tick timer"
461 Select this option if you want to disable continuous timer ticks
462 and have them programmed to occur as required. This option saves
463 power as the system can remain in idle state for longer.
465 By default dynamic tick is disabled during the boot, and can be
466 manually enabled with:
468 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
470 Alternatively, if you want dynamic tick automatically enabled
471 during boot, pass "dyntick=enable" via the kernel command string.
473 Please note that dynamic tick may affect the accuracy of
474 timekeeping on some platforms depending on the implementation.
475 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
476 to have accurate timekeeping with dynamic tick.
480 default 128 if ARCH_L7200
481 default 200 if ARCH_EBSA110 || ARCH_S3C2410
482 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
486 bool "Use the ARM EABI to compile the kernel"
488 This option allows for the kernel to be compiled using the latest
489 ARM ABI (aka EABI). This is only useful if you are using a user
490 space environment that is also compiled with EABI.
492 Since there are major incompatibilities between the legacy ABI and
493 EABI, especially with regard to structure member alignment, this
494 option also changes the kernel syscall calling convention to
495 disambiguate both ABIs and allow for backward compatibility support
496 (selected with CONFIG_OABI_COMPAT).
498 To use this you need GCC version 4.0.0 or later.
501 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
502 depends on AEABI && EXPERIMENTAL
505 This option preserves the old syscall interface along with the
506 new (ARM EABI) one. It also provides a compatibility layer to
507 intercept syscalls that have structure arguments which layout
508 in memory differs between the legacy ABI and the new ARM EABI
509 (only for non "thumb" binaries). This option adds a tiny
510 overhead to all syscalls and produces a slightly larger kernel.
511 If you know you'll be using only pure EABI user space then you
512 can say N here. If this option is not selected and you attempt
513 to execute a legacy ABI binary then the result will be
514 UNPREDICTABLE (in fact it can be predicted that it won't work
515 at all). If in doubt say Y.
517 config ARCH_DISCONTIGMEM_ENABLE
519 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
521 Say Y to support efficient handling of discontiguous physical memory,
522 for architectures which are either NUMA (Non-Uniform Memory Access)
523 or have huge holes in the physical address space for other reasons.
524 See <file:Documentation/vm/numa> for more.
528 default "4" if ARCH_LH7A40X
530 depends on NEED_MULTIPLE_NODES
535 bool "Timer and CPU usage LEDs"
536 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
537 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
538 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
539 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
540 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
543 If you say Y here, the LEDs on your machine will be used
544 to provide useful information about your current system status.
546 If you are compiling a kernel for a NetWinder or EBSA-285, you will
547 be able to select which LEDs are active using the options below. If
548 you are compiling a kernel for the EBSA-110 or the LART however, the
549 red LED will simply flash regularly to indicate that the system is
550 still functional. It is safe to say Y here if you have a CATS
551 system, but the driver will do nothing.
554 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
555 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
557 default y if ARCH_EBSA110
559 If you say Y here, one of the system LEDs (the green one on the
560 NetWinder, the amber one on the EBSA285, or the red one on the LART)
561 will flash regularly to indicate that the system is still
562 operational. This is mainly useful to kernel hackers who are
563 debugging unstable kernels.
565 The LART uses the same LED for both Timer LED and CPU usage LED
566 functions. You may choose to use both, but the Timer LED function
567 will overrule the CPU usage LED.
570 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
571 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
574 If you say Y here, the red LED will be used to give a good real
575 time indication of CPU usage, by lighting whenever the idle task
576 is not currently executing.
578 The LART uses the same LED for both Timer LED and CPU usage LED
579 functions. You may choose to use both, but the Timer LED function
580 will overrule the CPU usage LED.
582 config ALIGNMENT_TRAP
584 default y if !ARCH_EBSA110
586 ARM processors can not fetch/store information which is not
587 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
588 address divisible by 4. On 32-bit ARM processors, these non-aligned
589 fetch/store instructions will be emulated in software if you say
590 here, which has a severe performance impact. This is necessary for
591 correct operation of some network protocols. With an IP-only
592 configuration it is safe to say N, otherwise say Y.
598 # Compressed boot loader in ROM. Yes, we really want to ask about
599 # TEXT and BSS so we preserve their values in the config files.
600 config ZBOOT_ROM_TEXT
601 hex "Compressed ROM boot loader base address"
604 The physical address at which the ROM-able zImage is to be
605 placed in the target. Platforms which normally make use of
606 ROM-able zImage formats normally set this to a suitable
607 value in their defconfig file.
609 If ZBOOT_ROM is not enabled, this has no effect.
612 hex "Compressed ROM boot loader BSS address"
615 The base address of 64KiB of read/write memory in the target
616 for the ROM-able zImage, which must be available while the
617 decompressor is running. Platforms which normally make use of
618 ROM-able zImage formats normally set this to a suitable
619 value in their defconfig file.
621 If ZBOOT_ROM is not enabled, this has no effect.
624 bool "Compressed boot loader in ROM/flash"
625 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
627 Say Y here if you intend to execute your compressed kernel image
628 (zImage) directly from ROM or flash. If unsure, say N.
631 string "Default kernel command string"
634 On some architectures (EBSA110 and CATS), there is currently no way
635 for the boot loader to pass arguments to the kernel. For these
636 architectures, you should supply some command-line options at build
637 time by entering them here. As a minimum, you should specify the
638 memory size and the root device (e.g., mem=64M root=/dev/nfs).
641 bool "Kernel Execute-In-Place from ROM"
642 depends on !ZBOOT_ROM
644 Execute-In-Place allows the kernel to run from non-volatile storage
645 directly addressable by the CPU, such as NOR flash. This saves RAM
646 space since the text section of the kernel is not loaded from flash
647 to RAM. Read-write sections, such as the data section and stack,
648 are still copied to RAM. The XIP kernel is not compressed since
649 it has to run directly from flash, so it will take more space to
650 store it. The flash address used to link the kernel object files,
651 and for storing it, is configuration dependent. Therefore, if you
652 say Y here, you must know the proper physical address where to
653 store the kernel image depending on your own flash memory usage.
655 Also note that the make target becomes "make xipImage" rather than
656 "make zImage" or "make Image". The final kernel binary to put in
657 ROM memory will be arch/arm/boot/xipImage.
662 hex "XIP Kernel Physical Location"
663 depends on XIP_KERNEL
666 This is the physical address in your flash memory the kernel will
667 be linked for and stored to. This address is dependent on your
672 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
674 menu "CPU Frequency scaling"
676 source "drivers/cpufreq/Kconfig"
678 config CPU_FREQ_SA1100
680 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
683 config CPU_FREQ_SA1110
685 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
688 config CPU_FREQ_INTEGRATOR
689 tristate "CPUfreq driver for ARM Integrator CPUs"
690 depends on ARCH_INTEGRATOR && CPU_FREQ
693 This enables the CPUfreq driver for ARM Integrator CPUs.
695 For details, take a look at <file:Documentation/cpu-freq>.
703 menu "Floating point emulation"
705 comment "At least one emulation must be selected"
708 bool "NWFPE math emulation"
709 depends on !AEABI || OABI_COMPAT
711 Say Y to include the NWFPE floating point emulator in the kernel.
712 This is necessary to run most binaries. Linux does not currently
713 support floating point hardware so you need to say Y here even if
714 your machine has an FPA or floating point co-processor podule.
716 You may say N here if you are going to load the Acorn FPEmulator
720 bool "Support extended precision"
723 Say Y to include 80-bit support in the kernel floating-point
724 emulator. Otherwise, only 32 and 64-bit support is compiled in.
725 Note that gcc does not generate 80-bit operations by default,
726 so in most cases this option only enlarges the size of the
727 floating point emulator without any good reason.
729 You almost surely want to say N here.
732 bool "FastFPE math emulation (EXPERIMENTAL)"
733 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
735 Say Y here to include the FAST floating point emulator in the kernel.
736 This is an experimental much faster emulator which now also has full
737 precision for the mantissa. It does not support any exceptions.
738 It is very simple, and approximately 3-6 times faster than NWFPE.
740 It should be sufficient for most programs. It may be not suitable
741 for scientific calculations, but you have to check this for yourself.
742 If you do not feel you need a faster FP emulation you should better
746 bool "VFP-format floating point maths"
747 depends on CPU_V6 || CPU_ARM926T
749 Say Y to include VFP support code in the kernel. This is needed
750 if your hardware includes a VFP unit.
752 Please see <file:Documentation/arm/VFP/release-notes.txt> for
753 release notes and additional status information.
755 Say N if your target does not have VFP hardware.
759 menu "Userspace binary formats"
761 source "fs/Kconfig.binfmt"
764 tristate "RISC OS personality"
767 Say Y here to include the kernel code necessary if you want to run
768 Acorn RISC OS/Arthur binaries under Linux. This code is still very
769 experimental; if this sounds frightening, say N and sleep in peace.
770 You can also say M here to compile this support as a module (which
771 will be called arthur).
775 menu "Power management options"
777 source "kernel/power/Kconfig"
780 tristate "Advanced Power Management Emulation"
782 APM is a BIOS specification for saving power using several different
783 techniques. This is mostly useful for battery powered laptops with
784 APM compliant BIOSes. If you say Y here, the system time will be
785 reset after a RESUME operation, the /proc/apm device will provide
786 battery status information, and user-space programs will receive
787 notification of APM "events" (e.g. battery status change).
789 In order to use APM, you will need supporting software. For location
790 and more information, read <file:Documentation/pm.txt> and the
791 Battery Powered Linux mini-HOWTO, available from
792 <http://www.tldp.org/docs.html#howto>.
794 This driver does not spin down disk drives (see the hdparm(8)
795 manpage ("man 8 hdparm") for that), and it doesn't turn off
796 VESA-compliant "green" monitors.
798 Generally, if you don't have a battery in your machine, there isn't
799 much point in using this driver and you should say N. If you get
800 random kernel OOPSes or reboots that don't seem to be related to
801 anything, try disabling/enabling this option (or disabling/enabling
808 menu "Device Drivers"
810 source "drivers/base/Kconfig"
812 source "drivers/connector/Kconfig"
815 source "drivers/mtd/Kconfig"
818 source "drivers/parport/Kconfig"
820 source "drivers/pnp/Kconfig"
822 source "drivers/block/Kconfig"
824 source "drivers/acorn/block/Kconfig"
826 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
827 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
828 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
830 source "drivers/ide/Kconfig"
833 source "drivers/scsi/Kconfig"
835 source "drivers/md/Kconfig"
837 source "drivers/message/fusion/Kconfig"
839 source "drivers/ieee1394/Kconfig"
841 source "drivers/message/i2o/Kconfig"
843 source "drivers/net/Kconfig"
845 source "drivers/isdn/Kconfig"
847 # input before char - char/joystick depends on it. As does USB.
849 source "drivers/input/Kconfig"
851 source "drivers/char/Kconfig"
853 source "drivers/i2c/Kconfig"
855 source "drivers/spi/Kconfig"
857 source "drivers/w1/Kconfig"
859 source "drivers/hwmon/Kconfig"
861 #source "drivers/l3/Kconfig"
863 source "drivers/misc/Kconfig"
865 source "drivers/mfd/Kconfig"
867 source "drivers/leds/Kconfig"
869 source "drivers/media/Kconfig"
871 source "drivers/video/Kconfig"
873 source "sound/Kconfig"
875 source "drivers/usb/Kconfig"
877 source "drivers/mmc/Kconfig"
879 source "drivers/rtc/Kconfig"
885 source "arch/arm/oprofile/Kconfig"
887 source "arch/arm/Kconfig.debug"
889 source "security/Kconfig"
891 source "crypto/Kconfig"