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 GENERIC_ISA_DMA
78 prompt "ARM system type"
82 bool "Cirrus-CL-PS7500FE"
87 bool "CLPS711x/EP721x-based"
92 select FOOTBRIDGE_ADDIN
98 This is an evaluation board for the StrongARM processor available
99 from Digital. It has limited hardware on-board, including an onboard
100 Ethernet interface, two PCMCIA sockets, two serial ports and a
106 This enables support for Altera's Excalibur XA10 development board.
107 If you would like to build your kernel to run on one of these boards
108 then you must say 'Y' here. Otherwise say 'N'
110 config ARCH_FOOTBRIDGE
114 config ARCH_INTEGRATOR
129 bool "IXP2400/2800-based"
136 Say Y here if you intend to run this kernel on a LinkUp Systems
137 L7200 Software Development Board which uses an ARM720T processor.
138 Information on this board can be obtained at:
140 <http://www.linkupsys.com/>
142 If you have any questions or comments about the Linux kernel port
143 to this board, send e-mail to <sjhill@cotw.com>.
154 On the Acorn Risc-PC, Linux can support the internal IDE disk and
155 CD-ROM interface, serial and parallel port, and the floppy drive.
160 select ARCH_DISCONTIGMEM_ENABLE
163 bool "Samsung S3C2410"
165 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
166 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
167 the Samsung SMDK2410 development board (and derviatives).
178 Say Y here for systems based on one of the Sharp LH7A40X
179 System on a Chip processors. These CPUs include an ARM922T
180 core with a wide array of integrated devices for
181 hand-held and low-power applications.
186 config ARCH_VERSATILE
191 This enables support for ARM Ltd Versatile board.
197 bool "Hynix-HMS720x-based"
199 This enables support for systems based on the Hynix HMS720x
202 bool "Agilent AAEC-2000 based"
204 This enables support for systems based on the Agilent AAEC-2000
208 source "arch/arm/mach-clps711x/Kconfig"
210 source "arch/arm/mach-epxa10db/Kconfig"
212 source "arch/arm/mach-footbridge/Kconfig"
214 source "arch/arm/mach-integrator/Kconfig"
216 source "arch/arm/mach-iop3xx/Kconfig"
218 source "arch/arm/mach-ixp4xx/Kconfig"
220 source "arch/arm/mach-ixp2000/Kconfig"
222 source "arch/arm/mach-pxa/Kconfig"
224 source "arch/arm/mach-sa1100/Kconfig"
226 source "arch/arm/plat-omap/Kconfig"
228 source "arch/arm/mach-omap1/Kconfig"
230 source "arch/arm/mach-s3c2410/Kconfig"
232 source "arch/arm/mach-lh7a40x/Kconfig"
234 source "arch/arm/mach-imx/Kconfig"
236 source "arch/arm/mach-h720x/Kconfig"
238 source "arch/arm/mach-versatile/Kconfig"
240 source "arch/arm/mach-aaec2000/Kconfig"
242 # Definitions to make life easier
246 source arch/arm/mm/Kconfig
248 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
251 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
256 source "arch/arm/common/Kconfig"
258 config FORCE_MAX_ZONEORDER
271 Find out whether you have ISA slots on your motherboard. ISA is the
272 name of a bus system, i.e. the way the CPU talks to the other stuff
273 inside your box. Other bus systems are PCI, EISA, MicroChannel
274 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
275 newer boards don't support it. If you have ISA, say Y, otherwise N.
285 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
287 Find out whether you have a PCI motherboard. PCI is the name of a
288 bus system, i.e. the way the CPU talks to the other stuff inside
289 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
290 VESA. If you have PCI, say Y, otherwise N.
292 The PCI-HOWTO, available from
293 <http://www.tldp.org/docs.html#howto>, contains valuable
294 information about which PCI hardware does work under Linux and which
297 # Select the host bridge type
298 config PCI_HOST_VIA82C505
300 depends on PCI && ARCH_SHARK
303 source "drivers/pci/Kconfig"
305 source "drivers/pcmcia/Kconfig"
309 menu "Kernel Features"
312 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
313 depends on EXPERIMENTAL && BROKEN #&& n
315 This enables support for systems with more than one CPU. If you have
316 a system with only one CPU, like most personal computers, say N. If
317 you have a system with more than one CPU, say Y.
319 If you say N here, the kernel will run on single and multiprocessor
320 machines, but will use only one CPU of a multiprocessor machine. If
321 you say Y here, the kernel will run on many, but not all, single
322 processor machines. On a single processor machine, the kernel will
323 run faster if you say N here.
325 See also the <file:Documentation/smp.tex>,
326 <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
327 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
328 <http://www.linuxdoc.org/docs.html#howto>.
330 If you don't know what to do here, say N.
333 int "Maximum number of CPUs (2-32)"
339 bool "Preemptible Kernel (EXPERIMENTAL)"
340 depends on EXPERIMENTAL
342 This option reduces the latency of the kernel when reacting to
343 real-time or interactive events by allowing a low priority process to
344 be preempted even if it is in kernel mode executing a system call.
345 This allows applications to run more reliably even when the system is
348 Say Y here if you are building a kernel for a desktop, embedded
349 or real-time system. Say N if you are unsure.
352 bool "Dynamic tick timer"
354 Select this option if you want to disable continuous timer ticks
355 and have them programmed to occur as required. This option saves
356 power as the system can remain in idle state for longer.
358 By default dynamic tick is disabled during the boot, and can be
359 manually enabled with:
361 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
363 Alternatively, if you want dynamic tick automatically enabled
364 during boot, pass "dyntick=enable" via the kernel command string.
366 Please note that dynamic tick may affect the accuracy of
367 timekeeping on some platforms depending on the implementation.
368 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
369 to have accurate timekeeping with dynamic tick.
371 config ARCH_DISCONTIGMEM_ENABLE
373 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
375 Say Y to support efficient handling of discontiguous physical memory,
376 for architectures which are either NUMA (Non-Uniform Memory Access)
377 or have huge holes in the physical address space for other reasons.
378 See <file:Documentation/vm/numa> for more.
383 bool "Timer and CPU usage LEDs"
384 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
385 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
386 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
387 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
388 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE
390 If you say Y here, the LEDs on your machine will be used
391 to provide useful information about your current system status.
393 If you are compiling a kernel for a NetWinder or EBSA-285, you will
394 be able to select which LEDs are active using the options below. If
395 you are compiling a kernel for the EBSA-110 or the LART however, the
396 red LED will simply flash regularly to indicate that the system is
397 still functional. It is safe to say Y here if you have a CATS
398 system, but the driver will do nothing.
401 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
402 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
404 default y if ARCH_EBSA110
406 If you say Y here, one of the system LEDs (the green one on the
407 NetWinder, the amber one on the EBSA285, or the red one on the LART)
408 will flash regularly to indicate that the system is still
409 operational. This is mainly useful to kernel hackers who are
410 debugging unstable kernels.
412 The LART uses the same LED for both Timer LED and CPU usage LED
413 functions. You may choose to use both, but the Timer LED function
414 will overrule the CPU usage LED.
417 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
418 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
421 If you say Y here, the red LED will be used to give a good real
422 time indication of CPU usage, by lighting whenever the idle task
423 is not currently executing.
425 The LART uses the same LED for both Timer LED and CPU usage LED
426 functions. You may choose to use both, but the Timer LED function
427 will overrule the CPU usage LED.
429 config ALIGNMENT_TRAP
431 default y if !ARCH_EBSA110
433 ARM processors can not fetch/store information which is not
434 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
435 address divisible by 4. On 32-bit ARM processors, these non-aligned
436 fetch/store instructions will be emulated in software if you say
437 here, which has a severe performance impact. This is necessary for
438 correct operation of some network protocols. With an IP-only
439 configuration it is safe to say N, otherwise say Y.
445 # Compressed boot loader in ROM. Yes, we really want to ask about
446 # TEXT and BSS so we preserve their values in the config files.
447 config ZBOOT_ROM_TEXT
448 hex "Compressed ROM boot loader base address"
451 The physical address at which the ROM-able zImage is to be
452 placed in the target. Platforms which normally make use of
453 ROM-able zImage formats normally set this to a suitable
454 value in their defconfig file.
456 If ZBOOT_ROM is not enabled, this has no effect.
459 hex "Compressed ROM boot loader BSS address"
462 The base address of 64KiB of read/write memory in the target
463 for the ROM-able zImage, which must be available while the
464 decompressor is running. Platforms which normally make use of
465 ROM-able zImage formats normally set this to a suitable
466 value in their defconfig file.
468 If ZBOOT_ROM is not enabled, this has no effect.
471 bool "Compressed boot loader in ROM/flash"
472 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
474 Say Y here if you intend to execute your compressed kernel image
475 (zImage) directly from ROM or flash. If unsure, say N.
478 string "Default kernel command string"
481 On some architectures (EBSA110 and CATS), there is currently no way
482 for the boot loader to pass arguments to the kernel. For these
483 architectures, you should supply some command-line options at build
484 time by entering them here. As a minimum, you should specify the
485 memory size and the root device (e.g., mem=64M root=/dev/nfs).
488 bool "Kernel Execute-In-Place from ROM"
489 depends on !ZBOOT_ROM
491 Execute-In-Place allows the kernel to run from non-volatile storage
492 directly addressable by the CPU, such as NOR flash. This saves RAM
493 space since the text section of the kernel is not loaded from flash
494 to RAM. Read-write sections, such as the data section and stack,
495 are still copied to RAM. The XIP kernel is not compressed since
496 it has to run directly from flash, so it will take more space to
497 store it. The flash address used to link the kernel object files,
498 and for storing it, is configuration dependent. Therefore, if you
499 say Y here, you must know the proper physical address where to
500 store the kernel image depending on your own flash memory usage.
502 Also note that the make target becomes "make xipImage" rather than
503 "make zImage" or "make Image". The final kernel binary to put in
504 ROM memory will be arch/arm/boot/xipImage.
509 hex "XIP Kernel Physical Location"
510 depends on XIP_KERNEL
513 This is the physical address in your flash memory the kernel will
514 be linked for and stored to. This address is dependent on your
519 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
521 menu "CPU Frequency scaling"
523 source "drivers/cpufreq/Kconfig"
525 config CPU_FREQ_SA1100
527 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
530 config CPU_FREQ_SA1110
532 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
535 config CPU_FREQ_INTEGRATOR
536 tristate "CPUfreq driver for ARM Integrator CPUs"
537 depends on ARCH_INTEGRATOR && CPU_FREQ
540 This enables the CPUfreq driver for ARM Integrator CPUs.
542 For details, take a look at <file:Documentation/cpu-freq>.
550 menu "Floating point emulation"
552 comment "At least one emulation must be selected"
555 bool "NWFPE math emulation"
557 Say Y to include the NWFPE floating point emulator in the kernel.
558 This is necessary to run most binaries. Linux does not currently
559 support floating point hardware so you need to say Y here even if
560 your machine has an FPA or floating point co-processor podule.
562 You may say N here if you are going to load the Acorn FPEmulator
566 bool "Support extended precision"
567 depends on FPE_NWFPE && !CPU_BIG_ENDIAN
569 Say Y to include 80-bit support in the kernel floating-point
570 emulator. Otherwise, only 32 and 64-bit support is compiled in.
571 Note that gcc does not generate 80-bit operations by default,
572 so in most cases this option only enlarges the size of the
573 floating point emulator without any good reason.
575 You almost surely want to say N here.
578 bool "FastFPE math emulation (EXPERIMENTAL)"
579 depends on !CPU_32v3 && EXPERIMENTAL
581 Say Y here to include the FAST floating point emulator in the kernel.
582 This is an experimental much faster emulator which now also has full
583 precision for the mantissa. It does not support any exceptions.
584 It is very simple, and approximately 3-6 times faster than NWFPE.
586 It should be sufficient for most programs. It may be not suitable
587 for scientific calculations, but you have to check this for yourself.
588 If you do not feel you need a faster FP emulation you should better
592 bool "VFP-format floating point maths"
593 depends on CPU_V6 || CPU_ARM926T
595 Say Y to include VFP support code in the kernel. This is needed
596 if your hardware includes a VFP unit.
598 Please see <file:Documentation/arm/VFP/release-notes.txt> for
599 release notes and additional status information.
601 Say N if your target does not have VFP hardware.
605 menu "Userspace binary formats"
607 source "fs/Kconfig.binfmt"
610 tristate "RISC OS personality"
612 Say Y here to include the kernel code necessary if you want to run
613 Acorn RISC OS/Arthur binaries under Linux. This code is still very
614 experimental; if this sounds frightening, say N and sleep in peace.
615 You can also say M here to compile this support as a module (which
616 will be called arthur).
620 menu "Power management options"
623 bool "Power Management support"
625 "Power Management" means that parts of your computer are shut
626 off or put into a power conserving "sleep" mode if they are not
627 being used. There are two competing standards for doing this: APM
628 and ACPI. If you want to use either one, say Y here and then also
629 to the requisite support below.
631 Power Management is most important for battery powered laptop
632 computers; if you have a laptop, check out the Linux Laptop home
633 page on the WWW at <http://www.linux-on-laptops.com/> or
634 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>
635 and the Battery Powered Linux mini-HOWTO, available from
636 <http://www.tldp.org/docs.html#howto>.
639 tristate "Advanced Power Management Emulation"
642 APM is a BIOS specification for saving power using several different
643 techniques. This is mostly useful for battery powered laptops with
644 APM compliant BIOSes. If you say Y here, the system time will be
645 reset after a RESUME operation, the /proc/apm device will provide
646 battery status information, and user-space programs will receive
647 notification of APM "events" (e.g. battery status change).
649 In order to use APM, you will need supporting software. For location
650 and more information, read <file:Documentation/pm.txt> and the
651 Battery Powered Linux mini-HOWTO, available from
652 <http://www.tldp.org/docs.html#howto>.
654 This driver does not spin down disk drives (see the hdparm(8)
655 manpage ("man 8 hdparm") for that), and it doesn't turn off
656 VESA-compliant "green" monitors.
658 Generally, if you don't have a battery in your machine, there isn't
659 much point in using this driver and you should say N. If you get
660 random kernel OOPSes or reboots that don't seem to be related to
661 anything, try disabling/enabling this option (or disabling/enabling
668 menu "Device Drivers"
670 source "drivers/base/Kconfig"
673 source "drivers/mtd/Kconfig"
676 source "drivers/parport/Kconfig"
678 source "drivers/pnp/Kconfig"
680 source "drivers/block/Kconfig"
682 source "drivers/acorn/block/Kconfig"
684 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
685 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
686 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
687 source "drivers/ide/Kconfig"
690 source "drivers/scsi/Kconfig"
692 source "drivers/md/Kconfig"
694 source "drivers/message/fusion/Kconfig"
696 source "drivers/ieee1394/Kconfig"
698 source "drivers/message/i2o/Kconfig"
700 source "drivers/net/Kconfig"
702 source "drivers/isdn/Kconfig"
704 # input before char - char/joystick depends on it. As does USB.
706 source "drivers/input/Kconfig"
708 source "drivers/char/Kconfig"
710 source "drivers/i2c/Kconfig"
712 source "drivers/hwmon/Kconfig"
714 #source "drivers/l3/Kconfig"
716 source "drivers/misc/Kconfig"
718 source "drivers/mfd/Kconfig"
720 source "drivers/media/Kconfig"
722 source "drivers/video/Kconfig"
724 source "sound/Kconfig"
726 source "drivers/usb/Kconfig"
728 source "drivers/mmc/Kconfig"
734 source "arch/arm/oprofile/Kconfig"
736 source "arch/arm/Kconfig.debug"
738 source "security/Kconfig"
740 source "crypto/Kconfig"