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 and AT91SAM9xxx 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
221 This enables support for the Cirrus EP93xx series of CPUs.
223 config ARCH_FOOTBRIDGE
227 Support for systems based on the DC21285 companion chip
228 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
231 bool "Hilscher NetX based"
234 This enables support for systems based on the Hilscher NetX Soc
237 bool "Hynix HMS720x-based"
240 This enables support for systems based on the Hynix HMS720x
246 select GENERIC_CLOCKEVENTS
248 Support for Motorola's i.MX family of processors (MX1, MXL).
255 select ARCH_SUPPORTS_MSI
257 Support for Intel's IOP13XX (XScale) family of processors.
265 Support for Intel's 80219 and IOP32X (XScale) family of
274 Support for Intel's IOP33X (XScale) family of processors.
281 Support for Intel's IXP23xx (XScale) family of processors.
284 bool "IXP2400/2800-based"
288 Support for Intel's IXP2400/2800 (XScale) family of processors.
295 select GENERIC_CLOCKEVENTS
297 Support for Intel's IXP4XX (XScale) family of processors.
303 Say Y here if you intend to run this kernel on a LinkUp Systems
304 L7200 Software Development Board which uses an ARM720T processor.
305 Information on this board can be obtained at:
307 <http://www.linkupsys.com/>
309 If you have any questions or comments about the Linux kernel port
310 to this board, send e-mail to <sjhill@cotw.com>.
313 bool "Micrel/Kendin KS8695"
316 Support for Micrel/Kendin KS8695 "Centaur" (ARM922T) based
317 System-on-Chip devices.
320 bool "NetSilicon NS9xxx"
323 select GENERIC_CLOCKEVENTS
325 Say Y here if you intend to run this kernel on a NetSilicon NS9xxx
328 <http://www.digi.com/products/microprocessors/index.jsp>
331 bool "Freescale MXC/iMX-based"
334 Support for Freescale MXC/iMX-based family of processors
341 Support for Marvell Orion System on Chip family.
344 bool "Philips Nexperia PNX4008 Mobile"
346 This enables support for Philips PNX4008 mobile platform.
349 bool "PXA2xx/PXA3xx-based"
354 select GENERIC_CLOCKEVENTS
356 Support for Intel/Marvell's PXA2xx/PXA3xx processor line.
363 select ARCH_MAY_HAVE_PC_FDC
367 On the Acorn Risc-PC, Linux can support the internal IDE disk and
368 CD-ROM interface, serial and parallel port, and the floppy drive.
373 select ARCH_DISCONTIGMEM_ENABLE
377 Support for StrongARM 11x0 based boards.
380 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442, S3C2443"
383 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
384 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
385 the Samsung SMDK2410 development board (and derivatives).
393 Support for the StrongARM based Digital DNARD machine, also known
394 as "Shark" (<http://www.shark-linux.de/shark.html>).
399 Say Y here for systems based on one of the Sharp LH7A40X
400 System on a Chip processors. These CPUs include an ARM922T
401 core with a wide array of integrated devices for
402 hand-held and low-power applications.
407 select GENERIC_CLOCKEVENTS
410 Support for TI's DaVinci platform.
417 Support for TI's OMAP platform (OMAP1 and OMAP2).
421 source "arch/arm/mach-clps711x/Kconfig"
423 source "arch/arm/mach-ep93xx/Kconfig"
425 source "arch/arm/mach-footbridge/Kconfig"
427 source "arch/arm/mach-integrator/Kconfig"
429 source "arch/arm/mach-iop32x/Kconfig"
431 source "arch/arm/mach-iop33x/Kconfig"
433 source "arch/arm/mach-iop13xx/Kconfig"
435 source "arch/arm/mach-ixp4xx/Kconfig"
437 source "arch/arm/mach-ixp2000/Kconfig"
439 source "arch/arm/mach-ixp23xx/Kconfig"
441 source "arch/arm/mach-pxa/Kconfig"
443 source "arch/arm/mach-sa1100/Kconfig"
445 source "arch/arm/plat-omap/Kconfig"
447 source "arch/arm/mach-omap1/Kconfig"
449 source "arch/arm/mach-omap2/Kconfig"
451 source "arch/arm/mach-orion/Kconfig"
453 source "arch/arm/plat-s3c24xx/Kconfig"
454 source "arch/arm/plat-s3c/Kconfig"
457 source "arch/arm/mach-s3c2400/Kconfig"
458 source "arch/arm/mach-s3c2410/Kconfig"
459 source "arch/arm/mach-s3c2412/Kconfig"
460 source "arch/arm/mach-s3c2440/Kconfig"
461 source "arch/arm/mach-s3c2442/Kconfig"
462 source "arch/arm/mach-s3c2443/Kconfig"
465 source "arch/arm/mach-lh7a40x/Kconfig"
467 source "arch/arm/mach-imx/Kconfig"
469 source "arch/arm/mach-h720x/Kconfig"
471 source "arch/arm/mach-versatile/Kconfig"
473 source "arch/arm/mach-aaec2000/Kconfig"
475 source "arch/arm/mach-realview/Kconfig"
477 source "arch/arm/mach-at91/Kconfig"
479 source "arch/arm/plat-mxc/Kconfig"
481 source "arch/arm/mach-netx/Kconfig"
483 source "arch/arm/mach-ns9xxx/Kconfig"
485 source "arch/arm/mach-davinci/Kconfig"
487 source "arch/arm/mach-ks8695/Kconfig"
489 # Definitions to make life easier
496 source arch/arm/mm/Kconfig
499 bool "Enable iWMMXt support"
500 depends on CPU_XSCALE || CPU_XSC3
501 default y if PXA27x || PXA3xx
503 Enable support for iWMMXt context switching at run time if
504 running on a CPU that supports it.
506 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
509 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
513 source "arch/arm/Kconfig-nommu"
518 source "arch/arm/common/Kconfig"
520 config FORCE_MAX_ZONEORDER
533 Find out whether you have ISA slots on your motherboard. ISA is the
534 name of a bus system, i.e. the way the CPU talks to the other stuff
535 inside your box. Other bus systems are PCI, EISA, MicroChannel
536 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
537 newer boards don't support it. If you have ISA, say Y, otherwise N.
539 # Select ISA DMA controller support
544 # Select ISA DMA interface
549 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX || ARCH_KS8695 || MACH_ARMCORE
551 Find out whether you have a PCI motherboard. PCI is the name of a
552 bus system, i.e. the way the CPU talks to the other stuff inside
553 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
554 VESA. If you have PCI, say Y, otherwise N.
556 The PCI-HOWTO, available from
557 <http://www.tldp.org/docs.html#howto>, contains valuable
558 information about which PCI hardware does work under Linux and which
564 # Select the host bridge type
565 config PCI_HOST_VIA82C505
567 depends on PCI && ARCH_SHARK
570 config PCI_HOST_ITE8152
572 depends on PCI && MACH_ARMCORE
576 source "drivers/pci/Kconfig"
578 source "drivers/pcmcia/Kconfig"
582 menu "Kernel Features"
584 source "kernel/time/Kconfig"
587 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
588 depends on EXPERIMENTAL && REALVIEW_MPCORE
590 This enables support for systems with more than one CPU. If you have
591 a system with only one CPU, like most personal computers, say N. If
592 you have a system with more than one CPU, say Y.
594 If you say N here, the kernel will run on single and multiprocessor
595 machines, but will use only one CPU of a multiprocessor machine. If
596 you say Y here, the kernel will run on many, but not all, single
597 processor machines. On a single processor machine, the kernel will
598 run faster if you say N here.
600 See also the <file:Documentation/smp.txt>,
601 <file:Documentation/i386/IO-APIC.txt>,
602 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
603 <http://www.linuxdoc.org/docs.html#howto>.
605 If you don't know what to do here, say N.
608 int "Maximum number of CPUs (2-32)"
614 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
615 depends on SMP && HOTPLUG && EXPERIMENTAL
617 Say Y here to experiment with turning CPUs off and on. CPUs
618 can be controlled through /sys/devices/system/cpu.
621 bool "Use local timer interrupts"
622 depends on SMP && REALVIEW_MPCORE
625 Enable support for local timers on SMP platforms, rather then the
626 legacy IPI broadcast method. Local timers allows the system
627 accounting to be spread across the timer interval, preventing a
628 "thundering herd" at every timer tick.
631 bool "Preemptible Kernel (EXPERIMENTAL)"
632 depends on EXPERIMENTAL
634 This option reduces the latency of the kernel when reacting to
635 real-time or interactive events by allowing a low priority process to
636 be preempted even if it is in kernel mode executing a system call.
637 This allows applications to run more reliably even when the system is
640 Say Y here if you are building a kernel for a desktop, embedded
641 or real-time system. Say N if you are unsure.
644 bool "Dynamic tick timer"
645 depends on !GENERIC_CLOCKEVENTS
647 Select this option if you want to disable continuous timer ticks
648 and have them programmed to occur as required. This option saves
649 power as the system can remain in idle state for longer.
651 By default dynamic tick is disabled during the boot, and can be
652 manually enabled with:
654 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
656 Alternatively, if you want dynamic tick automatically enabled
657 during boot, pass "dyntick=enable" via the kernel command string.
659 Please note that dynamic tick may affect the accuracy of
660 timekeeping on some platforms depending on the implementation.
661 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
662 to have accurate timekeeping with dynamic tick.
666 default 128 if ARCH_L7200
667 default 200 if ARCH_EBSA110 || ARCH_S3C2410
668 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
672 bool "Use the ARM EABI to compile the kernel"
674 This option allows for the kernel to be compiled using the latest
675 ARM ABI (aka EABI). This is only useful if you are using a user
676 space environment that is also compiled with EABI.
678 Since there are major incompatibilities between the legacy ABI and
679 EABI, especially with regard to structure member alignment, this
680 option also changes the kernel syscall calling convention to
681 disambiguate both ABIs and allow for backward compatibility support
682 (selected with CONFIG_OABI_COMPAT).
684 To use this you need GCC version 4.0.0 or later.
687 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
688 depends on AEABI && EXPERIMENTAL
691 This option preserves the old syscall interface along with the
692 new (ARM EABI) one. It also provides a compatibility layer to
693 intercept syscalls that have structure arguments which layout
694 in memory differs between the legacy ABI and the new ARM EABI
695 (only for non "thumb" binaries). This option adds a tiny
696 overhead to all syscalls and produces a slightly larger kernel.
697 If you know you'll be using only pure EABI user space then you
698 can say N here. If this option is not selected and you attempt
699 to execute a legacy ABI binary then the result will be
700 UNPREDICTABLE (in fact it can be predicted that it won't work
701 at all). If in doubt say Y.
703 config ARCH_DISCONTIGMEM_ENABLE
705 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
707 Say Y to support efficient handling of discontiguous physical memory,
708 for architectures which are either NUMA (Non-Uniform Memory Access)
709 or have huge holes in the physical address space for other reasons.
710 See <file:Documentation/vm/numa> for more.
714 default "4" if ARCH_LH7A40X
716 depends on NEED_MULTIPLE_NODES
721 bool "Timer and CPU usage LEDs"
722 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
723 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
724 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
725 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
726 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
727 ARCH_AT91 || MACH_TRIZEPS4 || ARCH_DAVINCI || \
730 If you say Y here, the LEDs on your machine will be used
731 to provide useful information about your current system status.
733 If you are compiling a kernel for a NetWinder or EBSA-285, you will
734 be able to select which LEDs are active using the options below. If
735 you are compiling a kernel for the EBSA-110 or the LART however, the
736 red LED will simply flash regularly to indicate that the system is
737 still functional. It is safe to say Y here if you have a CATS
738 system, but the driver will do nothing.
741 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
742 OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
743 || MACH_OMAP_PERSEUS2
745 depends on !GENERIC_CLOCKEVENTS
746 default y if ARCH_EBSA110
748 If you say Y here, one of the system LEDs (the green one on the
749 NetWinder, the amber one on the EBSA285, or the red one on the LART)
750 will flash regularly to indicate that the system is still
751 operational. This is mainly useful to kernel hackers who are
752 debugging unstable kernels.
754 The LART uses the same LED for both Timer LED and CPU usage LED
755 functions. You may choose to use both, but the Timer LED function
756 will overrule the CPU usage LED.
759 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
761 || OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
762 || MACH_OMAP_PERSEUS2
765 If you say Y here, the red LED will be used to give a good real
766 time indication of CPU usage, by lighting whenever the idle task
767 is not currently executing.
769 The LART uses the same LED for both Timer LED and CPU usage LED
770 functions. You may choose to use both, but the Timer LED function
771 will overrule the CPU usage LED.
773 config ALIGNMENT_TRAP
775 depends on CPU_CP15_MMU
776 default y if !ARCH_EBSA110
778 ARM processors cannot fetch/store information which is not
779 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
780 address divisible by 4. On 32-bit ARM processors, these non-aligned
781 fetch/store instructions will be emulated in software if you say
782 here, which has a severe performance impact. This is necessary for
783 correct operation of some network protocols. With an IP-only
784 configuration it is safe to say N, otherwise say Y.
790 # Compressed boot loader in ROM. Yes, we really want to ask about
791 # TEXT and BSS so we preserve their values in the config files.
792 config ZBOOT_ROM_TEXT
793 hex "Compressed ROM boot loader base address"
796 The physical address at which the ROM-able zImage is to be
797 placed in the target. Platforms which normally make use of
798 ROM-able zImage formats normally set this to a suitable
799 value in their defconfig file.
801 If ZBOOT_ROM is not enabled, this has no effect.
804 hex "Compressed ROM boot loader BSS address"
807 The base address of an area of read/write memory in the target
808 for the ROM-able zImage which must be available while the
809 decompressor is running. It must be large enough to hold the
810 entire decompressed kernel plus an additional 128 KiB.
811 Platforms which normally make use of ROM-able zImage formats
812 normally set this to a suitable value in their defconfig file.
814 If ZBOOT_ROM is not enabled, this has no effect.
817 bool "Compressed boot loader in ROM/flash"
818 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
820 Say Y here if you intend to execute your compressed kernel image
821 (zImage) directly from ROM or flash. If unsure, say N.
824 string "Default kernel command string"
827 On some architectures (EBSA110 and CATS), there is currently no way
828 for the boot loader to pass arguments to the kernel. For these
829 architectures, you should supply some command-line options at build
830 time by entering them here. As a minimum, you should specify the
831 memory size and the root device (e.g., mem=64M root=/dev/nfs).
834 bool "Kernel Execute-In-Place from ROM"
835 depends on !ZBOOT_ROM
837 Execute-In-Place allows the kernel to run from non-volatile storage
838 directly addressable by the CPU, such as NOR flash. This saves RAM
839 space since the text section of the kernel is not loaded from flash
840 to RAM. Read-write sections, such as the data section and stack,
841 are still copied to RAM. The XIP kernel is not compressed since
842 it has to run directly from flash, so it will take more space to
843 store it. The flash address used to link the kernel object files,
844 and for storing it, is configuration dependent. Therefore, if you
845 say Y here, you must know the proper physical address where to
846 store the kernel image depending on your own flash memory usage.
848 Also note that the make target becomes "make xipImage" rather than
849 "make zImage" or "make Image". The final kernel binary to put in
850 ROM memory will be arch/arm/boot/xipImage.
855 hex "XIP Kernel Physical Location"
856 depends on XIP_KERNEL
859 This is the physical address in your flash memory the kernel will
860 be linked for and stored to. This address is dependent on your
864 bool "Kexec system call (EXPERIMENTAL)"
865 depends on EXPERIMENTAL
867 kexec is a system call that implements the ability to shutdown your
868 current kernel, and to start another kernel. It is like a reboot
869 but it is independent of the system firmware. And like a reboot
870 you can start any kernel with it, not just Linux.
872 It is an ongoing process to be certain the hardware in a machine
873 is properly shutdown, so do not be surprised if this code does not
874 initially work for you. It may help to enable device hotplugging
879 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
881 menu "CPU Frequency scaling"
883 source "drivers/cpufreq/Kconfig"
885 config CPU_FREQ_SA1100
887 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
890 config CPU_FREQ_SA1110
892 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
895 config CPU_FREQ_INTEGRATOR
896 tristate "CPUfreq driver for ARM Integrator CPUs"
897 depends on ARCH_INTEGRATOR && CPU_FREQ
900 This enables the CPUfreq driver for ARM Integrator CPUs.
902 For details, take a look at <file:Documentation/cpu-freq>.
907 tristate "CPUfreq driver for i.MX CPUs"
908 depends on ARCH_IMX && CPU_FREQ
911 This enables the CPUfreq driver for i.MX CPUs.
919 menu "Floating point emulation"
921 comment "At least one emulation must be selected"
924 bool "NWFPE math emulation"
925 depends on !AEABI || OABI_COMPAT
927 Say Y to include the NWFPE floating point emulator in the kernel.
928 This is necessary to run most binaries. Linux does not currently
929 support floating point hardware so you need to say Y here even if
930 your machine has an FPA or floating point co-processor podule.
932 You may say N here if you are going to load the Acorn FPEmulator
936 bool "Support extended precision"
939 Say Y to include 80-bit support in the kernel floating-point
940 emulator. Otherwise, only 32 and 64-bit support is compiled in.
941 Note that gcc does not generate 80-bit operations by default,
942 so in most cases this option only enlarges the size of the
943 floating point emulator without any good reason.
945 You almost surely want to say N here.
948 bool "FastFPE math emulation (EXPERIMENTAL)"
949 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
951 Say Y here to include the FAST floating point emulator in the kernel.
952 This is an experimental much faster emulator which now also has full
953 precision for the mantissa. It does not support any exceptions.
954 It is very simple, and approximately 3-6 times faster than NWFPE.
956 It should be sufficient for most programs. It may be not suitable
957 for scientific calculations, but you have to check this for yourself.
958 If you do not feel you need a faster FP emulation you should better
962 bool "VFP-format floating point maths"
963 depends on CPU_V6 || CPU_ARM926T || CPU_FEROCEON
965 Say Y to include VFP support code in the kernel. This is needed
966 if your hardware includes a VFP unit.
968 Please see <file:Documentation/arm/VFP/release-notes.txt> for
969 release notes and additional status information.
971 Say N if your target does not have VFP hardware.
975 menu "Userspace binary formats"
977 source "fs/Kconfig.binfmt"
980 tristate "RISC OS personality"
983 Say Y here to include the kernel code necessary if you want to run
984 Acorn RISC OS/Arthur binaries under Linux. This code is still very
985 experimental; if this sounds frightening, say N and sleep in peace.
986 You can also say M here to compile this support as a module (which
987 will be called arthur).
991 menu "Power management options"
993 source "kernel/power/Kconfig"
999 menu "Device Drivers"
1001 source "drivers/base/Kconfig"
1003 source "drivers/connector/Kconfig"
1005 if ALIGNMENT_TRAP || !CPU_CP15_MMU
1006 source "drivers/mtd/Kconfig"
1009 source "drivers/parport/Kconfig"
1011 source "drivers/pnp/Kconfig"
1013 source "drivers/block/Kconfig"
1015 # misc before ide - BLK_DEV_SGIIOC4 depends on SGI_IOC4
1017 source "drivers/misc/Kconfig"
1019 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
1020 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
1021 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
1023 source "drivers/ide/Kconfig"
1026 source "drivers/scsi/Kconfig"
1028 source "drivers/ata/Kconfig"
1030 source "drivers/md/Kconfig"
1032 source "drivers/message/fusion/Kconfig"
1034 source "drivers/ieee1394/Kconfig"
1036 source "drivers/message/i2o/Kconfig"
1038 source "drivers/net/Kconfig"
1040 source "drivers/isdn/Kconfig"
1042 # input before char - char/joystick depends on it. As does USB.
1044 source "drivers/input/Kconfig"
1046 source "drivers/char/Kconfig"
1048 source "drivers/i2c/Kconfig"
1050 source "drivers/spi/Kconfig"
1052 source "drivers/w1/Kconfig"
1054 source "drivers/power/Kconfig"
1056 source "drivers/hwmon/Kconfig"
1058 source "drivers/watchdog/Kconfig"
1060 source "drivers/ssb/Kconfig"
1062 #source "drivers/l3/Kconfig"
1064 source "drivers/mfd/Kconfig"
1066 source "drivers/media/Kconfig"
1068 source "drivers/video/Kconfig"
1070 source "sound/Kconfig"
1072 source "drivers/hid/Kconfig"
1074 source "drivers/usb/Kconfig"
1076 source "drivers/mmc/Kconfig"
1078 source "drivers/leds/Kconfig"
1080 source "drivers/rtc/Kconfig"
1082 source "drivers/dma/Kconfig"
1084 source "drivers/dca/Kconfig"
1090 source "arch/arm/Kconfig.instrumentation"
1092 source "arch/arm/Kconfig.debug"
1094 source "security/Kconfig"
1096 source "crypto/Kconfig"
1098 source "lib/Kconfig"