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-omap2/Kconfig"
244 source "arch/arm/mach-s3c2410/Kconfig"
246 source "arch/arm/mach-lh7a40x/Kconfig"
248 source "arch/arm/mach-imx/Kconfig"
250 source "arch/arm/mach-h720x/Kconfig"
252 source "arch/arm/mach-versatile/Kconfig"
254 source "arch/arm/mach-aaec2000/Kconfig"
256 source "arch/arm/mach-realview/Kconfig"
258 # Definitions to make life easier
262 source arch/arm/mm/Kconfig
264 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
267 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
272 source "arch/arm/common/Kconfig"
274 config FORCE_MAX_ZONEORDER
287 Find out whether you have ISA slots on your motherboard. ISA is the
288 name of a bus system, i.e. the way the CPU talks to the other stuff
289 inside your box. Other bus systems are PCI, EISA, MicroChannel
290 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
291 newer boards don't support it. If you have ISA, say Y, otherwise N.
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.
404 config ARCH_DISCONTIGMEM_ENABLE
406 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
408 Say Y to support efficient handling of discontiguous physical memory,
409 for architectures which are either NUMA (Non-Uniform Memory Access)
410 or have huge holes in the physical address space for other reasons.
411 See <file:Documentation/vm/numa> for more.
416 bool "Timer and CPU usage LEDs"
417 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
418 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
419 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
420 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
421 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE
423 If you say Y here, the LEDs on your machine will be used
424 to provide useful information about your current system status.
426 If you are compiling a kernel for a NetWinder or EBSA-285, you will
427 be able to select which LEDs are active using the options below. If
428 you are compiling a kernel for the EBSA-110 or the LART however, the
429 red LED will simply flash regularly to indicate that the system is
430 still functional. It is safe to say Y here if you have a CATS
431 system, but the driver will do nothing.
434 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
435 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
437 default y if ARCH_EBSA110
439 If you say Y here, one of the system LEDs (the green one on the
440 NetWinder, the amber one on the EBSA285, or the red one on the LART)
441 will flash regularly to indicate that the system is still
442 operational. This is mainly useful to kernel hackers who are
443 debugging unstable kernels.
445 The LART uses the same LED for both Timer LED and CPU usage LED
446 functions. You may choose to use both, but the Timer LED function
447 will overrule the CPU usage LED.
450 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
451 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
454 If you say Y here, the red LED will be used to give a good real
455 time indication of CPU usage, by lighting whenever the idle task
456 is not currently executing.
458 The LART uses the same LED for both Timer LED and CPU usage LED
459 functions. You may choose to use both, but the Timer LED function
460 will overrule the CPU usage LED.
462 config ALIGNMENT_TRAP
464 default y if !ARCH_EBSA110
466 ARM processors can not fetch/store information which is not
467 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
468 address divisible by 4. On 32-bit ARM processors, these non-aligned
469 fetch/store instructions will be emulated in software if you say
470 here, which has a severe performance impact. This is necessary for
471 correct operation of some network protocols. With an IP-only
472 configuration it is safe to say N, otherwise say Y.
478 # Compressed boot loader in ROM. Yes, we really want to ask about
479 # TEXT and BSS so we preserve their values in the config files.
480 config ZBOOT_ROM_TEXT
481 hex "Compressed ROM boot loader base address"
484 The physical address at which the ROM-able zImage is to be
485 placed in the target. Platforms which normally make use of
486 ROM-able zImage formats normally set this to a suitable
487 value in their defconfig file.
489 If ZBOOT_ROM is not enabled, this has no effect.
492 hex "Compressed ROM boot loader BSS address"
495 The base address of 64KiB of read/write memory in the target
496 for the ROM-able zImage, which must be available while the
497 decompressor is running. Platforms which normally make use of
498 ROM-able zImage formats normally set this to a suitable
499 value in their defconfig file.
501 If ZBOOT_ROM is not enabled, this has no effect.
504 bool "Compressed boot loader in ROM/flash"
505 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
507 Say Y here if you intend to execute your compressed kernel image
508 (zImage) directly from ROM or flash. If unsure, say N.
511 string "Default kernel command string"
514 On some architectures (EBSA110 and CATS), there is currently no way
515 for the boot loader to pass arguments to the kernel. For these
516 architectures, you should supply some command-line options at build
517 time by entering them here. As a minimum, you should specify the
518 memory size and the root device (e.g., mem=64M root=/dev/nfs).
521 bool "Kernel Execute-In-Place from ROM"
522 depends on !ZBOOT_ROM
524 Execute-In-Place allows the kernel to run from non-volatile storage
525 directly addressable by the CPU, such as NOR flash. This saves RAM
526 space since the text section of the kernel is not loaded from flash
527 to RAM. Read-write sections, such as the data section and stack,
528 are still copied to RAM. The XIP kernel is not compressed since
529 it has to run directly from flash, so it will take more space to
530 store it. The flash address used to link the kernel object files,
531 and for storing it, is configuration dependent. Therefore, if you
532 say Y here, you must know the proper physical address where to
533 store the kernel image depending on your own flash memory usage.
535 Also note that the make target becomes "make xipImage" rather than
536 "make zImage" or "make Image". The final kernel binary to put in
537 ROM memory will be arch/arm/boot/xipImage.
542 hex "XIP Kernel Physical Location"
543 depends on XIP_KERNEL
546 This is the physical address in your flash memory the kernel will
547 be linked for and stored to. This address is dependent on your
552 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
554 menu "CPU Frequency scaling"
556 source "drivers/cpufreq/Kconfig"
558 config CPU_FREQ_SA1100
560 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
563 config CPU_FREQ_SA1110
565 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
568 config CPU_FREQ_INTEGRATOR
569 tristate "CPUfreq driver for ARM Integrator CPUs"
570 depends on ARCH_INTEGRATOR && CPU_FREQ
573 This enables the CPUfreq driver for ARM Integrator CPUs.
575 For details, take a look at <file:Documentation/cpu-freq>.
583 menu "Floating point emulation"
585 comment "At least one emulation must be selected"
588 bool "NWFPE math emulation"
590 Say Y to include the NWFPE floating point emulator in the kernel.
591 This is necessary to run most binaries. Linux does not currently
592 support floating point hardware so you need to say Y here even if
593 your machine has an FPA or floating point co-processor podule.
595 You may say N here if you are going to load the Acorn FPEmulator
599 bool "Support extended precision"
602 Say Y to include 80-bit support in the kernel floating-point
603 emulator. Otherwise, only 32 and 64-bit support is compiled in.
604 Note that gcc does not generate 80-bit operations by default,
605 so in most cases this option only enlarges the size of the
606 floating point emulator without any good reason.
608 You almost surely want to say N here.
611 bool "FastFPE math emulation (EXPERIMENTAL)"
612 depends on !CPU_32v3 && EXPERIMENTAL
614 Say Y here to include the FAST floating point emulator in the kernel.
615 This is an experimental much faster emulator which now also has full
616 precision for the mantissa. It does not support any exceptions.
617 It is very simple, and approximately 3-6 times faster than NWFPE.
619 It should be sufficient for most programs. It may be not suitable
620 for scientific calculations, but you have to check this for yourself.
621 If you do not feel you need a faster FP emulation you should better
625 bool "VFP-format floating point maths"
626 depends on CPU_V6 || CPU_ARM926T
628 Say Y to include VFP support code in the kernel. This is needed
629 if your hardware includes a VFP unit.
631 Please see <file:Documentation/arm/VFP/release-notes.txt> for
632 release notes and additional status information.
634 Say N if your target does not have VFP hardware.
638 menu "Userspace binary formats"
640 source "fs/Kconfig.binfmt"
643 tristate "RISC OS personality"
645 Say Y here to include the kernel code necessary if you want to run
646 Acorn RISC OS/Arthur binaries under Linux. This code is still very
647 experimental; if this sounds frightening, say N and sleep in peace.
648 You can also say M here to compile this support as a module (which
649 will be called arthur).
653 menu "Power management options"
656 bool "Power Management support"
658 "Power Management" means that parts of your computer are shut
659 off or put into a power conserving "sleep" mode if they are not
660 being used. There are two competing standards for doing this: APM
661 and ACPI. If you want to use either one, say Y here and then also
662 to the requisite support below.
664 Power Management is most important for battery powered laptop
665 computers; if you have a laptop, check out the Linux Laptop home
666 page on the WWW at <http://www.linux-on-laptops.com/> or
667 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>
668 and the Battery Powered Linux mini-HOWTO, available from
669 <http://www.tldp.org/docs.html#howto>.
672 tristate "Advanced Power Management Emulation"
675 APM is a BIOS specification for saving power using several different
676 techniques. This is mostly useful for battery powered laptops with
677 APM compliant BIOSes. If you say Y here, the system time will be
678 reset after a RESUME operation, the /proc/apm device will provide
679 battery status information, and user-space programs will receive
680 notification of APM "events" (e.g. battery status change).
682 In order to use APM, you will need supporting software. For location
683 and more information, read <file:Documentation/pm.txt> and the
684 Battery Powered Linux mini-HOWTO, available from
685 <http://www.tldp.org/docs.html#howto>.
687 This driver does not spin down disk drives (see the hdparm(8)
688 manpage ("man 8 hdparm") for that), and it doesn't turn off
689 VESA-compliant "green" monitors.
691 Generally, if you don't have a battery in your machine, there isn't
692 much point in using this driver and you should say N. If you get
693 random kernel OOPSes or reboots that don't seem to be related to
694 anything, try disabling/enabling this option (or disabling/enabling
701 menu "Device Drivers"
703 source "drivers/base/Kconfig"
705 source "drivers/connector/Kconfig"
708 source "drivers/mtd/Kconfig"
711 source "drivers/parport/Kconfig"
713 source "drivers/pnp/Kconfig"
715 source "drivers/block/Kconfig"
717 source "drivers/acorn/block/Kconfig"
719 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
720 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
721 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
722 source "drivers/ide/Kconfig"
725 source "drivers/scsi/Kconfig"
727 source "drivers/md/Kconfig"
729 source "drivers/message/fusion/Kconfig"
731 source "drivers/ieee1394/Kconfig"
733 source "drivers/message/i2o/Kconfig"
735 source "drivers/net/Kconfig"
737 source "drivers/isdn/Kconfig"
739 # input before char - char/joystick depends on it. As does USB.
741 source "drivers/input/Kconfig"
743 source "drivers/char/Kconfig"
745 source "drivers/i2c/Kconfig"
747 source "drivers/hwmon/Kconfig"
749 #source "drivers/l3/Kconfig"
751 source "drivers/misc/Kconfig"
753 source "drivers/mfd/Kconfig"
755 source "drivers/media/Kconfig"
757 source "drivers/video/Kconfig"
759 source "sound/Kconfig"
761 source "drivers/usb/Kconfig"
763 source "drivers/mmc/Kconfig"
769 source "arch/arm/oprofile/Kconfig"
771 source "arch/arm/Kconfig.debug"
773 source "security/Kconfig"
775 source "crypto/Kconfig"