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