Kconfig.mmu 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418
  1. config GENERIC_IOMAP
  2. bool
  3. default y
  4. config ARCH_MAY_HAVE_PC_FDC
  5. bool
  6. depends on BROKEN && (Q40 || SUN3X)
  7. default y
  8. config ARCH_USES_GETTIMEOFFSET
  9. def_bool y
  10. config EISA
  11. bool
  12. ---help---
  13. The Extended Industry Standard Architecture (EISA) bus was
  14. developed as an open alternative to the IBM MicroChannel bus.
  15. The EISA bus provided some of the features of the IBM MicroChannel
  16. bus while maintaining backward compatibility with cards made for
  17. the older ISA bus. The EISA bus saw limited use between 1988 and
  18. 1995 when it was made obsolete by the PCI bus.
  19. Say Y here if you are building a kernel for an EISA-based machine.
  20. Otherwise, say N.
  21. config MCA
  22. bool
  23. help
  24. MicroChannel Architecture is found in some IBM PS/2 machines and
  25. laptops. It is a bus system similar to PCI or ISA. See
  26. <file:Documentation/mca.txt> (and especially the web page given
  27. there) before attempting to build an MCA bus kernel.
  28. config PCMCIA
  29. tristate
  30. ---help---
  31. Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
  32. computer. These are credit-card size devices such as network cards,
  33. modems or hard drives often used with laptops computers. There are
  34. actually two varieties of these cards: the older 16 bit PCMCIA cards
  35. and the newer 32 bit CardBus cards. If you want to use CardBus
  36. cards, you need to say Y here and also to "CardBus support" below.
  37. To use your PC-cards, you will need supporting software from David
  38. Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
  39. for location). Please also read the PCMCIA-HOWTO, available from
  40. <http://www.tldp.org/docs.html#howto>.
  41. To compile this driver as modules, choose M here: the
  42. modules will be called pcmcia_core and ds.
  43. config AMIGA
  44. bool "Amiga support"
  45. select MMU_MOTOROLA if MMU
  46. help
  47. This option enables support for the Amiga series of computers. If
  48. you plan to use this kernel on an Amiga, say Y here and browse the
  49. material available in <file:Documentation/m68k>; otherwise say N.
  50. config ATARI
  51. bool "Atari support"
  52. select MMU_MOTOROLA if MMU
  53. help
  54. This option enables support for the 68000-based Atari series of
  55. computers (including the TT, Falcon and Medusa). If you plan to use
  56. this kernel on an Atari, say Y here and browse the material
  57. available in <file:Documentation/m68k>; otherwise say N.
  58. config MAC
  59. bool "Macintosh support"
  60. select MMU_MOTOROLA if MMU
  61. help
  62. This option enables support for the Apple Macintosh series of
  63. computers (yes, there is experimental support now, at least for part
  64. of the series).
  65. Say N unless you're willing to code the remaining necessary support.
  66. ;)
  67. config NUBUS
  68. bool
  69. depends on MAC
  70. default y
  71. config M68K_L2_CACHE
  72. bool
  73. depends on MAC
  74. default y
  75. config APOLLO
  76. bool "Apollo support"
  77. select MMU_MOTOROLA if MMU
  78. help
  79. Say Y here if you want to run Linux on an MC680x0-based Apollo
  80. Domain workstation such as the DN3500.
  81. config VME
  82. bool "VME (Motorola and BVM) support"
  83. select MMU_MOTOROLA if MMU
  84. help
  85. Say Y here if you want to build a kernel for a 680x0 based VME
  86. board. Boards currently supported include Motorola boards MVME147,
  87. MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
  88. BVME6000 boards from BVM Ltd are also supported.
  89. config MVME147
  90. bool "MVME147 support"
  91. depends on VME
  92. help
  93. Say Y to include support for early Motorola VME boards. This will
  94. build a kernel which can run on MVME147 single-board computers. If
  95. you select this option you will have to select the appropriate
  96. drivers for SCSI, Ethernet and serial ports later on.
  97. config MVME16x
  98. bool "MVME162, 166 and 167 support"
  99. depends on VME
  100. help
  101. Say Y to include support for Motorola VME boards. This will build a
  102. kernel which can run on MVME162, MVME166, MVME167, MVME172, and
  103. MVME177 boards. If you select this option you will have to select
  104. the appropriate drivers for SCSI, Ethernet and serial ports later
  105. on.
  106. config BVME6000
  107. bool "BVME4000 and BVME6000 support"
  108. depends on VME
  109. help
  110. Say Y to include support for VME boards from BVM Ltd. This will
  111. build a kernel which can run on BVME4000 and BVME6000 boards. If
  112. you select this option you will have to select the appropriate
  113. drivers for SCSI, Ethernet and serial ports later on.
  114. config HP300
  115. bool "HP9000/300 and HP9000/400 support"
  116. select MMU_MOTOROLA if MMU
  117. help
  118. This option enables support for the HP9000/300 and HP9000/400 series
  119. of workstations. Support for these machines is still somewhat
  120. experimental. If you plan to try to use the kernel on such a machine
  121. say Y here.
  122. Everybody else says N.
  123. config DIO
  124. bool "DIO bus support"
  125. depends on HP300
  126. default y
  127. help
  128. Say Y here to enable support for the "DIO" expansion bus used in
  129. HP300 machines. If you are using such a system you almost certainly
  130. want this.
  131. config SUN3X
  132. bool "Sun3x support"
  133. select MMU_MOTOROLA if MMU
  134. select M68030
  135. help
  136. This option enables support for the Sun 3x series of workstations.
  137. Be warned that this support is very experimental.
  138. Note that Sun 3x kernels are not compatible with Sun 3 hardware.
  139. General Linux information on the Sun 3x series (now discontinued)
  140. is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
  141. If you don't want to compile a kernel for a Sun 3x, say N.
  142. config Q40
  143. bool "Q40/Q60 support"
  144. select MMU_MOTOROLA if MMU
  145. help
  146. The Q40 is a Motorola 68040-based successor to the Sinclair QL
  147. manufactured in Germany. There is an official Q40 home page at
  148. <http://www.q40.de/>. This option enables support for the Q40 and
  149. Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
  150. emulation.
  151. config SUN3
  152. bool "Sun3 support"
  153. depends on !MMU_MOTOROLA
  154. select MMU_SUN3 if MMU
  155. select M68020
  156. help
  157. This option enables support for the Sun 3 series of workstations
  158. (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
  159. that all other hardware types must be disabled, as Sun 3 kernels
  160. are incompatible with all other m68k targets (including Sun 3x!).
  161. If you don't want to compile a kernel exclusively for a Sun 3, say N.
  162. config NATFEAT
  163. bool "ARAnyM emulator support"
  164. depends on ATARI
  165. help
  166. This option enables support for ARAnyM native features, such as
  167. access to a disk image as /dev/hda.
  168. config NFBLOCK
  169. tristate "NatFeat block device support"
  170. depends on BLOCK && NATFEAT
  171. help
  172. Say Y to include support for the ARAnyM NatFeat block device
  173. which allows direct access to the hard drives without using
  174. the hardware emulation.
  175. config NFCON
  176. tristate "NatFeat console driver"
  177. depends on NATFEAT
  178. help
  179. Say Y to include support for the ARAnyM NatFeat console driver
  180. which allows the console output to be redirected to the stderr
  181. output of ARAnyM.
  182. config NFETH
  183. tristate "NatFeat Ethernet support"
  184. depends on NET_ETHERNET && NATFEAT
  185. help
  186. Say Y to include support for the ARAnyM NatFeat network device
  187. which will emulate a regular ethernet device while presenting an
  188. ethertap device to the host system.
  189. comment "Processor type"
  190. config M68020
  191. bool "68020 support"
  192. help
  193. If you anticipate running this kernel on a computer with a MC68020
  194. processor, say Y. Otherwise, say N. Note that the 68020 requires a
  195. 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
  196. Sun 3, which provides its own version.
  197. config M68030
  198. bool "68030 support"
  199. depends on !MMU_SUN3
  200. help
  201. If you anticipate running this kernel on a computer with a MC68030
  202. processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
  203. work, as it does not include an MMU (Memory Management Unit).
  204. config M68040
  205. bool "68040 support"
  206. depends on !MMU_SUN3
  207. help
  208. If you anticipate running this kernel on a computer with a MC68LC040
  209. or MC68040 processor, say Y. Otherwise, say N. Note that an
  210. MC68EC040 will not work, as it does not include an MMU (Memory
  211. Management Unit).
  212. config M68060
  213. bool "68060 support"
  214. depends on !MMU_SUN3
  215. help
  216. If you anticipate running this kernel on a computer with a MC68060
  217. processor, say Y. Otherwise, say N.
  218. config MMU_MOTOROLA
  219. bool
  220. config MMU_SUN3
  221. bool
  222. depends on MMU && !MMU_MOTOROLA
  223. config M68KFPU_EMU
  224. bool "Math emulation support (EXPERIMENTAL)"
  225. depends on EXPERIMENTAL
  226. help
  227. At some point in the future, this will cause floating-point math
  228. instructions to be emulated by the kernel on machines that lack a
  229. floating-point math coprocessor. Thrill-seekers and chronically
  230. sleep-deprived psychotic hacker types can say Y now, everyone else
  231. should probably wait a while.
  232. config M68KFPU_EMU_EXTRAPREC
  233. bool "Math emulation extra precision"
  234. depends on M68KFPU_EMU
  235. help
  236. The fpu uses normally a few bit more during calculations for
  237. correct rounding, the emulator can (often) do the same but this
  238. extra calculation can cost quite some time, so you can disable
  239. it here. The emulator will then "only" calculate with a 64 bit
  240. mantissa and round slightly incorrect, what is more than enough
  241. for normal usage.
  242. config M68KFPU_EMU_ONLY
  243. bool "Math emulation only kernel"
  244. depends on M68KFPU_EMU
  245. help
  246. This option prevents any floating-point instructions from being
  247. compiled into the kernel, thereby the kernel doesn't save any
  248. floating point context anymore during task switches, so this
  249. kernel will only be usable on machines without a floating-point
  250. math coprocessor. This makes the kernel a bit faster as no tests
  251. needs to be executed whether a floating-point instruction in the
  252. kernel should be executed or not.
  253. config ADVANCED
  254. bool "Advanced configuration options"
  255. ---help---
  256. This gives you access to some advanced options for the CPU. The
  257. defaults should be fine for most users, but these options may make
  258. it possible for you to improve performance somewhat if you know what
  259. you are doing.
  260. Note that the answer to this question won't directly affect the
  261. kernel: saying N will just cause the configurator to skip all
  262. the questions about these options.
  263. Most users should say N to this question.
  264. config RMW_INSNS
  265. bool "Use read-modify-write instructions"
  266. depends on ADVANCED
  267. ---help---
  268. This allows to use certain instructions that work with indivisible
  269. read-modify-write bus cycles. While this is faster than the
  270. workaround of disabling interrupts, it can conflict with DMA
  271. ( = direct memory access) on many Amiga systems, and it is also said
  272. to destabilize other machines. It is very likely that this will
  273. cause serious problems on any Amiga or Atari Medusa if set. The only
  274. configuration where it should work are 68030-based Ataris, where it
  275. apparently improves performance. But you've been warned! Unless you
  276. really know what you are doing, say N. Try Y only if you're quite
  277. adventurous.
  278. config SINGLE_MEMORY_CHUNK
  279. bool "Use one physical chunk of memory only" if ADVANCED && !SUN3
  280. default y if SUN3
  281. select NEED_MULTIPLE_NODES
  282. help
  283. Ignore all but the first contiguous chunk of physical memory for VM
  284. purposes. This will save a few bytes kernel size and may speed up
  285. some operations. Say N if not sure.
  286. config 060_WRITETHROUGH
  287. bool "Use write-through caching for 68060 supervisor accesses"
  288. depends on ADVANCED && M68060
  289. ---help---
  290. The 68060 generally uses copyback caching of recently accessed data.
  291. Copyback caching means that memory writes will be held in an on-chip
  292. cache and only written back to memory some time later. Saying Y
  293. here will force supervisor (kernel) accesses to use writethrough
  294. caching. Writethrough caching means that data is written to memory
  295. straight away, so that cache and memory data always agree.
  296. Writethrough caching is less efficient, but is needed for some
  297. drivers on 68060 based systems where the 68060 bus snooping signal
  298. is hardwired on. The 53c710 SCSI driver is known to suffer from
  299. this problem.
  300. config ARCH_DISCONTIGMEM_ENABLE
  301. def_bool !SINGLE_MEMORY_CHUNK
  302. config NODES_SHIFT
  303. int
  304. default "3"
  305. depends on !SINGLE_MEMORY_CHUNK
  306. config ZORRO
  307. bool "Amiga Zorro (AutoConfig) bus support"
  308. depends on AMIGA
  309. help
  310. This enables support for the Zorro bus in the Amiga. If you have
  311. expansion cards in your Amiga that conform to the Amiga
  312. AutoConfig(tm) specification, say Y, otherwise N. Note that even
  313. expansion cards that do not fit in the Zorro slots but fit in e.g.
  314. the CPU slot may fall in this category, so you have to say Y to let
  315. Linux use these.
  316. config AMIGA_PCMCIA
  317. bool "Amiga 1200/600 PCMCIA support (EXPERIMENTAL)"
  318. depends on AMIGA && EXPERIMENTAL
  319. help
  320. Include support in the kernel for pcmcia on Amiga 1200 and Amiga
  321. 600. If you intend to use pcmcia cards say Y; otherwise say N.
  322. config STRAM_PROC
  323. bool "ST-RAM statistics in /proc"
  324. depends on ATARI
  325. help
  326. Say Y here to report ST-RAM usage statistics in /proc/stram.
  327. config HEARTBEAT
  328. bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || MAC ||Q40
  329. default y if !AMIGA && !APOLLO && !ATARI && !MAC && !Q40 && HP300
  330. help
  331. Use the power-on LED on your machine as a load meter. The exact
  332. behavior is platform-dependent, but normally the flash frequency is
  333. a hyperbolic function of the 5-minute load average.
  334. # We have a dedicated heartbeat LED. :-)
  335. config PROC_HARDWARE
  336. bool "/proc/hardware support"
  337. help
  338. Say Y here to support the /proc/hardware file, which gives you
  339. access to information about the machine you're running on,
  340. including the model, CPU, MMU, clock speed, BogoMIPS rating,
  341. and memory size.
  342. config ISA
  343. bool
  344. depends on Q40 || AMIGA_PCMCIA
  345. default y
  346. help
  347. Find out whether you have ISA slots on your motherboard. ISA is the
  348. name of a bus system, i.e. the way the CPU talks to the other stuff
  349. inside your box. Other bus systems are PCI, EISA, MicroChannel
  350. (MCA) or VESA. ISA is an older system, now being displaced by PCI;
  351. newer boards don't support it. If you have ISA, say Y, otherwise N.
  352. config GENERIC_ISA_DMA
  353. bool
  354. depends on Q40 || AMIGA_PCMCIA
  355. default y
  356. source "drivers/pci/Kconfig"
  357. source "drivers/zorro/Kconfig"