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"
89 bool "CLPS711x/EP721x-based"
94 select FOOTBRIDGE_ADDIN
100 This is an evaluation board for the StrongARM processor available
101 from Digital. It has limited hardware on-board, including an onboard
102 Ethernet interface, two PCMCIA sockets, two serial ports and a
105 config ARCH_FOOTBRIDGE
109 config ARCH_INTEGRATOR
124 bool "IXP2400/2800-based"
131 Say Y here if you intend to run this kernel on a LinkUp Systems
132 L7200 Software Development Board which uses an ARM720T processor.
133 Information on this board can be obtained at:
135 <http://www.linkupsys.com/>
137 If you have any questions or comments about the Linux kernel port
138 to this board, send e-mail to <sjhill@cotw.com>.
149 select ARCH_MAY_HAVE_PC_FDC
152 On the Acorn Risc-PC, Linux can support the internal IDE disk and
153 CD-ROM interface, serial and parallel port, and the floppy drive.
158 select ARCH_DISCONTIGMEM_ENABLE
162 bool "Samsung S3C2410"
164 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
165 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
166 the Samsung SMDK2410 development board (and derviatives).
177 Say Y here for systems based on one of the Sharp LH7A40X
178 System on a Chip processors. These CPUs include an ARM922T
179 core with a wide array of integrated devices for
180 hand-held and low-power applications.
185 config ARCH_VERSATILE
191 This enables support for ARM Ltd Versatile board.
198 This enables support for ARM Ltd RealView boards.
204 bool "Hynix-HMS720x-based"
207 This enables support for systems based on the Hynix HMS720x
210 bool "Agilent AAEC-2000 based"
213 This enables support for systems based on the Agilent AAEC-2000
215 config ARCH_AT91RM9200
218 Say Y here if you intend to run this kernel on an AT91RM9200-based
223 source "arch/arm/mach-clps711x/Kconfig"
225 source "arch/arm/mach-footbridge/Kconfig"
227 source "arch/arm/mach-integrator/Kconfig"
229 source "arch/arm/mach-iop3xx/Kconfig"
231 source "arch/arm/mach-ixp4xx/Kconfig"
233 source "arch/arm/mach-ixp2000/Kconfig"
235 source "arch/arm/mach-pxa/Kconfig"
237 source "arch/arm/mach-sa1100/Kconfig"
239 source "arch/arm/plat-omap/Kconfig"
241 source "arch/arm/mach-omap1/Kconfig"
243 source "arch/arm/mach-omap2/Kconfig"
245 source "arch/arm/mach-s3c2410/Kconfig"
247 source "arch/arm/mach-lh7a40x/Kconfig"
249 source "arch/arm/mach-imx/Kconfig"
251 source "arch/arm/mach-h720x/Kconfig"
253 source "arch/arm/mach-versatile/Kconfig"
255 source "arch/arm/mach-aaec2000/Kconfig"
257 source "arch/arm/mach-realview/Kconfig"
259 source "arch/arm/mach-at91rm9200/Kconfig"
261 # Definitions to make life easier
265 source arch/arm/mm/Kconfig
267 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
270 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
275 source "arch/arm/common/Kconfig"
277 config FORCE_MAX_ZONEORDER
290 Find out whether you have ISA slots on your motherboard. ISA is the
291 name of a bus system, i.e. the way the CPU talks to the other stuff
292 inside your box. Other bus systems are PCI, EISA, MicroChannel
293 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
294 newer boards don't support it. If you have ISA, say Y, otherwise N.
296 # Select ISA DMA controller support
301 # Select ISA DMA interface
306 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
308 Find out whether you have a PCI motherboard. PCI is the name of a
309 bus system, i.e. the way the CPU talks to the other stuff inside
310 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
311 VESA. If you have PCI, say Y, otherwise N.
313 The PCI-HOWTO, available from
314 <http://www.tldp.org/docs.html#howto>, contains valuable
315 information about which PCI hardware does work under Linux and which
318 # Select the host bridge type
319 config PCI_HOST_VIA82C505
321 depends on PCI && ARCH_SHARK
324 source "drivers/pci/Kconfig"
326 source "drivers/pcmcia/Kconfig"
330 menu "Kernel Features"
333 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
334 depends on EXPERIMENTAL && REALVIEW_MPCORE
336 This enables support for systems with more than one CPU. If you have
337 a system with only one CPU, like most personal computers, say N. If
338 you have a system with more than one CPU, say Y.
340 If you say N here, the kernel will run on single and multiprocessor
341 machines, but will use only one CPU of a multiprocessor machine. If
342 you say Y here, the kernel will run on many, but not all, single
343 processor machines. On a single processor machine, the kernel will
344 run faster if you say N here.
346 See also the <file:Documentation/smp.txt>,
347 <file:Documentation/i386/IO-APIC.txt>,
348 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
349 <http://www.linuxdoc.org/docs.html#howto>.
351 If you don't know what to do here, say N.
354 int "Maximum number of CPUs (2-32)"
360 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
361 depends on SMP && HOTPLUG && EXPERIMENTAL
363 Say Y here to experiment with turning CPUs off and on. CPUs
364 can be controlled through /sys/devices/system/cpu.
367 bool "Use local timer interrupts"
368 depends on SMP && REALVIEW_MPCORE
371 Enable support for local timers on SMP platforms, rather then the
372 legacy IPI broadcast method. Local timers allows the system
373 accounting to be spread across the timer interval, preventing a
374 "thundering herd" at every timer tick.
377 bool "Preemptible Kernel (EXPERIMENTAL)"
378 depends on EXPERIMENTAL
380 This option reduces the latency of the kernel when reacting to
381 real-time or interactive events by allowing a low priority process to
382 be preempted even if it is in kernel mode executing a system call.
383 This allows applications to run more reliably even when the system is
386 Say Y here if you are building a kernel for a desktop, embedded
387 or real-time system. Say N if you are unsure.
390 bool "Dynamic tick timer"
392 Select this option if you want to disable continuous timer ticks
393 and have them programmed to occur as required. This option saves
394 power as the system can remain in idle state for longer.
396 By default dynamic tick is disabled during the boot, and can be
397 manually enabled with:
399 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
401 Alternatively, if you want dynamic tick automatically enabled
402 during boot, pass "dyntick=enable" via the kernel command string.
404 Please note that dynamic tick may affect the accuracy of
405 timekeeping on some platforms depending on the implementation.
406 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
407 to have accurate timekeeping with dynamic tick.
410 bool "Use the ARM EABI to compile the kernel"
412 This option allows for the kernel to be compiled using the latest
413 ARM ABI (aka EABI). This is only useful if you are using a user
414 space environment that is also compiled with EABI.
416 Since there are major incompatibilities between the legacy ABI and
417 EABI, especially with regard to structure member alignment, this
418 option also changes the kernel syscall calling convention to
419 disambiguate both ABIs and allow for backward compatibility support
420 (selected with CONFIG_OABI_COMPAT).
422 To use this you need GCC version 4.0.0 or later.
425 bool "Allow old ABI binaries to run with this kernel"
429 This option preserves the old syscall interface along with the
430 new (ARM EABI) one. It also provides a compatibility layer to
431 intercept syscalls that have structure arguments which layout
432 in memory differs between the legacy ABI and the new ARM EABI
433 (only for non "thumb" binaries). This option adds a tiny
434 overhead to all syscalls and produces a slightly larger kernel.
435 If you know you'll be using only pure EABI user space then you
436 can say N here. If this option is not selected and you attempt
437 to execute a legacy ABI binary then the result will be
438 UNPREDICTABLE (in fact it can be predicted that it won't work
439 at all). If in doubt say Y.
441 config ARCH_DISCONTIGMEM_ENABLE
443 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
445 Say Y to support efficient handling of discontiguous physical memory,
446 for architectures which are either NUMA (Non-Uniform Memory Access)
447 or have huge holes in the physical address space for other reasons.
448 See <file:Documentation/vm/numa> for more.
453 bool "Timer and CPU usage LEDs"
454 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
455 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
456 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
457 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
458 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
461 If you say Y here, the LEDs on your machine will be used
462 to provide useful information about your current system status.
464 If you are compiling a kernel for a NetWinder or EBSA-285, you will
465 be able to select which LEDs are active using the options below. If
466 you are compiling a kernel for the EBSA-110 or the LART however, the
467 red LED will simply flash regularly to indicate that the system is
468 still functional. It is safe to say Y here if you have a CATS
469 system, but the driver will do nothing.
472 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
473 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
475 default y if ARCH_EBSA110
477 If you say Y here, one of the system LEDs (the green one on the
478 NetWinder, the amber one on the EBSA285, or the red one on the LART)
479 will flash regularly to indicate that the system is still
480 operational. This is mainly useful to kernel hackers who are
481 debugging unstable kernels.
483 The LART uses the same LED for both Timer LED and CPU usage LED
484 functions. You may choose to use both, but the Timer LED function
485 will overrule the CPU usage LED.
488 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
489 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
492 If you say Y here, the red LED will be used to give a good real
493 time indication of CPU usage, by lighting whenever the idle task
494 is not currently executing.
496 The LART uses the same LED for both Timer LED and CPU usage LED
497 functions. You may choose to use both, but the Timer LED function
498 will overrule the CPU usage LED.
500 config ALIGNMENT_TRAP
502 default y if !ARCH_EBSA110
504 ARM processors can not fetch/store information which is not
505 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
506 address divisible by 4. On 32-bit ARM processors, these non-aligned
507 fetch/store instructions will be emulated in software if you say
508 here, which has a severe performance impact. This is necessary for
509 correct operation of some network protocols. With an IP-only
510 configuration it is safe to say N, otherwise say Y.
516 # Compressed boot loader in ROM. Yes, we really want to ask about
517 # TEXT and BSS so we preserve their values in the config files.
518 config ZBOOT_ROM_TEXT
519 hex "Compressed ROM boot loader base address"
522 The physical address at which the ROM-able zImage is to be
523 placed in the target. Platforms which normally make use of
524 ROM-able zImage formats normally set this to a suitable
525 value in their defconfig file.
527 If ZBOOT_ROM is not enabled, this has no effect.
530 hex "Compressed ROM boot loader BSS address"
533 The base address of 64KiB of read/write memory in the target
534 for the ROM-able zImage, which must be available while the
535 decompressor is running. Platforms which normally make use of
536 ROM-able zImage formats normally set this to a suitable
537 value in their defconfig file.
539 If ZBOOT_ROM is not enabled, this has no effect.
542 bool "Compressed boot loader in ROM/flash"
543 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
545 Say Y here if you intend to execute your compressed kernel image
546 (zImage) directly from ROM or flash. If unsure, say N.
549 string "Default kernel command string"
552 On some architectures (EBSA110 and CATS), there is currently no way
553 for the boot loader to pass arguments to the kernel. For these
554 architectures, you should supply some command-line options at build
555 time by entering them here. As a minimum, you should specify the
556 memory size and the root device (e.g., mem=64M root=/dev/nfs).
559 bool "Kernel Execute-In-Place from ROM"
560 depends on !ZBOOT_ROM
562 Execute-In-Place allows the kernel to run from non-volatile storage
563 directly addressable by the CPU, such as NOR flash. This saves RAM
564 space since the text section of the kernel is not loaded from flash
565 to RAM. Read-write sections, such as the data section and stack,
566 are still copied to RAM. The XIP kernel is not compressed since
567 it has to run directly from flash, so it will take more space to
568 store it. The flash address used to link the kernel object files,
569 and for storing it, is configuration dependent. Therefore, if you
570 say Y here, you must know the proper physical address where to
571 store the kernel image depending on your own flash memory usage.
573 Also note that the make target becomes "make xipImage" rather than
574 "make zImage" or "make Image". The final kernel binary to put in
575 ROM memory will be arch/arm/boot/xipImage.
580 hex "XIP Kernel Physical Location"
581 depends on XIP_KERNEL
584 This is the physical address in your flash memory the kernel will
585 be linked for and stored to. This address is dependent on your
590 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
592 menu "CPU Frequency scaling"
594 source "drivers/cpufreq/Kconfig"
596 config CPU_FREQ_SA1100
598 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
601 config CPU_FREQ_SA1110
603 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
606 config CPU_FREQ_INTEGRATOR
607 tristate "CPUfreq driver for ARM Integrator CPUs"
608 depends on ARCH_INTEGRATOR && CPU_FREQ
611 This enables the CPUfreq driver for ARM Integrator CPUs.
613 For details, take a look at <file:Documentation/cpu-freq>.
621 menu "Floating point emulation"
623 comment "At least one emulation must be selected"
626 bool "NWFPE math emulation"
627 depends on !AEABI || OABI_COMPAT
629 Say Y to include the NWFPE floating point emulator in the kernel.
630 This is necessary to run most binaries. Linux does not currently
631 support floating point hardware so you need to say Y here even if
632 your machine has an FPA or floating point co-processor podule.
634 You may say N here if you are going to load the Acorn FPEmulator
638 bool "Support extended precision"
641 Say Y to include 80-bit support in the kernel floating-point
642 emulator. Otherwise, only 32 and 64-bit support is compiled in.
643 Note that gcc does not generate 80-bit operations by default,
644 so in most cases this option only enlarges the size of the
645 floating point emulator without any good reason.
647 You almost surely want to say N here.
650 bool "FastFPE math emulation (EXPERIMENTAL)"
651 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
653 Say Y here to include the FAST floating point emulator in the kernel.
654 This is an experimental much faster emulator which now also has full
655 precision for the mantissa. It does not support any exceptions.
656 It is very simple, and approximately 3-6 times faster than NWFPE.
658 It should be sufficient for most programs. It may be not suitable
659 for scientific calculations, but you have to check this for yourself.
660 If you do not feel you need a faster FP emulation you should better
664 bool "VFP-format floating point maths"
665 depends on CPU_V6 || CPU_ARM926T
667 Say Y to include VFP support code in the kernel. This is needed
668 if your hardware includes a VFP unit.
670 Please see <file:Documentation/arm/VFP/release-notes.txt> for
671 release notes and additional status information.
673 Say N if your target does not have VFP hardware.
677 menu "Userspace binary formats"
679 source "fs/Kconfig.binfmt"
682 tristate "RISC OS personality"
685 Say Y here to include the kernel code necessary if you want to run
686 Acorn RISC OS/Arthur binaries under Linux. This code is still very
687 experimental; if this sounds frightening, say N and sleep in peace.
688 You can also say M here to compile this support as a module (which
689 will be called arthur).
693 menu "Power management options"
695 source "kernel/power/Kconfig"
698 tristate "Advanced Power Management Emulation"
700 APM is a BIOS specification for saving power using several different
701 techniques. This is mostly useful for battery powered laptops with
702 APM compliant BIOSes. If you say Y here, the system time will be
703 reset after a RESUME operation, the /proc/apm device will provide
704 battery status information, and user-space programs will receive
705 notification of APM "events" (e.g. battery status change).
707 In order to use APM, you will need supporting software. For location
708 and more information, read <file:Documentation/pm.txt> and the
709 Battery Powered Linux mini-HOWTO, available from
710 <http://www.tldp.org/docs.html#howto>.
712 This driver does not spin down disk drives (see the hdparm(8)
713 manpage ("man 8 hdparm") for that), and it doesn't turn off
714 VESA-compliant "green" monitors.
716 Generally, if you don't have a battery in your machine, there isn't
717 much point in using this driver and you should say N. If you get
718 random kernel OOPSes or reboots that don't seem to be related to
719 anything, try disabling/enabling this option (or disabling/enabling
726 menu "Device Drivers"
728 source "drivers/base/Kconfig"
730 source "drivers/connector/Kconfig"
733 source "drivers/mtd/Kconfig"
736 source "drivers/parport/Kconfig"
738 source "drivers/pnp/Kconfig"
740 source "drivers/block/Kconfig"
742 source "drivers/acorn/block/Kconfig"
744 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
745 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
746 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
747 source "drivers/ide/Kconfig"
750 source "drivers/scsi/Kconfig"
752 source "drivers/md/Kconfig"
754 source "drivers/message/fusion/Kconfig"
756 source "drivers/ieee1394/Kconfig"
758 source "drivers/message/i2o/Kconfig"
760 source "drivers/net/Kconfig"
762 source "drivers/isdn/Kconfig"
764 # input before char - char/joystick depends on it. As does USB.
766 source "drivers/input/Kconfig"
768 source "drivers/char/Kconfig"
770 source "drivers/i2c/Kconfig"
772 source "drivers/spi/Kconfig"
774 source "drivers/hwmon/Kconfig"
776 #source "drivers/l3/Kconfig"
778 source "drivers/misc/Kconfig"
780 source "drivers/mfd/Kconfig"
782 source "drivers/media/Kconfig"
784 source "drivers/video/Kconfig"
786 source "sound/Kconfig"
788 source "drivers/usb/Kconfig"
790 source "drivers/mmc/Kconfig"
796 source "arch/arm/oprofile/Kconfig"
798 source "arch/arm/Kconfig.debug"
800 source "security/Kconfig"
802 source "crypto/Kconfig"