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.
201 bool "Hynix-HMS720x-based"
203 This enables support for systems based on the Hynix HMS720x
206 bool "Agilent AAEC-2000 based"
208 This enables support for systems based on the Agilent AAEC-2000
212 source "arch/arm/mach-clps711x/Kconfig"
214 source "arch/arm/mach-epxa10db/Kconfig"
216 source "arch/arm/mach-footbridge/Kconfig"
218 source "arch/arm/mach-integrator/Kconfig"
220 source "arch/arm/mach-iop3xx/Kconfig"
222 source "arch/arm/mach-ixp4xx/Kconfig"
224 source "arch/arm/mach-ixp2000/Kconfig"
226 source "arch/arm/mach-pxa/Kconfig"
228 source "arch/arm/mach-sa1100/Kconfig"
230 source "arch/arm/plat-omap/Kconfig"
232 source "arch/arm/mach-omap1/Kconfig"
234 source "arch/arm/mach-s3c2410/Kconfig"
236 source "arch/arm/mach-lh7a40x/Kconfig"
238 source "arch/arm/mach-imx/Kconfig"
240 source "arch/arm/mach-h720x/Kconfig"
242 source "arch/arm/mach-versatile/Kconfig"
244 source "arch/arm/mach-aaec2000/Kconfig"
246 # Definitions to make life easier
250 source arch/arm/mm/Kconfig
252 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
255 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
260 source "arch/arm/common/Kconfig"
262 config FORCE_MAX_ZONEORDER
275 Find out whether you have ISA slots on your motherboard. ISA is the
276 name of a bus system, i.e. the way the CPU talks to the other stuff
277 inside your box. Other bus systems are PCI, EISA, MicroChannel
278 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
279 newer boards don't support it. If you have ISA, say Y, otherwise N.
289 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
291 Find out whether you have a PCI motherboard. PCI is the name of a
292 bus system, i.e. the way the CPU talks to the other stuff inside
293 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
294 VESA. If you have PCI, say Y, otherwise N.
296 The PCI-HOWTO, available from
297 <http://www.tldp.org/docs.html#howto>, contains valuable
298 information about which PCI hardware does work under Linux and which
301 # Select the host bridge type
302 config PCI_HOST_VIA82C505
304 depends on PCI && ARCH_SHARK
307 source "drivers/pci/Kconfig"
309 source "drivers/pcmcia/Kconfig"
313 menu "Kernel Features"
316 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
317 depends on EXPERIMENTAL && BROKEN #&& n
319 This enables support for systems with more than one CPU. If you have
320 a system with only one CPU, like most personal computers, say N. If
321 you have a system with more than one CPU, say Y.
323 If you say N here, the kernel will run on single and multiprocessor
324 machines, but will use only one CPU of a multiprocessor machine. If
325 you say Y here, the kernel will run on many, but not all, single
326 processor machines. On a single processor machine, the kernel will
327 run faster if you say N here.
329 See also the <file:Documentation/smp.txt>,
330 <file:Documentation/i386/IO-APIC.txt>,
331 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
332 <http://www.linuxdoc.org/docs.html#howto>.
334 If you don't know what to do here, say N.
337 int "Maximum number of CPUs (2-32)"
343 bool "Preemptible Kernel (EXPERIMENTAL)"
344 depends on EXPERIMENTAL
346 This option reduces the latency of the kernel when reacting to
347 real-time or interactive events by allowing a low priority process to
348 be preempted even if it is in kernel mode executing a system call.
349 This allows applications to run more reliably even when the system is
352 Say Y here if you are building a kernel for a desktop, embedded
353 or real-time system. Say N if you are unsure.
356 bool "Dynamic tick timer"
358 Select this option if you want to disable continuous timer ticks
359 and have them programmed to occur as required. This option saves
360 power as the system can remain in idle state for longer.
362 By default dynamic tick is disabled during the boot, and can be
363 manually enabled with:
365 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
367 Alternatively, if you want dynamic tick automatically enabled
368 during boot, pass "dyntick=enable" via the kernel command string.
370 Please note that dynamic tick may affect the accuracy of
371 timekeeping on some platforms depending on the implementation.
372 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
373 to have accurate timekeeping with dynamic tick.
375 config ARCH_DISCONTIGMEM_ENABLE
377 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
379 Say Y to support efficient handling of discontiguous physical memory,
380 for architectures which are either NUMA (Non-Uniform Memory Access)
381 or have huge holes in the physical address space for other reasons.
382 See <file:Documentation/vm/numa> for more.
387 bool "Timer and CPU usage LEDs"
388 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
389 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
390 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
391 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
392 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE
394 If you say Y here, the LEDs on your machine will be used
395 to provide useful information about your current system status.
397 If you are compiling a kernel for a NetWinder or EBSA-285, you will
398 be able to select which LEDs are active using the options below. If
399 you are compiling a kernel for the EBSA-110 or the LART however, the
400 red LED will simply flash regularly to indicate that the system is
401 still functional. It is safe to say Y here if you have a CATS
402 system, but the driver will do nothing.
405 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
406 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
408 default y if ARCH_EBSA110
410 If you say Y here, one of the system LEDs (the green one on the
411 NetWinder, the amber one on the EBSA285, or the red one on the LART)
412 will flash regularly to indicate that the system is still
413 operational. This is mainly useful to kernel hackers who are
414 debugging unstable kernels.
416 The LART uses the same LED for both Timer LED and CPU usage LED
417 functions. You may choose to use both, but the Timer LED function
418 will overrule the CPU usage LED.
421 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
422 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
425 If you say Y here, the red LED will be used to give a good real
426 time indication of CPU usage, by lighting whenever the idle task
427 is not currently executing.
429 The LART uses the same LED for both Timer LED and CPU usage LED
430 functions. You may choose to use both, but the Timer LED function
431 will overrule the CPU usage LED.
433 config ALIGNMENT_TRAP
435 default y if !ARCH_EBSA110
437 ARM processors can not fetch/store information which is not
438 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
439 address divisible by 4. On 32-bit ARM processors, these non-aligned
440 fetch/store instructions will be emulated in software if you say
441 here, which has a severe performance impact. This is necessary for
442 correct operation of some network protocols. With an IP-only
443 configuration it is safe to say N, otherwise say Y.
449 # Compressed boot loader in ROM. Yes, we really want to ask about
450 # TEXT and BSS so we preserve their values in the config files.
451 config ZBOOT_ROM_TEXT
452 hex "Compressed ROM boot loader base address"
455 The physical address at which the ROM-able zImage is to be
456 placed in the target. Platforms which normally make use of
457 ROM-able zImage formats normally set this to a suitable
458 value in their defconfig file.
460 If ZBOOT_ROM is not enabled, this has no effect.
463 hex "Compressed ROM boot loader BSS address"
466 The base address of 64KiB of read/write memory in the target
467 for the ROM-able zImage, which must be available while the
468 decompressor is running. Platforms which normally make use of
469 ROM-able zImage formats normally set this to a suitable
470 value in their defconfig file.
472 If ZBOOT_ROM is not enabled, this has no effect.
475 bool "Compressed boot loader in ROM/flash"
476 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
478 Say Y here if you intend to execute your compressed kernel image
479 (zImage) directly from ROM or flash. If unsure, say N.
482 string "Default kernel command string"
485 On some architectures (EBSA110 and CATS), there is currently no way
486 for the boot loader to pass arguments to the kernel. For these
487 architectures, you should supply some command-line options at build
488 time by entering them here. As a minimum, you should specify the
489 memory size and the root device (e.g., mem=64M root=/dev/nfs).
492 bool "Kernel Execute-In-Place from ROM"
493 depends on !ZBOOT_ROM
495 Execute-In-Place allows the kernel to run from non-volatile storage
496 directly addressable by the CPU, such as NOR flash. This saves RAM
497 space since the text section of the kernel is not loaded from flash
498 to RAM. Read-write sections, such as the data section and stack,
499 are still copied to RAM. The XIP kernel is not compressed since
500 it has to run directly from flash, so it will take more space to
501 store it. The flash address used to link the kernel object files,
502 and for storing it, is configuration dependent. Therefore, if you
503 say Y here, you must know the proper physical address where to
504 store the kernel image depending on your own flash memory usage.
506 Also note that the make target becomes "make xipImage" rather than
507 "make zImage" or "make Image". The final kernel binary to put in
508 ROM memory will be arch/arm/boot/xipImage.
513 hex "XIP Kernel Physical Location"
514 depends on XIP_KERNEL
517 This is the physical address in your flash memory the kernel will
518 be linked for and stored to. This address is dependent on your
523 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
525 menu "CPU Frequency scaling"
527 source "drivers/cpufreq/Kconfig"
529 config CPU_FREQ_SA1100
531 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
534 config CPU_FREQ_SA1110
536 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
539 config CPU_FREQ_INTEGRATOR
540 tristate "CPUfreq driver for ARM Integrator CPUs"
541 depends on ARCH_INTEGRATOR && CPU_FREQ
544 This enables the CPUfreq driver for ARM Integrator CPUs.
546 For details, take a look at <file:Documentation/cpu-freq>.
554 menu "Floating point emulation"
556 comment "At least one emulation must be selected"
559 bool "NWFPE math emulation"
561 Say Y to include the NWFPE floating point emulator in the kernel.
562 This is necessary to run most binaries. Linux does not currently
563 support floating point hardware so you need to say Y here even if
564 your machine has an FPA or floating point co-processor podule.
566 You may say N here if you are going to load the Acorn FPEmulator
570 bool "Support extended precision"
571 depends on FPE_NWFPE && !CPU_BIG_ENDIAN
573 Say Y to include 80-bit support in the kernel floating-point
574 emulator. Otherwise, only 32 and 64-bit support is compiled in.
575 Note that gcc does not generate 80-bit operations by default,
576 so in most cases this option only enlarges the size of the
577 floating point emulator without any good reason.
579 You almost surely want to say N here.
582 bool "FastFPE math emulation (EXPERIMENTAL)"
583 depends on !CPU_32v3 && EXPERIMENTAL
585 Say Y here to include the FAST floating point emulator in the kernel.
586 This is an experimental much faster emulator which now also has full
587 precision for the mantissa. It does not support any exceptions.
588 It is very simple, and approximately 3-6 times faster than NWFPE.
590 It should be sufficient for most programs. It may be not suitable
591 for scientific calculations, but you have to check this for yourself.
592 If you do not feel you need a faster FP emulation you should better
596 bool "VFP-format floating point maths"
597 depends on CPU_V6 || CPU_ARM926T
599 Say Y to include VFP support code in the kernel. This is needed
600 if your hardware includes a VFP unit.
602 Please see <file:Documentation/arm/VFP/release-notes.txt> for
603 release notes and additional status information.
605 Say N if your target does not have VFP hardware.
609 menu "Userspace binary formats"
611 source "fs/Kconfig.binfmt"
614 tristate "RISC OS personality"
616 Say Y here to include the kernel code necessary if you want to run
617 Acorn RISC OS/Arthur binaries under Linux. This code is still very
618 experimental; if this sounds frightening, say N and sleep in peace.
619 You can also say M here to compile this support as a module (which
620 will be called arthur).
624 menu "Power management options"
627 bool "Power Management support"
629 "Power Management" means that parts of your computer are shut
630 off or put into a power conserving "sleep" mode if they are not
631 being used. There are two competing standards for doing this: APM
632 and ACPI. If you want to use either one, say Y here and then also
633 to the requisite support below.
635 Power Management is most important for battery powered laptop
636 computers; if you have a laptop, check out the Linux Laptop home
637 page on the WWW at <http://www.linux-on-laptops.com/> or
638 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>
639 and the Battery Powered Linux mini-HOWTO, available from
640 <http://www.tldp.org/docs.html#howto>.
643 tristate "Advanced Power Management Emulation"
646 APM is a BIOS specification for saving power using several different
647 techniques. This is mostly useful for battery powered laptops with
648 APM compliant BIOSes. If you say Y here, the system time will be
649 reset after a RESUME operation, the /proc/apm device will provide
650 battery status information, and user-space programs will receive
651 notification of APM "events" (e.g. battery status change).
653 In order to use APM, you will need supporting software. For location
654 and more information, read <file:Documentation/pm.txt> and the
655 Battery Powered Linux mini-HOWTO, available from
656 <http://www.tldp.org/docs.html#howto>.
658 This driver does not spin down disk drives (see the hdparm(8)
659 manpage ("man 8 hdparm") for that), and it doesn't turn off
660 VESA-compliant "green" monitors.
662 Generally, if you don't have a battery in your machine, there isn't
663 much point in using this driver and you should say N. If you get
664 random kernel OOPSes or reboots that don't seem to be related to
665 anything, try disabling/enabling this option (or disabling/enabling
672 menu "Device Drivers"
674 source "drivers/base/Kconfig"
677 source "drivers/mtd/Kconfig"
680 source "drivers/parport/Kconfig"
682 source "drivers/pnp/Kconfig"
684 source "drivers/block/Kconfig"
686 source "drivers/acorn/block/Kconfig"
688 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
689 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
690 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
691 source "drivers/ide/Kconfig"
694 source "drivers/scsi/Kconfig"
696 source "drivers/md/Kconfig"
698 source "drivers/message/fusion/Kconfig"
700 source "drivers/ieee1394/Kconfig"
702 source "drivers/message/i2o/Kconfig"
704 source "drivers/net/Kconfig"
706 source "drivers/isdn/Kconfig"
708 # input before char - char/joystick depends on it. As does USB.
710 source "drivers/input/Kconfig"
712 source "drivers/char/Kconfig"
714 source "drivers/i2c/Kconfig"
716 source "drivers/hwmon/Kconfig"
718 #source "drivers/l3/Kconfig"
720 source "drivers/misc/Kconfig"
722 source "drivers/mfd/Kconfig"
724 source "drivers/media/Kconfig"
726 source "drivers/video/Kconfig"
728 source "sound/Kconfig"
730 source "drivers/usb/Kconfig"
732 source "drivers/mmc/Kconfig"
738 source "arch/arm/oprofile/Kconfig"
740 source "arch/arm/Kconfig.debug"
742 source "security/Kconfig"
744 source "crypto/Kconfig"