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 default 0xffff0000 if MMU
78 default DRAM_BASE if REMAP_VECTORS_TO_RAM
81 The base address of exception vectors.
88 prompt "ARM system type"
89 default ARCH_VERSATILE
92 bool "Cirrus-CL-PS7500FE"
96 Support for the Cirrus Logic PS7500FE system-on-a-chip.
99 bool "CLPS711x/EP721x-based"
101 Support for Cirrus Logic 711x/721x based boards.
106 select FOOTBRIDGE_ADDIN
108 Support for Intel's EBSA285 companion chip.
114 This is an evaluation board for the StrongARM processor available
115 from Digital. It has limited hardware on-board, including an
116 Ethernet interface, two PCMCIA sockets, two serial ports and a
119 config ARCH_FOOTBRIDGE
123 Support for systems based on the DC21285 companion chip
124 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
126 config ARCH_INTEGRATOR
131 Support for ARM's Integrator platform.
137 Support for Intel's IOP3XX (XScale) family of processors.
144 Support for Intel's IXP4XX (XScale) family of processors.
147 bool "IXP2400/2800-based"
150 Support for Intel's IXP2400/2800 (XScale) family of processors.
156 Say Y here if you intend to run this kernel on a LinkUp Systems
157 L7200 Software Development Board which uses an ARM720T processor.
158 Information on this board can be obtained at:
160 <http://www.linkupsys.com/>
162 If you have any questions or comments about the Linux kernel port
163 to this board, send e-mail to <sjhill@cotw.com>.
169 Support for Intel's PXA2XX processor line.
176 select ARCH_MAY_HAVE_PC_FDC
179 On the Acorn Risc-PC, Linux can support the internal IDE disk and
180 CD-ROM interface, serial and parallel port, and the floppy drive.
185 select ARCH_DISCONTIGMEM_ENABLE
188 Support for StrongARM 11x0 based boards.
191 bool "Samsung S3C2410"
193 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
194 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
195 the Samsung SMDK2410 development board (and derivatives).
203 Support for the StrongARM based Digital DNARD machine, also known
204 as "Shark" (<http://www.shark-linux.de/shark.html>).
209 Say Y here for systems based on one of the Sharp LH7A40X
210 System on a Chip processors. These CPUs include an ARM922T
211 core with a wide array of integrated devices for
212 hand-held and low-power applications.
217 Support for TI's OMAP platform (OMAP1 and OMAP2).
219 config ARCH_VERSATILE
225 This enables support for ARM Ltd Versatile board.
232 This enables support for ARM Ltd RealView boards.
237 Support for Motorola's i.MX family of processors (MX1, MXL).
240 bool "Hynix-HMS720x-based"
243 This enables support for systems based on the Hynix HMS720x
246 bool "Agilent AAEC-2000 based"
249 This enables support for systems based on the Agilent AAEC-2000
251 config ARCH_AT91RM9200
254 Say Y here if you intend to run this kernel on an Atmel
255 AT91RM9200-based board.
259 source "arch/arm/mach-clps711x/Kconfig"
261 source "arch/arm/mach-footbridge/Kconfig"
263 source "arch/arm/mach-integrator/Kconfig"
265 source "arch/arm/mach-iop3xx/Kconfig"
267 source "arch/arm/mach-ixp4xx/Kconfig"
269 source "arch/arm/mach-ixp2000/Kconfig"
271 source "arch/arm/mach-pxa/Kconfig"
273 source "arch/arm/mach-sa1100/Kconfig"
275 source "arch/arm/plat-omap/Kconfig"
277 source "arch/arm/mach-omap1/Kconfig"
279 source "arch/arm/mach-omap2/Kconfig"
281 source "arch/arm/mach-s3c2410/Kconfig"
283 source "arch/arm/mach-lh7a40x/Kconfig"
285 source "arch/arm/mach-imx/Kconfig"
287 source "arch/arm/mach-h720x/Kconfig"
289 source "arch/arm/mach-versatile/Kconfig"
291 source "arch/arm/mach-aaec2000/Kconfig"
293 source "arch/arm/mach-realview/Kconfig"
295 source "arch/arm/mach-at91rm9200/Kconfig"
297 # Definitions to make life easier
301 source arch/arm/mm/Kconfig
303 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
306 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
311 source "arch/arm/common/Kconfig"
313 config FORCE_MAX_ZONEORDER
326 Find out whether you have ISA slots on your motherboard. ISA is the
327 name of a bus system, i.e. the way the CPU talks to the other stuff
328 inside your box. Other bus systems are PCI, EISA, MicroChannel
329 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
330 newer boards don't support it. If you have ISA, say Y, otherwise N.
332 # Select ISA DMA controller support
337 # Select ISA DMA interface
342 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
344 Find out whether you have a PCI motherboard. PCI is the name of a
345 bus system, i.e. the way the CPU talks to the other stuff inside
346 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
347 VESA. If you have PCI, say Y, otherwise N.
349 The PCI-HOWTO, available from
350 <http://www.tldp.org/docs.html#howto>, contains valuable
351 information about which PCI hardware does work under Linux and which
354 # Select the host bridge type
355 config PCI_HOST_VIA82C505
357 depends on PCI && ARCH_SHARK
360 source "drivers/pci/Kconfig"
362 source "drivers/pcmcia/Kconfig"
366 menu "Kernel Features"
369 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
370 depends on EXPERIMENTAL && REALVIEW_MPCORE
372 This enables support for systems with more than one CPU. If you have
373 a system with only one CPU, like most personal computers, say N. If
374 you have a system with more than one CPU, say Y.
376 If you say N here, the kernel will run on single and multiprocessor
377 machines, but will use only one CPU of a multiprocessor machine. If
378 you say Y here, the kernel will run on many, but not all, single
379 processor machines. On a single processor machine, the kernel will
380 run faster if you say N here.
382 See also the <file:Documentation/smp.txt>,
383 <file:Documentation/i386/IO-APIC.txt>,
384 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
385 <http://www.linuxdoc.org/docs.html#howto>.
387 If you don't know what to do here, say N.
390 int "Maximum number of CPUs (2-32)"
396 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
397 depends on SMP && HOTPLUG && EXPERIMENTAL
399 Say Y here to experiment with turning CPUs off and on. CPUs
400 can be controlled through /sys/devices/system/cpu.
403 bool "Use local timer interrupts"
404 depends on SMP && REALVIEW_MPCORE
407 Enable support for local timers on SMP platforms, rather then the
408 legacy IPI broadcast method. Local timers allows the system
409 accounting to be spread across the timer interval, preventing a
410 "thundering herd" at every timer tick.
413 bool "Preemptible Kernel (EXPERIMENTAL)"
414 depends on EXPERIMENTAL
416 This option reduces the latency of the kernel when reacting to
417 real-time or interactive events by allowing a low priority process to
418 be preempted even if it is in kernel mode executing a system call.
419 This allows applications to run more reliably even when the system is
422 Say Y here if you are building a kernel for a desktop, embedded
423 or real-time system. Say N if you are unsure.
426 bool "Dynamic tick timer"
428 Select this option if you want to disable continuous timer ticks
429 and have them programmed to occur as required. This option saves
430 power as the system can remain in idle state for longer.
432 By default dynamic tick is disabled during the boot, and can be
433 manually enabled with:
435 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
437 Alternatively, if you want dynamic tick automatically enabled
438 during boot, pass "dyntick=enable" via the kernel command string.
440 Please note that dynamic tick may affect the accuracy of
441 timekeeping on some platforms depending on the implementation.
442 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
443 to have accurate timekeeping with dynamic tick.
446 bool "Use the ARM EABI to compile the kernel"
448 This option allows for the kernel to be compiled using the latest
449 ARM ABI (aka EABI). This is only useful if you are using a user
450 space environment that is also compiled with EABI.
452 Since there are major incompatibilities between the legacy ABI and
453 EABI, especially with regard to structure member alignment, this
454 option also changes the kernel syscall calling convention to
455 disambiguate both ABIs and allow for backward compatibility support
456 (selected with CONFIG_OABI_COMPAT).
458 To use this you need GCC version 4.0.0 or later.
461 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
462 depends on AEABI && EXPERIMENTAL
465 This option preserves the old syscall interface along with the
466 new (ARM EABI) one. It also provides a compatibility layer to
467 intercept syscalls that have structure arguments which layout
468 in memory differs between the legacy ABI and the new ARM EABI
469 (only for non "thumb" binaries). This option adds a tiny
470 overhead to all syscalls and produces a slightly larger kernel.
471 If you know you'll be using only pure EABI user space then you
472 can say N here. If this option is not selected and you attempt
473 to execute a legacy ABI binary then the result will be
474 UNPREDICTABLE (in fact it can be predicted that it won't work
475 at all). If in doubt say Y.
477 config ARCH_DISCONTIGMEM_ENABLE
479 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
481 Say Y to support efficient handling of discontiguous physical memory,
482 for architectures which are either NUMA (Non-Uniform Memory Access)
483 or have huge holes in the physical address space for other reasons.
484 See <file:Documentation/vm/numa> for more.
489 bool "Timer and CPU usage LEDs"
490 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
491 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
492 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
493 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
494 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
497 If you say Y here, the LEDs on your machine will be used
498 to provide useful information about your current system status.
500 If you are compiling a kernel for a NetWinder or EBSA-285, you will
501 be able to select which LEDs are active using the options below. If
502 you are compiling a kernel for the EBSA-110 or the LART however, the
503 red LED will simply flash regularly to indicate that the system is
504 still functional. It is safe to say Y here if you have a CATS
505 system, but the driver will do nothing.
508 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
509 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
511 default y if ARCH_EBSA110
513 If you say Y here, one of the system LEDs (the green one on the
514 NetWinder, the amber one on the EBSA285, or the red one on the LART)
515 will flash regularly to indicate that the system is still
516 operational. This is mainly useful to kernel hackers who are
517 debugging unstable kernels.
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.
524 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
525 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
528 If you say Y here, the red LED will be used to give a good real
529 time indication of CPU usage, by lighting whenever the idle task
530 is not currently executing.
532 The LART uses the same LED for both Timer LED and CPU usage LED
533 functions. You may choose to use both, but the Timer LED function
534 will overrule the CPU usage LED.
536 config ALIGNMENT_TRAP
538 default y if !ARCH_EBSA110
540 ARM processors can not fetch/store information which is not
541 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
542 address divisible by 4. On 32-bit ARM processors, these non-aligned
543 fetch/store instructions will be emulated in software if you say
544 here, which has a severe performance impact. This is necessary for
545 correct operation of some network protocols. With an IP-only
546 configuration it is safe to say N, otherwise say Y.
552 # Compressed boot loader in ROM. Yes, we really want to ask about
553 # TEXT and BSS so we preserve their values in the config files.
554 config ZBOOT_ROM_TEXT
555 hex "Compressed ROM boot loader base address"
558 The physical address at which the ROM-able zImage is to be
559 placed in the target. Platforms which normally make use of
560 ROM-able zImage formats normally set this to a suitable
561 value in their defconfig file.
563 If ZBOOT_ROM is not enabled, this has no effect.
566 hex "Compressed ROM boot loader BSS address"
569 The base address of 64KiB of read/write memory in the target
570 for the ROM-able zImage, which must be available while the
571 decompressor is running. Platforms which normally make use of
572 ROM-able zImage formats normally set this to a suitable
573 value in their defconfig file.
575 If ZBOOT_ROM is not enabled, this has no effect.
578 bool "Compressed boot loader in ROM/flash"
579 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
581 Say Y here if you intend to execute your compressed kernel image
582 (zImage) directly from ROM or flash. If unsure, say N.
585 string "Default kernel command string"
588 On some architectures (EBSA110 and CATS), there is currently no way
589 for the boot loader to pass arguments to the kernel. For these
590 architectures, you should supply some command-line options at build
591 time by entering them here. As a minimum, you should specify the
592 memory size and the root device (e.g., mem=64M root=/dev/nfs).
595 bool "Kernel Execute-In-Place from ROM"
596 depends on !ZBOOT_ROM
598 Execute-In-Place allows the kernel to run from non-volatile storage
599 directly addressable by the CPU, such as NOR flash. This saves RAM
600 space since the text section of the kernel is not loaded from flash
601 to RAM. Read-write sections, such as the data section and stack,
602 are still copied to RAM. The XIP kernel is not compressed since
603 it has to run directly from flash, so it will take more space to
604 store it. The flash address used to link the kernel object files,
605 and for storing it, is configuration dependent. Therefore, if you
606 say Y here, you must know the proper physical address where to
607 store the kernel image depending on your own flash memory usage.
609 Also note that the make target becomes "make xipImage" rather than
610 "make zImage" or "make Image". The final kernel binary to put in
611 ROM memory will be arch/arm/boot/xipImage.
616 hex "XIP Kernel Physical Location"
617 depends on XIP_KERNEL
620 This is the physical address in your flash memory the kernel will
621 be linked for and stored to. This address is dependent on your
626 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
628 menu "CPU Frequency scaling"
630 source "drivers/cpufreq/Kconfig"
632 config CPU_FREQ_SA1100
634 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
637 config CPU_FREQ_SA1110
639 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
642 config CPU_FREQ_INTEGRATOR
643 tristate "CPUfreq driver for ARM Integrator CPUs"
644 depends on ARCH_INTEGRATOR && CPU_FREQ
647 This enables the CPUfreq driver for ARM Integrator CPUs.
649 For details, take a look at <file:Documentation/cpu-freq>.
657 menu "Floating point emulation"
659 comment "At least one emulation must be selected"
662 bool "NWFPE math emulation"
663 depends on !AEABI || OABI_COMPAT
665 Say Y to include the NWFPE floating point emulator in the kernel.
666 This is necessary to run most binaries. Linux does not currently
667 support floating point hardware so you need to say Y here even if
668 your machine has an FPA or floating point co-processor podule.
670 You may say N here if you are going to load the Acorn FPEmulator
674 bool "Support extended precision"
677 Say Y to include 80-bit support in the kernel floating-point
678 emulator. Otherwise, only 32 and 64-bit support is compiled in.
679 Note that gcc does not generate 80-bit operations by default,
680 so in most cases this option only enlarges the size of the
681 floating point emulator without any good reason.
683 You almost surely want to say N here.
686 bool "FastFPE math emulation (EXPERIMENTAL)"
687 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
689 Say Y here to include the FAST floating point emulator in the kernel.
690 This is an experimental much faster emulator which now also has full
691 precision for the mantissa. It does not support any exceptions.
692 It is very simple, and approximately 3-6 times faster than NWFPE.
694 It should be sufficient for most programs. It may be not suitable
695 for scientific calculations, but you have to check this for yourself.
696 If you do not feel you need a faster FP emulation you should better
700 bool "VFP-format floating point maths"
701 depends on CPU_V6 || CPU_ARM926T
703 Say Y to include VFP support code in the kernel. This is needed
704 if your hardware includes a VFP unit.
706 Please see <file:Documentation/arm/VFP/release-notes.txt> for
707 release notes and additional status information.
709 Say N if your target does not have VFP hardware.
713 menu "Userspace binary formats"
715 source "fs/Kconfig.binfmt"
718 tristate "RISC OS personality"
721 Say Y here to include the kernel code necessary if you want to run
722 Acorn RISC OS/Arthur binaries under Linux. This code is still very
723 experimental; if this sounds frightening, say N and sleep in peace.
724 You can also say M here to compile this support as a module (which
725 will be called arthur).
729 menu "Power management options"
731 source "kernel/power/Kconfig"
734 tristate "Advanced Power Management Emulation"
736 APM is a BIOS specification for saving power using several different
737 techniques. This is mostly useful for battery powered laptops with
738 APM compliant BIOSes. If you say Y here, the system time will be
739 reset after a RESUME operation, the /proc/apm device will provide
740 battery status information, and user-space programs will receive
741 notification of APM "events" (e.g. battery status change).
743 In order to use APM, you will need supporting software. For location
744 and more information, read <file:Documentation/pm.txt> and the
745 Battery Powered Linux mini-HOWTO, available from
746 <http://www.tldp.org/docs.html#howto>.
748 This driver does not spin down disk drives (see the hdparm(8)
749 manpage ("man 8 hdparm") for that), and it doesn't turn off
750 VESA-compliant "green" monitors.
752 Generally, if you don't have a battery in your machine, there isn't
753 much point in using this driver and you should say N. If you get
754 random kernel OOPSes or reboots that don't seem to be related to
755 anything, try disabling/enabling this option (or disabling/enabling
762 menu "Device Drivers"
764 source "drivers/base/Kconfig"
766 source "drivers/connector/Kconfig"
769 source "drivers/mtd/Kconfig"
772 source "drivers/parport/Kconfig"
774 source "drivers/pnp/Kconfig"
776 source "drivers/block/Kconfig"
778 source "drivers/acorn/block/Kconfig"
780 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
781 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
782 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
783 source "drivers/ide/Kconfig"
786 source "drivers/scsi/Kconfig"
788 source "drivers/md/Kconfig"
790 source "drivers/message/fusion/Kconfig"
792 source "drivers/ieee1394/Kconfig"
794 source "drivers/message/i2o/Kconfig"
796 source "drivers/net/Kconfig"
798 source "drivers/isdn/Kconfig"
800 # input before char - char/joystick depends on it. As does USB.
802 source "drivers/input/Kconfig"
804 source "drivers/char/Kconfig"
806 source "drivers/i2c/Kconfig"
808 source "drivers/spi/Kconfig"
810 source "drivers/w1/Kconfig"
812 source "drivers/hwmon/Kconfig"
814 #source "drivers/l3/Kconfig"
816 source "drivers/misc/Kconfig"
818 source "drivers/mfd/Kconfig"
820 source "drivers/media/Kconfig"
822 source "drivers/video/Kconfig"
824 source "sound/Kconfig"
826 source "drivers/usb/Kconfig"
828 source "drivers/mmc/Kconfig"
834 source "arch/arm/oprofile/Kconfig"
836 source "arch/arm/Kconfig.debug"
838 source "security/Kconfig"
840 source "crypto/Kconfig"