2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "Linux Kernel Configuration"
12 select SYS_SUPPORTS_APM_EMULATION
14 The ARM series is a line of low-power-consumption RISC chip designs
15 licensed by ARM Ltd and targeted at embedded applications and
16 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
17 manufactured, but legacy ARM-based PC hardware remains popular in
18 Europe. There is an ARM Linux project with a web page at
19 <http://www.arm.linux.org.uk/>.
21 config SYS_SUPPORTS_APM_EMULATION
32 config GENERIC_CLOCKEVENTS
47 The Extended Industry Standard Architecture (EISA) bus was
48 developed as an open alternative to the IBM MicroChannel bus.
50 The EISA bus provided some of the features of the IBM MicroChannel
51 bus while maintaining backward compatibility with cards made for
52 the older ISA bus. The EISA bus saw limited use between 1988 and
53 1995 when it was made obsolete by the PCI bus.
55 Say Y here if you are building a kernel for an EISA-based machine.
65 MicroChannel Architecture is found in some IBM PS/2 machines and
66 laptops. It is a bus system similar to PCI or ISA. See
67 <file:Documentation/mca.txt> (and especially the web page given
68 there) before attempting to build an MCA bus kernel.
70 config GENERIC_HARDIRQS
74 config STACKTRACE_SUPPORT
78 config LOCKDEP_SUPPORT
82 config TRACE_IRQFLAGS_SUPPORT
86 config HARDIRQS_SW_RESEND
90 config GENERIC_IRQ_PROBE
94 config RWSEM_GENERIC_SPINLOCK
98 config RWSEM_XCHGADD_ALGORITHM
101 config ARCH_HAS_ILOG2_U32
105 config ARCH_HAS_ILOG2_U64
109 config GENERIC_HWEIGHT
113 config GENERIC_CALIBRATE_DELAY
117 config ARCH_MAY_HAVE_PC_FDC
124 config GENERIC_ISA_DMA
135 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
136 default DRAM_BASE if REMAP_VECTORS_TO_RAM
139 The base address of exception vectors.
141 source "init/Kconfig"
146 prompt "ARM system type"
147 default ARCH_VERSATILE
150 bool "Agilent AAEC-2000 based"
153 This enables support for systems based on the Agilent AAEC-2000
155 config ARCH_INTEGRATOR
156 bool "ARM Ltd. Integrator family"
160 Support for ARM's Integrator platform.
163 bool "ARM Ltd. RealView family"
167 This enables support for ARM Ltd RealView boards.
169 config ARCH_VERSATILE
170 bool "ARM Ltd. Versatile family"
175 select GENERIC_CLOCKEVENTS
177 This enables support for ARM Ltd Versatile board.
183 This enables support for systems based on the Atmel AT91RM9200,
184 AT91SAM9 and AT91CAP9 processors.
187 bool "Cirrus CL-PS7500FE"
192 Support for the Cirrus Logic PS7500FE system-on-a-chip.
195 bool "Cirrus Logic CLPS711x/EP721x-based"
197 Support for Cirrus Logic 711x/721x based boards.
202 select FOOTBRIDGE_ADDIN
204 Support for Intel's EBSA285 companion chip.
211 This is an evaluation board for the StrongARM processor available
212 from Digital. It has limited hardware on-board, including an
213 Ethernet interface, two PCMCIA sockets, two serial ports and a
222 This enables support for the Cirrus EP93xx series of CPUs.
224 config ARCH_FOOTBRIDGE
228 Support for systems based on the DC21285 companion chip
229 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
232 bool "Hilscher NetX based"
235 This enables support for systems based on the Hilscher NetX Soc
238 bool "Hynix HMS720x-based"
241 This enables support for systems based on the Hynix HMS720x
247 select GENERIC_CLOCKEVENTS
249 Support for Motorola's i.MX family of processors (MX1, MXL).
256 select ARCH_SUPPORTS_MSI
258 Support for Intel's IOP13XX (XScale) family of processors.
266 Support for Intel's 80219 and IOP32X (XScale) family of
275 Support for Intel's IOP33X (XScale) family of processors.
282 Support for Intel's IXP23xx (XScale) family of processors.
285 bool "IXP2400/2800-based"
289 Support for Intel's IXP2400/2800 (XScale) family of processors.
296 select GENERIC_CLOCKEVENTS
298 Support for Intel's IXP4XX (XScale) family of processors.
304 Say Y here if you intend to run this kernel on a LinkUp Systems
305 L7200 Software Development Board which uses an ARM720T processor.
306 Information on this board can be obtained at:
308 <http://www.linkupsys.com/>
310 If you have any questions or comments about the Linux kernel port
311 to this board, send e-mail to <sjhill@cotw.com>.
314 bool "Micrel/Kendin KS8695"
317 Support for Micrel/Kendin KS8695 "Centaur" (ARM922T) based
318 System-on-Chip devices.
321 bool "NetSilicon NS9xxx"
324 select GENERIC_CLOCKEVENTS
326 Say Y here if you intend to run this kernel on a NetSilicon NS9xxx
329 <http://www.digi.com/products/microprocessors/index.jsp>
332 bool "Freescale MXC/iMX-based"
335 Support for Freescale MXC/iMX-based family of processors
343 select GENERIC_CLOCKEVENTS
345 Support for Marvell Orion System on Chip family.
348 bool "Philips Nexperia PNX4008 Mobile"
350 This enables support for Philips PNX4008 mobile platform.
353 bool "PXA2xx/PXA3xx-based"
358 select GENERIC_CLOCKEVENTS
360 Support for Intel/Marvell's PXA2xx/PXA3xx processor line.
367 select ARCH_MAY_HAVE_PC_FDC
371 On the Acorn Risc-PC, Linux can support the internal IDE disk and
372 CD-ROM interface, serial and parallel port, and the floppy drive.
377 select ARCH_DISCONTIGMEM_ENABLE
382 Support for StrongARM 11x0 based boards.
385 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442, S3C2443"
388 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
389 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
390 the Samsung SMDK2410 development board (and derivatives).
398 Support for the StrongARM based Digital DNARD machine, also known
399 as "Shark" (<http://www.shark-linux.de/shark.html>).
404 Say Y here for systems based on one of the Sharp LH7A40X
405 System on a Chip processors. These CPUs include an ARM922T
406 core with a wide array of integrated devices for
407 hand-held and low-power applications.
412 select GENERIC_CLOCKEVENTS
415 Support for TI's DaVinci platform.
422 Support for TI's OMAP platform (OMAP1 and OMAP2).
425 bool "Qualcomm MSM7X00A"
427 select GENERIC_CLOCKEVENTS
429 Support for Qualcomm MSM7X00A based systems. This runs on the ARM11
430 apps processor of the MSM7X00A and depends on a shared memory
431 interface to the ARM9 modem processor which runs the baseband stack
432 and controls some vital subsystems (clock and power control, etc).
433 <http://www.cdmatech.com/products/msm7200_chipset_solution.jsp>
437 source "arch/arm/mach-clps711x/Kconfig"
439 source "arch/arm/mach-ep93xx/Kconfig"
441 source "arch/arm/mach-footbridge/Kconfig"
443 source "arch/arm/mach-integrator/Kconfig"
445 source "arch/arm/mach-iop32x/Kconfig"
447 source "arch/arm/mach-iop33x/Kconfig"
449 source "arch/arm/mach-iop13xx/Kconfig"
451 source "arch/arm/mach-ixp4xx/Kconfig"
453 source "arch/arm/mach-ixp2000/Kconfig"
455 source "arch/arm/mach-ixp23xx/Kconfig"
457 source "arch/arm/mach-pxa/Kconfig"
459 source "arch/arm/mach-sa1100/Kconfig"
461 source "arch/arm/plat-omap/Kconfig"
463 source "arch/arm/mach-omap1/Kconfig"
465 source "arch/arm/mach-omap2/Kconfig"
467 source "arch/arm/mach-orion/Kconfig"
469 source "arch/arm/plat-s3c24xx/Kconfig"
470 source "arch/arm/plat-s3c/Kconfig"
473 source "arch/arm/mach-s3c2400/Kconfig"
474 source "arch/arm/mach-s3c2410/Kconfig"
475 source "arch/arm/mach-s3c2412/Kconfig"
476 source "arch/arm/mach-s3c2440/Kconfig"
477 source "arch/arm/mach-s3c2442/Kconfig"
478 source "arch/arm/mach-s3c2443/Kconfig"
481 source "arch/arm/mach-lh7a40x/Kconfig"
483 source "arch/arm/mach-imx/Kconfig"
485 source "arch/arm/mach-h720x/Kconfig"
487 source "arch/arm/mach-versatile/Kconfig"
489 source "arch/arm/mach-aaec2000/Kconfig"
491 source "arch/arm/mach-realview/Kconfig"
493 source "arch/arm/mach-at91/Kconfig"
495 source "arch/arm/plat-mxc/Kconfig"
497 source "arch/arm/mach-netx/Kconfig"
499 source "arch/arm/mach-ns9xxx/Kconfig"
501 source "arch/arm/mach-davinci/Kconfig"
503 source "arch/arm/mach-ks8695/Kconfig"
505 source "arch/arm/mach-msm/Kconfig"
507 # Definitions to make life easier
514 source arch/arm/mm/Kconfig
517 bool "Enable iWMMXt support"
518 depends on CPU_XSCALE || CPU_XSC3
519 default y if PXA27x || PXA3xx
521 Enable support for iWMMXt context switching at run time if
522 running on a CPU that supports it.
524 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
527 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
531 source "arch/arm/Kconfig-nommu"
536 source "arch/arm/common/Kconfig"
538 config FORCE_MAX_ZONEORDER
551 Find out whether you have ISA slots on your motherboard. ISA is the
552 name of a bus system, i.e. the way the CPU talks to the other stuff
553 inside your box. Other bus systems are PCI, EISA, MicroChannel
554 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
555 newer boards don't support it. If you have ISA, say Y, otherwise N.
557 # Select ISA DMA controller support
562 # Select ISA DMA interface
567 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX || ARCH_KS8695 || MACH_ARMCORE
569 Find out whether you have a PCI motherboard. PCI is the name of a
570 bus system, i.e. the way the CPU talks to the other stuff inside
571 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
572 VESA. If you have PCI, say Y, otherwise N.
574 The PCI-HOWTO, available from
575 <http://www.tldp.org/docs.html#howto>, contains valuable
576 information about which PCI hardware does work under Linux and which
582 # Select the host bridge type
583 config PCI_HOST_VIA82C505
585 depends on PCI && ARCH_SHARK
588 config PCI_HOST_ITE8152
590 depends on PCI && MACH_ARMCORE
594 source "drivers/pci/Kconfig"
596 source "drivers/pcmcia/Kconfig"
600 menu "Kernel Features"
602 source "kernel/time/Kconfig"
605 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
606 depends on EXPERIMENTAL && REALVIEW_MPCORE
608 This enables support for systems with more than one CPU. If you have
609 a system with only one CPU, like most personal computers, say N. If
610 you have a system with more than one CPU, say Y.
612 If you say N here, the kernel will run on single and multiprocessor
613 machines, but will use only one CPU of a multiprocessor machine. If
614 you say Y here, the kernel will run on many, but not all, single
615 processor machines. On a single processor machine, the kernel will
616 run faster if you say N here.
618 See also the <file:Documentation/smp.txt>,
619 <file:Documentation/i386/IO-APIC.txt>,
620 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
621 <http://www.linuxdoc.org/docs.html#howto>.
623 If you don't know what to do here, say N.
626 int "Maximum number of CPUs (2-32)"
632 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
633 depends on SMP && HOTPLUG && EXPERIMENTAL
635 Say Y here to experiment with turning CPUs off and on. CPUs
636 can be controlled through /sys/devices/system/cpu.
639 bool "Use local timer interrupts"
640 depends on SMP && REALVIEW_MPCORE
643 Enable support for local timers on SMP platforms, rather then the
644 legacy IPI broadcast method. Local timers allows the system
645 accounting to be spread across the timer interval, preventing a
646 "thundering herd" at every timer tick.
649 bool "Preemptible Kernel (EXPERIMENTAL)"
650 depends on EXPERIMENTAL
652 This option reduces the latency of the kernel when reacting to
653 real-time or interactive events by allowing a low priority process to
654 be preempted even if it is in kernel mode executing a system call.
655 This allows applications to run more reliably even when the system is
658 Say Y here if you are building a kernel for a desktop, embedded
659 or real-time system. Say N if you are unsure.
662 bool "Dynamic tick timer"
663 depends on !GENERIC_CLOCKEVENTS
665 Select this option if you want to disable continuous timer ticks
666 and have them programmed to occur as required. This option saves
667 power as the system can remain in idle state for longer.
669 By default dynamic tick is disabled during the boot, and can be
670 manually enabled with:
672 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
674 Alternatively, if you want dynamic tick automatically enabled
675 during boot, pass "dyntick=enable" via the kernel command string.
677 Please note that dynamic tick may affect the accuracy of
678 timekeeping on some platforms depending on the implementation.
679 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
680 to have accurate timekeeping with dynamic tick.
684 default 128 if ARCH_L7200
685 default 200 if ARCH_EBSA110 || ARCH_S3C2410
686 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
687 default AT91_TIMER_HZ if ARCH_AT91
691 bool "Use the ARM EABI to compile the kernel"
693 This option allows for the kernel to be compiled using the latest
694 ARM ABI (aka EABI). This is only useful if you are using a user
695 space environment that is also compiled with EABI.
697 Since there are major incompatibilities between the legacy ABI and
698 EABI, especially with regard to structure member alignment, this
699 option also changes the kernel syscall calling convention to
700 disambiguate both ABIs and allow for backward compatibility support
701 (selected with CONFIG_OABI_COMPAT).
703 To use this you need GCC version 4.0.0 or later.
706 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
707 depends on AEABI && EXPERIMENTAL
710 This option preserves the old syscall interface along with the
711 new (ARM EABI) one. It also provides a compatibility layer to
712 intercept syscalls that have structure arguments which layout
713 in memory differs between the legacy ABI and the new ARM EABI
714 (only for non "thumb" binaries). This option adds a tiny
715 overhead to all syscalls and produces a slightly larger kernel.
716 If you know you'll be using only pure EABI user space then you
717 can say N here. If this option is not selected and you attempt
718 to execute a legacy ABI binary then the result will be
719 UNPREDICTABLE (in fact it can be predicted that it won't work
720 at all). If in doubt say Y.
722 config ARCH_DISCONTIGMEM_ENABLE
724 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
726 Say Y to support efficient handling of discontiguous physical memory,
727 for architectures which are either NUMA (Non-Uniform Memory Access)
728 or have huge holes in the physical address space for other reasons.
729 See <file:Documentation/vm/numa> for more.
733 default "4" if ARCH_LH7A40X
735 depends on NEED_MULTIPLE_NODES
740 bool "Timer and CPU usage LEDs"
741 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
742 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
743 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
744 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
745 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
746 ARCH_AT91 || MACH_TRIZEPS4 || ARCH_DAVINCI || \
747 ARCH_KS8695 || MACH_RD88F5182
749 If you say Y here, the LEDs on your machine will be used
750 to provide useful information about your current system status.
752 If you are compiling a kernel for a NetWinder or EBSA-285, you will
753 be able to select which LEDs are active using the options below. If
754 you are compiling a kernel for the EBSA-110 or the LART however, the
755 red LED will simply flash regularly to indicate that the system is
756 still functional. It is safe to say Y here if you have a CATS
757 system, but the driver will do nothing.
760 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
761 OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
762 || MACH_OMAP_PERSEUS2
764 depends on !GENERIC_CLOCKEVENTS
765 default y if ARCH_EBSA110
767 If you say Y here, one of the system LEDs (the green one on the
768 NetWinder, the amber one on the EBSA285, or the red one on the LART)
769 will flash regularly to indicate that the system is still
770 operational. This is mainly useful to kernel hackers who are
771 debugging unstable kernels.
773 The LART uses the same LED for both Timer LED and CPU usage LED
774 functions. You may choose to use both, but the Timer LED function
775 will overrule the CPU usage LED.
778 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
780 || OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
781 || MACH_OMAP_PERSEUS2
784 If you say Y here, the red LED will be used to give a good real
785 time indication of CPU usage, by lighting whenever the idle task
786 is not currently executing.
788 The LART uses the same LED for both Timer LED and CPU usage LED
789 functions. You may choose to use both, but the Timer LED function
790 will overrule the CPU usage LED.
792 config ALIGNMENT_TRAP
794 depends on CPU_CP15_MMU
795 default y if !ARCH_EBSA110
797 ARM processors cannot fetch/store information which is not
798 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
799 address divisible by 4. On 32-bit ARM processors, these non-aligned
800 fetch/store instructions will be emulated in software if you say
801 here, which has a severe performance impact. This is necessary for
802 correct operation of some network protocols. With an IP-only
803 configuration it is safe to say N, otherwise say Y.
809 # Compressed boot loader in ROM. Yes, we really want to ask about
810 # TEXT and BSS so we preserve their values in the config files.
811 config ZBOOT_ROM_TEXT
812 hex "Compressed ROM boot loader base address"
815 The physical address at which the ROM-able zImage is to be
816 placed in the target. Platforms which normally make use of
817 ROM-able zImage formats normally set this to a suitable
818 value in their defconfig file.
820 If ZBOOT_ROM is not enabled, this has no effect.
823 hex "Compressed ROM boot loader BSS address"
826 The base address of an area of read/write memory in the target
827 for the ROM-able zImage which must be available while the
828 decompressor is running. It must be large enough to hold the
829 entire decompressed kernel plus an additional 128 KiB.
830 Platforms which normally make use of ROM-able zImage formats
831 normally set this to a suitable value in their defconfig file.
833 If ZBOOT_ROM is not enabled, this has no effect.
836 bool "Compressed boot loader in ROM/flash"
837 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
839 Say Y here if you intend to execute your compressed kernel image
840 (zImage) directly from ROM or flash. If unsure, say N.
843 string "Default kernel command string"
846 On some architectures (EBSA110 and CATS), there is currently no way
847 for the boot loader to pass arguments to the kernel. For these
848 architectures, you should supply some command-line options at build
849 time by entering them here. As a minimum, you should specify the
850 memory size and the root device (e.g., mem=64M root=/dev/nfs).
853 bool "Kernel Execute-In-Place from ROM"
854 depends on !ZBOOT_ROM
856 Execute-In-Place allows the kernel to run from non-volatile storage
857 directly addressable by the CPU, such as NOR flash. This saves RAM
858 space since the text section of the kernel is not loaded from flash
859 to RAM. Read-write sections, such as the data section and stack,
860 are still copied to RAM. The XIP kernel is not compressed since
861 it has to run directly from flash, so it will take more space to
862 store it. The flash address used to link the kernel object files,
863 and for storing it, is configuration dependent. Therefore, if you
864 say Y here, you must know the proper physical address where to
865 store the kernel image depending on your own flash memory usage.
867 Also note that the make target becomes "make xipImage" rather than
868 "make zImage" or "make Image". The final kernel binary to put in
869 ROM memory will be arch/arm/boot/xipImage.
874 hex "XIP Kernel Physical Location"
875 depends on XIP_KERNEL
878 This is the physical address in your flash memory the kernel will
879 be linked for and stored to. This address is dependent on your
883 bool "Kexec system call (EXPERIMENTAL)"
884 depends on EXPERIMENTAL
886 kexec is a system call that implements the ability to shutdown your
887 current kernel, and to start another kernel. It is like a reboot
888 but it is independent of the system firmware. And like a reboot
889 you can start any kernel with it, not just Linux.
891 It is an ongoing process to be certain the hardware in a machine
892 is properly shutdown, so do not be surprised if this code does not
893 initially work for you. It may help to enable device hotplugging
898 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
900 menu "CPU Frequency scaling"
902 source "drivers/cpufreq/Kconfig"
904 config CPU_FREQ_SA1100
906 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
909 config CPU_FREQ_SA1110
911 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
914 config CPU_FREQ_INTEGRATOR
915 tristate "CPUfreq driver for ARM Integrator CPUs"
916 depends on ARCH_INTEGRATOR && CPU_FREQ
919 This enables the CPUfreq driver for ARM Integrator CPUs.
921 For details, take a look at <file:Documentation/cpu-freq>.
926 tristate "CPUfreq driver for i.MX CPUs"
927 depends on ARCH_IMX && CPU_FREQ
930 This enables the CPUfreq driver for i.MX CPUs.
938 menu "Floating point emulation"
940 comment "At least one emulation must be selected"
943 bool "NWFPE math emulation"
944 depends on !AEABI || OABI_COMPAT
946 Say Y to include the NWFPE floating point emulator in the kernel.
947 This is necessary to run most binaries. Linux does not currently
948 support floating point hardware so you need to say Y here even if
949 your machine has an FPA or floating point co-processor podule.
951 You may say N here if you are going to load the Acorn FPEmulator
955 bool "Support extended precision"
958 Say Y to include 80-bit support in the kernel floating-point
959 emulator. Otherwise, only 32 and 64-bit support is compiled in.
960 Note that gcc does not generate 80-bit operations by default,
961 so in most cases this option only enlarges the size of the
962 floating point emulator without any good reason.
964 You almost surely want to say N here.
967 bool "FastFPE math emulation (EXPERIMENTAL)"
968 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
970 Say Y here to include the FAST floating point emulator in the kernel.
971 This is an experimental much faster emulator which now also has full
972 precision for the mantissa. It does not support any exceptions.
973 It is very simple, and approximately 3-6 times faster than NWFPE.
975 It should be sufficient for most programs. It may be not suitable
976 for scientific calculations, but you have to check this for yourself.
977 If you do not feel you need a faster FP emulation you should better
981 bool "VFP-format floating point maths"
982 depends on CPU_V6 || CPU_ARM926T || CPU_V7 || CPU_FEROCEON
984 Say Y to include VFP support code in the kernel. This is needed
985 if your hardware includes a VFP unit.
987 Please see <file:Documentation/arm/VFP/release-notes.txt> for
988 release notes and additional status information.
990 Say N if your target does not have VFP hardware.
998 bool "Advanced SIMD (NEON) Extension support"
999 depends on VFPv3 && CPU_V7
1001 Say Y to include support code for NEON, the ARMv7 Advanced SIMD
1006 menu "Userspace binary formats"
1008 source "fs/Kconfig.binfmt"
1011 tristate "RISC OS personality"
1014 Say Y here to include the kernel code necessary if you want to run
1015 Acorn RISC OS/Arthur binaries under Linux. This code is still very
1016 experimental; if this sounds frightening, say N and sleep in peace.
1017 You can also say M here to compile this support as a module (which
1018 will be called arthur).
1022 menu "Power management options"
1024 source "kernel/power/Kconfig"
1028 source "net/Kconfig"
1030 menu "Device Drivers"
1032 source "drivers/base/Kconfig"
1034 source "drivers/connector/Kconfig"
1036 if ALIGNMENT_TRAP || !CPU_CP15_MMU
1037 source "drivers/mtd/Kconfig"
1040 source "drivers/parport/Kconfig"
1042 source "drivers/pnp/Kconfig"
1044 source "drivers/block/Kconfig"
1046 # misc before ide - BLK_DEV_SGIIOC4 depends on SGI_IOC4
1048 source "drivers/misc/Kconfig"
1050 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
1051 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
1052 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
1054 source "drivers/ide/Kconfig"
1057 source "drivers/scsi/Kconfig"
1059 source "drivers/ata/Kconfig"
1061 source "drivers/md/Kconfig"
1063 source "drivers/message/fusion/Kconfig"
1065 source "drivers/ieee1394/Kconfig"
1067 source "drivers/message/i2o/Kconfig"
1069 source "drivers/net/Kconfig"
1071 source "drivers/isdn/Kconfig"
1073 # input before char - char/joystick depends on it. As does USB.
1075 source "drivers/input/Kconfig"
1077 source "drivers/char/Kconfig"
1079 source "drivers/i2c/Kconfig"
1081 source "drivers/spi/Kconfig"
1083 source "drivers/w1/Kconfig"
1085 source "drivers/power/Kconfig"
1087 source "drivers/hwmon/Kconfig"
1089 source "drivers/watchdog/Kconfig"
1091 source "drivers/ssb/Kconfig"
1093 #source "drivers/l3/Kconfig"
1095 source "drivers/mfd/Kconfig"
1097 source "drivers/media/Kconfig"
1099 source "drivers/video/Kconfig"
1101 source "sound/Kconfig"
1103 source "drivers/hid/Kconfig"
1105 source "drivers/usb/Kconfig"
1107 source "drivers/mmc/Kconfig"
1109 source "drivers/leds/Kconfig"
1111 source "drivers/rtc/Kconfig"
1113 source "drivers/dma/Kconfig"
1115 source "drivers/dca/Kconfig"
1121 source "arch/arm/Kconfig.instrumentation"
1123 source "arch/arm/Kconfig.debug"
1125 source "security/Kconfig"
1127 source "crypto/Kconfig"
1129 source "lib/Kconfig"