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