/arch/frv/Kconfig

https://bitbucket.org/evzijst/gittest · #! · 357 lines · 274 code · 83 blank · 0 comment · 0 complexity · 554caf9aabdf2709674bcd42ee2ee9f2 MD5 · raw file

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