2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "Linux Kernel Configuration"
13 The ARM series is a line of low-power-consumption RISC chip designs
14 licensed by ARM Ltd and targeted at embedded applications and
15 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
16 manufactured, but legacy ARM-based PC hardware remains popular in
17 Europe. There is an ARM Linux project with a web page at
18 <http://www.arm.linux.org.uk/>.
31 The Extended Industry Standard Architecture (EISA) bus was
32 developed as an open alternative to the IBM MicroChannel bus.
34 The EISA bus provided some of the features of the IBM MicroChannel
35 bus while maintaining backward compatibility with cards made for
36 the older ISA bus. The EISA bus saw limited use between 1988 and
37 1995 when it was made obsolete by the PCI bus.
39 Say Y here if you are building a kernel for an EISA-based machine.
49 MicroChannel Architecture is found in some IBM PS/2 machines and
50 laptops. It is a bus system similar to PCI or ISA. See
51 <file:Documentation/mca.txt> (and especially the web page given
52 there) before attempting to build an MCA bus kernel.
54 config GENERIC_HARDIRQS
58 config TRACE_IRQFLAGS_SUPPORT
62 config HARDIRQS_SW_RESEND
66 config GENERIC_IRQ_PROBE
70 config RWSEM_GENERIC_SPINLOCK
74 config RWSEM_XCHGADD_ALGORITHM
77 config ARCH_HAS_ILOG2_U32
81 config ARCH_HAS_ILOG2_U64
85 config GENERIC_HWEIGHT
89 config GENERIC_CALIBRATE_DELAY
93 config GENERIC_BUST_SPINLOCK
96 config ARCH_MAY_HAVE_PC_FDC
99 config GENERIC_ISA_DMA
110 default 0xffff0000 if MMU || CPU_HIGH_VECTOR
111 default DRAM_BASE if REMAP_VECTORS_TO_RAM
114 The base address of exception vectors.
116 source "init/Kconfig"
121 prompt "ARM system type"
122 default ARCH_VERSATILE
125 bool "Agilent AAEC-2000 based"
128 This enables support for systems based on the Agilent AAEC-2000
130 config ARCH_INTEGRATOR
131 bool "ARM Ltd. Integrator family"
135 Support for ARM's Integrator platform.
138 bool "ARM Ltd. RealView family"
142 This enables support for ARM Ltd RealView boards.
144 config ARCH_VERSATILE
145 bool "ARM Ltd. Versatile family"
150 This enables support for ARM Ltd Versatile board.
155 This enables support for systems based on the Atmel AT91RM9200
156 and AT91SAM9xxx processors.
159 bool "Cirrus CL-PS7500FE"
163 Support for the Cirrus Logic PS7500FE system-on-a-chip.
166 bool "Cirrus Logic CLPS711x/EP721x-based"
168 Support for Cirrus Logic 711x/721x based boards.
173 select FOOTBRIDGE_ADDIN
175 Support for Intel's EBSA285 companion chip.
181 This is an evaluation board for the StrongARM processor available
182 from Digital. It has limited hardware on-board, including an
183 Ethernet interface, two PCMCIA sockets, two serial ports and a
191 This enables support for the Cirrus EP93xx series of CPUs.
193 config ARCH_FOOTBRIDGE
197 Support for systems based on the DC21285 companion chip
198 ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
201 bool "Hilscher NetX based"
204 This enables support for systems based on the Hilscher NetX Soc
207 bool "Hynix HMS720x-based"
210 This enables support for systems based on the Hynix HMS720x
215 Support for Motorola's i.MX family of processors (MX1, MXL).
223 Support for Intel's 80219 and IOP32X (XScale) family of
232 Support for Intel's IOP33X (XScale) family of processors.
238 Support for Intel's IOP13XX (XScale) family of processors.
245 Support for Intel's IXP4XX (XScale) family of processors.
248 bool "IXP2400/2800-based"
252 Support for Intel's IXP2400/2800 (XScale) family of processors.
259 Support for Intel's IXP23xx (XScale) family of processors.
265 Say Y here if you intend to run this kernel on a LinkUp Systems
266 L7200 Software Development Board which uses an ARM720T processor.
267 Information on this board can be obtained at:
269 <http://www.linkupsys.com/>
271 If you have any questions or comments about the Linux kernel port
272 to this board, send e-mail to <sjhill@cotw.com>.
275 bool "Philips Nexperia PNX4008 Mobile"
277 This enables support for Philips PNX4008 mobile platform.
285 Support for Intel's PXA2XX processor line.
292 select ARCH_MAY_HAVE_PC_FDC
295 On the Acorn Risc-PC, Linux can support the internal IDE disk and
296 CD-ROM interface, serial and parallel port, and the floppy drive.
301 select ARCH_DISCONTIGMEM_ENABLE
304 Support for StrongARM 11x0 based boards.
307 bool "Samsung S3C2410, S3C2412, S3C2413, S3C2440, S3C2442, S3C2443"
309 Samsung S3C2410X CPU based systems, such as the Simtec Electronics
310 BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
311 the Samsung SMDK2410 development board (and derivatives).
319 Support for the StrongARM based Digital DNARD machine, also known
320 as "Shark" (<http://www.shark-linux.de/shark.html>).
325 Say Y here for systems based on one of the Sharp LH7A40X
326 System on a Chip processors. These CPUs include an ARM922T
327 core with a wide array of integrated devices for
328 hand-held and low-power applications.
333 Support for TI's OMAP platform (OMAP1 and OMAP2).
337 source "arch/arm/mach-clps711x/Kconfig"
339 source "arch/arm/mach-ep93xx/Kconfig"
341 source "arch/arm/mach-footbridge/Kconfig"
343 source "arch/arm/mach-integrator/Kconfig"
345 source "arch/arm/mach-iop32x/Kconfig"
347 source "arch/arm/mach-iop33x/Kconfig"
349 source "arch/arm/mach-iop13xx/Kconfig"
351 source "arch/arm/mach-ixp4xx/Kconfig"
353 source "arch/arm/mach-ixp2000/Kconfig"
355 source "arch/arm/mach-ixp23xx/Kconfig"
357 source "arch/arm/mach-pxa/Kconfig"
359 source "arch/arm/mach-sa1100/Kconfig"
361 source "arch/arm/plat-omap/Kconfig"
363 source "arch/arm/mach-omap1/Kconfig"
365 source "arch/arm/mach-omap2/Kconfig"
367 source "arch/arm/plat-s3c24xx/Kconfig"
370 source "arch/arm/mach-s3c2400/Kconfig"
371 source "arch/arm/mach-s3c2410/Kconfig"
372 source "arch/arm/mach-s3c2412/Kconfig"
373 source "arch/arm/mach-s3c2440/Kconfig"
374 source "arch/arm/mach-s3c2442/Kconfig"
375 source "arch/arm/mach-s3c2443/Kconfig"
378 source "arch/arm/mach-lh7a40x/Kconfig"
380 source "arch/arm/mach-imx/Kconfig"
382 source "arch/arm/mach-h720x/Kconfig"
384 source "arch/arm/mach-versatile/Kconfig"
386 source "arch/arm/mach-aaec2000/Kconfig"
388 source "arch/arm/mach-realview/Kconfig"
390 source "arch/arm/mach-at91/Kconfig"
392 source "arch/arm/mach-netx/Kconfig"
394 # Definitions to make life easier
401 source arch/arm/mm/Kconfig
404 bool "Enable iWMMXt support"
405 depends CPU_XSCALE || CPU_XSC3
408 Enable support for iWMMXt context switching at run time if
409 running on a CPU that supports it.
411 # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
414 depends on CPU_XSCALE && !XSCALE_PMU_TIMER
418 source "arch/arm/Kconfig-nommu"
423 source "arch/arm/common/Kconfig"
425 config FORCE_MAX_ZONEORDER
438 Find out whether you have ISA slots on your motherboard. ISA is the
439 name of a bus system, i.e. the way the CPU talks to the other stuff
440 inside your box. Other bus systems are PCI, EISA, MicroChannel
441 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
442 newer boards don't support it. If you have ISA, say Y, otherwise N.
444 # Select ISA DMA controller support
449 # Select ISA DMA interface
454 bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB || ARCH_IXP4XX
456 Find out whether you have a PCI motherboard. PCI is the name of a
457 bus system, i.e. the way the CPU talks to the other stuff inside
458 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
459 VESA. If you have PCI, say Y, otherwise N.
461 The PCI-HOWTO, available from
462 <http://www.tldp.org/docs.html#howto>, contains valuable
463 information about which PCI hardware does work under Linux and which
466 # Select the host bridge type
467 config PCI_HOST_VIA82C505
469 depends on PCI && ARCH_SHARK
472 source "drivers/pci/Kconfig"
474 source "drivers/pcmcia/Kconfig"
478 menu "Kernel Features"
481 bool "Symmetric Multi-Processing (EXPERIMENTAL)"
482 depends on EXPERIMENTAL && REALVIEW_MPCORE
484 This enables support for systems with more than one CPU. If you have
485 a system with only one CPU, like most personal computers, say N. If
486 you have a system with more than one CPU, say Y.
488 If you say N here, the kernel will run on single and multiprocessor
489 machines, but will use only one CPU of a multiprocessor machine. If
490 you say Y here, the kernel will run on many, but not all, single
491 processor machines. On a single processor machine, the kernel will
492 run faster if you say N here.
494 See also the <file:Documentation/smp.txt>,
495 <file:Documentation/i386/IO-APIC.txt>,
496 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
497 <http://www.linuxdoc.org/docs.html#howto>.
499 If you don't know what to do here, say N.
502 int "Maximum number of CPUs (2-32)"
508 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
509 depends on SMP && HOTPLUG && EXPERIMENTAL
511 Say Y here to experiment with turning CPUs off and on. CPUs
512 can be controlled through /sys/devices/system/cpu.
515 bool "Use local timer interrupts"
516 depends on SMP && REALVIEW_MPCORE
519 Enable support for local timers on SMP platforms, rather then the
520 legacy IPI broadcast method. Local timers allows the system
521 accounting to be spread across the timer interval, preventing a
522 "thundering herd" at every timer tick.
525 bool "Preemptible Kernel (EXPERIMENTAL)"
526 depends on EXPERIMENTAL
528 This option reduces the latency of the kernel when reacting to
529 real-time or interactive events by allowing a low priority process to
530 be preempted even if it is in kernel mode executing a system call.
531 This allows applications to run more reliably even when the system is
534 Say Y here if you are building a kernel for a desktop, embedded
535 or real-time system. Say N if you are unsure.
538 bool "Dynamic tick timer"
540 Select this option if you want to disable continuous timer ticks
541 and have them programmed to occur as required. This option saves
542 power as the system can remain in idle state for longer.
544 By default dynamic tick is disabled during the boot, and can be
545 manually enabled with:
547 echo 1 > /sys/devices/system/timer/timer0/dyn_tick
549 Alternatively, if you want dynamic tick automatically enabled
550 during boot, pass "dyntick=enable" via the kernel command string.
552 Please note that dynamic tick may affect the accuracy of
553 timekeeping on some platforms depending on the implementation.
554 Currently at least OMAP, PXA2xx and SA11x0 platforms are known
555 to have accurate timekeeping with dynamic tick.
559 default 128 if ARCH_L7200
560 default 200 if ARCH_EBSA110 || ARCH_S3C2410
561 default OMAP_32K_TIMER_HZ if ARCH_OMAP && OMAP_32K_TIMER
565 bool "Use the ARM EABI to compile the kernel"
567 This option allows for the kernel to be compiled using the latest
568 ARM ABI (aka EABI). This is only useful if you are using a user
569 space environment that is also compiled with EABI.
571 Since there are major incompatibilities between the legacy ABI and
572 EABI, especially with regard to structure member alignment, this
573 option also changes the kernel syscall calling convention to
574 disambiguate both ABIs and allow for backward compatibility support
575 (selected with CONFIG_OABI_COMPAT).
577 To use this you need GCC version 4.0.0 or later.
580 bool "Allow old ABI binaries to run with this kernel (EXPERIMENTAL)"
581 depends on AEABI && EXPERIMENTAL
584 This option preserves the old syscall interface along with the
585 new (ARM EABI) one. It also provides a compatibility layer to
586 intercept syscalls that have structure arguments which layout
587 in memory differs between the legacy ABI and the new ARM EABI
588 (only for non "thumb" binaries). This option adds a tiny
589 overhead to all syscalls and produces a slightly larger kernel.
590 If you know you'll be using only pure EABI user space then you
591 can say N here. If this option is not selected and you attempt
592 to execute a legacy ABI binary then the result will be
593 UNPREDICTABLE (in fact it can be predicted that it won't work
594 at all). If in doubt say Y.
596 config ARCH_DISCONTIGMEM_ENABLE
598 default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
600 Say Y to support efficient handling of discontiguous physical memory,
601 for architectures which are either NUMA (Non-Uniform Memory Access)
602 or have huge holes in the physical address space for other reasons.
603 See <file:Documentation/vm/numa> for more.
607 default "4" if ARCH_LH7A40X
609 depends on NEED_MULTIPLE_NODES
614 bool "Timer and CPU usage LEDs"
615 depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
616 ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
617 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
618 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
619 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
620 ARCH_AT91 || MACH_TRIZEPS4
622 If you say Y here, the LEDs on your machine will be used
623 to provide useful information about your current system status.
625 If you are compiling a kernel for a NetWinder or EBSA-285, you will
626 be able to select which LEDs are active using the options below. If
627 you are compiling a kernel for the EBSA-110 or the LART however, the
628 red LED will simply flash regularly to indicate that the system is
629 still functional. It is safe to say Y here if you have a CATS
630 system, but the driver will do nothing.
633 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
634 MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
636 default y if ARCH_EBSA110
638 If you say Y here, one of the system LEDs (the green one on the
639 NetWinder, the amber one on the EBSA285, or the red one on the LART)
640 will flash regularly to indicate that the system is still
641 operational. This is mainly useful to kernel hackers who are
642 debugging unstable kernels.
644 The LART uses the same LED for both Timer LED and CPU usage LED
645 functions. You may choose to use both, but the Timer LED function
646 will overrule the CPU usage LED.
649 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
650 !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
653 If you say Y here, the red LED will be used to give a good real
654 time indication of CPU usage, by lighting whenever the idle task
655 is not currently executing.
657 The LART uses the same LED for both Timer LED and CPU usage LED
658 functions. You may choose to use both, but the Timer LED function
659 will overrule the CPU usage LED.
661 config ALIGNMENT_TRAP
663 depends on CPU_CP15_MMU
664 default y if !ARCH_EBSA110
666 ARM processors cannot fetch/store information which is not
667 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
668 address divisible by 4. On 32-bit ARM processors, these non-aligned
669 fetch/store instructions will be emulated in software if you say
670 here, which has a severe performance impact. This is necessary for
671 correct operation of some network protocols. With an IP-only
672 configuration it is safe to say N, otherwise say Y.
678 # Compressed boot loader in ROM. Yes, we really want to ask about
679 # TEXT and BSS so we preserve their values in the config files.
680 config ZBOOT_ROM_TEXT
681 hex "Compressed ROM boot loader base address"
684 The physical address at which the ROM-able zImage is to be
685 placed in the target. Platforms which normally make use of
686 ROM-able zImage formats normally set this to a suitable
687 value in their defconfig file.
689 If ZBOOT_ROM is not enabled, this has no effect.
692 hex "Compressed ROM boot loader BSS address"
695 The base address of an area of read/write memory in the target
696 for the ROM-able zImage which must be available while the
697 decompressor is running. It must be large enough to hold the
698 entire decompressed kernel plus an additional 128 KiB.
699 Platforms which normally make use of ROM-able zImage formats
700 normally set this to a suitable value in their defconfig file.
702 If ZBOOT_ROM is not enabled, this has no effect.
705 bool "Compressed boot loader in ROM/flash"
706 depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
708 Say Y here if you intend to execute your compressed kernel image
709 (zImage) directly from ROM or flash. If unsure, say N.
712 string "Default kernel command string"
715 On some architectures (EBSA110 and CATS), there is currently no way
716 for the boot loader to pass arguments to the kernel. For these
717 architectures, you should supply some command-line options at build
718 time by entering them here. As a minimum, you should specify the
719 memory size and the root device (e.g., mem=64M root=/dev/nfs).
722 bool "Kernel Execute-In-Place from ROM"
723 depends on !ZBOOT_ROM
725 Execute-In-Place allows the kernel to run from non-volatile storage
726 directly addressable by the CPU, such as NOR flash. This saves RAM
727 space since the text section of the kernel is not loaded from flash
728 to RAM. Read-write sections, such as the data section and stack,
729 are still copied to RAM. The XIP kernel is not compressed since
730 it has to run directly from flash, so it will take more space to
731 store it. The flash address used to link the kernel object files,
732 and for storing it, is configuration dependent. Therefore, if you
733 say Y here, you must know the proper physical address where to
734 store the kernel image depending on your own flash memory usage.
736 Also note that the make target becomes "make xipImage" rather than
737 "make zImage" or "make Image". The final kernel binary to put in
738 ROM memory will be arch/arm/boot/xipImage.
743 hex "XIP Kernel Physical Location"
744 depends on XIP_KERNEL
747 This is the physical address in your flash memory the kernel will
748 be linked for and stored to. This address is dependent on your
752 bool "Kexec system call (EXPERIMENTAL)"
753 depends on EXPERIMENTAL
755 kexec is a system call that implements the ability to shutdown your
756 current kernel, and to start another kernel. It is like a reboot
757 but it is indepedent of the system firmware. And like a reboot
758 you can start any kernel with it, not just Linux.
760 It is an ongoing process to be certain the hardware in a machine
761 is properly shutdown, so do not be surprised if this code does not
762 initially work for you. It may help to enable device hotplugging
767 if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP || ARCH_IMX )
769 menu "CPU Frequency scaling"
771 source "drivers/cpufreq/Kconfig"
773 config CPU_FREQ_SA1100
775 depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
778 config CPU_FREQ_SA1110
780 depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
783 config CPU_FREQ_INTEGRATOR
784 tristate "CPUfreq driver for ARM Integrator CPUs"
785 depends on ARCH_INTEGRATOR && CPU_FREQ
788 This enables the CPUfreq driver for ARM Integrator CPUs.
790 For details, take a look at <file:Documentation/cpu-freq>.
795 tristate "CPUfreq driver for i.MX CPUs"
796 depends on ARCH_IMX && CPU_FREQ
799 This enables the CPUfreq driver for i.MX CPUs.
807 menu "Floating point emulation"
809 comment "At least one emulation must be selected"
812 bool "NWFPE math emulation"
813 depends on !AEABI || OABI_COMPAT
815 Say Y to include the NWFPE floating point emulator in the kernel.
816 This is necessary to run most binaries. Linux does not currently
817 support floating point hardware so you need to say Y here even if
818 your machine has an FPA or floating point co-processor podule.
820 You may say N here if you are going to load the Acorn FPEmulator
824 bool "Support extended precision"
827 Say Y to include 80-bit support in the kernel floating-point
828 emulator. Otherwise, only 32 and 64-bit support is compiled in.
829 Note that gcc does not generate 80-bit operations by default,
830 so in most cases this option only enlarges the size of the
831 floating point emulator without any good reason.
833 You almost surely want to say N here.
836 bool "FastFPE math emulation (EXPERIMENTAL)"
837 depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 && EXPERIMENTAL
839 Say Y here to include the FAST floating point emulator in the kernel.
840 This is an experimental much faster emulator which now also has full
841 precision for the mantissa. It does not support any exceptions.
842 It is very simple, and approximately 3-6 times faster than NWFPE.
844 It should be sufficient for most programs. It may be not suitable
845 for scientific calculations, but you have to check this for yourself.
846 If you do not feel you need a faster FP emulation you should better
850 bool "VFP-format floating point maths"
851 depends on CPU_V6 || CPU_ARM926T
853 Say Y to include VFP support code in the kernel. This is needed
854 if your hardware includes a VFP unit.
856 Please see <file:Documentation/arm/VFP/release-notes.txt> for
857 release notes and additional status information.
859 Say N if your target does not have VFP hardware.
863 menu "Userspace binary formats"
865 source "fs/Kconfig.binfmt"
868 tristate "RISC OS personality"
871 Say Y here to include the kernel code necessary if you want to run
872 Acorn RISC OS/Arthur binaries under Linux. This code is still very
873 experimental; if this sounds frightening, say N and sleep in peace.
874 You can also say M here to compile this support as a module (which
875 will be called arthur).
879 menu "Power management options"
881 source "kernel/power/Kconfig"
884 tristate "Advanced Power Management Emulation"
886 APM is a BIOS specification for saving power using several different
887 techniques. This is mostly useful for battery powered laptops with
888 APM compliant BIOSes. If you say Y here, the system time will be
889 reset after a RESUME operation, the /proc/apm device will provide
890 battery status information, and user-space programs will receive
891 notification of APM "events" (e.g. battery status change).
893 In order to use APM, you will need supporting software. For location
894 and more information, read <file:Documentation/pm.txt> and the
895 Battery Powered Linux mini-HOWTO, available from
896 <http://www.tldp.org/docs.html#howto>.
898 This driver does not spin down disk drives (see the hdparm(8)
899 manpage ("man 8 hdparm") for that), and it doesn't turn off
900 VESA-compliant "green" monitors.
902 Generally, if you don't have a battery in your machine, there isn't
903 much point in using this driver and you should say N. If you get
904 random kernel OOPSes or reboots that don't seem to be related to
905 anything, try disabling/enabling this option (or disabling/enabling
912 menu "Device Drivers"
914 source "drivers/base/Kconfig"
916 source "drivers/connector/Kconfig"
918 if ALIGNMENT_TRAP || !CPU_CP15_MMU
919 source "drivers/mtd/Kconfig"
922 source "drivers/parport/Kconfig"
924 source "drivers/pnp/Kconfig"
926 source "drivers/block/Kconfig"
928 source "drivers/acorn/block/Kconfig"
930 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
931 || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
932 || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
934 source "drivers/ide/Kconfig"
937 source "drivers/scsi/Kconfig"
939 source "drivers/ata/Kconfig"
941 source "drivers/md/Kconfig"
943 source "drivers/message/fusion/Kconfig"
945 source "drivers/ieee1394/Kconfig"
947 source "drivers/message/i2o/Kconfig"
949 source "drivers/net/Kconfig"
951 source "drivers/isdn/Kconfig"
953 # input before char - char/joystick depends on it. As does USB.
955 source "drivers/input/Kconfig"
957 source "drivers/char/Kconfig"
959 source "drivers/i2c/Kconfig"
961 source "drivers/spi/Kconfig"
963 source "drivers/w1/Kconfig"
965 source "drivers/hwmon/Kconfig"
967 #source "drivers/l3/Kconfig"
969 source "drivers/misc/Kconfig"
971 source "drivers/mfd/Kconfig"
973 source "drivers/leds/Kconfig"
975 source "drivers/media/Kconfig"
977 source "drivers/video/Kconfig"
979 source "sound/Kconfig"
981 source "drivers/hid/Kconfig"
983 source "drivers/usb/Kconfig"
985 source "drivers/mmc/Kconfig"
987 source "drivers/rtc/Kconfig"
993 source "arch/arm/oprofile/Kconfig"
995 source "arch/arm/Kconfig.debug"
997 source "security/Kconfig"
999 source "crypto/Kconfig"
1001 source "lib/Kconfig"