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
361 Support for Intel/Marvell's PXA2xx/PXA3xx processor line.
368 select ARCH_MAY_HAVE_PC_FDC
372 On the Acorn Risc-PC, Linux can support the internal IDE disk and
373 CD-ROM interface, serial and parallel port, and the floppy drive.
378 select ARCH_DISCONTIGMEM_ENABLE
383 Support for StrongARM 11x0 based boards.
386 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442, S3C2443"
389 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
390 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
391 the Samsung SMDK2410 development board (and derivatives).
399 Support for the StrongARM based Digital DNARD machine, also known
400 as "Shark" (<http://www.shark-linux.de/shark.html>).
405 Say Y here for systems based on one of the Sharp LH7A40X
406 System on a Chip processors. These CPUs include an ARM922T
407 core with a wide array of integrated devices for
408 hand-held and low-power applications.
413 select GENERIC_CLOCKEVENTS
416 Support for TI's DaVinci platform.
423 Support for TI's OMAP platform (OMAP1 and OMAP2).
426 bool "Qualcomm MSM7X00A"
428 select GENERIC_CLOCKEVENTS
430 Support for Qualcomm MSM7X00A based systems. This runs on the ARM11
431 apps processor of the MSM7X00A and depends on a shared memory
432 interface to the ARM9 modem processor which runs the baseband stack
433 and controls some vital subsystems (clock and power control, etc).
434 <http://www.cdmatech.com/products/msm7200_chipset_solution.jsp>
438 source "arch/arm/mach-clps711x/Kconfig"
440 source "arch/arm/mach-ep93xx/Kconfig"
442 source "arch/arm/mach-footbridge/Kconfig"
444 source "arch/arm/mach-integrator/Kconfig"
446 source "arch/arm/mach-iop32x/Kconfig"
448 source "arch/arm/mach-iop33x/Kconfig"
450 source "arch/arm/mach-iop13xx/Kconfig"
452 source "arch/arm/mach-ixp4xx/Kconfig"
454 source "arch/arm/mach-ixp2000/Kconfig"
456 source "arch/arm/mach-ixp23xx/Kconfig"
458 source "arch/arm/mach-pxa/Kconfig"
460 source "arch/arm/mach-sa1100/Kconfig"
462 source "arch/arm/plat-omap/Kconfig"
464 source "arch/arm/mach-omap1/Kconfig"
466 source "arch/arm/mach-omap2/Kconfig"
468 source "arch/arm/mach-orion/Kconfig"
470 source "arch/arm/plat-s3c24xx/Kconfig"
471 source "arch/arm/plat-s3c/Kconfig"
474 source "arch/arm/mach-s3c2400/Kconfig"
475 source "arch/arm/mach-s3c2410/Kconfig"
476 source "arch/arm/mach-s3c2412/Kconfig"
477 source "arch/arm/mach-s3c2440/Kconfig"
478 source "arch/arm/mach-s3c2442/Kconfig"
479 source "arch/arm/mach-s3c2443/Kconfig"
482 source "arch/arm/mach-lh7a40x/Kconfig"
484 source "arch/arm/mach-imx/Kconfig"
486 source "arch/arm/mach-h720x/Kconfig"
488 source "arch/arm/mach-versatile/Kconfig"
490 source "arch/arm/mach-aaec2000/Kconfig"
492 source "arch/arm/mach-realview/Kconfig"
494 source "arch/arm/mach-at91/Kconfig"
496 source "arch/arm/plat-mxc/Kconfig"
498 source "arch/arm/mach-netx/Kconfig"
500 source "arch/arm/mach-ns9xxx/Kconfig"
502 source "arch/arm/mach-davinci/Kconfig"
504 source "arch/arm/mach-ks8695/Kconfig"
506 source "arch/arm/mach-msm/Kconfig"
508 # Definitions to make life easier
515 source arch/arm/mm/Kconfig
518 bool "Enable iWMMXt support"
519 depends on CPU_XSCALE || CPU_XSC3
520 default y if PXA27x || PXA3xx
522 Enable support for iWMMXt context switching at run time if
523 running on a CPU that supports it.
525 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
528 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
532 source "arch/arm/Kconfig-nommu"
537 source "arch/arm/common/Kconfig"
539 config FORCE_MAX_ZONEORDER
552 Find out whether you have ISA slots on your motherboard. ISA is the
553 name of a bus system, i.e. the way the CPU talks to the other stuff
554 inside your box. Other bus systems are PCI, EISA, MicroChannel
555 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
556 newer boards don't support it. If you have ISA, say Y, otherwise N.
558 # Select ISA DMA controller support
563 # Select ISA DMA interface
568 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX || ARCH_KS8695 || MACH_ARMCORE
570 Find out whether you have a PCI motherboard. PCI is the name of a
571 bus system, i.e. the way the CPU talks to the other stuff inside
572 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
573 VESA. If you have PCI, say Y, otherwise N.
575 The PCI-HOWTO, available from
576 <http://www.tldp.org/docs.html#howto>, contains valuable
577 information about which PCI hardware does work under Linux and which
583 # Select the host bridge type
584 config PCI_HOST_VIA82C505
586 depends on PCI && ARCH_SHARK
589 config PCI_HOST_ITE8152
591 depends on PCI && MACH_ARMCORE
595 source "drivers/pci/Kconfig"
597 source "drivers/pcmcia/Kconfig"
601 menu "Kernel Features"
603 source "kernel/time/Kconfig"
606 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
607 depends on EXPERIMENTAL && REALVIEW_MPCORE
609 This enables support for systems with more than one CPU. If you have
610 a system with only one CPU, like most personal computers, say N. If
611 you have a system with more than one CPU, say Y.
613 If you say N here, the kernel will run on single and multiprocessor
614 machines, but will use only one CPU of a multiprocessor machine. If
615 you say Y here, the kernel will run on many, but not all, single
616 processor machines. On a single processor machine, the kernel will
617 run faster if you say N here.
619 See also the <file:Documentation/smp.txt>,
620 <file:Documentation/i386/IO-APIC.txt>,
621 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
622 <http://www.linuxdoc.org/docs.html#howto>.
624 If you don't know what to do here, say N.
627 int "Maximum number of CPUs (2-32)"
633 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
634 depends on SMP && HOTPLUG && EXPERIMENTAL
636 Say Y here to experiment with turning CPUs off and on. CPUs
637 can be controlled through /sys/devices/system/cpu.
640 bool "Use local timer interrupts"
641 depends on SMP && REALVIEW_MPCORE
644 Enable support for local timers on SMP platforms, rather then the
645 legacy IPI broadcast method. Local timers allows the system
646 accounting to be spread across the timer interval, preventing a
647 "thundering herd" at every timer tick.
650 bool "Preemptible Kernel (EXPERIMENTAL)"
651 depends on EXPERIMENTAL
653 This option reduces the latency of the kernel when reacting to
654 real-time or interactive events by allowing a low priority process to
655 be preempted even if it is in kernel mode executing a system call.
656 This allows applications to run more reliably even when the system is
659 Say Y here if you are building a kernel for a desktop, embedded
660 or real-time system. Say N if you are unsure.
663 bool "Dynamic tick timer"
664 depends on !GENERIC_CLOCKEVENTS
666 Select this option if you want to disable continuous timer ticks
667 and have them programmed to occur as required. This option saves
668 power as the system can remain in idle state for longer.
670 By default dynamic tick is disabled during the boot, and can be
671 manually enabled with:
673 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
675 Alternatively, if you want dynamic tick automatically enabled
676 during boot, pass "dyntick=enable" via the kernel command string.
678 Please note that dynamic tick may affect the accuracy of
679 timekeeping on some platforms depending on the implementation.
680 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
681 to have accurate timekeeping with dynamic tick.
685 default 128 if ARCH_L7200
686 default 200 if ARCH_EBSA110 || ARCH_S3C2410
687 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
688 default AT91_TIMER_HZ if ARCH_AT91
692 bool "Use the ARM EABI to compile the kernel"
694 This option allows for the kernel to be compiled using the latest
695 ARM ABI (aka EABI). This is only useful if you are using a user
696 space environment that is also compiled with EABI.
698 Since there are major incompatibilities between the legacy ABI and
699 EABI, especially with regard to structure member alignment, this
700 option also changes the kernel syscall calling convention to
701 disambiguate both ABIs and allow for backward compatibility support
702 (selected with CONFIG_OABI_COMPAT).
704 To use this you need GCC version 4.0.0 or later.
707 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
708 depends on AEABI && EXPERIMENTAL
711 This option preserves the old syscall interface along with the
712 new (ARM EABI) one. It also provides a compatibility layer to
713 intercept syscalls that have structure arguments which layout
714 in memory differs between the legacy ABI and the new ARM EABI
715 (only for non "thumb" binaries). This option adds a tiny
716 overhead to all syscalls and produces a slightly larger kernel.
717 If you know you'll be using only pure EABI user space then you
718 can say N here. If this option is not selected and you attempt
719 to execute a legacy ABI binary then the result will be
720 UNPREDICTABLE (in fact it can be predicted that it won't work
721 at all). If in doubt say Y.
723 config ARCH_DISCONTIGMEM_ENABLE
725 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
727 Say Y to support efficient handling of discontiguous physical memory,
728 for architectures which are either NUMA (Non-Uniform Memory Access)
729 or have huge holes in the physical address space for other reasons.
730 See <file:Documentation/vm/numa> for more.
734 default "4" if ARCH_LH7A40X
736 depends on NEED_MULTIPLE_NODES
741 bool "Timer and CPU usage LEDs"
742 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
743 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
744 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
745 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
746 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
747 ARCH_AT91 || MACH_TRIZEPS4 || ARCH_DAVINCI || \
748 ARCH_KS8695 || MACH_RD88F5182
750 If you say Y here, the LEDs on your machine will be used
751 to provide useful information about your current system status.
753 If you are compiling a kernel for a NetWinder or EBSA-285, you will
754 be able to select which LEDs are active using the options below. If
755 you are compiling a kernel for the EBSA-110 or the LART however, the
756 red LED will simply flash regularly to indicate that the system is
757 still functional. It is safe to say Y here if you have a CATS
758 system, but the driver will do nothing.
761 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
762 OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
763 || MACH_OMAP_PERSEUS2
765 depends on !GENERIC_CLOCKEVENTS
766 default y if ARCH_EBSA110
768 If you say Y here, one of the system LEDs (the green one on the
769 NetWinder, the amber one on the EBSA285, or the red one on the LART)
770 will flash regularly to indicate that the system is still
771 operational. This is mainly useful to kernel hackers who are
772 debugging unstable kernels.
774 The LART uses the same LED for both Timer LED and CPU usage LED
775 functions. You may choose to use both, but the Timer LED function
776 will overrule the CPU usage LED.
779 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
781 || OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
782 || MACH_OMAP_PERSEUS2
785 If you say Y here, the red LED will be used to give a good real
786 time indication of CPU usage, by lighting whenever the idle task
787 is not currently executing.
789 The LART uses the same LED for both Timer LED and CPU usage LED
790 functions. You may choose to use both, but the Timer LED function
791 will overrule the CPU usage LED.
793 config ALIGNMENT_TRAP
795 depends on CPU_CP15_MMU
796 default y if !ARCH_EBSA110
798 ARM processors cannot fetch/store information which is not
799 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
800 address divisible by 4. On 32-bit ARM processors, these non-aligned
801 fetch/store instructions will be emulated in software if you say
802 here, which has a severe performance impact. This is necessary for
803 correct operation of some network protocols. With an IP-only
804 configuration it is safe to say N, otherwise say Y.
810 # Compressed boot loader in ROM. Yes, we really want to ask about
811 # TEXT and BSS so we preserve their values in the config files.
812 config ZBOOT_ROM_TEXT
813 hex "Compressed ROM boot loader base address"
816 The physical address at which the ROM-able zImage is to be
817 placed in the target. Platforms which normally make use of
818 ROM-able zImage formats normally set this to a suitable
819 value in their defconfig file.
821 If ZBOOT_ROM is not enabled, this has no effect.
824 hex "Compressed ROM boot loader BSS address"
827 The base address of an area of read/write memory in the target
828 for the ROM-able zImage which must be available while the
829 decompressor is running. It must be large enough to hold the
830 entire decompressed kernel plus an additional 128 KiB.
831 Platforms which normally make use of ROM-able zImage formats
832 normally set this to a suitable value in their defconfig file.
834 If ZBOOT_ROM is not enabled, this has no effect.
837 bool "Compressed boot loader in ROM/flash"
838 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
840 Say Y here if you intend to execute your compressed kernel image
841 (zImage) directly from ROM or flash. If unsure, say N.
844 string "Default kernel command string"
847 On some architectures (EBSA110 and CATS), there is currently no way
848 for the boot loader to pass arguments to the kernel. For these
849 architectures, you should supply some command-line options at build
850 time by entering them here. As a minimum, you should specify the
851 memory size and the root device (e.g., mem=64M root=/dev/nfs).
854 bool "Kernel Execute-In-Place from ROM"
855 depends on !ZBOOT_ROM
857 Execute-In-Place allows the kernel to run from non-volatile storage
858 directly addressable by the CPU, such as NOR flash. This saves RAM
859 space since the text section of the kernel is not loaded from flash
860 to RAM. Read-write sections, such as the data section and stack,
861 are still copied to RAM. The XIP kernel is not compressed since
862 it has to run directly from flash, so it will take more space to
863 store it. The flash address used to link the kernel object files,
864 and for storing it, is configuration dependent. Therefore, if you
865 say Y here, you must know the proper physical address where to
866 store the kernel image depending on your own flash memory usage.
868 Also note that the make target becomes "make xipImage" rather than
869 "make zImage" or "make Image". The final kernel binary to put in
870 ROM memory will be arch/arm/boot/xipImage.
875 hex "XIP Kernel Physical Location"
876 depends on XIP_KERNEL
879 This is the physical address in your flash memory the kernel will
880 be linked for and stored to. This address is dependent on your
884 bool "Kexec system call (EXPERIMENTAL)"
885 depends on EXPERIMENTAL
887 kexec is a system call that implements the ability to shutdown your
888 current kernel, and to start another kernel. It is like a reboot
889 but it is independent of the system firmware. And like a reboot
890 you can start any kernel with it, not just Linux.
892 It is an ongoing process to be certain the hardware in a machine
893 is properly shutdown, so do not be surprised if this code does not
894 initially work for you. It may help to enable device hotplugging
899 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX || ARCH_PXA)
901 menu "CPU Frequency scaling"
903 source "drivers/cpufreq/Kconfig"
905 config CPU_FREQ_SA1100
907 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
910 config CPU_FREQ_SA1110
912 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
915 config CPU_FREQ_INTEGRATOR
916 tristate "CPUfreq driver for ARM Integrator CPUs"
917 depends on ARCH_INTEGRATOR && CPU_FREQ
920 This enables the CPUfreq driver for ARM Integrator CPUs.
922 For details, take a look at <file:Documentation/cpu-freq>.
927 tristate "CPUfreq driver for i.MX CPUs"
928 depends on ARCH_IMX && CPU_FREQ
931 This enables the CPUfreq driver for i.MX CPUs.
937 depends on CPU_FREQ && ARCH_PXA && PXA25x
939 select CPU_FREQ_DEFAULT_GOV_USERSPACE
945 menu "Floating point emulation"
947 comment "At least one emulation must be selected"
950 bool "NWFPE math emulation"
951 depends on !AEABI || OABI_COMPAT
953 Say Y to include the NWFPE floating point emulator in the kernel.
954 This is necessary to run most binaries. Linux does not currently
955 support floating point hardware so you need to say Y here even if
956 your machine has an FPA or floating point co-processor podule.
958 You may say N here if you are going to load the Acorn FPEmulator
962 bool "Support extended precision"
965 Say Y to include 80-bit support in the kernel floating-point
966 emulator. Otherwise, only 32 and 64-bit support is compiled in.
967 Note that gcc does not generate 80-bit operations by default,
968 so in most cases this option only enlarges the size of the
969 floating point emulator without any good reason.
971 You almost surely want to say N here.
974 bool "FastFPE math emulation (EXPERIMENTAL)"
975 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
977 Say Y here to include the FAST floating point emulator in the kernel.
978 This is an experimental much faster emulator which now also has full
979 precision for the mantissa. It does not support any exceptions.
980 It is very simple, and approximately 3-6 times faster than NWFPE.
982 It should be sufficient for most programs. It may be not suitable
983 for scientific calculations, but you have to check this for yourself.
984 If you do not feel you need a faster FP emulation you should better
988 bool "VFP-format floating point maths"
989 depends on CPU_V6 || CPU_ARM926T || CPU_V7 || CPU_FEROCEON
991 Say Y to include VFP support code in the kernel. This is needed
992 if your hardware includes a VFP unit.
994 Please see <file:Documentation/arm/VFP/release-notes.txt> for
995 release notes and additional status information.
997 Say N if your target does not have VFP hardware.
1005 bool "Advanced SIMD (NEON) Extension support"
1006 depends on VFPv3 && CPU_V7
1008 Say Y to include support code for NEON, the ARMv7 Advanced SIMD
1013 menu "Userspace binary formats"
1015 source "fs/Kconfig.binfmt"
1018 tristate "RISC OS personality"
1021 Say Y here to include the kernel code necessary if you want to run
1022 Acorn RISC OS/Arthur binaries under Linux. This code is still very
1023 experimental; if this sounds frightening, say N and sleep in peace.
1024 You can also say M here to compile this support as a module (which
1025 will be called arthur).
1029 menu "Power management options"
1031 source "kernel/power/Kconfig"
1035 source "net/Kconfig"
1037 menu "Device Drivers"
1039 source "drivers/base/Kconfig"
1041 source "drivers/connector/Kconfig"
1043 if ALIGNMENT_TRAP || !CPU_CP15_MMU
1044 source "drivers/mtd/Kconfig"
1047 source "drivers/parport/Kconfig"
1049 source "drivers/pnp/Kconfig"
1051 source "drivers/block/Kconfig"
1053 # misc before ide - BLK_DEV_SGIIOC4 depends on SGI_IOC4
1055 source "drivers/misc/Kconfig"
1057 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
1058 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
1059 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
1061 source "drivers/ide/Kconfig"
1064 source "drivers/scsi/Kconfig"
1066 source "drivers/ata/Kconfig"
1068 source "drivers/md/Kconfig"
1070 source "drivers/message/fusion/Kconfig"
1072 source "drivers/ieee1394/Kconfig"
1074 source "drivers/message/i2o/Kconfig"
1076 source "drivers/net/Kconfig"
1078 source "drivers/isdn/Kconfig"
1080 # input before char - char/joystick depends on it. As does USB.
1082 source "drivers/input/Kconfig"
1084 source "drivers/char/Kconfig"
1086 source "drivers/i2c/Kconfig"
1088 source "drivers/spi/Kconfig"
1090 source "drivers/w1/Kconfig"
1092 source "drivers/power/Kconfig"
1094 source "drivers/hwmon/Kconfig"
1096 source "drivers/watchdog/Kconfig"
1098 source "drivers/ssb/Kconfig"
1100 #source "drivers/l3/Kconfig"
1102 source "drivers/mfd/Kconfig"
1104 source "drivers/media/Kconfig"
1106 source "drivers/video/Kconfig"
1108 source "sound/Kconfig"
1110 source "drivers/hid/Kconfig"
1112 source "drivers/usb/Kconfig"
1114 source "drivers/mmc/Kconfig"
1116 source "drivers/leds/Kconfig"
1118 source "drivers/rtc/Kconfig"
1120 source "drivers/dma/Kconfig"
1122 source "drivers/dca/Kconfig"
1128 source "arch/arm/Kconfig.instrumentation"
1130 source "arch/arm/Kconfig.debug"
1132 source "security/Kconfig"
1134 source "crypto/Kconfig"
1136 source "lib/Kconfig"