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
43 The Extended Industry Standard Architecture (EISA) bus was
44 developed as an open alternative to the IBM MicroChannel bus.
46 The EISA bus provided some of the features of the IBM MicroChannel
47 bus while maintaining backward compatibility with cards made for
48 the older ISA bus. The EISA bus saw limited use between 1988 and
49 1995 when it was made obsolete by the PCI bus.
51 Say Y here if you are building a kernel for an EISA-based machine.
61 MicroChannel Architecture is found in some IBM PS/2 machines and
62 laptops. It is a bus system similar to PCI or ISA. See
63 <file:Documentation/mca.txt> (and especially the web page given
64 there) before attempting to build an MCA bus kernel.
66 config GENERIC_HARDIRQS
70 config TRACE_IRQFLAGS_SUPPORT
74 config HARDIRQS_SW_RESEND
78 config GENERIC_IRQ_PROBE
82 config RWSEM_GENERIC_SPINLOCK
86 config RWSEM_XCHGADD_ALGORITHM
89 config ARCH_HAS_ILOG2_U32
93 config ARCH_HAS_ILOG2_U64
97 config GENERIC_HWEIGHT
101 config GENERIC_CALIBRATE_DELAY
105 config GENERIC_BUST_SPINLOCK
108 config ARCH_MAY_HAVE_PC_FDC
115 config GENERIC_ISA_DMA
126 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
127 default DRAM_BASE if REMAP_VECTORS_TO_RAM
130 The base address of exception vectors.
132 source "init/Kconfig"
137 prompt "ARM system type"
138 default ARCH_VERSATILE
141 bool "Agilent AAEC-2000 based"
144 This enables support for systems based on the Agilent AAEC-2000
146 config ARCH_INTEGRATOR
147 bool "ARM Ltd. Integrator family"
151 Support for ARM's Integrator platform.
154 bool "ARM Ltd. RealView family"
158 This enables support for ARM Ltd RealView boards.
160 config ARCH_VERSATILE
161 bool "ARM Ltd. Versatile family"
166 This enables support for ARM Ltd Versatile board.
172 This enables support for systems based on the Atmel AT91RM9200
173 and AT91SAM9xxx processors.
176 bool "Cirrus CL-PS7500FE"
181 Support for the Cirrus Logic PS7500FE system-on-a-chip.
184 bool "Cirrus Logic CLPS711x/EP721x-based"
186 Support for Cirrus Logic 711x/721x based boards.
191 select FOOTBRIDGE_ADDIN
193 Support for Intel's EBSA285 companion chip.
200 This is an evaluation board for the StrongARM processor available
201 from Digital. It has limited hardware on-board, including an
202 Ethernet interface, two PCMCIA sockets, two serial ports and a
210 This enables support for the Cirrus EP93xx series of CPUs.
212 config ARCH_FOOTBRIDGE
216 Support for systems based on the DC21285 companion chip
217 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
220 bool "Hilscher NetX based"
223 This enables support for systems based on the Hilscher NetX Soc
226 bool "Hynix HMS720x-based"
229 This enables support for systems based on the Hynix HMS720x
234 Support for Motorola's i.MX family of processors (MX1, MXL).
242 Support for Intel's 80219 and IOP32X (XScale) family of
251 Support for Intel's IOP33X (XScale) family of processors.
259 Support for Intel's IOP13XX (XScale) family of processors.
266 Support for Intel's IXP4XX (XScale) family of processors.
269 bool "IXP2400/2800-based"
273 Support for Intel's IXP2400/2800 (XScale) family of processors.
280 Support for Intel's IXP23xx (XScale) family of processors.
286 Say Y here if you intend to run this kernel on a LinkUp Systems
287 L7200 Software Development Board which uses an ARM720T processor.
288 Information on this board can be obtained at:
290 <http://www.linkupsys.com/>
292 If you have any questions or comments about the Linux kernel port
293 to this board, send e-mail to <sjhill@cotw.com>.
296 bool "NetSilicon NS9xxx"
298 Say Y here if you intend to run this kernel on a NetSilicon NS9xxx
301 <http://www.digi.com/products/microprocessors/index.jsp>
304 bool "Philips Nexperia PNX4008 Mobile"
306 This enables support for Philips PNX4008 mobile platform.
315 Support for Intel's PXA2XX processor line.
322 select ARCH_MAY_HAVE_PC_FDC
326 On the Acorn Risc-PC, Linux can support the internal IDE disk and
327 CD-ROM interface, serial and parallel port, and the floppy drive.
332 select ARCH_DISCONTIGMEM_ENABLE
336 Support for StrongARM 11x0 based boards.
339 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442, S3C2443"
342 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
343 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
344 the Samsung SMDK2410 development board (and derivatives).
352 Support for the StrongARM based Digital DNARD machine, also known
353 as "Shark" (<http://www.shark-linux.de/shark.html>).
358 Say Y here for systems based on one of the Sharp LH7A40X
359 System on a Chip processors. These CPUs include an ARM922T
360 core with a wide array of integrated devices for
361 hand-held and low-power applications.
368 Support for TI's OMAP platform (OMAP1 and OMAP2).
372 source "arch/arm/mach-clps711x/Kconfig"
374 source "arch/arm/mach-ep93xx/Kconfig"
376 source "arch/arm/mach-footbridge/Kconfig"
378 source "arch/arm/mach-integrator/Kconfig"
380 source "arch/arm/mach-iop32x/Kconfig"
382 source "arch/arm/mach-iop33x/Kconfig"
384 source "arch/arm/mach-iop13xx/Kconfig"
386 source "arch/arm/mach-ixp4xx/Kconfig"
388 source "arch/arm/mach-ixp2000/Kconfig"
390 source "arch/arm/mach-ixp23xx/Kconfig"
392 source "arch/arm/mach-pxa/Kconfig"
394 source "arch/arm/mach-sa1100/Kconfig"
396 source "arch/arm/plat-omap/Kconfig"
398 source "arch/arm/mach-omap1/Kconfig"
400 source "arch/arm/mach-omap2/Kconfig"
402 source "arch/arm/plat-s3c24xx/Kconfig"
405 source "arch/arm/mach-s3c2400/Kconfig"
406 source "arch/arm/mach-s3c2410/Kconfig"
407 source "arch/arm/mach-s3c2412/Kconfig"
408 source "arch/arm/mach-s3c2440/Kconfig"
409 source "arch/arm/mach-s3c2442/Kconfig"
410 source "arch/arm/mach-s3c2443/Kconfig"
413 source "arch/arm/mach-lh7a40x/Kconfig"
415 source "arch/arm/mach-imx/Kconfig"
417 source "arch/arm/mach-h720x/Kconfig"
419 source "arch/arm/mach-versatile/Kconfig"
421 source "arch/arm/mach-aaec2000/Kconfig"
423 source "arch/arm/mach-realview/Kconfig"
425 source "arch/arm/mach-at91/Kconfig"
427 source "arch/arm/mach-netx/Kconfig"
429 source "arch/arm/mach-ns9xxx/Kconfig"
431 # Definitions to make life easier
438 source arch/arm/mm/Kconfig
441 bool "Enable iWMMXt support"
442 depends on CPU_XSCALE || CPU_XSC3
445 Enable support for iWMMXt context switching at run time if
446 running on a CPU that supports it.
448 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
451 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
455 source "arch/arm/Kconfig-nommu"
460 source "arch/arm/common/Kconfig"
462 config FORCE_MAX_ZONEORDER
475 Find out whether you have ISA slots on your motherboard. ISA is the
476 name of a bus system, i.e. the way the CPU talks to the other stuff
477 inside your box. Other bus systems are PCI, EISA, MicroChannel
478 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
479 newer boards don't support it. If you have ISA, say Y, otherwise N.
481 # Select ISA DMA controller support
486 # Select ISA DMA interface
491 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
493 Find out whether you have a PCI motherboard. PCI is the name of a
494 bus system, i.e. the way the CPU talks to the other stuff inside
495 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
496 VESA. If you have PCI, say Y, otherwise N.
498 The PCI-HOWTO, available from
499 <http://www.tldp.org/docs.html#howto>, contains valuable
500 information about which PCI hardware does work under Linux and which
503 # Select the host bridge type
504 config PCI_HOST_VIA82C505
506 depends on PCI && ARCH_SHARK
509 source "drivers/pci/Kconfig"
511 source "drivers/pcmcia/Kconfig"
515 menu "Kernel Features"
518 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
519 depends on EXPERIMENTAL && REALVIEW_MPCORE
521 This enables support for systems with more than one CPU. If you have
522 a system with only one CPU, like most personal computers, say N. If
523 you have a system with more than one CPU, say Y.
525 If you say N here, the kernel will run on single and multiprocessor
526 machines, but will use only one CPU of a multiprocessor machine. If
527 you say Y here, the kernel will run on many, but not all, single
528 processor machines. On a single processor machine, the kernel will
529 run faster if you say N here.
531 See also the <file:Documentation/smp.txt>,
532 <file:Documentation/i386/IO-APIC.txt>,
533 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
534 <http://www.linuxdoc.org/docs.html#howto>.
536 If you don't know what to do here, say N.
539 int "Maximum number of CPUs (2-32)"
545 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
546 depends on SMP && HOTPLUG && EXPERIMENTAL
548 Say Y here to experiment with turning CPUs off and on. CPUs
549 can be controlled through /sys/devices/system/cpu.
552 bool "Use local timer interrupts"
553 depends on SMP && REALVIEW_MPCORE
556 Enable support for local timers on SMP platforms, rather then the
557 legacy IPI broadcast method. Local timers allows the system
558 accounting to be spread across the timer interval, preventing a
559 "thundering herd" at every timer tick.
562 bool "Preemptible Kernel (EXPERIMENTAL)"
563 depends on EXPERIMENTAL
565 This option reduces the latency of the kernel when reacting to
566 real-time or interactive events by allowing a low priority process to
567 be preempted even if it is in kernel mode executing a system call.
568 This allows applications to run more reliably even when the system is
571 Say Y here if you are building a kernel for a desktop, embedded
572 or real-time system. Say N if you are unsure.
575 bool "Dynamic tick timer"
577 Select this option if you want to disable continuous timer ticks
578 and have them programmed to occur as required. This option saves
579 power as the system can remain in idle state for longer.
581 By default dynamic tick is disabled during the boot, and can be
582 manually enabled with:
584 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
586 Alternatively, if you want dynamic tick automatically enabled
587 during boot, pass "dyntick=enable" via the kernel command string.
589 Please note that dynamic tick may affect the accuracy of
590 timekeeping on some platforms depending on the implementation.
591 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
592 to have accurate timekeeping with dynamic tick.
596 default 128 if ARCH_L7200
597 default 200 if ARCH_EBSA110 || ARCH_S3C2410
598 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
602 bool "Use the ARM EABI to compile the kernel"
604 This option allows for the kernel to be compiled using the latest
605 ARM ABI (aka EABI). This is only useful if you are using a user
606 space environment that is also compiled with EABI.
608 Since there are major incompatibilities between the legacy ABI and
609 EABI, especially with regard to structure member alignment, this
610 option also changes the kernel syscall calling convention to
611 disambiguate both ABIs and allow for backward compatibility support
612 (selected with CONFIG_OABI_COMPAT).
614 To use this you need GCC version 4.0.0 or later.
617 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
618 depends on AEABI && EXPERIMENTAL
621 This option preserves the old syscall interface along with the
622 new (ARM EABI) one. It also provides a compatibility layer to
623 intercept syscalls that have structure arguments which layout
624 in memory differs between the legacy ABI and the new ARM EABI
625 (only for non "thumb" binaries). This option adds a tiny
626 overhead to all syscalls and produces a slightly larger kernel.
627 If you know you'll be using only pure EABI user space then you
628 can say N here. If this option is not selected and you attempt
629 to execute a legacy ABI binary then the result will be
630 UNPREDICTABLE (in fact it can be predicted that it won't work
631 at all). If in doubt say Y.
633 config ARCH_DISCONTIGMEM_ENABLE
635 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
637 Say Y to support efficient handling of discontiguous physical memory,
638 for architectures which are either NUMA (Non-Uniform Memory Access)
639 or have huge holes in the physical address space for other reasons.
640 See <file:Documentation/vm/numa> for more.
644 default "4" if ARCH_LH7A40X
646 depends on NEED_MULTIPLE_NODES
651 bool "Timer and CPU usage LEDs"
652 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
653 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
654 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
655 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
656 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
657 ARCH_AT91 || MACH_TRIZEPS4
659 If you say Y here, the LEDs on your machine will be used
660 to provide useful information about your current system status.
662 If you are compiling a kernel for a NetWinder or EBSA-285, you will
663 be able to select which LEDs are active using the options below. If
664 you are compiling a kernel for the EBSA-110 or the LART however, the
665 red LED will simply flash regularly to indicate that the system is
666 still functional. It is safe to say Y here if you have a CATS
667 system, but the driver will do nothing.
670 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
671 OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
672 || MACH_OMAP_PERSEUS2
674 default y if ARCH_EBSA110
676 If you say Y here, one of the system LEDs (the green one on the
677 NetWinder, the amber one on the EBSA285, or the red one on the LART)
678 will flash regularly to indicate that the system is still
679 operational. This is mainly useful to kernel hackers who are
680 debugging unstable kernels.
682 The LART uses the same LED for both Timer LED and CPU usage LED
683 functions. You may choose to use both, but the Timer LED function
684 will overrule the CPU usage LED.
687 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
689 || OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
690 || MACH_OMAP_PERSEUS2
693 If you say Y here, the red LED will be used to give a good real
694 time indication of CPU usage, by lighting whenever the idle task
695 is not currently executing.
697 The LART uses the same LED for both Timer LED and CPU usage LED
698 functions. You may choose to use both, but the Timer LED function
699 will overrule the CPU usage LED.
701 config ALIGNMENT_TRAP
703 depends on CPU_CP15_MMU
704 default y if !ARCH_EBSA110
706 ARM processors cannot fetch/store information which is not
707 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
708 address divisible by 4. On 32-bit ARM processors, these non-aligned
709 fetch/store instructions will be emulated in software if you say
710 here, which has a severe performance impact. This is necessary for
711 correct operation of some network protocols. With an IP-only
712 configuration it is safe to say N, otherwise say Y.
718 # Compressed boot loader in ROM. Yes, we really want to ask about
719 # TEXT and BSS so we preserve their values in the config files.
720 config ZBOOT_ROM_TEXT
721 hex "Compressed ROM boot loader base address"
724 The physical address at which the ROM-able zImage is to be
725 placed in the target. Platforms which normally make use of
726 ROM-able zImage formats normally set this to a suitable
727 value in their defconfig file.
729 If ZBOOT_ROM is not enabled, this has no effect.
732 hex "Compressed ROM boot loader BSS address"
735 The base address of an area of read/write memory in the target
736 for the ROM-able zImage which must be available while the
737 decompressor is running. It must be large enough to hold the
738 entire decompressed kernel plus an additional 128 KiB.
739 Platforms which normally make use of ROM-able zImage formats
740 normally set this to a suitable value in their defconfig file.
742 If ZBOOT_ROM is not enabled, this has no effect.
745 bool "Compressed boot loader in ROM/flash"
746 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
748 Say Y here if you intend to execute your compressed kernel image
749 (zImage) directly from ROM or flash. If unsure, say N.
752 string "Default kernel command string"
755 On some architectures (EBSA110 and CATS), there is currently no way
756 for the boot loader to pass arguments to the kernel. For these
757 architectures, you should supply some command-line options at build
758 time by entering them here. As a minimum, you should specify the
759 memory size and the root device (e.g., mem=64M root=/dev/nfs).
762 bool "Kernel Execute-In-Place from ROM"
763 depends on !ZBOOT_ROM
765 Execute-In-Place allows the kernel to run from non-volatile storage
766 directly addressable by the CPU, such as NOR flash. This saves RAM
767 space since the text section of the kernel is not loaded from flash
768 to RAM. Read-write sections, such as the data section and stack,
769 are still copied to RAM. The XIP kernel is not compressed since
770 it has to run directly from flash, so it will take more space to
771 store it. The flash address used to link the kernel object files,
772 and for storing it, is configuration dependent. Therefore, if you
773 say Y here, you must know the proper physical address where to
774 store the kernel image depending on your own flash memory usage.
776 Also note that the make target becomes "make xipImage" rather than
777 "make zImage" or "make Image". The final kernel binary to put in
778 ROM memory will be arch/arm/boot/xipImage.
783 hex "XIP Kernel Physical Location"
784 depends on XIP_KERNEL
787 This is the physical address in your flash memory the kernel will
788 be linked for and stored to. This address is dependent on your
792 bool "Kexec system call (EXPERIMENTAL)"
793 depends on EXPERIMENTAL
795 kexec is a system call that implements the ability to shutdown your
796 current kernel, and to start another kernel. It is like a reboot
797 but it is indepedent of the system firmware. And like a reboot
798 you can start any kernel with it, not just Linux.
800 It is an ongoing process to be certain the hardware in a machine
801 is properly shutdown, so do not be surprised if this code does not
802 initially work for you. It may help to enable device hotplugging
807 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
809 menu "CPU Frequency scaling"
811 source "drivers/cpufreq/Kconfig"
813 config CPU_FREQ_SA1100
815 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
818 config CPU_FREQ_SA1110
820 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
823 config CPU_FREQ_INTEGRATOR
824 tristate "CPUfreq driver for ARM Integrator CPUs"
825 depends on ARCH_INTEGRATOR && CPU_FREQ
828 This enables the CPUfreq driver for ARM Integrator CPUs.
830 For details, take a look at <file:Documentation/cpu-freq>.
835 tristate "CPUfreq driver for i.MX CPUs"
836 depends on ARCH_IMX && CPU_FREQ
839 This enables the CPUfreq driver for i.MX CPUs.
847 menu "Floating point emulation"
849 comment "At least one emulation must be selected"
852 bool "NWFPE math emulation"
853 depends on !AEABI || OABI_COMPAT
855 Say Y to include the NWFPE floating point emulator in the kernel.
856 This is necessary to run most binaries. Linux does not currently
857 support floating point hardware so you need to say Y here even if
858 your machine has an FPA or floating point co-processor podule.
860 You may say N here if you are going to load the Acorn FPEmulator
864 bool "Support extended precision"
867 Say Y to include 80-bit support in the kernel floating-point
868 emulator. Otherwise, only 32 and 64-bit support is compiled in.
869 Note that gcc does not generate 80-bit operations by default,
870 so in most cases this option only enlarges the size of the
871 floating point emulator without any good reason.
873 You almost surely want to say N here.
876 bool "FastFPE math emulation (EXPERIMENTAL)"
877 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
879 Say Y here to include the FAST floating point emulator in the kernel.
880 This is an experimental much faster emulator which now also has full
881 precision for the mantissa. It does not support any exceptions.
882 It is very simple, and approximately 3-6 times faster than NWFPE.
884 It should be sufficient for most programs. It may be not suitable
885 for scientific calculations, but you have to check this for yourself.
886 If you do not feel you need a faster FP emulation you should better
890 bool "VFP-format floating point maths"
891 depends on CPU_V6 || CPU_ARM926T
893 Say Y to include VFP support code in the kernel. This is needed
894 if your hardware includes a VFP unit.
896 Please see <file:Documentation/arm/VFP/release-notes.txt> for
897 release notes and additional status information.
899 Say N if your target does not have VFP hardware.
903 menu "Userspace binary formats"
905 source "fs/Kconfig.binfmt"
908 tristate "RISC OS personality"
911 Say Y here to include the kernel code necessary if you want to run
912 Acorn RISC OS/Arthur binaries under Linux. This code is still very
913 experimental; if this sounds frightening, say N and sleep in peace.
914 You can also say M here to compile this support as a module (which
915 will be called arthur).
919 menu "Power management options"
921 source "kernel/power/Kconfig"
927 menu "Device Drivers"
929 source "drivers/base/Kconfig"
931 source "drivers/connector/Kconfig"
933 if ALIGNMENT_TRAP || !CPU_CP15_MMU
934 source "drivers/mtd/Kconfig"
937 source "drivers/parport/Kconfig"
939 source "drivers/pnp/Kconfig"
941 source "drivers/block/Kconfig"
943 source "drivers/acorn/block/Kconfig"
945 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
946 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
947 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
949 source "drivers/ide/Kconfig"
952 source "drivers/scsi/Kconfig"
954 source "drivers/ata/Kconfig"
956 source "drivers/md/Kconfig"
958 source "drivers/message/fusion/Kconfig"
960 source "drivers/ieee1394/Kconfig"
962 source "drivers/message/i2o/Kconfig"
964 source "drivers/net/Kconfig"
966 source "drivers/isdn/Kconfig"
968 # input before char - char/joystick depends on it. As does USB.
970 source "drivers/input/Kconfig"
972 source "drivers/char/Kconfig"
974 source "drivers/i2c/Kconfig"
976 source "drivers/spi/Kconfig"
978 source "drivers/w1/Kconfig"
980 source "drivers/hwmon/Kconfig"
982 #source "drivers/l3/Kconfig"
984 source "drivers/misc/Kconfig"
986 source "drivers/mfd/Kconfig"
988 source "drivers/leds/Kconfig"
990 source "drivers/media/Kconfig"
992 source "drivers/video/Kconfig"
994 source "sound/Kconfig"
996 source "drivers/hid/Kconfig"
998 source "drivers/usb/Kconfig"
1000 source "drivers/mmc/Kconfig"
1002 source "drivers/rtc/Kconfig"
1005 source "drivers/cbus/Kconfig"
1012 source "arch/arm/oprofile/Kconfig"
1014 source "arch/arm/Kconfig.debug"
1016 source "security/Kconfig"
1018 source "crypto/Kconfig"
1020 source "lib/Kconfig"