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
80 prompt "ARM system type"
84 bool "Cirrus-CL-PS7500FE"
88 Support for the Cirrus Logic PS7500FE system-on-a-chip.
91 bool "CLPS711x/EP721x-based"
93 Support for Cirrus Logic 711x/721x based boards.
98 select FOOTBRIDGE_ADDIN
100 Support for Intel's EBSA285 companion chip.
106 This is an evaluation board for the StrongARM processor available
107 from Digital. It has limited hardware on-board, including an
108 Ethernet interface, two PCMCIA sockets, two serial ports and a
111 config ARCH_FOOTBRIDGE
115 Support for systems based on the DC21285 companion chip
116 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
118 config ARCH_INTEGRATOR
123 Support for ARM's Integrator platform.
129 Support for Intel's IOP3XX (XScale) family of processors.
136 Support for Intel's IXP4XX (XScale) family of processors.
139 bool "IXP2400/2800-based"
142 Support for Intel's IXP2400/2800 (XScale) family of processors.
148 Say Y here if you intend to run this kernel on a LinkUp Systems
149 L7200 Software Development Board which uses an ARM720T processor.
150 Information on this board can be obtained at:
152 <http://www.linkupsys.com/>
154 If you have any questions or comments about the Linux kernel port
155 to this board, send e-mail to <sjhill@cotw.com>.
161 Support for Intel's PXA2XX processor line.
168 select ARCH_MAY_HAVE_PC_FDC
171 On the Acorn Risc-PC, Linux can support the internal IDE disk and
172 CD-ROM interface, serial and parallel port, and the floppy drive.
177 select ARCH_DISCONTIGMEM_ENABLE
180 Support for StrongARM 11x0 based boards.
183 bool "Samsung S3C2410"
185 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
186 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
187 the Samsung SMDK2410 development board (and derivatives).
195 Support for the StrongARM based Digital DNARD machine, also known
196 as "Shark" (<http://www.shark-linux.de/shark.html>).
201 Say Y here for systems based on one of the Sharp LH7A40X
202 System on a Chip processors. These CPUs include an ARM922T
203 core with a wide array of integrated devices for
204 hand-held and low-power applications.
209 Support for TI's OMAP platform (OMAP1 and OMAP2).
211 config ARCH_VERSATILE
217 This enables support for ARM Ltd Versatile board.
224 This enables support for ARM Ltd RealView boards.
229 Support for Motorola's i.MX family of processors (MX1, MXL).
232 bool "Hynix-HMS720x-based"
235 This enables support for systems based on the Hynix HMS720x
238 bool "Agilent AAEC-2000 based"
241 This enables support for systems based on the Agilent AAEC-2000
243 config ARCH_AT91RM9200
246 Say Y here if you intend to run this kernel on an Atmel
247 AT91RM9200-based board.
251 source "arch/arm/mach-clps711x/Kconfig"
253 source "arch/arm/mach-footbridge/Kconfig"
255 source "arch/arm/mach-integrator/Kconfig"
257 source "arch/arm/mach-iop3xx/Kconfig"
259 source "arch/arm/mach-ixp4xx/Kconfig"
261 source "arch/arm/mach-ixp2000/Kconfig"
263 source "arch/arm/mach-pxa/Kconfig"
265 source "arch/arm/mach-sa1100/Kconfig"
267 source "arch/arm/plat-omap/Kconfig"
269 source "arch/arm/mach-omap1/Kconfig"
271 source "arch/arm/mach-omap2/Kconfig"
273 source "arch/arm/mach-s3c2410/Kconfig"
275 source "arch/arm/mach-lh7a40x/Kconfig"
277 source "arch/arm/mach-imx/Kconfig"
279 source "arch/arm/mach-h720x/Kconfig"
281 source "arch/arm/mach-versatile/Kconfig"
283 source "arch/arm/mach-aaec2000/Kconfig"
285 source "arch/arm/mach-realview/Kconfig"
287 source "arch/arm/mach-at91rm9200/Kconfig"
289 # Definitions to make life easier
293 source arch/arm/mm/Kconfig
295 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
298 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
303 source "arch/arm/common/Kconfig"
305 config FORCE_MAX_ZONEORDER
318 Find out whether you have ISA slots on your motherboard. ISA is the
319 name of a bus system, i.e. the way the CPU talks to the other stuff
320 inside your box. Other bus systems are PCI, EISA, MicroChannel
321 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
322 newer boards don't support it. If you have ISA, say Y, otherwise N.
324 # Select ISA DMA controller support
329 # Select ISA DMA interface
334 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
336 Find out whether you have a PCI motherboard. PCI is the name of a
337 bus system, i.e. the way the CPU talks to the other stuff inside
338 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
339 VESA. If you have PCI, say Y, otherwise N.
341 The PCI-HOWTO, available from
342 <http://www.tldp.org/docs.html#howto>, contains valuable
343 information about which PCI hardware does work under Linux and which
346 # Select the host bridge type
347 config PCI_HOST_VIA82C505
349 depends on PCI && ARCH_SHARK
352 source "drivers/pci/Kconfig"
354 source "drivers/pcmcia/Kconfig"
358 menu "Kernel Features"
361 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
362 depends on EXPERIMENTAL && REALVIEW_MPCORE
364 This enables support for systems with more than one CPU. If you have
365 a system with only one CPU, like most personal computers, say N. If
366 you have a system with more than one CPU, say Y.
368 If you say N here, the kernel will run on single and multiprocessor
369 machines, but will use only one CPU of a multiprocessor machine. If
370 you say Y here, the kernel will run on many, but not all, single
371 processor machines. On a single processor machine, the kernel will
372 run faster if you say N here.
374 See also the <file:Documentation/smp.txt>,
375 <file:Documentation/i386/IO-APIC.txt>,
376 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
377 <http://www.linuxdoc.org/docs.html#howto>.
379 If you don't know what to do here, say N.
382 int "Maximum number of CPUs (2-32)"
388 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
389 depends on SMP && HOTPLUG && EXPERIMENTAL
391 Say Y here to experiment with turning CPUs off and on. CPUs
392 can be controlled through /sys/devices/system/cpu.
395 bool "Use local timer interrupts"
396 depends on SMP && REALVIEW_MPCORE
399 Enable support for local timers on SMP platforms, rather then the
400 legacy IPI broadcast method. Local timers allows the system
401 accounting to be spread across the timer interval, preventing a
402 "thundering herd" at every timer tick.
405 bool "Preemptible Kernel (EXPERIMENTAL)"
406 depends on EXPERIMENTAL
408 This option reduces the latency of the kernel when reacting to
409 real-time or interactive events by allowing a low priority process to
410 be preempted even if it is in kernel mode executing a system call.
411 This allows applications to run more reliably even when the system is
414 Say Y here if you are building a kernel for a desktop, embedded
415 or real-time system. Say N if you are unsure.
418 bool "Dynamic tick timer"
420 Select this option if you want to disable continuous timer ticks
421 and have them programmed to occur as required. This option saves
422 power as the system can remain in idle state for longer.
424 By default dynamic tick is disabled during the boot, and can be
425 manually enabled with:
427 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
429 Alternatively, if you want dynamic tick automatically enabled
430 during boot, pass "dyntick=enable" via the kernel command string.
432 Please note that dynamic tick may affect the accuracy of
433 timekeeping on some platforms depending on the implementation.
434 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
435 to have accurate timekeeping with dynamic tick.
438 bool "Use the ARM EABI to compile the kernel"
440 This option allows for the kernel to be compiled using the latest
441 ARM ABI (aka EABI). This is only useful if you are using a user
442 space environment that is also compiled with EABI.
444 Since there are major incompatibilities between the legacy ABI and
445 EABI, especially with regard to structure member alignment, this
446 option also changes the kernel syscall calling convention to
447 disambiguate both ABIs and allow for backward compatibility support
448 (selected with CONFIG_OABI_COMPAT).
450 To use this you need GCC version 4.0.0 or later.
453 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
454 depends on AEABI && EXPERIMENTAL
457 This option preserves the old syscall interface along with the
458 new (ARM EABI) one. It also provides a compatibility layer to
459 intercept syscalls that have structure arguments which layout
460 in memory differs between the legacy ABI and the new ARM EABI
461 (only for non "thumb" binaries). This option adds a tiny
462 overhead to all syscalls and produces a slightly larger kernel.
463 If you know you'll be using only pure EABI user space then you
464 can say N here. If this option is not selected and you attempt
465 to execute a legacy ABI binary then the result will be
466 UNPREDICTABLE (in fact it can be predicted that it won't work
467 at all). If in doubt say Y.
469 config ARCH_DISCONTIGMEM_ENABLE
471 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
473 Say Y to support efficient handling of discontiguous physical memory,
474 for architectures which are either NUMA (Non-Uniform Memory Access)
475 or have huge holes in the physical address space for other reasons.
476 See <file:Documentation/vm/numa> for more.
481 bool "Timer and CPU usage LEDs"
482 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
483 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
484 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
485 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
486 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
489 If you say Y here, the LEDs on your machine will be used
490 to provide useful information about your current system status.
492 If you are compiling a kernel for a NetWinder or EBSA-285, you will
493 be able to select which LEDs are active using the options below. If
494 you are compiling a kernel for the EBSA-110 or the LART however, the
495 red LED will simply flash regularly to indicate that the system is
496 still functional. It is safe to say Y here if you have a CATS
497 system, but the driver will do nothing.
500 bool "Timer LED" if !ARCH_CDB89712
502 default y if ARCH_EBSA110
504 If you say Y here, one of the system LEDs (the green one on the
505 NetWinder, the amber one on the EBSA285, or the red one on the LART)
506 will flash regularly to indicate that the system is still
507 operational. This is mainly useful to kernel hackers who are
508 debugging unstable kernels.
510 The LART uses the same LED for both Timer LED and CPU usage LED
511 functions. You may choose to use both, but the Timer LED function
512 will overrule the CPU usage LED.
515 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110)
518 If you say Y here, the red LED will be used to give a good real
519 time indication of CPU usage, by lighting whenever the idle task
520 is not currently executing.
522 The LART uses the same LED for both Timer LED and CPU usage LED
523 functions. You may choose to use both, but the Timer LED function
524 will overrule the CPU usage LED.
526 config ALIGNMENT_TRAP
528 default y if !ARCH_EBSA110
530 ARM processors can not fetch/store information which is not
531 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
532 address divisible by 4. On 32-bit ARM processors, these non-aligned
533 fetch/store instructions will be emulated in software if you say
534 here, which has a severe performance impact. This is necessary for
535 correct operation of some network protocols. With an IP-only
536 configuration it is safe to say N, otherwise say Y.
542 # Compressed boot loader in ROM. Yes, we really want to ask about
543 # TEXT and BSS so we preserve their values in the config files.
544 config ZBOOT_ROM_TEXT
545 hex "Compressed ROM boot loader base address"
548 The physical address at which the ROM-able zImage is to be
549 placed in the target. Platforms which normally make use of
550 ROM-able zImage formats normally set this to a suitable
551 value in their defconfig file.
553 If ZBOOT_ROM is not enabled, this has no effect.
556 hex "Compressed ROM boot loader BSS address"
559 The base address of 64KiB of read/write memory in the target
560 for the ROM-able zImage, which must be available while the
561 decompressor is running. Platforms which normally make use of
562 ROM-able zImage formats normally set this to a suitable
563 value in their defconfig file.
565 If ZBOOT_ROM is not enabled, this has no effect.
568 bool "Compressed boot loader in ROM/flash"
569 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
571 Say Y here if you intend to execute your compressed kernel image
572 (zImage) directly from ROM or flash. If unsure, say N.
575 string "Default kernel command string"
578 On some architectures (EBSA110 and CATS), there is currently no way
579 for the boot loader to pass arguments to the kernel. For these
580 architectures, you should supply some command-line options at build
581 time by entering them here. As a minimum, you should specify the
582 memory size and the root device (e.g., mem=64M root=/dev/nfs).
585 bool "Kernel Execute-In-Place from ROM"
586 depends on !ZBOOT_ROM
588 Execute-In-Place allows the kernel to run from non-volatile storage
589 directly addressable by the CPU, such as NOR flash. This saves RAM
590 space since the text section of the kernel is not loaded from flash
591 to RAM. Read-write sections, such as the data section and stack,
592 are still copied to RAM. The XIP kernel is not compressed since
593 it has to run directly from flash, so it will take more space to
594 store it. The flash address used to link the kernel object files,
595 and for storing it, is configuration dependent. Therefore, if you
596 say Y here, you must know the proper physical address where to
597 store the kernel image depending on your own flash memory usage.
599 Also note that the make target becomes "make xipImage" rather than
600 "make zImage" or "make Image". The final kernel binary to put in
601 ROM memory will be arch/arm/boot/xipImage.
606 hex "XIP Kernel Physical Location"
607 depends on XIP_KERNEL
610 This is the physical address in your flash memory the kernel will
611 be linked for and stored to. This address is dependent on your
616 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
618 menu "CPU Frequency scaling"
620 source "drivers/cpufreq/Kconfig"
622 config CPU_FREQ_SA1100
624 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
627 config CPU_FREQ_SA1110
629 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
632 config CPU_FREQ_INTEGRATOR
633 tristate "CPUfreq driver for ARM Integrator CPUs"
634 depends on ARCH_INTEGRATOR && CPU_FREQ
637 This enables the CPUfreq driver for ARM Integrator CPUs.
639 For details, take a look at <file:Documentation/cpu-freq>.
647 menu "Floating point emulation"
649 comment "At least one emulation must be selected"
652 bool "NWFPE math emulation"
653 depends on !AEABI || OABI_COMPAT
655 Say Y to include the NWFPE floating point emulator in the kernel.
656 This is necessary to run most binaries. Linux does not currently
657 support floating point hardware so you need to say Y here even if
658 your machine has an FPA or floating point co-processor podule.
660 You may say N here if you are going to load the Acorn FPEmulator
664 bool "Support extended precision"
667 Say Y to include 80-bit support in the kernel floating-point
668 emulator. Otherwise, only 32 and 64-bit support is compiled in.
669 Note that gcc does not generate 80-bit operations by default,
670 so in most cases this option only enlarges the size of the
671 floating point emulator without any good reason.
673 You almost surely want to say N here.
676 bool "FastFPE math emulation (EXPERIMENTAL)"
677 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
679 Say Y here to include the FAST floating point emulator in the kernel.
680 This is an experimental much faster emulator which now also has full
681 precision for the mantissa. It does not support any exceptions.
682 It is very simple, and approximately 3-6 times faster than NWFPE.
684 It should be sufficient for most programs. It may be not suitable
685 for scientific calculations, but you have to check this for yourself.
686 If you do not feel you need a faster FP emulation you should better
690 bool "VFP-format floating point maths"
691 depends on CPU_V6 || CPU_ARM926T
693 Say Y to include VFP support code in the kernel. This is needed
694 if your hardware includes a VFP unit.
696 Please see <file:Documentation/arm/VFP/release-notes.txt> for
697 release notes and additional status information.
699 Say N if your target does not have VFP hardware.
703 menu "Userspace binary formats"
705 source "fs/Kconfig.binfmt"
708 tristate "RISC OS personality"
711 Say Y here to include the kernel code necessary if you want to run
712 Acorn RISC OS/Arthur binaries under Linux. This code is still very
713 experimental; if this sounds frightening, say N and sleep in peace.
714 You can also say M here to compile this support as a module (which
715 will be called arthur).
719 menu "Power management options"
721 source "kernel/power/Kconfig"
724 tristate "Advanced Power Management Emulation"
726 APM is a BIOS specification for saving power using several different
727 techniques. This is mostly useful for battery powered laptops with
728 APM compliant BIOSes. If you say Y here, the system time will be
729 reset after a RESUME operation, the /proc/apm device will provide
730 battery status information, and user-space programs will receive
731 notification of APM "events" (e.g. battery status change).
733 In order to use APM, you will need supporting software. For location
734 and more information, read <file:Documentation/pm.txt> and the
735 Battery Powered Linux mini-HOWTO, available from
736 <http://www.tldp.org/docs.html#howto>.
738 This driver does not spin down disk drives (see the hdparm(8)
739 manpage ("man 8 hdparm") for that), and it doesn't turn off
740 VESA-compliant "green" monitors.
742 Generally, if you don't have a battery in your machine, there isn't
743 much point in using this driver and you should say N. If you get
744 random kernel OOPSes or reboots that don't seem to be related to
745 anything, try disabling/enabling this option (or disabling/enabling
752 menu "Device Drivers"
754 source "drivers/base/Kconfig"
756 source "drivers/connector/Kconfig"
759 source "drivers/mtd/Kconfig"
762 source "drivers/parport/Kconfig"
764 source "drivers/pnp/Kconfig"
766 source "drivers/block/Kconfig"
768 source "drivers/acorn/block/Kconfig"
770 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
771 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
772 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
773 source "drivers/ide/Kconfig"
776 source "drivers/scsi/Kconfig"
778 source "drivers/md/Kconfig"
780 source "drivers/message/fusion/Kconfig"
782 source "drivers/ieee1394/Kconfig"
784 source "drivers/message/i2o/Kconfig"
786 source "drivers/net/Kconfig"
788 source "drivers/isdn/Kconfig"
790 # input before char - char/joystick depends on it. As does USB.
792 source "drivers/input/Kconfig"
794 source "drivers/char/Kconfig"
796 source "drivers/i2c/Kconfig"
798 source "drivers/spi/Kconfig"
800 source "drivers/hwmon/Kconfig"
802 #source "drivers/l3/Kconfig"
804 source "drivers/misc/Kconfig"
806 source "drivers/mfd/Kconfig"
808 source "drivers/media/Kconfig"
810 source "drivers/video/Kconfig"
812 source "sound/Kconfig"
814 source "drivers/usb/Kconfig"
816 source "drivers/mmc/Kconfig"
818 source "drivers/ssi/Kconfig"
821 source "drivers/cbus/Kconfig"
828 source "arch/arm/oprofile/Kconfig"
830 source "arch/arm/Kconfig.debug"
832 source "security/Kconfig"
834 source "crypto/Kconfig"