Kconfig 9.3 KB

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