Kconfig 9.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376
  1. #
  2. # For a description of the syntax of this configuration file,
  3. # see Documentation/kbuild/kconfig-language.txt.
  4. #
  5. config FRV
  6. bool
  7. default y
  8. config RWSEM_GENERIC_SPINLOCK
  9. bool
  10. default y
  11. config RWSEM_XCHGADD_ALGORITHM
  12. bool
  13. config GENERIC_FIND_NEXT_BIT
  14. bool
  15. default y
  16. config GENERIC_HWEIGHT
  17. bool
  18. default y
  19. config GENERIC_CALIBRATE_DELAY
  20. bool
  21. default n
  22. config GENERIC_HARDIRQS
  23. bool
  24. default y
  25. config GENERIC_HARDIRQS_NO__DO_IRQ
  26. bool
  27. default y
  28. config GENERIC_TIME
  29. bool
  30. default y
  31. config TIME_LOW_RES
  32. bool
  33. default y
  34. mainmenu "Fujitsu FR-V Kernel Configuration"
  35. source "init/Kconfig"
  36. menu "Fujitsu FR-V system setup"
  37. config MMU
  38. bool "MMU support"
  39. help
  40. This options switches on and off support for the FR-V MMU
  41. (effectively switching between vmlinux and uClinux). Not all FR-V
  42. CPUs support this. Currently only the FR451 has a sufficiently
  43. featured MMU.
  44. config FRV_OUTOFLINE_ATOMIC_OPS
  45. bool "Out-of-line the FRV atomic operations"
  46. default n
  47. help
  48. Setting this option causes the FR-V atomic operations to be mostly
  49. implemented out-of-line.
  50. See Documentation/fujitsu/frv/atomic-ops.txt for more information.
  51. config HIGHMEM
  52. bool "High memory support"
  53. depends on MMU
  54. default y
  55. help
  56. If you wish to use more than 256MB of memory with your MMU based
  57. system, you will need to select this option. The kernel can only see
  58. the memory between 0xC0000000 and 0xD0000000 directly... everything
  59. else must be kmapped.
  60. The arch is, however, capable of supporting up to 3GB of SDRAM.
  61. config HIGHPTE
  62. bool "Allocate page tables in highmem"
  63. depends on HIGHMEM
  64. default y
  65. help
  66. The VM uses one page of memory for each page table. For systems
  67. with a lot of RAM, this can be wasteful of precious low memory.
  68. Setting this option will put user-space page tables in high memory.
  69. config LARGE_ALLOCS
  70. bool "Allow allocating large blocks (> 1MB) of memory"
  71. help
  72. Allow the slab memory allocator to keep chains for very large memory
  73. sizes - up to 32MB. You may need this if your system has a lot of
  74. RAM, and you need to able to allocate very large contiguous chunks.
  75. If unsure, say N.
  76. source "mm/Kconfig"
  77. choice
  78. prompt "uClinux kernel load address"
  79. depends on !MMU
  80. default UCPAGE_OFFSET_C0000000
  81. help
  82. This option sets the base address for the uClinux kernel. The kernel
  83. will rearrange the SDRAM layout to start at this address, and move
  84. itself to start there. It must be greater than 0, and it must be
  85. sufficiently less than 0xE0000000 that the SDRAM does not intersect
  86. the I/O region.
  87. The base address must also be aligned such that the SDRAM controller
  88. can decode it. For instance, a 512MB SDRAM bank must be 512MB aligned.
  89. config UCPAGE_OFFSET_20000000
  90. bool "0x20000000"
  91. config UCPAGE_OFFSET_40000000
  92. bool "0x40000000"
  93. config UCPAGE_OFFSET_60000000
  94. bool "0x60000000"
  95. config UCPAGE_OFFSET_80000000
  96. bool "0x80000000"
  97. config UCPAGE_OFFSET_A0000000
  98. bool "0xA0000000"
  99. config UCPAGE_OFFSET_C0000000
  100. bool "0xC0000000 (Recommended)"
  101. endchoice
  102. config PROTECT_KERNEL
  103. bool "Protect core kernel against userspace"
  104. depends on !MMU
  105. default y
  106. help
  107. Selecting this option causes the uClinux kernel to change the
  108. permittivity of DAMPR register covering the core kernel image to
  109. prevent userspace accessing the underlying memory directly.
  110. choice
  111. prompt "CPU Caching mode"
  112. default FRV_DEFL_CACHE_WBACK
  113. help
  114. This option determines the default caching mode for the kernel.
  115. Write-Back caching mode involves the all reads and writes causing
  116. the affected cacheline to be read into the cache first before being
  117. operated upon. Memory is not then updated by a write until the cache
  118. is filled and a cacheline needs to be displaced from the cache to
  119. make room. Only at that point is it written back.
  120. Write-Behind caching is similar to Write-Back caching, except that a
  121. write won't fetch a cacheline into the cache if there isn't already
  122. one there; it will write directly to memory instead.
  123. Write-Through caching only fetches cachelines from memory on a
  124. read. Writes always get written directly to memory. If the affected
  125. cacheline is also in cache, it will be updated too.
  126. The final option is to turn of caching entirely.
  127. Note that not all CPUs support Write-Behind caching. If the CPU on
  128. which the kernel is running doesn't, it'll fall back to Write-Back
  129. caching.
  130. config FRV_DEFL_CACHE_WBACK
  131. bool "Write-Back"
  132. config FRV_DEFL_CACHE_WBEHIND
  133. bool "Write-Behind"
  134. config FRV_DEFL_CACHE_WTHRU
  135. bool "Write-Through"
  136. config FRV_DEFL_CACHE_DISABLED
  137. bool "Disabled"
  138. endchoice
  139. menu "CPU core support"
  140. config CPU_FR401
  141. bool "Include FR401 core support"
  142. depends on !MMU
  143. default y
  144. help
  145. This enables support for the FR401, FR401A and FR403 CPUs
  146. config CPU_FR405
  147. bool "Include FR405 core support"
  148. depends on !MMU
  149. default y
  150. help
  151. This enables support for the FR405 CPU
  152. config CPU_FR451
  153. bool "Include FR451 core support"
  154. default y
  155. help
  156. This enables support for the FR451 CPU
  157. config CPU_FR451_COMPILE
  158. bool "Specifically compile for FR451 core"
  159. depends on CPU_FR451 && !CPU_FR401 && !CPU_FR405 && !CPU_FR551
  160. default y
  161. help
  162. This causes appropriate flags to be passed to the compiler to
  163. optimise for the FR451 CPU
  164. config CPU_FR551
  165. bool "Include FR551 core support"
  166. depends on !MMU
  167. default y
  168. help
  169. This enables support for the FR555 CPU
  170. config CPU_FR551_COMPILE
  171. bool "Specifically compile for FR551 core"
  172. depends on CPU_FR551 && !CPU_FR401 && !CPU_FR405 && !CPU_FR451
  173. default y
  174. help
  175. This causes appropriate flags to be passed to the compiler to
  176. optimise for the FR555 CPU
  177. config FRV_L1_CACHE_SHIFT
  178. int
  179. default "5" if CPU_FR401 || CPU_FR405 || CPU_FR451
  180. default "6" if CPU_FR551
  181. endmenu
  182. choice
  183. prompt "System support"
  184. default MB93091_VDK
  185. config MB93091_VDK
  186. bool "MB93091 CPU board with or without motherboard"
  187. config MB93093_PDK
  188. bool "MB93093 PDK unit"
  189. endchoice
  190. if MB93091_VDK
  191. choice
  192. prompt "Motherboard support"
  193. default MB93090_MB00
  194. config MB93090_MB00
  195. bool "Use the MB93090-MB00 motherboard"
  196. help
  197. Select this option if the MB93091 CPU board is going to be used with
  198. a MB93090-MB00 VDK motherboard
  199. config MB93091_NO_MB
  200. bool "Use standalone"
  201. help
  202. Select this option if the MB93091 CPU board is going to be used
  203. without a motherboard
  204. endchoice
  205. endif
  206. config FUJITSU_MB93493
  207. bool "MB93493 Multimedia chip"
  208. help
  209. Select this option if the MB93493 multimedia chip is going to be
  210. used.
  211. choice
  212. prompt "GP-Relative data support"
  213. default GPREL_DATA_8
  214. help
  215. This option controls what data, if any, should be placed in the GP
  216. relative data sections. Using this means that the compiler can
  217. generate accesses to the data using GR16-relative addressing which
  218. is faster than absolute instructions and saves space (2 instructions
  219. per access).
  220. However, the GPREL region is limited in size because the immediate
  221. value used in the load and store instructions is limited to a 12-bit
  222. signed number.
  223. So if the linker starts complaining that accesses to GPREL data are
  224. out of range, try changing this option from the default.
  225. Note that modules will always be compiled with this feature disabled
  226. as the module data will not be in range of the GP base address.
  227. config GPREL_DATA_8
  228. bool "Put data objects of up to 8 bytes into GP-REL"
  229. config GPREL_DATA_4
  230. bool "Put data objects of up to 4 bytes into GP-REL"
  231. config GPREL_DATA_NONE
  232. bool "Don't use GP-REL"
  233. endchoice
  234. config FRV_ONCPU_SERIAL
  235. bool "Use on-CPU serial ports"
  236. select SERIAL_8250
  237. default y
  238. config PCI
  239. bool "Use PCI"
  240. depends on MB93090_MB00
  241. default y
  242. help
  243. Some FR-V systems (such as the MB93090-MB00 VDK) have PCI
  244. onboard. If you have one of these boards and you wish to use the PCI
  245. facilities, say Y here.
  246. The PCI-HOWTO, available from
  247. <http://www.tldp.org/docs.html#howto>, contains valuable
  248. information about which PCI hardware does work under Linux and which
  249. doesn't.
  250. config RESERVE_DMA_COHERENT
  251. bool "Reserve DMA coherent memory"
  252. depends on PCI && !MMU
  253. default y
  254. help
  255. Many PCI drivers require access to uncached memory for DMA device
  256. communications (such as is done with some Ethernet buffer rings). If
  257. a fully featured MMU is available, this can be done through page
  258. table settings, but if not, a region has to be set aside and marked
  259. with a special DAMPR register.
  260. Setting this option causes uClinux to set aside a portion of the
  261. available memory for use in this manner. The memory will then be
  262. unavailable for normal kernel use.
  263. source "drivers/pci/Kconfig"
  264. source "drivers/pcmcia/Kconfig"
  265. #config MATH_EMULATION
  266. # bool "Math emulation support (EXPERIMENTAL)"
  267. # depends on EXPERIMENTAL
  268. # help
  269. # At some point in the future, this will cause floating-point math
  270. # instructions to be emulated by the kernel on machines that lack a
  271. # floating-point math coprocessor. Thrill-seekers and chronically
  272. # sleep-deprived psychotic hacker types can say Y now, everyone else
  273. # should probably wait a while.
  274. menu "Power management options"
  275. source kernel/power/Kconfig
  276. endmenu
  277. endmenu
  278. menu "Executable formats"
  279. source "fs/Kconfig.binfmt"
  280. endmenu
  281. source "net/Kconfig"
  282. source "drivers/Kconfig"
  283. source "fs/Kconfig"
  284. source "arch/frv/Kconfig.debug"
  285. source "security/Kconfig"
  286. source "crypto/Kconfig"
  287. source "lib/Kconfig"