Kconfig 9.3 KB

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