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.
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/mach-omap/Kconfig"
228 source "arch/arm/mach-s3c2410/Kconfig"
230 source "arch/arm/mach-lh7a40x/Kconfig"
232 source "arch/arm/mach-imx/Kconfig"
234 source "arch/arm/mach-h720x/Kconfig"
236 source "arch/arm/mach-versatile/Kconfig"
238 source "arch/arm/mach-aaec2000/Kconfig"
240 # Definitions to make life easier
244 source arch/arm/mm/Kconfig
246 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
249 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
254 source "arch/arm/common/Kconfig"
256 config FORCE_MAX_ZONEORDER
269 Find out whether you have ISA slots on your motherboard. ISA is the
270 name of a bus system, i.e. the way the CPU talks to the other stuff
271 inside your box. Other bus systems are PCI, EISA, MicroChannel
272 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
273 newer boards don't support it. If you have ISA, say Y, otherwise N.
283 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
285 Find out whether you have a PCI motherboard. PCI is the name of a
286 bus system, i.e. the way the CPU talks to the other stuff inside
287 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
288 VESA. If you have PCI, say Y, otherwise N.
290 The PCI-HOWTO, available from
291 <http://www.tldp.org/docs.html#howto>, contains valuable
292 information about which PCI hardware does work under Linux and which
295 # Select the host bridge type
296 config PCI_HOST_VIA82C505
298 depends on PCI && ARCH_SHARK
301 source "drivers/pci/Kconfig"
303 source "drivers/pcmcia/Kconfig"
307 menu "Kernel Features"
310 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
311 depends on EXPERIMENTAL #&& n
313 This enables support for systems with more than one CPU. If you have
314 a system with only one CPU, like most personal computers, say N. If
315 you have a system with more than one CPU, say Y.
317 If you say N here, the kernel will run on single and multiprocessor
318 machines, but will use only one CPU of a multiprocessor machine. If
319 you say Y here, the kernel will run on many, but not all, single
320 processor machines. On a single processor machine, the kernel will
321 run faster if you say N here.
323 See also the <file:Documentation/smp.tex>,
324 <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
325 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
326 <http://www.linuxdoc.org/docs.html#howto>.
328 If you don't know what to do here, say N.
331 int "Maximum number of CPUs (2-32)"
337 bool "Preemptible Kernel (EXPERIMENTAL)"
338 depends on EXPERIMENTAL
340 This option reduces the latency of the kernel when reacting to
341 real-time or interactive events by allowing a low priority process to
342 be preempted even if it is in kernel mode executing a system call.
343 This allows applications to run more reliably even when the system is
346 Say Y here if you are building a kernel for a desktop, embedded
347 or real-time system. Say N if you are unsure.
349 config ARCH_DISCONTIGMEM_ENABLE
351 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
353 Say Y to support efficient handling of discontiguous physical memory,
354 for architectures which are either NUMA (Non-Uniform Memory Access)
355 or have huge holes in the physical address space for other reasons.
356 See <file:Documentation/vm/numa> for more.
361 bool "Timer and CPU usage LEDs"
362 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
363 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
364 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
365 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
366 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE
368 If you say Y here, the LEDs on your machine will be used
369 to provide useful information about your current system status.
371 If you are compiling a kernel for a NetWinder or EBSA-285, you will
372 be able to select which LEDs are active using the options below. If
373 you are compiling a kernel for the EBSA-110 or the LART however, the
374 red LED will simply flash regularly to indicate that the system is
375 still functional. It is safe to say Y here if you have a CATS
376 system, but the driver will do nothing.
379 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
380 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
382 default y if ARCH_EBSA110
384 If you say Y here, one of the system LEDs (the green one on the
385 NetWinder, the amber one on the EBSA285, or the red one on the LART)
386 will flash regularly to indicate that the system is still
387 operational. This is mainly useful to kernel hackers who are
388 debugging unstable kernels.
390 The LART uses the same LED for both Timer LED and CPU usage LED
391 functions. You may choose to use both, but the Timer LED function
392 will overrule the CPU usage LED.
395 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
396 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
399 If you say Y here, the red LED will be used to give a good real
400 time indication of CPU usage, by lighting whenever the idle task
401 is not currently executing.
403 The LART uses the same LED for both Timer LED and CPU usage LED
404 functions. You may choose to use both, but the Timer LED function
405 will overrule the CPU usage LED.
407 config ALIGNMENT_TRAP
409 default y if !ARCH_EBSA110
411 ARM processors can not fetch/store information which is not
412 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
413 address divisible by 4. On 32-bit ARM processors, these non-aligned
414 fetch/store instructions will be emulated in software if you say
415 here, which has a severe performance impact. This is necessary for
416 correct operation of some network protocols. With an IP-only
417 configuration it is safe to say N, otherwise say Y.
423 # Compressed boot loader in ROM. Yes, we really want to ask about
424 # TEXT and BSS so we preserve their values in the config files.
425 config ZBOOT_ROM_TEXT
426 hex "Compressed ROM boot loader base address"
429 The physical address at which the ROM-able zImage is to be
430 placed in the target. Platforms which normally make use of
431 ROM-able zImage formats normally set this to a suitable
432 value in their defconfig file.
434 If ZBOOT_ROM is not enabled, this has no effect.
437 hex "Compressed ROM boot loader BSS address"
440 The base address of 64KiB of read/write memory in the target
441 for the ROM-able zImage, which must be available while the
442 decompressor is running. Platforms which normally make use of
443 ROM-able zImage formats normally set this to a suitable
444 value in their defconfig file.
446 If ZBOOT_ROM is not enabled, this has no effect.
449 bool "Compressed boot loader in ROM/flash"
450 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
452 Say Y here if you intend to execute your compressed kernel image
453 (zImage) directly from ROM or flash. If unsure, say N.
456 string "Default kernel command string"
459 On some architectures (EBSA110 and CATS), there is currently no way
460 for the boot loader to pass arguments to the kernel. For these
461 architectures, you should supply some command-line options at build
462 time by entering them here. As a minimum, you should specify the
463 memory size and the root device (e.g., mem=64M root=/dev/nfs).
466 bool "Kernel Execute-In-Place from ROM"
467 depends on !ZBOOT_ROM
469 Execute-In-Place allows the kernel to run from non-volatile storage
470 directly addressable by the CPU, such as NOR flash. This saves RAM
471 space since the text section of the kernel is not loaded from flash
472 to RAM. Read-write sections, such as the data section and stack,
473 are still copied to RAM. The XIP kernel is not compressed since
474 it has to run directly from flash, so it will take more space to
475 store it. The flash address used to link the kernel object files,
476 and for storing it, is configuration dependent. Therefore, if you
477 say Y here, you must know the proper physical address where to
478 store the kernel image depending on your own flash memory usage.
480 Also note that the make target becomes "make xipImage" rather than
481 "make zImage" or "make Image". The final kernel binary to put in
482 ROM memory will be arch/arm/boot/xipImage.
487 hex "XIP Kernel Physical Location"
488 depends on XIP_KERNEL
491 This is the physical address in your flash memory the kernel will
492 be linked for and stored to. This address is dependent on your
497 if (ARCH_SA1100 || ARCH_INTEGRATOR)
499 menu "CPU Frequency scaling"
501 source "drivers/cpufreq/Kconfig"
503 config CPU_FREQ_SA1100
505 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
508 config CPU_FREQ_SA1110
510 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
513 config CPU_FREQ_INTEGRATOR
514 tristate "CPUfreq driver for ARM Integrator CPUs"
515 depends on ARCH_INTEGRATOR && CPU_FREQ
518 This enables the CPUfreq driver for ARM Integrator CPUs.
520 For details, take a look at <file:Documentation/cpu-freq>.
528 menu "Floating point emulation"
530 comment "At least one emulation must be selected"
533 bool "NWFPE math emulation"
535 Say Y to include the NWFPE floating point emulator in the kernel.
536 This is necessary to run most binaries. Linux does not currently
537 support floating point hardware so you need to say Y here even if
538 your machine has an FPA or floating point co-processor podule.
540 You may say N here if you are going to load the Acorn FPEmulator
544 bool "Support extended precision"
545 depends on FPE_NWFPE && !CPU_BIG_ENDIAN
547 Say Y to include 80-bit support in the kernel floating-point
548 emulator. Otherwise, only 32 and 64-bit support is compiled in.
549 Note that gcc does not generate 80-bit operations by default,
550 so in most cases this option only enlarges the size of the
551 floating point emulator without any good reason.
553 You almost surely want to say N here.
556 bool "FastFPE math emulation (EXPERIMENTAL)"
557 depends on !CPU_32v3 && EXPERIMENTAL
559 Say Y here to include the FAST floating point emulator in the kernel.
560 This is an experimental much faster emulator which now also has full
561 precision for the mantissa. It does not support any exceptions.
562 It is very simple, and approximately 3-6 times faster than NWFPE.
564 It should be sufficient for most programs. It may be not suitable
565 for scientific calculations, but you have to check this for yourself.
566 If you do not feel you need a faster FP emulation you should better
570 bool "VFP-format floating point maths"
571 depends on CPU_V6 || CPU_ARM926T
573 Say Y to include VFP support code in the kernel. This is needed
574 if your hardware includes a VFP unit.
576 Please see <file:Documentation/arm/VFP/release-notes.txt> for
577 release notes and additional status information.
579 Say N if your target does not have VFP hardware.
583 menu "Userspace binary formats"
585 source "fs/Kconfig.binfmt"
588 tristate "RISC OS personality"
590 Say Y here to include the kernel code necessary if you want to run
591 Acorn RISC OS/Arthur binaries under Linux. This code is still very
592 experimental; if this sounds frightening, say N and sleep in peace.
593 You can also say M here to compile this support as a module (which
594 will be called arthur).
598 menu "Power management options"
601 bool "Power Management support"
603 "Power Management" means that parts of your computer are shut
604 off or put into a power conserving "sleep" mode if they are not
605 being used. There are two competing standards for doing this: APM
606 and ACPI. If you want to use either one, say Y here and then also
607 to the requisite support below.
609 Power Management is most important for battery powered laptop
610 computers; if you have a laptop, check out the Linux Laptop home
611 page on the WWW at <http://www.linux-on-laptops.com/> or
612 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>
613 and the Battery Powered Linux mini-HOWTO, available from
614 <http://www.tldp.org/docs.html#howto>.
616 Note that, even if you say N here, Linux on the x86 architecture
617 will issue the hlt instruction if nothing is to be done, thereby
618 sending the processor to sleep and saving power.
621 tristate "Advanced Power Management Emulation"
624 APM is a BIOS specification for saving power using several different
625 techniques. This is mostly useful for battery powered laptops with
626 APM compliant BIOSes. If you say Y here, the system time will be
627 reset after a RESUME operation, the /proc/apm device will provide
628 battery status information, and user-space programs will receive
629 notification of APM "events" (e.g. battery status change).
631 If you select "Y" here, you can disable actual use of the APM
632 BIOS by passing the "apm=off" option to the kernel at boot time.
634 Note that the APM support is almost completely disabled for
635 machines with more than one CPU.
637 In order to use APM, you will need supporting software. For location
638 and more information, read <file:Documentation/pm.txt> and the
639 Battery Powered Linux mini-HOWTO, available from
640 <http://www.tldp.org/docs.html#howto>.
642 This driver does not spin down disk drives (see the hdparm(8)
643 manpage ("man 8 hdparm") for that), and it doesn't turn off
644 VESA-compliant "green" monitors.
646 This driver does not support the TI 4000M TravelMate and the ACER
647 486/DX4/75 because they don't have compliant BIOSes. Many "green"
648 desktop machines also don't have compliant BIOSes, and this driver
649 may cause those machines to panic during the boot phase.
651 Generally, if you don't have a battery in your machine, there isn't
652 much point in using this driver and you should say N. If you get
653 random kernel OOPSes or reboots that don't seem to be related to
654 anything, try disabling/enabling this option (or disabling/enabling
657 Some other things you should try when experiencing seemingly random,
660 1) make sure that you have enough swap space and that it is
662 2) pass the "no-hlt" option to the kernel
663 3) switch on floating point emulation in the kernel and pass
664 the "no387" option to the kernel
665 4) pass the "floppy=nodma" option to the kernel
666 5) pass the "mem=4M" option to the kernel (thereby disabling
667 all but the first 4 MB of RAM)
668 6) make sure that the CPU is not over clocked.
669 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
670 8) disable the cache from your BIOS settings
671 9) install a fan for the video card or exchange video RAM
672 10) install a better fan for the CPU
673 11) exchange RAM chips
674 12) exchange the motherboard.
676 To compile this driver as a module, choose M here: the
677 module will be called apm.
681 menu "Device Drivers"
683 source "drivers/base/Kconfig"
686 source "drivers/mtd/Kconfig"
689 source "drivers/parport/Kconfig"
691 source "drivers/pnp/Kconfig"
693 source "drivers/block/Kconfig"
695 source "drivers/acorn/block/Kconfig"
697 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
698 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
699 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
700 source "drivers/ide/Kconfig"
703 source "drivers/scsi/Kconfig"
705 source "drivers/md/Kconfig"
707 source "drivers/message/fusion/Kconfig"
709 source "drivers/ieee1394/Kconfig"
711 source "drivers/message/i2o/Kconfig"
715 source "drivers/isdn/Kconfig"
717 # input before char - char/joystick depends on it. As does USB.
719 source "drivers/input/Kconfig"
721 source "drivers/char/Kconfig"
723 source "drivers/i2c/Kconfig"
725 #source "drivers/l3/Kconfig"
727 source "drivers/misc/Kconfig"
729 source "drivers/media/Kconfig"
731 source "drivers/video/Kconfig"
733 source "sound/Kconfig"
735 source "drivers/usb/Kconfig"
737 source "drivers/mmc/Kconfig"
743 source "arch/arm/oprofile/Kconfig"
745 source "arch/arm/Kconfig.debug"
747 source "security/Kconfig"
749 source "crypto/Kconfig"