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