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"
86 bool "CLPS711x/EP721x-based"
91 select FOOTBRIDGE_ADDIN
97 This is an evaluation board for the StrongARM processor available
98 from Digital. It has limited hardware on-board, including an onboard
99 Ethernet interface, two PCMCIA sockets, two serial ports and a
102 config ARCH_FOOTBRIDGE
106 config ARCH_INTEGRATOR
121 bool "IXP2400/2800-based"
128 Say Y here if you intend to run this kernel on a LinkUp Systems
129 L7200 Software Development Board which uses an ARM720T processor.
130 Information on this board can be obtained at:
132 <http://www.linkupsys.com/>
134 If you have any questions or comments about the Linux kernel port
135 to this board, send e-mail to <sjhill@cotw.com>.
145 select ARCH_MAY_HAVE_PC_FDC
148 On the Acorn Risc-PC, Linux can support the internal IDE disk and
149 CD-ROM interface, serial and parallel port, and the floppy drive.
154 select ARCH_DISCONTIGMEM_ENABLE
157 bool "Samsung S3C2410"
159 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
160 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
161 the Samsung SMDK2410 development board (and derviatives).
172 Say Y here for systems based on one of the Sharp LH7A40X
173 System on a Chip processors. These CPUs include an ARM922T
174 core with a wide array of integrated devices for
175 hand-held and low-power applications.
180 config ARCH_VERSATILE
186 This enables support for ARM Ltd Versatile board.
193 This enables support for ARM Ltd RealView boards.
199 bool "Hynix-HMS720x-based"
202 This enables support for systems based on the Hynix HMS720x
205 bool "Agilent AAEC-2000 based"
208 This enables support for systems based on the Agilent AAEC-2000
210 config ARCH_AT91RM9200
213 Say Y here if you intend to run this kernel on an AT91RM9200-based
218 source "arch/arm/mach-clps711x/Kconfig"
220 source "arch/arm/mach-footbridge/Kconfig"
222 source "arch/arm/mach-integrator/Kconfig"
224 source "arch/arm/mach-iop3xx/Kconfig"
226 source "arch/arm/mach-ixp4xx/Kconfig"
228 source "arch/arm/mach-ixp2000/Kconfig"
230 source "arch/arm/mach-pxa/Kconfig"
232 source "arch/arm/mach-sa1100/Kconfig"
234 source "arch/arm/plat-omap/Kconfig"
236 source "arch/arm/mach-omap1/Kconfig"
238 source "arch/arm/mach-omap2/Kconfig"
240 source "arch/arm/mach-s3c2410/Kconfig"
242 source "arch/arm/mach-lh7a40x/Kconfig"
244 source "arch/arm/mach-imx/Kconfig"
246 source "arch/arm/mach-h720x/Kconfig"
248 source "arch/arm/mach-versatile/Kconfig"
250 source "arch/arm/mach-aaec2000/Kconfig"
252 source "arch/arm/mach-realview/Kconfig"
254 source "arch/arm/mach-at91rm9200/Kconfig"
256 # Definitions to make life easier
260 source arch/arm/mm/Kconfig
262 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
265 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
270 source "arch/arm/common/Kconfig"
272 config FORCE_MAX_ZONEORDER
285 Find out whether you have ISA slots on your motherboard. ISA is the
286 name of a bus system, i.e. the way the CPU talks to the other stuff
287 inside your box. Other bus systems are PCI, EISA, MicroChannel
288 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
289 newer boards don't support it. If you have ISA, say Y, otherwise N.
291 # Select ISA DMA controller support
296 # Select ISA DMA interface
301 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
303 Find out whether you have a PCI motherboard. PCI is the name of a
304 bus system, i.e. the way the CPU talks to the other stuff inside
305 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
306 VESA. If you have PCI, say Y, otherwise N.
308 The PCI-HOWTO, available from
309 <http://www.tldp.org/docs.html#howto>, contains valuable
310 information about which PCI hardware does work under Linux and which
313 # Select the host bridge type
314 config PCI_HOST_VIA82C505
316 depends on PCI && ARCH_SHARK
319 source "drivers/pci/Kconfig"
321 source "drivers/pcmcia/Kconfig"
325 menu "Kernel Features"
328 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
329 depends on EXPERIMENTAL && REALVIEW_MPCORE
331 This enables support for systems with more than one CPU. If you have
332 a system with only one CPU, like most personal computers, say N. If
333 you have a system with more than one CPU, say Y.
335 If you say N here, the kernel will run on single and multiprocessor
336 machines, but will use only one CPU of a multiprocessor machine. If
337 you say Y here, the kernel will run on many, but not all, single
338 processor machines. On a single processor machine, the kernel will
339 run faster if you say N here.
341 See also the <file:Documentation/smp.txt>,
342 <file:Documentation/i386/IO-APIC.txt>,
343 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
344 <http://www.linuxdoc.org/docs.html#howto>.
346 If you don't know what to do here, say N.
349 int "Maximum number of CPUs (2-32)"
355 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
356 depends on SMP && HOTPLUG && EXPERIMENTAL
358 Say Y here to experiment with turning CPUs off and on. CPUs
359 can be controlled through /sys/devices/system/cpu.
362 bool "Use local timer interrupts"
363 depends on SMP && REALVIEW_MPCORE
366 Enable support for local timers on SMP platforms, rather then the
367 legacy IPI broadcast method. Local timers allows the system
368 accounting to be spread across the timer interval, preventing a
369 "thundering herd" at every timer tick.
372 bool "Preemptible Kernel (EXPERIMENTAL)"
373 depends on EXPERIMENTAL
375 This option reduces the latency of the kernel when reacting to
376 real-time or interactive events by allowing a low priority process to
377 be preempted even if it is in kernel mode executing a system call.
378 This allows applications to run more reliably even when the system is
381 Say Y here if you are building a kernel for a desktop, embedded
382 or real-time system. Say N if you are unsure.
385 bool "Dynamic tick timer"
387 Select this option if you want to disable continuous timer ticks
388 and have them programmed to occur as required. This option saves
389 power as the system can remain in idle state for longer.
391 By default dynamic tick is disabled during the boot, and can be
392 manually enabled with:
394 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
396 Alternatively, if you want dynamic tick automatically enabled
397 during boot, pass "dyntick=enable" via the kernel command string.
399 Please note that dynamic tick may affect the accuracy of
400 timekeeping on some platforms depending on the implementation.
401 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
402 to have accurate timekeeping with dynamic tick.
405 bool "Use the ARM EABI to compile the kernel"
407 This option allows for the kernel to be compiled using the latest
408 ARM ABI (aka EABI). This is only useful if you are using a user
409 space environment that is also compiled with EABI.
411 Since there are major incompatibilities between the legacy ABI and
412 EABI, especially with regard to structure member alignment, this
413 option also changes the kernel syscall calling convention to
414 disambiguate both ABIs and allow for backward compatibility support
415 (selected with CONFIG_OABI_COMPAT).
417 To use this you need GCC version 4.0.0 or later.
420 bool "Allow old ABI binaries to run with this kernel"
424 This option preserves the old syscall interface along with the
425 new (ARM EABI) one. It also provides a compatibility layer to
426 intercept syscalls that have structure arguments which layout
427 in memory differs between the legacy ABI and the new ARM EABI
428 (only for non "thumb" binaries). This option adds a tiny
429 overhead to all syscalls and produces a slightly larger kernel.
430 If you know you'll be using only pure EABI user space then you
431 can say N here. If this option is not selected and you attempt
432 to execute a legacy ABI binary then the result will be
433 UNPREDICTABLE (in fact it can be predicted that it won't work
434 at all). If in doubt say Y.
436 config ARCH_DISCONTIGMEM_ENABLE
438 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
440 Say Y to support efficient handling of discontiguous physical memory,
441 for architectures which are either NUMA (Non-Uniform Memory Access)
442 or have huge holes in the physical address space for other reasons.
443 See <file:Documentation/vm/numa> for more.
448 bool "Timer and CPU usage LEDs"
449 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
450 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
451 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
452 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
453 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
456 If you say Y here, the LEDs on your machine will be used
457 to provide useful information about your current system status.
459 If you are compiling a kernel for a NetWinder or EBSA-285, you will
460 be able to select which LEDs are active using the options below. If
461 you are compiling a kernel for the EBSA-110 or the LART however, the
462 red LED will simply flash regularly to indicate that the system is
463 still functional. It is safe to say Y here if you have a CATS
464 system, but the driver will do nothing.
467 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
468 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
470 default y if ARCH_EBSA110
472 If you say Y here, one of the system LEDs (the green one on the
473 NetWinder, the amber one on the EBSA285, or the red one on the LART)
474 will flash regularly to indicate that the system is still
475 operational. This is mainly useful to kernel hackers who are
476 debugging unstable kernels.
478 The LART uses the same LED for both Timer LED and CPU usage LED
479 functions. You may choose to use both, but the Timer LED function
480 will overrule the CPU usage LED.
483 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
484 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
487 If you say Y here, the red LED will be used to give a good real
488 time indication of CPU usage, by lighting whenever the idle task
489 is not currently executing.
491 The LART uses the same LED for both Timer LED and CPU usage LED
492 functions. You may choose to use both, but the Timer LED function
493 will overrule the CPU usage LED.
495 config ALIGNMENT_TRAP
497 default y if !ARCH_EBSA110
499 ARM processors can not fetch/store information which is not
500 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
501 address divisible by 4. On 32-bit ARM processors, these non-aligned
502 fetch/store instructions will be emulated in software if you say
503 here, which has a severe performance impact. This is necessary for
504 correct operation of some network protocols. With an IP-only
505 configuration it is safe to say N, otherwise say Y.
511 # Compressed boot loader in ROM. Yes, we really want to ask about
512 # TEXT and BSS so we preserve their values in the config files.
513 config ZBOOT_ROM_TEXT
514 hex "Compressed ROM boot loader base address"
517 The physical address at which the ROM-able zImage is to be
518 placed in the target. Platforms which normally make use of
519 ROM-able zImage formats normally set this to a suitable
520 value in their defconfig file.
522 If ZBOOT_ROM is not enabled, this has no effect.
525 hex "Compressed ROM boot loader BSS address"
528 The base address of 64KiB of read/write memory in the target
529 for the ROM-able zImage, which must be available while the
530 decompressor is running. Platforms which normally make use of
531 ROM-able zImage formats normally set this to a suitable
532 value in their defconfig file.
534 If ZBOOT_ROM is not enabled, this has no effect.
537 bool "Compressed boot loader in ROM/flash"
538 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
540 Say Y here if you intend to execute your compressed kernel image
541 (zImage) directly from ROM or flash. If unsure, say N.
544 string "Default kernel command string"
547 On some architectures (EBSA110 and CATS), there is currently no way
548 for the boot loader to pass arguments to the kernel. For these
549 architectures, you should supply some command-line options at build
550 time by entering them here. As a minimum, you should specify the
551 memory size and the root device (e.g., mem=64M root=/dev/nfs).
554 bool "Kernel Execute-In-Place from ROM"
555 depends on !ZBOOT_ROM
557 Execute-In-Place allows the kernel to run from non-volatile storage
558 directly addressable by the CPU, such as NOR flash. This saves RAM
559 space since the text section of the kernel is not loaded from flash
560 to RAM. Read-write sections, such as the data section and stack,
561 are still copied to RAM. The XIP kernel is not compressed since
562 it has to run directly from flash, so it will take more space to
563 store it. The flash address used to link the kernel object files,
564 and for storing it, is configuration dependent. Therefore, if you
565 say Y here, you must know the proper physical address where to
566 store the kernel image depending on your own flash memory usage.
568 Also note that the make target becomes "make xipImage" rather than
569 "make zImage" or "make Image". The final kernel binary to put in
570 ROM memory will be arch/arm/boot/xipImage.
575 hex "XIP Kernel Physical Location"
576 depends on XIP_KERNEL
579 This is the physical address in your flash memory the kernel will
580 be linked for and stored to. This address is dependent on your
585 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
587 menu "CPU Frequency scaling"
589 source "drivers/cpufreq/Kconfig"
591 config CPU_FREQ_SA1100
593 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
596 config CPU_FREQ_SA1110
598 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
601 config CPU_FREQ_INTEGRATOR
602 tristate "CPUfreq driver for ARM Integrator CPUs"
603 depends on ARCH_INTEGRATOR && CPU_FREQ
606 This enables the CPUfreq driver for ARM Integrator CPUs.
608 For details, take a look at <file:Documentation/cpu-freq>.
616 menu "Floating point emulation"
618 comment "At least one emulation must be selected"
621 bool "NWFPE math emulation"
622 depends on !AEABI || OABI_COMPAT
624 Say Y to include the NWFPE floating point emulator in the kernel.
625 This is necessary to run most binaries. Linux does not currently
626 support floating point hardware so you need to say Y here even if
627 your machine has an FPA or floating point co-processor podule.
629 You may say N here if you are going to load the Acorn FPEmulator
633 bool "Support extended precision"
636 Say Y to include 80-bit support in the kernel floating-point
637 emulator. Otherwise, only 32 and 64-bit support is compiled in.
638 Note that gcc does not generate 80-bit operations by default,
639 so in most cases this option only enlarges the size of the
640 floating point emulator without any good reason.
642 You almost surely want to say N here.
645 bool "FastFPE math emulation (EXPERIMENTAL)"
646 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
648 Say Y here to include the FAST floating point emulator in the kernel.
649 This is an experimental much faster emulator which now also has full
650 precision for the mantissa. It does not support any exceptions.
651 It is very simple, and approximately 3-6 times faster than NWFPE.
653 It should be sufficient for most programs. It may be not suitable
654 for scientific calculations, but you have to check this for yourself.
655 If you do not feel you need a faster FP emulation you should better
659 bool "VFP-format floating point maths"
660 depends on CPU_V6 || CPU_ARM926T
662 Say Y to include VFP support code in the kernel. This is needed
663 if your hardware includes a VFP unit.
665 Please see <file:Documentation/arm/VFP/release-notes.txt> for
666 release notes and additional status information.
668 Say N if your target does not have VFP hardware.
672 menu "Userspace binary formats"
674 source "fs/Kconfig.binfmt"
677 tristate "RISC OS personality"
680 Say Y here to include the kernel code necessary if you want to run
681 Acorn RISC OS/Arthur binaries under Linux. This code is still very
682 experimental; if this sounds frightening, say N and sleep in peace.
683 You can also say M here to compile this support as a module (which
684 will be called arthur).
688 menu "Power management options"
690 source "kernel/power/Kconfig"
693 tristate "Advanced Power Management Emulation"
695 APM is a BIOS specification for saving power using several different
696 techniques. This is mostly useful for battery powered laptops with
697 APM compliant BIOSes. If you say Y here, the system time will be
698 reset after a RESUME operation, the /proc/apm device will provide
699 battery status information, and user-space programs will receive
700 notification of APM "events" (e.g. battery status change).
702 In order to use APM, you will need supporting software. For location
703 and more information, read <file:Documentation/pm.txt> and the
704 Battery Powered Linux mini-HOWTO, available from
705 <http://www.tldp.org/docs.html#howto>.
707 This driver does not spin down disk drives (see the hdparm(8)
708 manpage ("man 8 hdparm") for that), and it doesn't turn off
709 VESA-compliant "green" monitors.
711 Generally, if you don't have a battery in your machine, there isn't
712 much point in using this driver and you should say N. If you get
713 random kernel OOPSes or reboots that don't seem to be related to
714 anything, try disabling/enabling this option (or disabling/enabling
721 menu "Device Drivers"
723 source "drivers/base/Kconfig"
725 source "drivers/connector/Kconfig"
728 source "drivers/mtd/Kconfig"
731 source "drivers/parport/Kconfig"
733 source "drivers/pnp/Kconfig"
735 source "drivers/block/Kconfig"
737 source "drivers/acorn/block/Kconfig"
739 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
740 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
741 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
742 source "drivers/ide/Kconfig"
745 source "drivers/scsi/Kconfig"
747 source "drivers/md/Kconfig"
749 source "drivers/message/fusion/Kconfig"
751 source "drivers/ieee1394/Kconfig"
753 source "drivers/message/i2o/Kconfig"
755 source "drivers/net/Kconfig"
757 source "drivers/isdn/Kconfig"
759 # input before char - char/joystick depends on it. As does USB.
761 source "drivers/input/Kconfig"
763 source "drivers/char/Kconfig"
765 source "drivers/i2c/Kconfig"
767 source "drivers/spi/Kconfig"
769 source "drivers/hwmon/Kconfig"
771 #source "drivers/l3/Kconfig"
773 source "drivers/misc/Kconfig"
775 source "drivers/mfd/Kconfig"
777 source "drivers/media/Kconfig"
779 source "drivers/video/Kconfig"
781 source "sound/Kconfig"
783 source "drivers/usb/Kconfig"
785 source "drivers/mmc/Kconfig"
791 source "arch/arm/oprofile/Kconfig"
793 source "arch/arm/Kconfig.debug"
795 source "security/Kconfig"
797 source "crypto/Kconfig"