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