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
106 config ARCH_FOOTBRIDGE
110 config ARCH_INTEGRATOR
125 bool "IXP2400/2800-based"
132 Say Y here if you intend to run this kernel on a LinkUp Systems
133 L7200 Software Development Board which uses an ARM720T processor.
134 Information on this board can be obtained at:
136 <http://www.linkupsys.com/>
138 If you have any questions or comments about the Linux kernel port
139 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
161 bool "Samsung S3C2410"
163 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
164 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
165 the Samsung SMDK2410 development board (and derviatives).
176 Say Y here for systems based on one of the Sharp LH7A40X
177 System on a Chip processors. These CPUs include an ARM922T
178 core with a wide array of integrated devices for
179 hand-held and low-power applications.
184 config ARCH_VERSATILE
189 This enables support for ARM Ltd Versatile board.
196 This enables support for ARM Ltd RealView boards.
202 bool "Hynix-HMS720x-based"
205 This enables support for systems based on the Hynix HMS720x
208 bool "Agilent AAEC-2000 based"
211 This enables support for systems based on the Agilent AAEC-2000
215 source "arch/arm/mach-clps711x/Kconfig"
217 source "arch/arm/mach-footbridge/Kconfig"
219 source "arch/arm/mach-integrator/Kconfig"
221 source "arch/arm/mach-iop3xx/Kconfig"
223 source "arch/arm/mach-ixp4xx/Kconfig"
225 source "arch/arm/mach-ixp2000/Kconfig"
227 source "arch/arm/mach-pxa/Kconfig"
229 source "arch/arm/mach-sa1100/Kconfig"
231 source "arch/arm/plat-omap/Kconfig"
233 source "arch/arm/mach-omap1/Kconfig"
235 source "arch/arm/mach-omap2/Kconfig"
237 source "arch/arm/mach-s3c2410/Kconfig"
239 source "arch/arm/mach-lh7a40x/Kconfig"
241 source "arch/arm/mach-imx/Kconfig"
243 source "arch/arm/mach-h720x/Kconfig"
245 source "arch/arm/mach-versatile/Kconfig"
247 source "arch/arm/mach-aaec2000/Kconfig"
249 source "arch/arm/mach-realview/Kconfig"
251 # Definitions to make life easier
255 source arch/arm/mm/Kconfig
257 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
260 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
265 source "arch/arm/common/Kconfig"
267 config FORCE_MAX_ZONEORDER
280 Find out whether you have ISA slots on your motherboard. ISA is the
281 name of a bus system, i.e. the way the CPU talks to the other stuff
282 inside your box. Other bus systems are PCI, EISA, MicroChannel
283 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
284 newer boards don't support it. If you have ISA, say Y, otherwise N.
286 # Select ISA DMA controller support
291 # Select ISA DMA interface
296 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
298 Find out whether you have a PCI motherboard. PCI is the name of a
299 bus system, i.e. the way the CPU talks to the other stuff inside
300 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
301 VESA. If you have PCI, say Y, otherwise N.
303 The PCI-HOWTO, available from
304 <http://www.tldp.org/docs.html#howto>, contains valuable
305 information about which PCI hardware does work under Linux and which
308 # Select the host bridge type
309 config PCI_HOST_VIA82C505
311 depends on PCI && ARCH_SHARK
314 source "drivers/pci/Kconfig"
316 source "drivers/pcmcia/Kconfig"
320 menu "Kernel Features"
323 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
324 depends on EXPERIMENTAL && REALVIEW_MPCORE
326 This enables support for systems with more than one CPU. If you have
327 a system with only one CPU, like most personal computers, say N. If
328 you have a system with more than one CPU, say Y.
330 If you say N here, the kernel will run on single and multiprocessor
331 machines, but will use only one CPU of a multiprocessor machine. If
332 you say Y here, the kernel will run on many, but not all, single
333 processor machines. On a single processor machine, the kernel will
334 run faster if you say N here.
336 See also the <file:Documentation/smp.txt>,
337 <file:Documentation/i386/IO-APIC.txt>,
338 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
339 <http://www.linuxdoc.org/docs.html#howto>.
341 If you don't know what to do here, say N.
344 int "Maximum number of CPUs (2-32)"
350 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
351 depends on SMP && HOTPLUG && EXPERIMENTAL
353 Say Y here to experiment with turning CPUs off and on. CPUs
354 can be controlled through /sys/devices/system/cpu.
357 bool "Use local timer interrupts"
358 depends on SMP && REALVIEW_MPCORE
361 Enable support for local timers on SMP platforms, rather then the
362 legacy IPI broadcast method. Local timers allows the system
363 accounting to be spread across the timer interval, preventing a
364 "thundering herd" at every timer tick.
367 bool "Preemptible Kernel (EXPERIMENTAL)"
368 depends on EXPERIMENTAL
370 This option reduces the latency of the kernel when reacting to
371 real-time or interactive events by allowing a low priority process to
372 be preempted even if it is in kernel mode executing a system call.
373 This allows applications to run more reliably even when the system is
376 Say Y here if you are building a kernel for a desktop, embedded
377 or real-time system. Say N if you are unsure.
380 bool "Dynamic tick timer"
382 Select this option if you want to disable continuous timer ticks
383 and have them programmed to occur as required. This option saves
384 power as the system can remain in idle state for longer.
386 By default dynamic tick is disabled during the boot, and can be
387 manually enabled with:
389 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
391 Alternatively, if you want dynamic tick automatically enabled
392 during boot, pass "dyntick=enable" via the kernel command string.
394 Please note that dynamic tick may affect the accuracy of
395 timekeeping on some platforms depending on the implementation.
396 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
397 to have accurate timekeeping with dynamic tick.
399 config ARCH_DISCONTIGMEM_ENABLE
401 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
403 Say Y to support efficient handling of discontiguous physical memory,
404 for architectures which are either NUMA (Non-Uniform Memory Access)
405 or have huge holes in the physical address space for other reasons.
406 See <file:Documentation/vm/numa> for more.
411 bool "Timer and CPU usage LEDs"
412 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
413 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
414 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
415 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
416 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE
418 If you say Y here, the LEDs on your machine will be used
419 to provide useful information about your current system status.
421 If you are compiling a kernel for a NetWinder or EBSA-285, you will
422 be able to select which LEDs are active using the options below. If
423 you are compiling a kernel for the EBSA-110 or the LART however, the
424 red LED will simply flash regularly to indicate that the system is
425 still functional. It is safe to say Y here if you have a CATS
426 system, but the driver will do nothing.
429 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
430 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
432 default y if ARCH_EBSA110
434 If you say Y here, one of the system LEDs (the green one on the
435 NetWinder, the amber one on the EBSA285, or the red one on the LART)
436 will flash regularly to indicate that the system is still
437 operational. This is mainly useful to kernel hackers who are
438 debugging unstable kernels.
440 The LART uses the same LED for both Timer LED and CPU usage LED
441 functions. You may choose to use both, but the Timer LED function
442 will overrule the CPU usage LED.
445 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
446 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
449 If you say Y here, the red LED will be used to give a good real
450 time indication of CPU usage, by lighting whenever the idle task
451 is not currently executing.
453 The LART uses the same LED for both Timer LED and CPU usage LED
454 functions. You may choose to use both, but the Timer LED function
455 will overrule the CPU usage LED.
457 config ALIGNMENT_TRAP
459 default y if !ARCH_EBSA110
461 ARM processors can not fetch/store information which is not
462 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
463 address divisible by 4. On 32-bit ARM processors, these non-aligned
464 fetch/store instructions will be emulated in software if you say
465 here, which has a severe performance impact. This is necessary for
466 correct operation of some network protocols. With an IP-only
467 configuration it is safe to say N, otherwise say Y.
473 # Compressed boot loader in ROM. Yes, we really want to ask about
474 # TEXT and BSS so we preserve their values in the config files.
475 config ZBOOT_ROM_TEXT
476 hex "Compressed ROM boot loader base address"
479 The physical address at which the ROM-able zImage is to be
480 placed in the target. Platforms which normally make use of
481 ROM-able zImage formats normally set this to a suitable
482 value in their defconfig file.
484 If ZBOOT_ROM is not enabled, this has no effect.
487 hex "Compressed ROM boot loader BSS address"
490 The base address of 64KiB of read/write memory in the target
491 for the ROM-able zImage, which must be available while the
492 decompressor is running. Platforms which normally make use of
493 ROM-able zImage formats normally set this to a suitable
494 value in their defconfig file.
496 If ZBOOT_ROM is not enabled, this has no effect.
499 bool "Compressed boot loader in ROM/flash"
500 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
502 Say Y here if you intend to execute your compressed kernel image
503 (zImage) directly from ROM or flash. If unsure, say N.
506 string "Default kernel command string"
509 On some architectures (EBSA110 and CATS), there is currently no way
510 for the boot loader to pass arguments to the kernel. For these
511 architectures, you should supply some command-line options at build
512 time by entering them here. As a minimum, you should specify the
513 memory size and the root device (e.g., mem=64M root=/dev/nfs).
516 bool "Kernel Execute-In-Place from ROM"
517 depends on !ZBOOT_ROM
519 Execute-In-Place allows the kernel to run from non-volatile storage
520 directly addressable by the CPU, such as NOR flash. This saves RAM
521 space since the text section of the kernel is not loaded from flash
522 to RAM. Read-write sections, such as the data section and stack,
523 are still copied to RAM. The XIP kernel is not compressed since
524 it has to run directly from flash, so it will take more space to
525 store it. The flash address used to link the kernel object files,
526 and for storing it, is configuration dependent. Therefore, if you
527 say Y here, you must know the proper physical address where to
528 store the kernel image depending on your own flash memory usage.
530 Also note that the make target becomes "make xipImage" rather than
531 "make zImage" or "make Image". The final kernel binary to put in
532 ROM memory will be arch/arm/boot/xipImage.
537 hex "XIP Kernel Physical Location"
538 depends on XIP_KERNEL
541 This is the physical address in your flash memory the kernel will
542 be linked for and stored to. This address is dependent on your
547 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
549 menu "CPU Frequency scaling"
551 source "drivers/cpufreq/Kconfig"
553 config CPU_FREQ_SA1100
555 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
558 config CPU_FREQ_SA1110
560 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
563 config CPU_FREQ_INTEGRATOR
564 tristate "CPUfreq driver for ARM Integrator CPUs"
565 depends on ARCH_INTEGRATOR && CPU_FREQ
568 This enables the CPUfreq driver for ARM Integrator CPUs.
570 For details, take a look at <file:Documentation/cpu-freq>.
578 menu "Floating point emulation"
580 comment "At least one emulation must be selected"
583 bool "NWFPE math emulation"
585 Say Y to include the NWFPE floating point emulator in the kernel.
586 This is necessary to run most binaries. Linux does not currently
587 support floating point hardware so you need to say Y here even if
588 your machine has an FPA or floating point co-processor podule.
590 You may say N here if you are going to load the Acorn FPEmulator
594 bool "Support extended precision"
597 Say Y to include 80-bit support in the kernel floating-point
598 emulator. Otherwise, only 32 and 64-bit support is compiled in.
599 Note that gcc does not generate 80-bit operations by default,
600 so in most cases this option only enlarges the size of the
601 floating point emulator without any good reason.
603 You almost surely want to say N here.
606 bool "FastFPE math emulation (EXPERIMENTAL)"
607 depends on !CPU_32v3 && EXPERIMENTAL
609 Say Y here to include the FAST floating point emulator in the kernel.
610 This is an experimental much faster emulator which now also has full
611 precision for the mantissa. It does not support any exceptions.
612 It is very simple, and approximately 3-6 times faster than NWFPE.
614 It should be sufficient for most programs. It may be not suitable
615 for scientific calculations, but you have to check this for yourself.
616 If you do not feel you need a faster FP emulation you should better
620 bool "VFP-format floating point maths"
621 depends on CPU_V6 || CPU_ARM926T
623 Say Y to include VFP support code in the kernel. This is needed
624 if your hardware includes a VFP unit.
626 Please see <file:Documentation/arm/VFP/release-notes.txt> for
627 release notes and additional status information.
629 Say N if your target does not have VFP hardware.
633 menu "Userspace binary formats"
635 source "fs/Kconfig.binfmt"
638 tristate "RISC OS personality"
640 Say Y here to include the kernel code necessary if you want to run
641 Acorn RISC OS/Arthur binaries under Linux. This code is still very
642 experimental; if this sounds frightening, say N and sleep in peace.
643 You can also say M here to compile this support as a module (which
644 will be called arthur).
648 menu "Power management options"
650 source "kernel/power/Kconfig"
653 tristate "Advanced Power Management Emulation"
655 APM is a BIOS specification for saving power using several different
656 techniques. This is mostly useful for battery powered laptops with
657 APM compliant BIOSes. If you say Y here, the system time will be
658 reset after a RESUME operation, the /proc/apm device will provide
659 battery status information, and user-space programs will receive
660 notification of APM "events" (e.g. battery status change).
662 In order to use APM, you will need supporting software. For location
663 and more information, read <file:Documentation/pm.txt> and the
664 Battery Powered Linux mini-HOWTO, available from
665 <http://www.tldp.org/docs.html#howto>.
667 This driver does not spin down disk drives (see the hdparm(8)
668 manpage ("man 8 hdparm") for that), and it doesn't turn off
669 VESA-compliant "green" monitors.
671 Generally, if you don't have a battery in your machine, there isn't
672 much point in using this driver and you should say N. If you get
673 random kernel OOPSes or reboots that don't seem to be related to
674 anything, try disabling/enabling this option (or disabling/enabling
681 menu "Device Drivers"
683 source "drivers/base/Kconfig"
685 source "drivers/connector/Kconfig"
688 source "drivers/mtd/Kconfig"
691 source "drivers/parport/Kconfig"
693 source "drivers/pnp/Kconfig"
695 source "drivers/block/Kconfig"
697 source "drivers/acorn/block/Kconfig"
699 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
700 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
701 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
702 source "drivers/ide/Kconfig"
705 source "drivers/scsi/Kconfig"
707 source "drivers/md/Kconfig"
709 source "drivers/message/fusion/Kconfig"
711 source "drivers/ieee1394/Kconfig"
713 source "drivers/message/i2o/Kconfig"
715 source "drivers/net/Kconfig"
717 source "drivers/isdn/Kconfig"
719 # input before char - char/joystick depends on it. As does USB.
721 source "drivers/input/Kconfig"
723 source "drivers/char/Kconfig"
725 source "drivers/i2c/Kconfig"
727 source "drivers/hwmon/Kconfig"
729 #source "drivers/l3/Kconfig"
731 source "drivers/misc/Kconfig"
733 source "drivers/mfd/Kconfig"
735 source "drivers/media/Kconfig"
737 source "drivers/video/Kconfig"
739 source "sound/Kconfig"
741 source "drivers/usb/Kconfig"
743 source "drivers/mmc/Kconfig"
749 source "arch/arm/oprofile/Kconfig"
751 source "arch/arm/Kconfig.debug"
753 source "security/Kconfig"
755 source "crypto/Kconfig"