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