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