[net-next-2.6.git] / arch / frv / Kconfig

config FRV
	bool
	default y
	select HAVE_IDE
	select HAVE_ARCH_TRACEHOOK
	select HAVE_PERF_EVENTS

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

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