[linux.git] / arch / frv / Kconfig

#
# For a description of the syntax of this configuration file,
# see Documentation/kbuild/kconfig-language.txt.
#
config FRV
	bool
	default y

config RWSEM_GENERIC_SPINLOCK
	bool
	default y

config RWSEM_XCHGADD_ALGORITHM
	bool

config GENERIC_FIND_NEXT_BIT
	bool
	default y

config GENERIC_HWEIGHT
	bool
	default y

config GENERIC_CALIBRATE_DELAY
	bool
	default n

config GENERIC_HARDIRQS
	bool
	default n

config TIME_LOW_RES
	bool
	default y

mainmenu "Fujitsu FR-V Kernel Configuration"

source "init/Kconfig"


menu "Fujitsu FR-V system setup"

config MMU
	bool "MMU support"
	help
	  This options switches on and off support for the FR-V MMU
	  (effectively switching between vmlinux and uClinux). Not all FR-V
	  CPUs support this. Currently only the FR451 has a sufficiently
	  featured MMU.

config FRV_OUTOFLINE_ATOMIC_OPS
	bool "Out-of-line the FRV atomic operations"
	default n
	help
	  Setting this option causes the FR-V atomic operations to be mostly
	  implemented out-of-line.

	  See Documentation/fujitsu/frv/atomic-ops.txt for more information.

config HIGHMEM
	bool "High memory support"
	depends on MMU
	default y
	help
	  If you wish to use more than 256MB of memory with your MMU based
	  system, you will need to select this option. The kernel can only see
	  the memory between 0xC0000000 and 0xD0000000 directly... everything
	  else must be kmapped.

	  The arch is, however, capable of supporting up to 3GB of SDRAM.

config HIGHPTE
	bool "Allocate page tables in highmem"
	depends on HIGHMEM
	default y
	help
	  The VM uses one page of memory for each page table.  For systems
	  with a lot of RAM, this can be wasteful of precious low memory.
	  Setting this option will put user-space page tables in high memory.

source "mm/Kconfig"

choice
	prompt "uClinux kernel load address"
	depends on !MMU
	default UCPAGE_OFFSET_C0000000
	help
	  This option sets the base address for the uClinux kernel. The kernel
	  will rearrange the SDRAM layout to start at this address, and move
	  itself to start there. It must be greater than 0, and it must be
	  sufficiently less than 0xE0000000 that the SDRAM does not intersect
	  the I/O region.

	  The base address must also be aligned such that the SDRAM controller
	  can decode it. For instance, a 512MB SDRAM bank must be 512MB aligned.

config UCPAGE_OFFSET_20000000
       bool "0x20000000"

config UCPAGE_OFFSET_40000000
       bool "0x40000000"

config UCPAGE_OFFSET_60000000
       bool "0x60000000"

config UCPAGE_OFFSET_80000000
       bool "0x80000000"

config UCPAGE_OFFSET_A0000000
       bool "0xA0000000"

config UCPAGE_OFFSET_C0000000
       bool "0xC0000000 (Recommended)"

endchoice

config PROTECT_KERNEL
	bool "Protect core kernel against userspace"
	depends on !MMU
	default y
	help
	  Selecting this option causes the uClinux kernel to change the
	  permittivity of DAMPR register covering the core kernel image to
	  prevent userspace accessing the underlying memory directly.

choice
	prompt "CPU Caching mode"
	default FRV_DEFL_CACHE_WBACK
	help
	  This option determines the default caching mode for the kernel.

	  Write-Back caching mode involves the all reads and writes causing
	  the affected cacheline to be read into the cache first before being
	  operated upon. Memory is not then updated by a write until the cache
	  is filled and a cacheline needs to be displaced from the cache to
	  make room. Only at that point is it written back.

	  Write-Behind caching is similar to Write-Back caching, except that a
	  write won't fetch a cacheline into the cache if there isn't already
	  one there; it will write directly to memory instead.

	  Write-Through caching only fetches cachelines from memory on a
	  read. Writes always get written directly to memory. If the affected
	  cacheline is also in cache, it will be updated too.

	  The final option is to turn of caching entirely.

	  Note that not all CPUs support Write-Behind caching. If the CPU on
	  which the kernel is running doesn't, it'll fall back to Write-Back
	  caching.

config FRV_DEFL_CACHE_WBACK
	bool "Write-Back"

config FRV_DEFL_CACHE_WBEHIND
	bool "Write-Behind"

config FRV_DEFL_CACHE_WTHRU
	bool "Write-Through"

config FRV_DEFL_CACHE_DISABLED
	bool "Disabled"

endchoice

menu "CPU core support"

config CPU_FR401
	bool "Include FR401 core support"
	depends on !MMU
	default y
	help
	  This enables support for the FR401, FR401A and FR403 CPUs

