[linux-2.6-block.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 ZONE_DMA
	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 y

config GENERIC_HARDIRQS_NO__DO_IRQ
	bool
	default y

config GENERIC_TIME
	bool
	default y

config TIME_LOW_RES
	bool
	default y

config ARCH_HAS_ILOG2_U32
	bool
	default y

config ARCH_HAS_ILOG2_U64
	bool
	default y

config ARCH_USES_SLAB_PAGE_STRUCT
	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.

config LARGE_ALLOCS
	bool "Allow allocating large blocks (> 1MB) of memory"
	help
	  Allow the slab memory allocator to keep chains for very large memory
	  sizes - up to 32MB. You may need this if your system has a lot of
	  RAM, and you need to able to allocate very large contiguous chunks.
	  If unsure, say N.

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

config FUJITSU_MB93493
	bool "MB93493 Multimedia chip"
	help
	  Select this option if the MB93493 multimedia chip is going to be
	  used.

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