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
158 On the Acorn Risc-PC, Linux can support the internal IDE disk and
159 CD-ROM interface, serial and parallel port, and the floppy drive.
164 select ARCH_DISCONTIGMEM_ENABLE
167 bool "Samsung S3C2410"
169 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
170 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
171 the Samsung SMDK2410 development board (and derviatives).
182 Say Y here for systems based on one of the Sharp LH7A40X
183 System on a Chip processors. These CPUs include an ARM922T
184 core with a wide array of integrated devices for
185 hand-held and low-power applications.
190 config ARCH_VERSATILE
195 This enables support for ARM Ltd Versatile board.
202 This enables support for ARM Ltd RealView boards.
208 bool "Hynix-HMS720x-based"
210 This enables support for systems based on the Hynix HMS720x
213 bool "Agilent AAEC-2000 based"
216 This enables support for systems based on the Agilent AAEC-2000
220 source "arch/arm/mach-clps711x/Kconfig"
222 source "arch/arm/mach-epxa10db/Kconfig"
224 source "arch/arm/mach-footbridge/Kconfig"
226 source "arch/arm/mach-integrator/Kconfig"
228 source "arch/arm/mach-iop3xx/Kconfig"
230 source "arch/arm/mach-ixp4xx/Kconfig"
232 source "arch/arm/mach-ixp2000/Kconfig"
234 source "arch/arm/mach-pxa/Kconfig"
236 source "arch/arm/mach-sa1100/Kconfig"
238 source "arch/arm/plat-omap/Kconfig"
240 source "arch/arm/mach-omap1/Kconfig"
242 source "arch/arm/mach-s3c2410/Kconfig"
244 source "arch/arm/mach-lh7a40x/Kconfig"
246 source "arch/arm/mach-imx/Kconfig"
248 source "arch/arm/mach-h720x/Kconfig"
250 source "arch/arm/mach-versatile/Kconfig"
252 source "arch/arm/mach-aaec2000/Kconfig"
254 source "arch/arm/mach-realview/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.
299 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
301 Find out whether you have a PCI motherboard. PCI is the name of a
302 bus system, i.e. the way the CPU talks to the other stuff inside
303 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
304 VESA. If you have PCI, say Y, otherwise N.
306 The PCI-HOWTO, available from
307 <http://www.tldp.org/docs.html#howto>, contains valuable
308 information about which PCI hardware does work under Linux and which
311 # Select the host bridge type
312 config PCI_HOST_VIA82C505
314 depends on PCI && ARCH_SHARK
317 source "drivers/pci/Kconfig"
319 source "drivers/pcmcia/Kconfig"
323 menu "Kernel Features"
326 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
327 depends on EXPERIMENTAL && BROKEN #&& n
329 This enables support for systems with more than one CPU. If you have
330 a system with only one CPU, like most personal computers, say N. If
331 you have a system with more than one CPU, say Y.
333 If you say N here, the kernel will run on single and multiprocessor
334 machines, but will use only one CPU of a multiprocessor machine. If
335 you say Y here, the kernel will run on many, but not all, single
336 processor machines. On a single processor machine, the kernel will
337 run faster if you say N here.
339 See also the <file:Documentation/smp.txt>,
340 <file:Documentation/i386/IO-APIC.txt>,
341 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
342 <http://www.linuxdoc.org/docs.html#howto>.
344 If you don't know what to do here, say N.
347 int "Maximum number of CPUs (2-32)"
353 bool "Preemptible Kernel (EXPERIMENTAL)"
354 depends on EXPERIMENTAL
356 This option reduces the latency of the kernel when reacting to
357 real-time or interactive events by allowing a low priority process to
358 be preempted even if it is in kernel mode executing a system call.
359 This allows applications to run more reliably even when the system is
362 Say Y here if you are building a kernel for a desktop, embedded
363 or real-time system. Say N if you are unsure.
366 bool "Dynamic tick timer"
368 Select this option if you want to disable continuous timer ticks
369 and have them programmed to occur as required. This option saves
370 power as the system can remain in idle state for longer.
372 By default dynamic tick is disabled during the boot, and can be
373 manually enabled with:
375 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
377 Alternatively, if you want dynamic tick automatically enabled
378 during boot, pass "dyntick=enable" via the kernel command string.
380 Please note that dynamic tick may affect the accuracy of
381 timekeeping on some platforms depending on the implementation.
382 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
383 to have accurate timekeeping with dynamic tick.
385 config ARCH_DISCONTIGMEM_ENABLE
387 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
389 Say Y to support efficient handling of discontiguous physical memory,
390 for architectures which are either NUMA (Non-Uniform Memory Access)
391 or have huge holes in the physical address space for other reasons.
392 See <file:Documentation/vm/numa> for more.
397 bool "Timer and CPU usage LEDs"
398 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
399 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
400 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
401 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
402 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE
404 If you say Y here, the LEDs on your machine will be used
405 to provide useful information about your current system status.
407 If you are compiling a kernel for a NetWinder or EBSA-285, you will
408 be able to select which LEDs are active using the options below. If
409 you are compiling a kernel for the EBSA-110 or the LART however, the
410 red LED will simply flash regularly to indicate that the system is
411 still functional. It is safe to say Y here if you have a CATS
412 system, but the driver will do nothing.
415 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
416 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
418 default y if ARCH_EBSA110
420 If you say Y here, one of the system LEDs (the green one on the
421 NetWinder, the amber one on the EBSA285, or the red one on the LART)
422 will flash regularly to indicate that the system is still
423 operational. This is mainly useful to kernel hackers who are
424 debugging unstable kernels.
426 The LART uses the same LED for both Timer LED and CPU usage LED
427 functions. You may choose to use both, but the Timer LED function
428 will overrule the CPU usage LED.
431 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
432 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
435 If you say Y here, the red LED will be used to give a good real
436 time indication of CPU usage, by lighting whenever the idle task
437 is not currently executing.
439 The LART uses the same LED for both Timer LED and CPU usage LED
440 functions. You may choose to use both, but the Timer LED function
441 will overrule the CPU usage LED.
443 config ALIGNMENT_TRAP
445 default y if !ARCH_EBSA110
447 ARM processors can not fetch/store information which is not
448 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
449 address divisible by 4. On 32-bit ARM processors, these non-aligned
450 fetch/store instructions will be emulated in software if you say
451 here, which has a severe performance impact. This is necessary for
452 correct operation of some network protocols. With an IP-only
453 configuration it is safe to say N, otherwise say Y.
459 # Compressed boot loader in ROM. Yes, we really want to ask about
460 # TEXT and BSS so we preserve their values in the config files.
461 config ZBOOT_ROM_TEXT
462 hex "Compressed ROM boot loader base address"
465 The physical address at which the ROM-able zImage is to be
466 placed in the target. Platforms which normally make use of
467 ROM-able zImage formats normally set this to a suitable
468 value in their defconfig file.
470 If ZBOOT_ROM is not enabled, this has no effect.
473 hex "Compressed ROM boot loader BSS address"
476 The base address of 64KiB of read/write memory in the target
477 for the ROM-able zImage, which must be available while the
478 decompressor is running. Platforms which normally make use of
479 ROM-able zImage formats normally set this to a suitable
480 value in their defconfig file.
482 If ZBOOT_ROM is not enabled, this has no effect.
485 bool "Compressed boot loader in ROM/flash"
486 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
488 Say Y here if you intend to execute your compressed kernel image
489 (zImage) directly from ROM or flash. If unsure, say N.
492 string "Default kernel command string"
495 On some architectures (EBSA110 and CATS), there is currently no way
496 for the boot loader to pass arguments to the kernel. For these
497 architectures, you should supply some command-line options at build
498 time by entering them here. As a minimum, you should specify the
499 memory size and the root device (e.g., mem=64M root=/dev/nfs).
502 bool "Kernel Execute-In-Place from ROM"
503 depends on !ZBOOT_ROM
505 Execute-In-Place allows the kernel to run from non-volatile storage
506 directly addressable by the CPU, such as NOR flash. This saves RAM
507 space since the text section of the kernel is not loaded from flash
508 to RAM. Read-write sections, such as the data section and stack,
509 are still copied to RAM. The XIP kernel is not compressed since
510 it has to run directly from flash, so it will take more space to
511 store it. The flash address used to link the kernel object files,
512 and for storing it, is configuration dependent. Therefore, if you
513 say Y here, you must know the proper physical address where to
514 store the kernel image depending on your own flash memory usage.
516 Also note that the make target becomes "make xipImage" rather than
517 "make zImage" or "make Image". The final kernel binary to put in
518 ROM memory will be arch/arm/boot/xipImage.
523 hex "XIP Kernel Physical Location"
524 depends on XIP_KERNEL
527 This is the physical address in your flash memory the kernel will
528 be linked for and stored to. This address is dependent on your
533 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
535 menu "CPU Frequency scaling"
537 source "drivers/cpufreq/Kconfig"
539 config CPU_FREQ_SA1100
541 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
544 config CPU_FREQ_SA1110
546 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
549 config CPU_FREQ_INTEGRATOR
550 tristate "CPUfreq driver for ARM Integrator CPUs"
551 depends on ARCH_INTEGRATOR && CPU_FREQ
554 This enables the CPUfreq driver for ARM Integrator CPUs.
556 For details, take a look at <file:Documentation/cpu-freq>.
564 menu "Floating point emulation"
566 comment "At least one emulation must be selected"
569 bool "NWFPE math emulation"
571 Say Y to include the NWFPE floating point emulator in the kernel.
572 This is necessary to run most binaries. Linux does not currently
573 support floating point hardware so you need to say Y here even if
574 your machine has an FPA or floating point co-processor podule.
576 You may say N here if you are going to load the Acorn FPEmulator
580 bool "Support extended precision"
581 depends on FPE_NWFPE && !CPU_BIG_ENDIAN
583 Say Y to include 80-bit support in the kernel floating-point
584 emulator. Otherwise, only 32 and 64-bit support is compiled in.
585 Note that gcc does not generate 80-bit operations by default,
586 so in most cases this option only enlarges the size of the
587 floating point emulator without any good reason.
589 You almost surely want to say N here.
592 bool "FastFPE math emulation (EXPERIMENTAL)"
593 depends on !CPU_32v3 && EXPERIMENTAL
595 Say Y here to include the FAST floating point emulator in the kernel.
596 This is an experimental much faster emulator which now also has full
597 precision for the mantissa. It does not support any exceptions.
598 It is very simple, and approximately 3-6 times faster than NWFPE.
600 It should be sufficient for most programs. It may be not suitable
601 for scientific calculations, but you have to check this for yourself.
602 If you do not feel you need a faster FP emulation you should better
606 bool "VFP-format floating point maths"
607 depends on CPU_V6 || CPU_ARM926T
609 Say Y to include VFP support code in the kernel. This is needed
610 if your hardware includes a VFP unit.
612 Please see <file:Documentation/arm/VFP/release-notes.txt> for
613 release notes and additional status information.
615 Say N if your target does not have VFP hardware.
619 menu "Userspace binary formats"
621 source "fs/Kconfig.binfmt"
624 tristate "RISC OS personality"
626 Say Y here to include the kernel code necessary if you want to run
627 Acorn RISC OS/Arthur binaries under Linux. This code is still very
628 experimental; if this sounds frightening, say N and sleep in peace.
629 You can also say M here to compile this support as a module (which
630 will be called arthur).
634 menu "Power management options"
637 bool "Power Management support"
639 "Power Management" means that parts of your computer are shut
640 off or put into a power conserving "sleep" mode if they are not
641 being used. There are two competing standards for doing this: APM
642 and ACPI. If you want to use either one, say Y here and then also
643 to the requisite support below.
645 Power Management is most important for battery powered laptop
646 computers; if you have a laptop, check out the Linux Laptop home
647 page on the WWW at <http://www.linux-on-laptops.com/> or
648 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>
649 and the Battery Powered Linux mini-HOWTO, available from
650 <http://www.tldp.org/docs.html#howto>.
653 tristate "Advanced Power Management Emulation"
656 APM is a BIOS specification for saving power using several different
657 techniques. This is mostly useful for battery powered laptops with
658 APM compliant BIOSes. If you say Y here, the system time will be
659 reset after a RESUME operation, the /proc/apm device will provide
660 battery status information, and user-space programs will receive
661 notification of APM "events" (e.g. battery status change).
663 In order to use APM, you will need supporting software. For location
664 and more information, read <file:Documentation/pm.txt> and the
665 Battery Powered Linux mini-HOWTO, available from
666 <http://www.tldp.org/docs.html#howto>.
668 This driver does not spin down disk drives (see the hdparm(8)
669 manpage ("man 8 hdparm") for that), and it doesn't turn off
670 VESA-compliant "green" monitors.
672 Generally, if you don't have a battery in your machine, there isn't
673 much point in using this driver and you should say N. If you get
674 random kernel OOPSes or reboots that don't seem to be related to
675 anything, try disabling/enabling this option (or disabling/enabling
682 menu "Device Drivers"
684 source "drivers/base/Kconfig"
687 source "drivers/mtd/Kconfig"
690 source "drivers/parport/Kconfig"
692 source "drivers/pnp/Kconfig"
694 source "drivers/block/Kconfig"
696 source "drivers/acorn/block/Kconfig"
698 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
699 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
700 || 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"