[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 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 GENERIC_TIME
	bool
	default y

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