[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

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

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