[net-next-2.6.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
	select HAVE_IDE

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 QUICKLIST
	bool
	default y

config ARCH_HAS_ILOG2_U32
	bool
	default y

config ARCH_HAS_ILOG2_U64
	bool
	default y

config HZ
	int
	default 1000

mainmenu "Fujitsu FR-V Kernel Configuration"

source "init/Kconfig"

source "kernel/Kconfig.freezer"


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/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 PAGE_OFFSET
	hex
	default 0x20000000 if UCPAGE_OFFSET_20000000
	default 0x40000000 if UCPAGE_OFFSET_40000000
	default 0x60000000 if UCPAGE_OFFSET_60000000
	default 0x80000000 if UCPAGE_OFFSET_80000000
	default 0xA0000000 if UCPAGE_OFFSET_A0000000
	default 0xC0000000

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.

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"

config ARCH_SUSPEND_POSSIBLE
	def_bool y
	depends on !SMP

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