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