xref: /openbmc/linux/arch/arm/Kconfig (revision d5cb9783536a41df9f9cba5b0a1d78047ed787f7)
1#
2# For a description of the syntax of this configuration file,
3# see Documentation/kbuild/kconfig-language.txt.
4#
5
6mainmenu "Linux Kernel Configuration"
7
8config ARM
9	bool
10	default y
11	help
12	  The ARM series is a line of low-power-consumption RISC chip designs
13	  licensed by ARM ltd and targeted at embedded applications and
14	  handhelds such as the Compaq IPAQ.  ARM-based PCs are no longer
15	  manufactured, but  legacy ARM-based PC hardware remains popular in
16	  Europe.  There is an ARM Linux project with a web page at
17	  <http://www.arm.linux.org.uk/>.
18
19config MMU
20	bool
21	default y
22
23config EISA
24	bool
25	---help---
26	  The Extended Industry Standard Architecture (EISA) bus was
27	  developed as an open alternative to the IBM MicroChannel bus.
28
29	  The EISA bus provided some of the features of the IBM MicroChannel
30	  bus while maintaining backward compatibility with cards made for
31	  the older ISA bus.  The EISA bus saw limited use between 1988 and
32	  1995 when it was made obsolete by the PCI bus.
33
34	  Say Y here if you are building a kernel for an EISA-based machine.
35
36	  Otherwise, say N.
37
38config SBUS
39	bool
40
41config MCA
42	bool
43	help
44	  MicroChannel Architecture is found in some IBM PS/2 machines and
45	  laptops.  It is a bus system similar to PCI or ISA. See
46	  <file:Documentation/mca.txt> (and especially the web page given
47	  there) before attempting to build an MCA bus kernel.
48
49config UID16
50	bool
51	default y
52
53config RWSEM_GENERIC_SPINLOCK
54	bool
55	default y
56
57config RWSEM_XCHGADD_ALGORITHM
58	bool
59
60config GENERIC_CALIBRATE_DELAY
61	bool
62	default y
63
64config GENERIC_BUST_SPINLOCK
65	bool
66
67config ARCH_MAY_HAVE_PC_FDC
68	bool
69
70config GENERIC_ISA_DMA
71	bool
72
73config FIQ
74	bool
75
76source "init/Kconfig"
77
78menu "System Type"
79
80choice
81	prompt "ARM system type"
82	default ARCH_RPC
83
84config ARCH_CLPS7500
85	bool "Cirrus-CL-PS7500FE"
86	select TIMER_ACORN
87	select ISA
88
89config ARCH_CLPS711X
90	bool "CLPS711x/EP721x-based"
91
92config ARCH_CO285
93	bool "Co-EBSA285"
94	select FOOTBRIDGE
95	select FOOTBRIDGE_ADDIN
96
97config ARCH_EBSA110
98	bool "EBSA-110"
99	select ISA
100	help
101	  This is an evaluation board for the StrongARM processor available
102	  from Digital. It has limited hardware on-board, including an onboard
103	  Ethernet interface, two PCMCIA sockets, two serial ports and a
104	  parallel port.
105
106config ARCH_CAMELOT
107	bool "Epxa10db"
108	help
109	  This enables support for Altera's Excalibur XA10 development board.
110	  If you would like to build your kernel to run on one of these boards
111	  then you must say 'Y' here. Otherwise say 'N'
112
113config ARCH_FOOTBRIDGE
114	bool "FootBridge"
115	select FOOTBRIDGE
116
117config ARCH_INTEGRATOR
118	bool "Integrator"
119	select ARM_AMBA
120	select ICST525
121
122config ARCH_IOP3XX
123	bool "IOP3xx-based"
124	select PCI
125
126config ARCH_IXP4XX
127	bool "IXP4xx-based"
128	select DMABOUNCE
129	select PCI
130
131config ARCH_IXP2000
132	bool "IXP2400/2800-based"
133	select PCI
134
135config ARCH_L7200
136	bool "LinkUp-L7200"
137	select FIQ
138	help
139	  Say Y here if you intend to run this kernel on a LinkUp Systems
140	  L7200 Software Development Board which uses an ARM720T processor.
141	  Information on this board can be obtained at:
142
143	  <http://www.linkupsys.com/>
144
145	  If you have any questions or comments about the Linux kernel port
146	  to this board, send e-mail to <sjhill@cotw.com>.
147
148config ARCH_PXA
149	bool "PXA2xx-based"
150
151config ARCH_RPC
152	bool "RiscPC"
153	select ARCH_ACORN
154	select FIQ
155	select TIMER_ACORN
156	select ARCH_MAY_HAVE_PC_FDC
157	help
158	  On the Acorn Risc-PC, Linux can support the internal IDE disk and
159	  CD-ROM interface, serial and parallel port, and the floppy drive.
160
161config ARCH_SA1100
162	bool "SA1100-based"
163	select ISA
164	select ARCH_DISCONTIGMEM_ENABLE
165
166config ARCH_S3C2410
167	bool "Samsung S3C2410"
168	help
169	  Samsung S3C2410X CPU based systems, such as the Simtec Electronics
170	  BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
171	  the Samsung SMDK2410 development board (and derviatives).
172
173config ARCH_SHARK
174	bool "Shark"
175	select ISA
176	select ISA_DMA
177	select PCI
178
179config ARCH_LH7A40X
180	bool "Sharp LH7A40X"
181	help
182	  Say Y here for systems based on one of the Sharp LH7A40X
183	  System on a Chip processors.  These CPUs include an ARM922T
184	  core with a wide array of integrated devices for
185	  hand-held and low-power applications.
186
187config ARCH_OMAP
188	bool "TI OMAP"
189
190config ARCH_VERSATILE
191	bool "Versatile"
192	select ARM_AMBA
193	select ICST307
194	help
195	  This enables support for ARM Ltd Versatile board.
196
197config ARCH_REALVIEW
198	bool "RealView"
199	select ARM_AMBA
200	select ICST307
201	help
202	  This enables support for ARM Ltd RealView boards.
203
204config ARCH_IMX
205	bool "IMX"
206
207config ARCH_H720X
208	bool "Hynix-HMS720x-based"
209	help
210	  This enables support for systems based on the Hynix HMS720x
211
212config ARCH_AAEC2000
213	bool "Agilent AAEC-2000 based"
214	select ARM_AMBA
215	help
216	  This enables support for systems based on the Agilent AAEC-2000
217
218endchoice
219
220source "arch/arm/mach-clps711x/Kconfig"
221
222source "arch/arm/mach-epxa10db/Kconfig"
223
224source "arch/arm/mach-footbridge/Kconfig"
225
226source "arch/arm/mach-integrator/Kconfig"
227
228source "arch/arm/mach-iop3xx/Kconfig"
229
230source "arch/arm/mach-ixp4xx/Kconfig"
231
232source "arch/arm/mach-ixp2000/Kconfig"
233
234source "arch/arm/mach-pxa/Kconfig"
235
236source "arch/arm/mach-sa1100/Kconfig"
237
238source "arch/arm/plat-omap/Kconfig"
239
240source "arch/arm/mach-omap1/Kconfig"
241
242source "arch/arm/mach-s3c2410/Kconfig"
243
244source "arch/arm/mach-lh7a40x/Kconfig"
245
246source "arch/arm/mach-imx/Kconfig"
247
248source "arch/arm/mach-h720x/Kconfig"
249
250source "arch/arm/mach-versatile/Kconfig"
251
252source "arch/arm/mach-aaec2000/Kconfig"
253
254source "arch/arm/mach-realview/Kconfig"
255
256# Definitions to make life easier
257config ARCH_ACORN
258	bool
259
260source arch/arm/mm/Kconfig
261
262#  bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
263config XSCALE_PMU
264	bool
265	depends on CPU_XSCALE && !XSCALE_PMU_TIMER
266	default y
267
268endmenu
269
270source "arch/arm/common/Kconfig"
271
272config FORCE_MAX_ZONEORDER
273	int
274	depends on SA1111
275	default "9"
276
277menu "Bus support"
278
279config ARM_AMBA
280	bool
281
282config ISA
283	bool
284	help
285	  Find out whether you have ISA slots on your motherboard.  ISA is the
286	  name of a bus system, i.e. the way the CPU talks to the other stuff
287	  inside your box.  Other bus systems are PCI, EISA, MicroChannel
288	  (MCA) or VESA.  ISA is an older system, now being displaced by PCI;
289	  newer boards don't support it.  If you have ISA, say Y, otherwise N.
290
291config ISA_DMA
292	bool
293
294config ISA_DMA_API
295	bool
296	default y
297
298config PCI
299	bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
300	help
301	  Find out whether you have a PCI motherboard. PCI is the name of a
302	  bus system, i.e. the way the CPU talks to the other stuff inside
303	  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
304	  VESA. If you have PCI, say Y, otherwise N.
305
306	  The PCI-HOWTO, available from
307	  <http://www.tldp.org/docs.html#howto>, contains valuable
308	  information about which PCI hardware does work under Linux and which
309	  doesn't.
310
311# Select the host bridge type
312config PCI_HOST_VIA82C505
313	bool
314	depends on PCI && ARCH_SHARK
315	default y
316
317source "drivers/pci/Kconfig"
318
319source "drivers/pcmcia/Kconfig"
320
321endmenu
322
323menu "Kernel Features"
324
325config SMP
326	bool "Symmetric Multi-Processing (EXPERIMENTAL)"
327	depends on EXPERIMENTAL && BROKEN #&& n
328	help
329	  This enables support for systems with more than one CPU. If you have
330	  a system with only one CPU, like most personal computers, say N. If
331	  you have a system with more than one CPU, say Y.
332
333	  If you say N here, the kernel will run on single and multiprocessor
334	  machines, but will use only one CPU of a multiprocessor machine. If
335	  you say Y here, the kernel will run on many, but not all, single
336	  processor machines. On a single processor machine, the kernel will
337	  run faster if you say N here.
338
339	  See also the <file:Documentation/smp.txt>,
340	  <file:Documentation/i386/IO-APIC.txt>,
341	  <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
342	  <http://www.linuxdoc.org/docs.html#howto>.
343
344	  If you don't know what to do here, say N.
345
346config NR_CPUS
347	int "Maximum number of CPUs (2-32)"
348	range 2 32
349	depends on SMP
350	default "4"
351
352config HOTPLUG_CPU
353	bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
354	depends on SMP && HOTPLUG && EXPERIMENTAL
355	help
356	  Say Y here to experiment with turning CPUs off and on.  CPUs
357	  can be controlled through /sys/devices/system/cpu.
358
359config PREEMPT
360	bool "Preemptible Kernel (EXPERIMENTAL)"
361	depends on EXPERIMENTAL
362	help
363	  This option reduces the latency of the kernel when reacting to
364	  real-time or interactive events by allowing a low priority process to
365	  be preempted even if it is in kernel mode executing a system call.
366	  This allows applications to run more reliably even when the system is
367	  under load.
368
369	  Say Y here if you are building a kernel for a desktop, embedded
370	  or real-time system.  Say N if you are unsure.
371
372config NO_IDLE_HZ
373	bool "Dynamic tick timer"
374	help
375	  Select this option if you want to disable continuous timer ticks
376	  and have them programmed to occur as required. This option saves
377	  power as the system can remain in idle state for longer.
378
379	  By default dynamic tick is disabled during the boot, and can be
380	  manually enabled with:
381
382	    echo 1 > /sys/devices/system/timer/timer0/dyn_tick
383
384	  Alternatively, if you want dynamic tick automatically enabled
385	  during boot, pass "dyntick=enable" via the kernel command string.
386
387	  Please note that dynamic tick may affect the accuracy of
388	  timekeeping on some platforms depending on the implementation.
389	  Currently at least OMAP, PXA2xx and SA11x0 platforms are known
390	  to have accurate timekeeping with dynamic tick.
391
392config ARCH_DISCONTIGMEM_ENABLE
393	bool
394	default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
395	help
396	  Say Y to support efficient handling of discontiguous physical memory,
397	  for architectures which are either NUMA (Non-Uniform Memory Access)
398	  or have huge holes in the physical address space for other reasons.
399	  See <file:Documentation/vm/numa> for more.
400
401source "mm/Kconfig"
402
403config LEDS
404	bool "Timer and CPU usage LEDs"
405	depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
406		   ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
407		   ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
408		   ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
409		   ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE
410	help
411	  If you say Y here, the LEDs on your machine will be used
412	  to provide useful information about your current system status.
413
414	  If you are compiling a kernel for a NetWinder or EBSA-285, you will
415	  be able to select which LEDs are active using the options below. If
416	  you are compiling a kernel for the EBSA-110 or the LART however, the
417	  red LED will simply flash regularly to indicate that the system is
418	  still functional. It is safe to say Y here if you have a CATS
419	  system, but the driver will do nothing.
420
421config LEDS_TIMER
422	bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
423			    MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
424	depends on LEDS
425	default y if ARCH_EBSA110
426	help
427	  If you say Y here, one of the system LEDs (the green one on the
428	  NetWinder, the amber one on the EBSA285, or the red one on the LART)
429	  will flash regularly to indicate that the system is still
430	  operational. This is mainly useful to kernel hackers who are
431	  debugging unstable kernels.
432
433	  The LART uses the same LED for both Timer LED and CPU usage LED
434	  functions. You may choose to use both, but the Timer LED function
435	  will overrule the CPU usage LED.
436
437config LEDS_CPU
438	bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
439			!ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
440	depends on LEDS
441	help
442	  If you say Y here, the red LED will be used to give a good real
443	  time indication of CPU usage, by lighting whenever the idle task
444	  is not currently executing.
445
446	  The LART uses the same LED for both Timer LED and CPU usage LED
447	  functions. You may choose to use both, but the Timer LED function
448	  will overrule the CPU usage LED.
449
450config ALIGNMENT_TRAP
451	bool
452	default y if !ARCH_EBSA110
453	help
454	  ARM processors can not fetch/store information which is not
455	  naturally aligned on the bus, i.e., a 4 byte fetch must start at an
456	  address divisible by 4. On 32-bit ARM processors, these non-aligned
457	  fetch/store instructions will be emulated in software if you say
458	  here, which has a severe performance impact. This is necessary for
459	  correct operation of some network protocols. With an IP-only
460	  configuration it is safe to say N, otherwise say Y.
461
462endmenu
463
464menu "Boot options"
465
466# Compressed boot loader in ROM.  Yes, we really want to ask about
467# TEXT and BSS so we preserve their values in the config files.
468config ZBOOT_ROM_TEXT
469	hex "Compressed ROM boot loader base address"
470	default "0"
471	help
472	  The physical address at which the ROM-able zImage is to be
473	  placed in the target.  Platforms which normally make use of
474	  ROM-able zImage formats normally set this to a suitable
475	  value in their defconfig file.
476
477	  If ZBOOT_ROM is not enabled, this has no effect.
478
479config ZBOOT_ROM_BSS
480	hex "Compressed ROM boot loader BSS address"
481	default "0"
482	help
483	  The base address of 64KiB of read/write memory in the target
484	  for the ROM-able zImage, which must be available while the
485	  decompressor is running.  Platforms which normally make use of
486	  ROM-able zImage formats normally set this to a suitable
487	  value in their defconfig file.
488
489	  If ZBOOT_ROM is not enabled, this has no effect.
490
491config ZBOOT_ROM
492	bool "Compressed boot loader in ROM/flash"
493	depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
494	help
495	  Say Y here if you intend to execute your compressed kernel image
496	  (zImage) directly from ROM or flash.  If unsure, say N.
497
498config CMDLINE
499	string "Default kernel command string"
500	default ""
501	help
502	  On some architectures (EBSA110 and CATS), there is currently no way
503	  for the boot loader to pass arguments to the kernel. For these
504	  architectures, you should supply some command-line options at build
505	  time by entering them here. As a minimum, you should specify the
506	  memory size and the root device (e.g., mem=64M root=/dev/nfs).
507
508config XIP_KERNEL
509	bool "Kernel Execute-In-Place from ROM"
510	depends on !ZBOOT_ROM
511	help
512	  Execute-In-Place allows the kernel to run from non-volatile storage
513	  directly addressable by the CPU, such as NOR flash. This saves RAM
514	  space since the text section of the kernel is not loaded from flash
515	  to RAM.  Read-write sections, such as the data section and stack,
516	  are still copied to RAM.  The XIP kernel is not compressed since
517	  it has to run directly from flash, so it will take more space to
518	  store it.  The flash address used to link the kernel object files,
519	  and for storing it, is configuration dependent. Therefore, if you
520	  say Y here, you must know the proper physical address where to
521	  store the kernel image depending on your own flash memory usage.
522
523	  Also note that the make target becomes "make xipImage" rather than
524	  "make zImage" or "make Image".  The final kernel binary to put in
525	  ROM memory will be arch/arm/boot/xipImage.
526
527	  If unsure, say N.
528
529config XIP_PHYS_ADDR
530	hex "XIP Kernel Physical Location"
531	depends on XIP_KERNEL
532	default "0x00080000"
533	help
534	  This is the physical address in your flash memory the kernel will
535	  be linked for and stored to.  This address is dependent on your
536	  own flash usage.
537
538endmenu
539
540if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
541
542menu "CPU Frequency scaling"
543
544source "drivers/cpufreq/Kconfig"
545
546config CPU_FREQ_SA1100
547	bool
548	depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
549	default y
550
551config CPU_FREQ_SA1110
552	bool
553	depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
554	default y
555
556config CPU_FREQ_INTEGRATOR
557	tristate "CPUfreq driver for ARM Integrator CPUs"
558	depends on ARCH_INTEGRATOR && CPU_FREQ
559	default y
560	help
561	  This enables the CPUfreq driver for ARM Integrator CPUs.
562
563	  For details, take a look at <file:Documentation/cpu-freq>.
564
565	  If in doubt, say Y.
566
567endmenu
568
569endif
570
571menu "Floating point emulation"
572
573comment "At least one emulation must be selected"
574
575config FPE_NWFPE
576	bool "NWFPE math emulation"
577	---help---
578	  Say Y to include the NWFPE floating point emulator in the kernel.
579	  This is necessary to run most binaries. Linux does not currently
580	  support floating point hardware so you need to say Y here even if
581	  your machine has an FPA or floating point co-processor podule.
582
583	  You may say N here if you are going to load the Acorn FPEmulator
584	  early in the bootup.
585
586config FPE_NWFPE_XP
587	bool "Support extended precision"
588	depends on FPE_NWFPE && !CPU_BIG_ENDIAN
589	help
590	  Say Y to include 80-bit support in the kernel floating-point
591	  emulator.  Otherwise, only 32 and 64-bit support is compiled in.
592	  Note that gcc does not generate 80-bit operations by default,
593	  so in most cases this option only enlarges the size of the
594	  floating point emulator without any good reason.
595
596	  You almost surely want to say N here.
597
598config FPE_FASTFPE
599	bool "FastFPE math emulation (EXPERIMENTAL)"
600	depends on !CPU_32v3 && EXPERIMENTAL
601	---help---
602	  Say Y here to include the FAST floating point emulator in the kernel.
603	  This is an experimental much faster emulator which now also has full
604	  precision for the mantissa.  It does not support any exceptions.
605	  It is very simple, and approximately 3-6 times faster than NWFPE.
606
607	  It should be sufficient for most programs.  It may be not suitable
608	  for scientific calculations, but you have to check this for yourself.
609	  If you do not feel you need a faster FP emulation you should better
610	  choose NWFPE.
611
612config VFP
613	bool "VFP-format floating point maths"
614	depends on CPU_V6 || CPU_ARM926T
615	help
616	  Say Y to include VFP support code in the kernel. This is needed
617	  if your hardware includes a VFP unit.
618
619	  Please see <file:Documentation/arm/VFP/release-notes.txt> for
620	  release notes and additional status information.
621
622	  Say N if your target does not have VFP hardware.
623
624endmenu
625
626menu "Userspace binary formats"
627
628source "fs/Kconfig.binfmt"
629
630config ARTHUR
631	tristate "RISC OS personality"
632	help
633	  Say Y here to include the kernel code necessary if you want to run
634	  Acorn RISC OS/Arthur binaries under Linux. This code is still very
635	  experimental; if this sounds frightening, say N and sleep in peace.
636	  You can also say M here to compile this support as a module (which
637	  will be called arthur).
638
639endmenu
640
641menu "Power management options"
642
643config PM
644	bool "Power Management support"
645	---help---
646	  "Power Management" means that parts of your computer are shut
647	  off or put into a power conserving "sleep" mode if they are not
648	  being used.  There are two competing standards for doing this: APM
649	  and ACPI.  If you want to use either one, say Y here and then also
650	  to the requisite support below.
651
652	  Power Management is most important for battery powered laptop
653	  computers; if you have a laptop, check out the Linux Laptop home
654	  page on the WWW at <http://www.linux-on-laptops.com/> or
655	  Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>
656	  and the Battery Powered Linux mini-HOWTO, available from
657	  <http://www.tldp.org/docs.html#howto>.
658
659config APM
660	tristate "Advanced Power Management Emulation"
661	depends on PM
662	---help---
663	  APM is a BIOS specification for saving power using several different
664	  techniques. This is mostly useful for battery powered laptops with
665	  APM compliant BIOSes. If you say Y here, the system time will be
666	  reset after a RESUME operation, the /proc/apm device will provide
667	  battery status information, and user-space programs will receive
668	  notification of APM "events" (e.g. battery status change).
669
670	  In order to use APM, you will need supporting software. For location
671	  and more information, read <file:Documentation/pm.txt> and the
672	  Battery Powered Linux mini-HOWTO, available from
673	  <http://www.tldp.org/docs.html#howto>.
674
675	  This driver does not spin down disk drives (see the hdparm(8)
676	  manpage ("man 8 hdparm") for that), and it doesn't turn off
677	  VESA-compliant "green" monitors.
678
679	  Generally, if you don't have a battery in your machine, there isn't
680	  much point in using this driver and you should say N. If you get
681	  random kernel OOPSes or reboots that don't seem to be related to
682	  anything, try disabling/enabling this option (or disabling/enabling
683	  APM in your BIOS).
684
685endmenu
686
687source "net/Kconfig"
688
689menu "Device Drivers"
690
691source "drivers/base/Kconfig"
692
693if ALIGNMENT_TRAP
694source "drivers/mtd/Kconfig"
695endif
696
697source "drivers/parport/Kconfig"
698
699source "drivers/pnp/Kconfig"
700
701source "drivers/block/Kconfig"
702
703source "drivers/acorn/block/Kconfig"
704
705if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
706	|| ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
707	|| ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
708source "drivers/ide/Kconfig"
709endif
710
711source "drivers/scsi/Kconfig"
712
713source "drivers/md/Kconfig"
714
715source "drivers/message/fusion/Kconfig"
716
717source "drivers/ieee1394/Kconfig"
718
719source "drivers/message/i2o/Kconfig"
720
721source "drivers/net/Kconfig"
722
723source "drivers/isdn/Kconfig"
724
725# input before char - char/joystick depends on it. As does USB.
726
727source "drivers/input/Kconfig"
728
729source "drivers/char/Kconfig"
730
731source "drivers/i2c/Kconfig"
732
733source "drivers/hwmon/Kconfig"
734
735#source "drivers/l3/Kconfig"
736
737source "drivers/misc/Kconfig"
738
739source "drivers/mfd/Kconfig"
740
741source "drivers/media/Kconfig"
742
743source "drivers/video/Kconfig"
744
745source "sound/Kconfig"
746
747source "drivers/usb/Kconfig"
748
749source "drivers/mmc/Kconfig"
750
751endmenu
752
753source "fs/Kconfig"
754
755source "arch/arm/oprofile/Kconfig"
756
757source "arch/arm/Kconfig.debug"
758
759source "security/Kconfig"
760
761source "crypto/Kconfig"
762
763source "lib/Kconfig"
764