Kconfig 21 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746
  1. #
  2. # For a description of the syntax of this configuration file,
  3. # see Documentation/kbuild/kconfig-language.txt.
  4. #
  5. mainmenu "Linux Kernel Configuration"
  6. config ARM
  7. bool
  8. default y
  9. help
  10. The ARM series is a line of low-power-consumption RISC chip designs
  11. licensed by ARM ltd and targeted at embedded applications and
  12. handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
  13. manufactured, but legacy ARM-based PC hardware remains popular in
  14. Europe. There is an ARM Linux project with a web page at
  15. <http://www.arm.linux.org.uk/>.
  16. config MMU
  17. bool
  18. default y
  19. config EISA
  20. bool
  21. ---help---
  22. The Extended Industry Standard Architecture (EISA) bus was
  23. developed as an open alternative to the IBM MicroChannel bus.
  24. The EISA bus provided some of the features of the IBM MicroChannel
  25. bus while maintaining backward compatibility with cards made for
  26. the older ISA bus. The EISA bus saw limited use between 1988 and
  27. 1995 when it was made obsolete by the PCI bus.
  28. Say Y here if you are building a kernel for an EISA-based machine.
  29. Otherwise, say N.
  30. config SBUS
  31. bool
  32. config MCA
  33. bool
  34. help
  35. MicroChannel Architecture is found in some IBM PS/2 machines and
  36. laptops. It is a bus system similar to PCI or ISA. See
  37. <file:Documentation/mca.txt> (and especially the web page given
  38. there) before attempting to build an MCA bus kernel.
  39. config UID16
  40. bool
  41. default y
  42. config RWSEM_GENERIC_SPINLOCK
  43. bool
  44. default y
  45. config RWSEM_XCHGADD_ALGORITHM
  46. bool
  47. config GENERIC_CALIBRATE_DELAY
  48. bool
  49. default y
  50. config GENERIC_BUST_SPINLOCK
  51. bool
  52. config ARCH_MAY_HAVE_PC_FDC
  53. bool
  54. config GENERIC_ISA_DMA
  55. bool
  56. config FIQ
  57. bool
  58. source "init/Kconfig"
  59. menu "System Type"
  60. choice
  61. prompt "ARM system type"
  62. default ARCH_RPC
  63. config ARCH_CLPS7500
  64. bool "Cirrus-CL-PS7500FE"
  65. select TIMER_ACORN
  66. select ISA
  67. config ARCH_CLPS711X
  68. bool "CLPS711x/EP721x-based"
  69. config ARCH_CO285
  70. bool "Co-EBSA285"
  71. select FOOTBRIDGE
  72. select FOOTBRIDGE_ADDIN
  73. config ARCH_EBSA110
  74. bool "EBSA-110"
  75. select ISA
  76. help
  77. This is an evaluation board for the StrongARM processor available
  78. from Digital. It has limited hardware on-board, including an onboard
  79. Ethernet interface, two PCMCIA sockets, two serial ports and a
  80. parallel port.
  81. config ARCH_CAMELOT
  82. bool "Epxa10db"
  83. help
  84. This enables support for Altera's Excalibur XA10 development board.
  85. If you would like to build your kernel to run on one of these boards
  86. then you must say 'Y' here. Otherwise say 'N'
  87. config ARCH_FOOTBRIDGE
  88. bool "FootBridge"
  89. select FOOTBRIDGE
  90. config ARCH_INTEGRATOR
  91. bool "Integrator"
  92. select ARM_AMBA
  93. select ICST525
  94. config ARCH_IOP3XX
  95. bool "IOP3xx-based"
  96. select PCI
  97. config ARCH_IXP4XX
  98. bool "IXP4xx-based"
  99. select DMABOUNCE
  100. select PCI
  101. config ARCH_IXP2000
  102. bool "IXP2400/2800-based"
  103. select PCI
  104. config ARCH_L7200
  105. bool "LinkUp-L7200"
  106. select FIQ
  107. help
  108. Say Y here if you intend to run this kernel on a LinkUp Systems
  109. L7200 Software Development Board which uses an ARM720T processor.
  110. Information on this board can be obtained at:
  111. <http://www.linkupsys.com/>
  112. If you have any questions or comments about the Linux kernel port
  113. to this board, send e-mail to <sjhill@cotw.com>.
  114. config ARCH_PXA
  115. bool "PXA2xx-based"
  116. config ARCH_RPC
  117. bool "RiscPC"
  118. select ARCH_ACORN
  119. select FIQ
  120. select TIMER_ACORN
  121. select ARCH_MAY_HAVE_PC_FDC
  122. help
  123. On the Acorn Risc-PC, Linux can support the internal IDE disk and
  124. CD-ROM interface, serial and parallel port, and the floppy drive.
  125. config ARCH_SA1100
  126. bool "SA1100-based"
  127. select ISA
  128. select ARCH_DISCONTIGMEM_ENABLE
  129. config ARCH_S3C2410
  130. bool "Samsung S3C2410"
  131. help
  132. Samsung S3C2410X CPU based systems, such as the Simtec Electronics
  133. BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
  134. the Samsung SMDK2410 development board (and derviatives).
  135. config ARCH_SHARK
  136. bool "Shark"
  137. select ISA
  138. select ISA_DMA
  139. select PCI
  140. config ARCH_LH7A40X
  141. bool "Sharp LH7A40X"
  142. help
  143. Say Y here for systems based on one of the Sharp LH7A40X
  144. System on a Chip processors. These CPUs include an ARM922T
  145. core with a wide array of integrated devices for
  146. hand-held and low-power applications.
  147. config ARCH_OMAP
  148. bool "TI OMAP"
  149. config ARCH_VERSATILE
  150. bool "Versatile"
  151. select ARM_AMBA
  152. select ICST307
  153. help
  154. This enables support for ARM Ltd Versatile board.
  155. config ARCH_IMX
  156. bool "IMX"
  157. config ARCH_H720X
  158. bool "Hynix-HMS720x-based"
  159. help
  160. This enables support for systems based on the Hynix HMS720x
  161. config ARCH_AAEC2000
  162. bool "Agilent AAEC-2000 based"
  163. help
  164. This enables support for systems based on the Agilent AAEC-2000
  165. endchoice
  166. source "arch/arm/mach-clps711x/Kconfig"
  167. source "arch/arm/mach-epxa10db/Kconfig"
  168. source "arch/arm/mach-footbridge/Kconfig"
  169. source "arch/arm/mach-integrator/Kconfig"
  170. source "arch/arm/mach-iop3xx/Kconfig"
  171. source "arch/arm/mach-ixp4xx/Kconfig"
  172. source "arch/arm/mach-ixp2000/Kconfig"
  173. source "arch/arm/mach-pxa/Kconfig"
  174. source "arch/arm/mach-sa1100/Kconfig"
  175. source "arch/arm/plat-omap/Kconfig"
  176. source "arch/arm/mach-omap1/Kconfig"
  177. source "arch/arm/mach-s3c2410/Kconfig"
  178. source "arch/arm/mach-lh7a40x/Kconfig"
  179. source "arch/arm/mach-imx/Kconfig"
  180. source "arch/arm/mach-h720x/Kconfig"
  181. source "arch/arm/mach-versatile/Kconfig"
  182. source "arch/arm/mach-aaec2000/Kconfig"
  183. # Definitions to make life easier
  184. config ARCH_ACORN
  185. bool
  186. source arch/arm/mm/Kconfig
  187. # bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
  188. config XSCALE_PMU
  189. bool
  190. depends on CPU_XSCALE && !XSCALE_PMU_TIMER
  191. default y
  192. endmenu
  193. source "arch/arm/common/Kconfig"
  194. config FORCE_MAX_ZONEORDER
  195. int
  196. depends on SA1111
  197. default "9"
  198. menu "Bus support"
  199. config ARM_AMBA
  200. bool
  201. config ISA
  202. bool
  203. help
  204. Find out whether you have ISA slots on your motherboard. ISA is the
  205. name of a bus system, i.e. the way the CPU talks to the other stuff
  206. inside your box. Other bus systems are PCI, EISA, MicroChannel
  207. (MCA) or VESA. ISA is an older system, now being displaced by PCI;
  208. newer boards don't support it. If you have ISA, say Y, otherwise N.
  209. config ISA_DMA
  210. bool
  211. config ISA_DMA_API
  212. bool
  213. default y
  214. config PCI
  215. bool "PCI support" if ARCH_INTEGRATOR_AP || ARCH_VERSATILE_PB
  216. help
  217. Find out whether you have a PCI motherboard. PCI is the name of a
  218. bus system, i.e. the way the CPU talks to the other stuff inside
  219. your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
  220. VESA. If you have PCI, say Y, otherwise N.
  221. The PCI-HOWTO, available from
  222. <http://www.tldp.org/docs.html#howto>, contains valuable
  223. information about which PCI hardware does work under Linux and which
  224. doesn't.
  225. # Select the host bridge type
  226. config PCI_HOST_VIA82C505
  227. bool
  228. depends on PCI && ARCH_SHARK
  229. default y
  230. source "drivers/pci/Kconfig"
  231. source "drivers/pcmcia/Kconfig"
  232. endmenu
  233. menu "Kernel Features"
  234. config SMP
  235. bool "Symmetric Multi-Processing (EXPERIMENTAL)"
  236. depends on EXPERIMENTAL && BROKEN #&& n
  237. help
  238. This enables support for systems with more than one CPU. If you have
  239. a system with only one CPU, like most personal computers, say N. If
  240. you have a system with more than one CPU, say Y.
  241. If you say N here, the kernel will run on single and multiprocessor
  242. machines, but will use only one CPU of a multiprocessor machine. If
  243. you say Y here, the kernel will run on many, but not all, single
  244. processor machines. On a single processor machine, the kernel will
  245. run faster if you say N here.
  246. See also the <file:Documentation/smp.txt>,
  247. <file:Documentation/i386/IO-APIC.txt>,
  248. <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
  249. <http://www.linuxdoc.org/docs.html#howto>.
  250. If you don't know what to do here, say N.
  251. config NR_CPUS
  252. int "Maximum number of CPUs (2-32)"
  253. range 2 32
  254. depends on SMP
  255. default "4"
  256. config PREEMPT
  257. bool "Preemptible Kernel (EXPERIMENTAL)"
  258. depends on EXPERIMENTAL
  259. help
  260. This option reduces the latency of the kernel when reacting to
  261. real-time or interactive events by allowing a low priority process to
  262. be preempted even if it is in kernel mode executing a system call.
  263. This allows applications to run more reliably even when the system is
  264. under load.
  265. Say Y here if you are building a kernel for a desktop, embedded
  266. or real-time system. Say N if you are unsure.
  267. config NO_IDLE_HZ
  268. bool "Dynamic tick timer"
  269. help
  270. Select this option if you want to disable continuous timer ticks
  271. and have them programmed to occur as required. This option saves
  272. power as the system can remain in idle state for longer.
  273. By default dynamic tick is disabled during the boot, and can be
  274. manually enabled with:
  275. echo 1 > /sys/devices/system/timer/timer0/dyn_tick
  276. Alternatively, if you want dynamic tick automatically enabled
  277. during boot, pass "dyntick=enable" via the kernel command string.
  278. Please note that dynamic tick may affect the accuracy of
  279. timekeeping on some platforms depending on the implementation.
  280. Currently at least OMAP, PXA2xx and SA11x0 platforms are known
  281. to have accurate timekeeping with dynamic tick.
  282. config ARCH_DISCONTIGMEM_ENABLE
  283. bool
  284. default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
  285. help
  286. Say Y to support efficient handling of discontiguous physical memory,
  287. for architectures which are either NUMA (Non-Uniform Memory Access)
  288. or have huge holes in the physical address space for other reasons.
  289. See <file:Documentation/vm/numa> for more.
  290. source "mm/Kconfig"
  291. config LEDS
  292. bool "Timer and CPU usage LEDs"
  293. depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
  294. ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
  295. ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
  296. ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
  297. ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE
  298. help
  299. If you say Y here, the LEDs on your machine will be used
  300. to provide useful information about your current system status.
  301. If you are compiling a kernel for a NetWinder or EBSA-285, you will
  302. be able to select which LEDs are active using the options below. If
  303. you are compiling a kernel for the EBSA-110 or the LART however, the
  304. red LED will simply flash regularly to indicate that the system is
  305. still functional. It is safe to say Y here if you have a CATS
  306. system, but the driver will do nothing.
  307. config LEDS_TIMER
  308. bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
  309. MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
  310. depends on LEDS
  311. default y if ARCH_EBSA110
  312. help
  313. If you say Y here, one of the system LEDs (the green one on the
  314. NetWinder, the amber one on the EBSA285, or the red one on the LART)
  315. will flash regularly to indicate that the system is still
  316. operational. This is mainly useful to kernel hackers who are
  317. debugging unstable kernels.
  318. The LART uses the same LED for both Timer LED and CPU usage LED
  319. functions. You may choose to use both, but the Timer LED function
  320. will overrule the CPU usage LED.
  321. config LEDS_CPU
  322. bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
  323. !ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
  324. depends on LEDS
  325. help
  326. If you say Y here, the red LED will be used to give a good real
  327. time indication of CPU usage, by lighting whenever the idle task
  328. is not currently executing.
  329. The LART uses the same LED for both Timer LED and CPU usage LED
  330. functions. You may choose to use both, but the Timer LED function
  331. will overrule the CPU usage LED.
  332. config ALIGNMENT_TRAP
  333. bool
  334. default y if !ARCH_EBSA110
  335. help
  336. ARM processors can not fetch/store information which is not
  337. naturally aligned on the bus, i.e., a 4 byte fetch must start at an
  338. address divisible by 4. On 32-bit ARM processors, these non-aligned
  339. fetch/store instructions will be emulated in software if you say
  340. here, which has a severe performance impact. This is necessary for
  341. correct operation of some network protocols. With an IP-only
  342. configuration it is safe to say N, otherwise say Y.
  343. endmenu
  344. menu "Boot options"
  345. # Compressed boot loader in ROM. Yes, we really want to ask about
  346. # TEXT and BSS so we preserve their values in the config files.
  347. config ZBOOT_ROM_TEXT
  348. hex "Compressed ROM boot loader base address"
  349. default "0"
  350. help
  351. The physical address at which the ROM-able zImage is to be
  352. placed in the target. Platforms which normally make use of
  353. ROM-able zImage formats normally set this to a suitable
  354. value in their defconfig file.
  355. If ZBOOT_ROM is not enabled, this has no effect.
  356. config ZBOOT_ROM_BSS
  357. hex "Compressed ROM boot loader BSS address"
  358. default "0"
  359. help
  360. The base address of 64KiB of read/write memory in the target
  361. for the ROM-able zImage, which must be available while the
  362. decompressor is running. Platforms which normally make use of
  363. ROM-able zImage formats normally set this to a suitable
  364. value in their defconfig file.
  365. If ZBOOT_ROM is not enabled, this has no effect.
  366. config ZBOOT_ROM
  367. bool "Compressed boot loader in ROM/flash"
  368. depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
  369. help
  370. Say Y here if you intend to execute your compressed kernel image
  371. (zImage) directly from ROM or flash. If unsure, say N.
  372. config CMDLINE
  373. string "Default kernel command string"
  374. default ""
  375. help
  376. On some architectures (EBSA110 and CATS), there is currently no way
  377. for the boot loader to pass arguments to the kernel. For these
  378. architectures, you should supply some command-line options at build
  379. time by entering them here. As a minimum, you should specify the
  380. memory size and the root device (e.g., mem=64M root=/dev/nfs).
  381. config XIP_KERNEL
  382. bool "Kernel Execute-In-Place from ROM"
  383. depends on !ZBOOT_ROM
  384. help
  385. Execute-In-Place allows the kernel to run from non-volatile storage
  386. directly addressable by the CPU, such as NOR flash. This saves RAM
  387. space since the text section of the kernel is not loaded from flash
  388. to RAM. Read-write sections, such as the data section and stack,
  389. are still copied to RAM. The XIP kernel is not compressed since
  390. it has to run directly from flash, so it will take more space to
  391. store it. The flash address used to link the kernel object files,
  392. and for storing it, is configuration dependent. Therefore, if you
  393. say Y here, you must know the proper physical address where to
  394. store the kernel image depending on your own flash memory usage.
  395. Also note that the make target becomes "make xipImage" rather than
  396. "make zImage" or "make Image". The final kernel binary to put in
  397. ROM memory will be arch/arm/boot/xipImage.
  398. If unsure, say N.
  399. config XIP_PHYS_ADDR
  400. hex "XIP Kernel Physical Location"
  401. depends on XIP_KERNEL
  402. default "0x00080000"
  403. help
  404. This is the physical address in your flash memory the kernel will
  405. be linked for and stored to. This address is dependent on your
  406. own flash usage.
  407. endmenu
  408. if (ARCH_SA1100 || ARCH_INTEGRATOR || ARCH_OMAP1)
  409. menu "CPU Frequency scaling"
  410. source "drivers/cpufreq/Kconfig"
  411. config CPU_FREQ_SA1100
  412. bool
  413. depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
  414. default y
  415. config CPU_FREQ_SA1110
  416. bool
  417. depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
  418. default y
  419. config CPU_FREQ_INTEGRATOR
  420. tristate "CPUfreq driver for ARM Integrator CPUs"
  421. depends on ARCH_INTEGRATOR && CPU_FREQ
  422. default y
  423. help
  424. This enables the CPUfreq driver for ARM Integrator CPUs.
  425. For details, take a look at <file:Documentation/cpu-freq>.
  426. If in doubt, say Y.
  427. endmenu
  428. endif
  429. menu "Floating point emulation"
  430. comment "At least one emulation must be selected"
  431. config FPE_NWFPE
  432. bool "NWFPE math emulation"
  433. ---help---
  434. Say Y to include the NWFPE floating point emulator in the kernel.
  435. This is necessary to run most binaries. Linux does not currently
  436. support floating point hardware so you need to say Y here even if
  437. your machine has an FPA or floating point co-processor podule.
  438. You may say N here if you are going to load the Acorn FPEmulator
  439. early in the bootup.
  440. config FPE_NWFPE_XP
  441. bool "Support extended precision"
  442. depends on FPE_NWFPE && !CPU_BIG_ENDIAN
  443. help
  444. Say Y to include 80-bit support in the kernel floating-point
  445. emulator. Otherwise, only 32 and 64-bit support is compiled in.
  446. Note that gcc does not generate 80-bit operations by default,
  447. so in most cases this option only enlarges the size of the
  448. floating point emulator without any good reason.
  449. You almost surely want to say N here.
  450. config FPE_FASTFPE
  451. bool "FastFPE math emulation (EXPERIMENTAL)"
  452. depends on !CPU_32v3 && EXPERIMENTAL
  453. ---help---
  454. Say Y here to include the FAST floating point emulator in the kernel.
  455. This is an experimental much faster emulator which now also has full
  456. precision for the mantissa. It does not support any exceptions.
  457. It is very simple, and approximately 3-6 times faster than NWFPE.
  458. It should be sufficient for most programs. It may be not suitable
  459. for scientific calculations, but you have to check this for yourself.
  460. If you do not feel you need a faster FP emulation you should better
  461. choose NWFPE.
  462. config VFP
  463. bool "VFP-format floating point maths"
  464. depends on CPU_V6 || CPU_ARM926T
  465. help
  466. Say Y to include VFP support code in the kernel. This is needed
  467. if your hardware includes a VFP unit.
  468. Please see <file:Documentation/arm/VFP/release-notes.txt> for
  469. release notes and additional status information.
  470. Say N if your target does not have VFP hardware.
  471. endmenu
  472. menu "Userspace binary formats"
  473. source "fs/Kconfig.binfmt"
  474. config ARTHUR
  475. tristate "RISC OS personality"
  476. help
  477. Say Y here to include the kernel code necessary if you want to run
  478. Acorn RISC OS/Arthur binaries under Linux. This code is still very
  479. experimental; if this sounds frightening, say N and sleep in peace.
  480. You can also say M here to compile this support as a module (which
  481. will be called arthur).
  482. endmenu
  483. menu "Power management options"
  484. config PM
  485. bool "Power Management support"
  486. ---help---
  487. "Power Management" means that parts of your computer are shut
  488. off or put into a power conserving "sleep" mode if they are not
  489. being used. There are two competing standards for doing this: APM
  490. and ACPI. If you want to use either one, say Y here and then also
  491. to the requisite support below.
  492. Power Management is most important for battery powered laptop
  493. computers; if you have a laptop, check out the Linux Laptop home
  494. page on the WWW at <http://www.linux-on-laptops.com/> or
  495. Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>
  496. and the Battery Powered Linux mini-HOWTO, available from
  497. <http://www.tldp.org/docs.html#howto>.
  498. config APM
  499. tristate "Advanced Power Management Emulation"
  500. depends on PM
  501. ---help---
  502. APM is a BIOS specification for saving power using several different
  503. techniques. This is mostly useful for battery powered laptops with
  504. APM compliant BIOSes. If you say Y here, the system time will be
  505. reset after a RESUME operation, the /proc/apm device will provide
  506. battery status information, and user-space programs will receive
  507. notification of APM "events" (e.g. battery status change).
  508. In order to use APM, you will need supporting software. For location
  509. and more information, read <file:Documentation/pm.txt> and the
  510. Battery Powered Linux mini-HOWTO, available from
  511. <http://www.tldp.org/docs.html#howto>.
  512. This driver does not spin down disk drives (see the hdparm(8)
  513. manpage ("man 8 hdparm") for that), and it doesn't turn off
  514. VESA-compliant "green" monitors.
  515. Generally, if you don't have a battery in your machine, there isn't
  516. much point in using this driver and you should say N. If you get
  517. random kernel OOPSes or reboots that don't seem to be related to
  518. anything, try disabling/enabling this option (or disabling/enabling
  519. APM in your BIOS).
  520. endmenu
  521. source "net/Kconfig"
  522. menu "Device Drivers"
  523. source "drivers/base/Kconfig"
  524. if ALIGNMENT_TRAP
  525. source "drivers/mtd/Kconfig"
  526. endif
  527. source "drivers/parport/Kconfig"
  528. source "drivers/pnp/Kconfig"
  529. source "drivers/block/Kconfig"
  530. source "drivers/acorn/block/Kconfig"
  531. if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
  532. || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
  533. || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
  534. source "drivers/ide/Kconfig"
  535. endif
  536. source "drivers/scsi/Kconfig"
  537. source "drivers/md/Kconfig"
  538. source "drivers/message/fusion/Kconfig"
  539. source "drivers/ieee1394/Kconfig"
  540. source "drivers/message/i2o/Kconfig"
  541. source "drivers/net/Kconfig"
  542. source "drivers/isdn/Kconfig"
  543. # input before char - char/joystick depends on it. As does USB.
  544. source "drivers/input/Kconfig"
  545. source "drivers/char/Kconfig"
  546. source "drivers/i2c/Kconfig"
  547. source "drivers/hwmon/Kconfig"
  548. #source "drivers/l3/Kconfig"
  549. source "drivers/misc/Kconfig"
  550. source "drivers/mfd/Kconfig"
  551. source "drivers/media/Kconfig"
  552. source "drivers/video/Kconfig"
  553. source "sound/Kconfig"
  554. source "drivers/usb/Kconfig"
  555. source "drivers/mmc/Kconfig"
  556. endmenu
  557. source "fs/Kconfig"
  558. source "arch/arm/oprofile/Kconfig"
  559. source "arch/arm/Kconfig.debug"
  560. source "security/Kconfig"
  561. source "crypto/Kconfig"
  562. source "lib/Kconfig"