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 prompt "ARM system type"
81 bool "Cirrus-CL-PS7500FE"
85 Support for the Cirrus Logic PS7500FE system-on-a-chip.
88 bool "CLPS711x/EP721x-based"
90 Support for Cirrus Logic 711x/721x based boards.
95 select FOOTBRIDGE_ADDIN
97 Support for Intel's EBSA285 companion chip.
103 This is an evaluation board for the StrongARM processor available
104 from Digital. It has limited hardware on-board, including an
105 Ethernet interface, two PCMCIA sockets, two serial ports and a
108 config ARCH_FOOTBRIDGE
112 Support for systems based on the DC21285 companion chip
113 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
115 config ARCH_INTEGRATOR
120 Support for ARM's Integrator platform.
126 Support for Intel's IOP3XX (XScale) family of processors.
133 Support for Intel's IXP4XX (XScale) family of processors.
136 bool "IXP2400/2800-based"
139 Support for Intel's IXP2400/2800 (XScale) family of processors.
145 Say Y here if you intend to run this kernel on a LinkUp Systems
146 L7200 Software Development Board which uses an ARM720T processor.
147 Information on this board can be obtained at:
149 <http://www.linkupsys.com/>
151 If you have any questions or comments about the Linux kernel port
152 to this board, send e-mail to <sjhill@cotw.com>.
157 Support for Intel's PXA2XX processor line.
164 select ARCH_MAY_HAVE_PC_FDC
167 On the Acorn Risc-PC, Linux can support the internal IDE disk and
168 CD-ROM interface, serial and parallel port, and the floppy drive.
173 select ARCH_DISCONTIGMEM_ENABLE
175 Support for StrongARM 11x0 based boards.
178 bool "Samsung S3C2410"
180 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
181 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
182 the Samsung SMDK2410 development board (and derivatives).
190 Support for the StrongARM based Digital DNARD machine, also known
191 as "Shark" (<http://www.shark-linux.de/shark.html>).
196 Say Y here for systems based on one of the Sharp LH7A40X
197 System on a Chip processors. These CPUs include an ARM922T
198 core with a wide array of integrated devices for
199 hand-held and low-power applications.
204 Support for TI's OMAP platform (OMAP1 and OMAP2).
206 config ARCH_VERSATILE
212 This enables support for ARM Ltd Versatile board.
219 This enables support for ARM Ltd RealView boards.
224 Support for Motorola's i.MX family of processors (MX1, MXL).
227 bool "Hynix-HMS720x-based"
230 This enables support for systems based on the Hynix HMS720x
233 bool "Agilent AAEC-2000 based"
236 This enables support for systems based on the Agilent AAEC-2000
238 config ARCH_AT91RM9200
241 Say Y here if you intend to run this kernel on an Atmel
242 AT91RM9200-based board.
246 source "arch/arm/mach-clps711x/Kconfig"
248 source "arch/arm/mach-footbridge/Kconfig"
250 source "arch/arm/mach-integrator/Kconfig"
252 source "arch/arm/mach-iop3xx/Kconfig"
254 source "arch/arm/mach-ixp4xx/Kconfig"
256 source "arch/arm/mach-ixp2000/Kconfig"
258 source "arch/arm/mach-pxa/Kconfig"
260 source "arch/arm/mach-sa1100/Kconfig"
262 source "arch/arm/plat-omap/Kconfig"
264 source "arch/arm/mach-omap1/Kconfig"
266 source "arch/arm/mach-omap2/Kconfig"
268 source "arch/arm/mach-s3c2410/Kconfig"
270 source "arch/arm/mach-lh7a40x/Kconfig"
272 source "arch/arm/mach-imx/Kconfig"
274 source "arch/arm/mach-h720x/Kconfig"
276 source "arch/arm/mach-versatile/Kconfig"
278 source "arch/arm/mach-aaec2000/Kconfig"
280 source "arch/arm/mach-realview/Kconfig"
282 source "arch/arm/mach-at91rm9200/Kconfig"
284 # Definitions to make life easier
288 source arch/arm/mm/Kconfig
290 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
293 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
298 source "arch/arm/common/Kconfig"
300 config FORCE_MAX_ZONEORDER
313 Find out whether you have ISA slots on your motherboard. ISA is the
314 name of a bus system, i.e. the way the CPU talks to the other stuff
315 inside your box. Other bus systems are PCI, EISA, MicroChannel
316 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
317 newer boards don't support it. If you have ISA, say Y, otherwise N.
319 # Select ISA DMA controller support
324 # Select ISA DMA interface
329 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
331 Find out whether you have a PCI motherboard. PCI is the name of a
332 bus system, i.e. the way the CPU talks to the other stuff inside
333 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
334 VESA. If you have PCI, say Y, otherwise N.
336 The PCI-HOWTO, available from
337 <http://www.tldp.org/docs.html#howto>, contains valuable
338 information about which PCI hardware does work under Linux and which
341 # Select the host bridge type
342 config PCI_HOST_VIA82C505
344 depends on PCI && ARCH_SHARK
347 source "drivers/pci/Kconfig"
349 source "drivers/pcmcia/Kconfig"
353 menu "Kernel Features"
356 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
357 depends on EXPERIMENTAL && REALVIEW_MPCORE
359 This enables support for systems with more than one CPU. If you have
360 a system with only one CPU, like most personal computers, say N. If
361 you have a system with more than one CPU, say Y.
363 If you say N here, the kernel will run on single and multiprocessor
364 machines, but will use only one CPU of a multiprocessor machine. If
365 you say Y here, the kernel will run on many, but not all, single
366 processor machines. On a single processor machine, the kernel will
367 run faster if you say N here.
369 See also the <file:Documentation/smp.txt>,
370 <file:Documentation/i386/IO-APIC.txt>,
371 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
372 <http://www.linuxdoc.org/docs.html#howto>.
374 If you don't know what to do here, say N.
377 int "Maximum number of CPUs (2-32)"
383 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
384 depends on SMP && HOTPLUG && EXPERIMENTAL
386 Say Y here to experiment with turning CPUs off and on. CPUs
387 can be controlled through /sys/devices/system/cpu.
390 bool "Use local timer interrupts"
391 depends on SMP && REALVIEW_MPCORE
394 Enable support for local timers on SMP platforms, rather then the
395 legacy IPI broadcast method. Local timers allows the system
396 accounting to be spread across the timer interval, preventing a
397 "thundering herd" at every timer tick.
400 bool "Preemptible Kernel (EXPERIMENTAL)"
401 depends on EXPERIMENTAL
403 This option reduces the latency of the kernel when reacting to
404 real-time or interactive events by allowing a low priority process to
405 be preempted even if it is in kernel mode executing a system call.
406 This allows applications to run more reliably even when the system is
409 Say Y here if you are building a kernel for a desktop, embedded
410 or real-time system. Say N if you are unsure.
413 bool "Dynamic tick timer"
415 Select this option if you want to disable continuous timer ticks
416 and have them programmed to occur as required. This option saves
417 power as the system can remain in idle state for longer.
419 By default dynamic tick is disabled during the boot, and can be
420 manually enabled with:
422 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
424 Alternatively, if you want dynamic tick automatically enabled
425 during boot, pass "dyntick=enable" via the kernel command string.
427 Please note that dynamic tick may affect the accuracy of
428 timekeeping on some platforms depending on the implementation.
429 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
430 to have accurate timekeeping with dynamic tick.
433 bool "Use the ARM EABI to compile the kernel"
435 This option allows for the kernel to be compiled using the latest
436 ARM ABI (aka EABI). This is only useful if you are using a user
437 space environment that is also compiled with EABI.
439 Since there are major incompatibilities between the legacy ABI and
440 EABI, especially with regard to structure member alignment, this
441 option also changes the kernel syscall calling convention to
442 disambiguate both ABIs and allow for backward compatibility support
443 (selected with CONFIG_OABI_COMPAT).
445 To use this you need GCC version 4.0.0 or later.
448 bool "Allow old ABI binaries to run with this kernel"
449 depends on AEABI && EXPERIMENTAL
452 This option preserves the old syscall interface along with the
453 new (ARM EABI) one. It also provides a compatibility layer to
454 intercept syscalls that have structure arguments which layout
455 in memory differs between the legacy ABI and the new ARM EABI
456 (only for non "thumb" binaries). This option adds a tiny
457 overhead to all syscalls and produces a slightly larger kernel.
458 If you know you'll be using only pure EABI user space then you
459 can say N here. If this option is not selected and you attempt
460 to execute a legacy ABI binary then the result will be
461 UNPREDICTABLE (in fact it can be predicted that it won't work
462 at all). If in doubt say Y.
464 config ARCH_DISCONTIGMEM_ENABLE
466 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
468 Say Y to support efficient handling of discontiguous physical memory,
469 for architectures which are either NUMA (Non-Uniform Memory Access)
470 or have huge holes in the physical address space for other reasons.
471 See <file:Documentation/vm/numa> for more.
476 bool "Timer and CPU usage LEDs"
477 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
478 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
479 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
480 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
481 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
484 If you say Y here, the LEDs on your machine will be used
485 to provide useful information about your current system status.
487 If you are compiling a kernel for a NetWinder or EBSA-285, you will
488 be able to select which LEDs are active using the options below. If
489 you are compiling a kernel for the EBSA-110 or the LART however, the
490 red LED will simply flash regularly to indicate that the system is
491 still functional. It is safe to say Y here if you have a CATS
492 system, but the driver will do nothing.
495 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
496 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
498 default y if ARCH_EBSA110
500 If you say Y here, one of the system LEDs (the green one on the
501 NetWinder, the amber one on the EBSA285, or the red one on the LART)
502 will flash regularly to indicate that the system is still
503 operational. This is mainly useful to kernel hackers who are
504 debugging unstable kernels.
506 The LART uses the same LED for both Timer LED and CPU usage LED
507 functions. You may choose to use both, but the Timer LED function
508 will overrule the CPU usage LED.
511 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
512 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
515 If you say Y here, the red LED will be used to give a good real
516 time indication of CPU usage, by lighting whenever the idle task
517 is not currently executing.
519 The LART uses the same LED for both Timer LED and CPU usage LED
520 functions. You may choose to use both, but the Timer LED function
521 will overrule the CPU usage LED.
523 config ALIGNMENT_TRAP
525 default y if !ARCH_EBSA110
527 ARM processors can not fetch/store information which is not
528 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
529 address divisible by 4. On 32-bit ARM processors, these non-aligned
530 fetch/store instructions will be emulated in software if you say
531 here, which has a severe performance impact. This is necessary for
532 correct operation of some network protocols. With an IP-only
533 configuration it is safe to say N, otherwise say Y.
539 # Compressed boot loader in ROM. Yes, we really want to ask about
540 # TEXT and BSS so we preserve their values in the config files.
541 config ZBOOT_ROM_TEXT
542 hex "Compressed ROM boot loader base address"
545 The physical address at which the ROM-able zImage is to be
546 placed in the target. Platforms which normally make use of
547 ROM-able zImage formats normally set this to a suitable
548 value in their defconfig file.
550 If ZBOOT_ROM is not enabled, this has no effect.
553 hex "Compressed ROM boot loader BSS address"
556 The base address of 64KiB of read/write memory in the target
557 for the ROM-able zImage, which must be available while the
558 decompressor is running. Platforms which normally make use of
559 ROM-able zImage formats normally set this to a suitable
560 value in their defconfig file.
562 If ZBOOT_ROM is not enabled, this has no effect.
565 bool "Compressed boot loader in ROM/flash"
566 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
568 Say Y here if you intend to execute your compressed kernel image
569 (zImage) directly from ROM or flash. If unsure, say N.
572 string "Default kernel command string"
575 On some architectures (EBSA110 and CATS), there is currently no way
576 for the boot loader to pass arguments to the kernel. For these
577 architectures, you should supply some command-line options at build
578 time by entering them here. As a minimum, you should specify the
579 memory size and the root device (e.g., mem=64M root=/dev/nfs).
582 bool "Kernel Execute-In-Place from ROM"
583 depends on !ZBOOT_ROM
585 Execute-In-Place allows the kernel to run from non-volatile storage
586 directly addressable by the CPU, such as NOR flash. This saves RAM
587 space since the text section of the kernel is not loaded from flash
588 to RAM. Read-write sections, such as the data section and stack,
589 are still copied to RAM. The XIP kernel is not compressed since
590 it has to run directly from flash, so it will take more space to
591 store it. The flash address used to link the kernel object files,
592 and for storing it, is configuration dependent. Therefore, if you
593 say Y here, you must know the proper physical address where to
594 store the kernel image depending on your own flash memory usage.
596 Also note that the make target becomes "make xipImage" rather than
597 "make zImage" or "make Image". The final kernel binary to put in
598 ROM memory will be arch/arm/boot/xipImage.
603 hex "XIP Kernel Physical Location"
604 depends on XIP_KERNEL
607 This is the physical address in your flash memory the kernel will
608 be linked for and stored to. This address is dependent on your
613 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
615 menu "CPU Frequency scaling"
617 source "drivers/cpufreq/Kconfig"
619 config CPU_FREQ_SA1100
621 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
624 config CPU_FREQ_SA1110
626 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
629 config CPU_FREQ_INTEGRATOR
630 tristate "CPUfreq driver for ARM Integrator CPUs"
631 depends on ARCH_INTEGRATOR && CPU_FREQ
634 This enables the CPUfreq driver for ARM Integrator CPUs.
636 For details, take a look at <file:Documentation/cpu-freq>.
644 menu "Floating point emulation"
646 comment "At least one emulation must be selected"
649 bool "NWFPE math emulation"
650 depends on !AEABI || OABI_COMPAT
652 Say Y to include the NWFPE floating point emulator in the kernel.
653 This is necessary to run most binaries. Linux does not currently
654 support floating point hardware so you need to say Y here even if
655 your machine has an FPA or floating point co-processor podule.
657 You may say N here if you are going to load the Acorn FPEmulator
661 bool "Support extended precision"
664 Say Y to include 80-bit support in the kernel floating-point
665 emulator. Otherwise, only 32 and 64-bit support is compiled in.
666 Note that gcc does not generate 80-bit operations by default,
667 so in most cases this option only enlarges the size of the
668 floating point emulator without any good reason.
670 You almost surely want to say N here.
673 bool "FastFPE math emulation (EXPERIMENTAL)"
674 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
676 Say Y here to include the FAST floating point emulator in the kernel.
677 This is an experimental much faster emulator which now also has full
678 precision for the mantissa. It does not support any exceptions.
679 It is very simple, and approximately 3-6 times faster than NWFPE.
681 It should be sufficient for most programs. It may be not suitable
682 for scientific calculations, but you have to check this for yourself.
683 If you do not feel you need a faster FP emulation you should better
687 bool "VFP-format floating point maths"
688 depends on CPU_V6 || CPU_ARM926T
690 Say Y to include VFP support code in the kernel. This is needed
691 if your hardware includes a VFP unit.
693 Please see <file:Documentation/arm/VFP/release-notes.txt> for
694 release notes and additional status information.
696 Say N if your target does not have VFP hardware.
700 menu "Userspace binary formats"
702 source "fs/Kconfig.binfmt"
705 tristate "RISC OS personality"
708 Say Y here to include the kernel code necessary if you want to run
709 Acorn RISC OS/Arthur binaries under Linux. This code is still very
710 experimental; if this sounds frightening, say N and sleep in peace.
711 You can also say M here to compile this support as a module (which
712 will be called arthur).
716 menu "Power management options"
718 source "kernel/power/Kconfig"
721 tristate "Advanced Power Management Emulation"
723 APM is a BIOS specification for saving power using several different
724 techniques. This is mostly useful for battery powered laptops with
725 APM compliant BIOSes. If you say Y here, the system time will be
726 reset after a RESUME operation, the /proc/apm device will provide
727 battery status information, and user-space programs will receive
728 notification of APM "events" (e.g. battery status change).
730 In order to use APM, you will need supporting software. For location
731 and more information, read <file:Documentation/pm.txt> and the
732 Battery Powered Linux mini-HOWTO, available from
733 <http://www.tldp.org/docs.html#howto>.
735 This driver does not spin down disk drives (see the hdparm(8)
736 manpage ("man 8 hdparm") for that), and it doesn't turn off
737 VESA-compliant "green" monitors.
739 Generally, if you don't have a battery in your machine, there isn't
740 much point in using this driver and you should say N. If you get
741 random kernel OOPSes or reboots that don't seem to be related to
742 anything, try disabling/enabling this option (or disabling/enabling
749 menu "Device Drivers"
751 source "drivers/base/Kconfig"
753 source "drivers/connector/Kconfig"
756 source "drivers/mtd/Kconfig"
759 source "drivers/parport/Kconfig"
761 source "drivers/pnp/Kconfig"
763 source "drivers/block/Kconfig"
765 source "drivers/acorn/block/Kconfig"
767 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
768 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
769 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
770 source "drivers/ide/Kconfig"
773 source "drivers/scsi/Kconfig"
775 source "drivers/md/Kconfig"
777 source "drivers/message/fusion/Kconfig"
779 source "drivers/ieee1394/Kconfig"
781 source "drivers/message/i2o/Kconfig"
783 source "drivers/net/Kconfig"
785 source "drivers/isdn/Kconfig"
787 # input before char - char/joystick depends on it. As does USB.
789 source "drivers/input/Kconfig"
791 source "drivers/char/Kconfig"
793 source "drivers/i2c/Kconfig"
795 source "drivers/spi/Kconfig"
797 source "drivers/hwmon/Kconfig"
799 #source "drivers/l3/Kconfig"
801 source "drivers/misc/Kconfig"
803 source "drivers/mfd/Kconfig"
805 source "drivers/media/Kconfig"
807 source "drivers/video/Kconfig"
809 source "sound/Kconfig"
811 source "drivers/usb/Kconfig"
813 source "drivers/mmc/Kconfig"
819 source "arch/arm/oprofile/Kconfig"
821 source "arch/arm/Kconfig.debug"
823 source "security/Kconfig"
825 source "crypto/Kconfig"