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