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.
53 config RWSEM_GENERIC_SPINLOCK
57 config RWSEM_XCHGADD_ALGORITHM
60 config GENERIC_CALIBRATE_DELAY
64 config GENERIC_BUST_SPINLOCK
67 config ARCH_MAY_HAVE_PC_FDC
70 config GENERIC_ISA_DMA
81 prompt "ARM system type"
85 bool "Cirrus-CL-PS7500FE"
90 bool "CLPS711x/EP721x-based"
95 select FOOTBRIDGE_ADDIN
101 This is an evaluation board for the StrongARM processor available
102 from Digital. It has limited hardware on-board, including an onboard
103 Ethernet interface, two PCMCIA sockets, two serial ports and a
109 This enables support for Altera's Excalibur XA10 development board.
110 If you would like to build your kernel to run on one of these boards
111 then you must say 'Y' here. Otherwise say 'N'
113 config ARCH_FOOTBRIDGE
117 config ARCH_INTEGRATOR
132 bool "IXP2400/2800-based"
139 Say Y here if you intend to run this kernel on a LinkUp Systems
140 L7200 Software Development Board which uses an ARM720T processor.
141 Information on this board can be obtained at:
143 <http://www.linkupsys.com/>
145 If you have any questions or comments about the Linux kernel port
146 to this board, send e-mail to <sjhill@cotw.com>.
156 select ARCH_MAY_HAVE_PC_FDC
159 On the Acorn Risc-PC, Linux can support the internal IDE disk and
160 CD-ROM interface, serial and parallel port, and the floppy drive.
165 select ARCH_DISCONTIGMEM_ENABLE
168 bool "Samsung S3C2410"
170 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
171 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
172 the Samsung SMDK2410 development board (and derviatives).
183 Say Y here for systems based on one of the Sharp LH7A40X
184 System on a Chip processors. These CPUs include an ARM922T
185 core with a wide array of integrated devices for
186 hand-held and low-power applications.
191 config ARCH_VERSATILE
196 This enables support for ARM Ltd Versatile board.
203 This enables support for ARM Ltd RealView boards.
209 bool "Hynix-HMS720x-based"
212 This enables support for systems based on the Hynix HMS720x
215 bool "Agilent AAEC-2000 based"
218 This enables support for systems based on the Agilent AAEC-2000
222 source "arch/arm/mach-clps711x/Kconfig"
224 source "arch/arm/mach-epxa10db/Kconfig"
226 source "arch/arm/mach-footbridge/Kconfig"
228 source "arch/arm/mach-integrator/Kconfig"
230 source "arch/arm/mach-iop3xx/Kconfig"
232 source "arch/arm/mach-ixp4xx/Kconfig"
234 source "arch/arm/mach-ixp2000/Kconfig"
236 source "arch/arm/mach-pxa/Kconfig"
238 source "arch/arm/mach-sa1100/Kconfig"
240 source "arch/arm/plat-omap/Kconfig"
242 source "arch/arm/mach-omap1/Kconfig"
244 source "arch/arm/mach-omap2/Kconfig"
246 source "arch/arm/mach-s3c2410/Kconfig"
248 source "arch/arm/mach-lh7a40x/Kconfig"
250 source "arch/arm/mach-imx/Kconfig"
252 source "arch/arm/mach-h720x/Kconfig"
254 source "arch/arm/mach-versatile/Kconfig"
256 source "arch/arm/mach-aaec2000/Kconfig"
258 source "arch/arm/mach-realview/Kconfig"
260 # Definitions to make life easier
264 source arch/arm/mm/Kconfig
266 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
269 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
274 source "arch/arm/common/Kconfig"
276 config FORCE_MAX_ZONEORDER
289 Find out whether you have ISA slots on your motherboard. ISA is the
290 name of a bus system, i.e. the way the CPU talks to the other stuff
291 inside your box. Other bus systems are PCI, EISA, MicroChannel
292 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
293 newer boards don't support it. If you have ISA, say Y, otherwise N.
295 # Select ISA DMA controller support
300 # Select ISA DMA interface
305 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
307 Find out whether you have a PCI motherboard. PCI is the name of a
308 bus system, i.e. the way the CPU talks to the other stuff inside
309 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
310 VESA. If you have PCI, say Y, otherwise N.
312 The PCI-HOWTO, available from
313 <http://www.tldp.org/docs.html#howto>, contains valuable
314 information about which PCI hardware does work under Linux and which
317 # Select the host bridge type
318 config PCI_HOST_VIA82C505
320 depends on PCI && ARCH_SHARK
323 source "drivers/pci/Kconfig"
325 source "drivers/pcmcia/Kconfig"
329 menu "Kernel Features"
332 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
333 depends on EXPERIMENTAL && REALVIEW_MPCORE
335 This enables support for systems with more than one CPU. If you have
336 a system with only one CPU, like most personal computers, say N. If
337 you have a system with more than one CPU, say Y.
339 If you say N here, the kernel will run on single and multiprocessor
340 machines, but will use only one CPU of a multiprocessor machine. If
341 you say Y here, the kernel will run on many, but not all, single
342 processor machines. On a single processor machine, the kernel will
343 run faster if you say N here.
345 See also the <file:Documentation/smp.txt>,
346 <file:Documentation/i386/IO-APIC.txt>,
347 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
348 <http://www.linuxdoc.org/docs.html#howto>.
350 If you don't know what to do here, say N.
353 int "Maximum number of CPUs (2-32)"
359 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
360 depends on SMP && HOTPLUG && EXPERIMENTAL
362 Say Y here to experiment with turning CPUs off and on. CPUs
363 can be controlled through /sys/devices/system/cpu.
366 bool "Use local timer interrupts"
367 depends on SMP && REALVIEW_MPCORE
370 Enable support for local timers on SMP platforms, rather then the
371 legacy IPI broadcast method. Local timers allows the system
372 accounting to be spread across the timer interval, preventing a
373 "thundering herd" at every timer tick.
376 bool "Preemptible Kernel (EXPERIMENTAL)"
377 depends on EXPERIMENTAL
379 This option reduces the latency of the kernel when reacting to
380 real-time or interactive events by allowing a low priority process to
381 be preempted even if it is in kernel mode executing a system call.
382 This allows applications to run more reliably even when the system is
385 Say Y here if you are building a kernel for a desktop, embedded
386 or real-time system. Say N if you are unsure.
389 bool "Dynamic tick timer"
391 Select this option if you want to disable continuous timer ticks
392 and have them programmed to occur as required. This option saves
393 power as the system can remain in idle state for longer.
395 By default dynamic tick is disabled during the boot, and can be
396 manually enabled with:
398 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
400 Alternatively, if you want dynamic tick automatically enabled
401 during boot, pass "dyntick=enable" via the kernel command string.
403 Please note that dynamic tick may affect the accuracy of
404 timekeeping on some platforms depending on the implementation.
405 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
406 to have accurate timekeeping with dynamic tick.
408 config ARCH_DISCONTIGMEM_ENABLE
410 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
412 Say Y to support efficient handling of discontiguous physical memory,
413 for architectures which are either NUMA (Non-Uniform Memory Access)
414 or have huge holes in the physical address space for other reasons.
415 See <file:Documentation/vm/numa> for more.
420 bool "Timer and CPU usage LEDs"
421 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
422 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
423 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
424 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
425 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE
427 If you say Y here, the LEDs on your machine will be used
428 to provide useful information about your current system status.
430 If you are compiling a kernel for a NetWinder or EBSA-285, you will
431 be able to select which LEDs are active using the options below. If
432 you are compiling a kernel for the EBSA-110 or the LART however, the
433 red LED will simply flash regularly to indicate that the system is
434 still functional. It is safe to say Y here if you have a CATS
435 system, but the driver will do nothing.
438 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
439 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
441 default y if ARCH_EBSA110
443 If you say Y here, one of the system LEDs (the green one on the
444 NetWinder, the amber one on the EBSA285, or the red one on the LART)
445 will flash regularly to indicate that the system is still
446 operational. This is mainly useful to kernel hackers who are
447 debugging unstable kernels.
449 The LART uses the same LED for both Timer LED and CPU usage LED
450 functions. You may choose to use both, but the Timer LED function
451 will overrule the CPU usage LED.
454 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
455 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
458 If you say Y here, the red LED will be used to give a good real
459 time indication of CPU usage, by lighting whenever the idle task
460 is not currently executing.
462 The LART uses the same LED for both Timer LED and CPU usage LED
463 functions. You may choose to use both, but the Timer LED function
464 will overrule the CPU usage LED.
466 config ALIGNMENT_TRAP
468 default y if !ARCH_EBSA110
470 ARM processors can not fetch/store information which is not
471 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
472 address divisible by 4. On 32-bit ARM processors, these non-aligned
473 fetch/store instructions will be emulated in software if you say
474 here, which has a severe performance impact. This is necessary for
475 correct operation of some network protocols. With an IP-only
476 configuration it is safe to say N, otherwise say Y.
482 # Compressed boot loader in ROM. Yes, we really want to ask about
483 # TEXT and BSS so we preserve their values in the config files.
484 config ZBOOT_ROM_TEXT
485 hex "Compressed ROM boot loader base address"
488 The physical address at which the ROM-able zImage is to be
489 placed in the target. Platforms which normally make use of
490 ROM-able zImage formats normally set this to a suitable
491 value in their defconfig file.
493 If ZBOOT_ROM is not enabled, this has no effect.
496 hex "Compressed ROM boot loader BSS address"
499 The base address of 64KiB of read/write memory in the target
500 for the ROM-able zImage, which must be available while the
501 decompressor is running. Platforms which normally make use of
502 ROM-able zImage formats normally set this to a suitable
503 value in their defconfig file.
505 If ZBOOT_ROM is not enabled, this has no effect.
508 bool "Compressed boot loader in ROM/flash"
509 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
511 Say Y here if you intend to execute your compressed kernel image
512 (zImage) directly from ROM or flash. If unsure, say N.
515 string "Default kernel command string"
518 On some architectures (EBSA110 and CATS), there is currently no way
519 for the boot loader to pass arguments to the kernel. For these
520 architectures, you should supply some command-line options at build
521 time by entering them here. As a minimum, you should specify the
522 memory size and the root device (e.g., mem=64M root=/dev/nfs).
525 bool "Kernel Execute-In-Place from ROM"
526 depends on !ZBOOT_ROM
528 Execute-In-Place allows the kernel to run from non-volatile storage
529 directly addressable by the CPU, such as NOR flash. This saves RAM
530 space since the text section of the kernel is not loaded from flash
531 to RAM. Read-write sections, such as the data section and stack,
532 are still copied to RAM. The XIP kernel is not compressed since
533 it has to run directly from flash, so it will take more space to
534 store it. The flash address used to link the kernel object files,
535 and for storing it, is configuration dependent. Therefore, if you
536 say Y here, you must know the proper physical address where to
537 store the kernel image depending on your own flash memory usage.
539 Also note that the make target becomes "make xipImage" rather than
540 "make zImage" or "make Image". The final kernel binary to put in
541 ROM memory will be arch/arm/boot/xipImage.
546 hex "XIP Kernel Physical Location"
547 depends on XIP_KERNEL
550 This is the physical address in your flash memory the kernel will
551 be linked for and stored to. This address is dependent on your
556 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
558 menu "CPU Frequency scaling"
560 source "drivers/cpufreq/Kconfig"
562 config CPU_FREQ_SA1100
564 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
567 config CPU_FREQ_SA1110
569 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
572 config CPU_FREQ_INTEGRATOR
573 tristate "CPUfreq driver for ARM Integrator CPUs"
574 depends on ARCH_INTEGRATOR && CPU_FREQ
577 This enables the CPUfreq driver for ARM Integrator CPUs.
579 For details, take a look at <file:Documentation/cpu-freq>.
587 menu "Floating point emulation"
589 comment "At least one emulation must be selected"
592 bool "NWFPE math emulation"
594 Say Y to include the NWFPE floating point emulator in the kernel.
595 This is necessary to run most binaries. Linux does not currently
596 support floating point hardware so you need to say Y here even if
597 your machine has an FPA or floating point co-processor podule.
599 You may say N here if you are going to load the Acorn FPEmulator
603 bool "Support extended precision"
606 Say Y to include 80-bit support in the kernel floating-point
607 emulator. Otherwise, only 32 and 64-bit support is compiled in.
608 Note that gcc does not generate 80-bit operations by default,
609 so in most cases this option only enlarges the size of the
610 floating point emulator without any good reason.
612 You almost surely want to say N here.
615 bool "FastFPE math emulation (EXPERIMENTAL)"
616 depends on !CPU_32v3 && EXPERIMENTAL
618 Say Y here to include the FAST floating point emulator in the kernel.
619 This is an experimental much faster emulator which now also has full
620 precision for the mantissa. It does not support any exceptions.
621 It is very simple, and approximately 3-6 times faster than NWFPE.
623 It should be sufficient for most programs. It may be not suitable
624 for scientific calculations, but you have to check this for yourself.
625 If you do not feel you need a faster FP emulation you should better
629 bool "VFP-format floating point maths"
630 depends on CPU_V6 || CPU_ARM926T
632 Say Y to include VFP support code in the kernel. This is needed
633 if your hardware includes a VFP unit.
635 Please see <file:Documentation/arm/VFP/release-notes.txt> for
636 release notes and additional status information.
638 Say N if your target does not have VFP hardware.
642 menu "Userspace binary formats"
644 source "fs/Kconfig.binfmt"
647 tristate "RISC OS personality"
649 Say Y here to include the kernel code necessary if you want to run
650 Acorn RISC OS/Arthur binaries under Linux. This code is still very
651 experimental; if this sounds frightening, say N and sleep in peace.
652 You can also say M here to compile this support as a module (which
653 will be called arthur).
657 menu "Power management options"
659 source "kernel/power/Kconfig"
662 tristate "Advanced Power Management Emulation"
665 APM is a BIOS specification for saving power using several different
666 techniques. This is mostly useful for battery powered laptops with
667 APM compliant BIOSes. If you say Y here, the system time will be
668 reset after a RESUME operation, the /proc/apm device will provide
669 battery status information, and user-space programs will receive
670 notification of APM "events" (e.g. battery status change).
672 In order to use APM, you will need supporting software. For location
673 and more information, read <file:Documentation/pm.txt> and the
674 Battery Powered Linux mini-HOWTO, available from
675 <http://www.tldp.org/docs.html#howto>.
677 This driver does not spin down disk drives (see the hdparm(8)
678 manpage ("man 8 hdparm") for that), and it doesn't turn off
679 VESA-compliant "green" monitors.
681 Generally, if you don't have a battery in your machine, there isn't
682 much point in using this driver and you should say N. If you get
683 random kernel OOPSes or reboots that don't seem to be related to
684 anything, try disabling/enabling this option (or disabling/enabling
691 menu "Device Drivers"
693 source "drivers/base/Kconfig"
695 source "drivers/connector/Kconfig"
698 source "drivers/mtd/Kconfig"
701 source "drivers/parport/Kconfig"
703 source "drivers/pnp/Kconfig"
705 source "drivers/block/Kconfig"
707 source "drivers/acorn/block/Kconfig"
709 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
710 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
711 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
712 source "drivers/ide/Kconfig"
715 source "drivers/scsi/Kconfig"
717 source "drivers/md/Kconfig"
719 source "drivers/message/fusion/Kconfig"
721 source "drivers/ieee1394/Kconfig"
723 source "drivers/message/i2o/Kconfig"
725 source "drivers/net/Kconfig"
727 source "drivers/isdn/Kconfig"
729 # input before char - char/joystick depends on it. As does USB.
731 source "drivers/input/Kconfig"
733 source "drivers/char/Kconfig"
735 source "drivers/i2c/Kconfig"
737 source "drivers/hwmon/Kconfig"
739 #source "drivers/l3/Kconfig"
741 source "drivers/misc/Kconfig"
743 source "drivers/mfd/Kconfig"
745 source "drivers/media/Kconfig"
747 source "drivers/video/Kconfig"
749 source "sound/Kconfig"
751 source "drivers/usb/Kconfig"
753 source "drivers/mmc/Kconfig"
759 source "arch/arm/oprofile/Kconfig"
761 source "arch/arm/Kconfig.debug"
763 source "security/Kconfig"
765 source "crypto/Kconfig"