config CPU_FR405
	bool "Include FR405 core support"
	depends on !MMU
	default y
	help
	  This enables support for the FR405 CPU

config CPU_FR451
	bool "Include FR451 core support"
	default y
	help
	  This enables support for the FR451 CPU

config CPU_FR451_COMPILE
	bool "Specifically compile for FR451 core"
	depends on CPU_FR451 && !CPU_FR401 && !CPU_FR405 && !CPU_FR551
	default y
	help
	  This causes appropriate flags to be passed to the compiler to
	  optimise for the FR451 CPU

config CPU_FR551
	bool "Include FR551 core support"
	depends on !MMU
	default y
	help
	  This enables support for the FR555 CPU

config CPU_FR551_COMPILE
	bool "Specifically compile for FR551 core"
	depends on CPU_FR551 && !CPU_FR401 && !CPU_FR405 && !CPU_FR451
	default y
	help
	  This causes appropriate flags to be passed to the compiler to
	  optimise for the FR555 CPU

config FRV_L1_CACHE_SHIFT
	int
	default "5" if CPU_FR401 || CPU_FR405 || CPU_FR451
	default "6" if CPU_FR551

endmenu

choice
	prompt "System support"
	default MB93091_VDK

config MB93091_VDK
	bool "MB93091 CPU board with or without motherboard"

config MB93093_PDK
	bool "MB93093 PDK unit"

endchoice

if MB93091_VDK
choice
	prompt "Motherboard support"
	default MB93090_MB00

config MB93090_MB00
	bool "Use the MB93090-MB00 motherboard"
	help
	  Select this option if the MB93091 CPU board is going to be used with
	  a MB93090-MB00 VDK motherboard

config MB93091_NO_MB
	bool "Use standalone"
	help
	  Select this option if the MB93091 CPU board is going to be used
	  without a motherboard

endchoice
endif

choice
	prompt "GP-Relative data support"
	default GPREL_DATA_8
	help
	  This option controls what data, if any, should be placed in the GP
	  relative data sections. Using this means that the compiler can
	  generate accesses to the data using GR16-relative addressing which
	  is faster than absolute instructions and saves space (2 instructions
	  per access).

	  However, the GPREL region is limited in size because the immediate
	  value used in the load and store instructions is limited to a 12-bit
	  signed number.

	  So if the linker starts complaining that accesses to GPREL data are
	  out of range, try changing this option from the default.

	  Note that modules will always be compiled with this feature disabled
	  as the module data will not be in range of the GP base address.

config GPREL_DATA_8
	bool "Put data objects of up to 8 bytes into GP-REL"

config GPREL_DATA_4
	bool "Put data objects of up to 4 bytes into GP-REL"

config GPREL_DATA_NONE
	bool "Don't use GP-REL"

endchoice

config FRV_ONCPU_SERIAL
	bool "Use on-CPU serial ports"
	select SERIAL_8250
	default y

config PCI
	bool "Use PCI"
	depends on MB93090_MB00
	default y
	help
	  Some FR-V systems (such as the MB93090-MB00 VDK) have PCI
	  onboard. If you have one of these boards and you wish to use the PCI
	  facilities, say Y here.

	  The PCI-HOWTO, available from
	  <http://www.tldp.org/docs.html#howto>, contains valuable
	  information about which PCI hardware does work under Linux and which
	  doesn't.

config RESERVE_DMA_COHERENT
	bool "Reserve DMA coherent memory"
	depends on PCI && !MMU
	default y
	help
	  Many PCI drivers require access to uncached memory for DMA device
	  communications (such as is done with some Ethernet buffer rings). If
	  a fully featured MMU is available, this can be done through page
	  table settings, but if not, a region has to be set aside and marked
	  with a special DAMPR register.

	  Setting this option causes uClinux to set aside a portion of the
	  available memory for use in this manner. The memory will then be
	  unavailable for normal kernel use.

source "drivers/pci/Kconfig"

source "drivers/pcmcia/Kconfig"

#config MATH_EMULATION
#	bool "Math emulation support (EXPERIMENTAL)"
#	depends on EXPERIMENTAL
#	help
#	  At some point in the future, this will cause floating-point math
#	  instructions to be emulated by the kernel on machines that lack a
#	  floating-point math coprocessor.  Thrill-seekers and chronically
#	  sleep-deprived psychotic hacker types can say Y now, everyone else
#	  should probably wait a while.

menu "Power management options"
source kernel/power/Kconfig
endmenu

endmenu


menu "Executable formats"

source "fs/Kconfig.binfmt"

endmenu

source "net/Kconfig"

source "drivers/Kconfig"

source "fs/Kconfig"

source "arch/frv/Kconfig.debug"

source "security/Kconfig"

source "crypto/Kconfig"

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