[deliverable/linux.git] / arch / arm / mach-ixp4xx / Kconfig

if ARCH_IXP4XX

config ARCH_SUPPORTS_BIG_ENDIAN
	bool
	default y

menu "Intel IXP4xx Implementation Options"

comment "IXP4xx Platforms"

config MACH_NSLU2
	bool
	prompt "Linksys NSLU2"
	select PCI
	help
	  Say 'Y' here if you want your kernel to support Linksys's
	  NSLU2 NAS device. For more information on this platform,
	  see http://www.nslu2-linux.org

config MACH_AVILA
	bool "Avila"
	select PCI
	help
	  Say 'Y' here if you want your kernel to support the Gateworks
	  Avila Network Platform. For more information on this platform,
	  see <file:Documentation/arm/IXP4xx>.

config MACH_LOFT
    bool "Loft"
    depends on MACH_AVILA
    help
	  Say 'Y' here if you want your kernel to support the Giant
	  Shoulder Inc Loft board (a minor variation on the standard
	  Gateworks Avila Network Platform).

config ARCH_ADI_COYOTE
	bool "Coyote"
	select PCI
	help
	  Say 'Y' here if you want your kernel to support the ADI 
	  Engineering Coyote Gateway Reference Platform. For more
	  information on this platform, see <file:Documentation/arm/IXP4xx>.

config MACH_GATEWAY7001
	bool "Gateway 7001"
	select PCI
	help
	  Say 'Y' here if you want your kernel to support Gateway's
	  7001 Access Point. For more information on this platform,
	  see http://openwrt.org

config MACH_WG302V2
	bool "Netgear WG302 v2 / WAG302 v2"
	select PCI
	help
	  Say 'Y' here if you want your kernel to support Netgear's
	  WG302 v2 or WAG302 v2 Access Points. For more information
	  on this platform, see http://openwrt.org

config ARCH_IXDP425
	bool "IXDP425"
	help
	  Say 'Y' here if you want your kernel to support Intel's 
	  IXDP425 Development Platform (Also known as Richfield).  
	  For more information on this platform, see <file:Documentation/arm/IXP4xx>.

config MACH_IXDPG425
	bool "IXDPG425"
	help
	  Say 'Y' here if you want your kernel to support Intel's
	  IXDPG425 Development Platform (Also known as Montajade).
	  For more information on this platform, see <file:Documentation/arm/IXP4xx>.

config MACH_IXDP465
	bool "IXDP465"
	help
	  Say 'Y' here if you want your kernel to support Intel's
	  IXDP465 Development Platform (Also known as BMP).
	  For more information on this platform, see <file:Documentation/arm/IXP4xx>.

config MACH_KIXRP435
	bool "KIXRP435"
	help
	  Say 'Y' here if you want your kernel to support Intel's
	  KIXRP435 Reference Platform.
	  For more information on this platform, see <file:Documentation/arm/IXP4xx>.

#
# IXCDP1100 is the exact same HW as IXDP425, but with a different machine 
# number from the bootloader due to marketing monkeys, so we just enable it 
# by default if IXDP425 is enabled.
#
config ARCH_IXCDP1100
	bool 
	depends on ARCH_IXDP425
	default y

config ARCH_PRPMC1100
	bool "PrPMC1100"
	help
	  Say 'Y' here if you want your kernel to support the Motorola
	  PrPCM1100 Processor Mezanine Module. For more information on
	  this platform, see <file:Documentation/arm/IXP4xx>.

config MACH_NAS100D
	bool
	prompt "NAS100D"
	select PCI
	help
	  Say 'Y' here if you want your kernel to support Iomega's
	  NAS 100d device. For more information on this platform,
	  see http://www.nslu2-linux.org/wiki/NAS100d/HomePage

config MACH_DSMG600
	bool
	prompt "D-Link DSM-G600 RevA"
	select PCI
	help
	  Say 'Y' here if you want your kernel to support D-Link's
	  DSM-G600 RevA device. For more information on this platform,
	  see http://www.nslu2-linux.org/wiki/DSMG600/HomePage

config	ARCH_IXDP4XX
	bool
	depends on ARCH_IXDP425 || MACH_IXDP465 || MACH_KIXRP435
	default y

config MACH_FSG
	bool
	prompt "Freecom FSG-3"
	select PCI
	help
	  Say 'Y' here if you want your kernel to support Freecom's
	  FSG-3 device. For more information on this platform,
	  see http://www.nslu2-linux.org/wiki/FSG3/HomePage

#
# Certain registers and IRQs are only enabled if supporting IXP465 CPUs
#
config CPU_IXP46X
	bool
	depends on MACH_IXDP465
	default y

config CPU_IXP43X
	bool
	depends on MACH_KIXRP435
	default y

config MACH_GTWX5715
	bool "Gemtek WX5715 (Linksys WRV54G)"
	depends on ARCH_IXP4XX
	select PCI
	help
		This board is currently inside the Linksys WRV54G Gateways.

		IXP425 - 266mhz
		32mb SDRAM
		8mb Flash
		miniPCI slot 0 does not have a card connector soldered to the board
		miniPCI slot 1 has an ISL3880 802.11g card (Prism54)
		npe0 is connected to a Kendin KS8995M Switch (4 ports)
		npe1 is the "wan" port
		"Console" UART is available on J11 as console
		"High Speed" UART is n/c (as far as I can tell)
		20 Pin ARM/Xscale JTAG interface on J2

comment "IXP4xx Options"

config DMABOUNCE
	bool
	default y
	depends on PCI

config IXP4XX_INDIRECT_PCI
	bool "Use indirect PCI memory access"
	depends on PCI
	help
          IXP4xx provides two methods of accessing PCI memory space:

          1) A direct mapped window from 0x48000000 to 0x4bffffff (64MB).
             To access PCI via this space, we simply ioremap() the BAR
             into the kernel and we can use the standard read[bwl]/write[bwl]
             macros. This is the preferred method due to speed but it
             limits the system to just 64MB of PCI memory. This can be 
             problematic if using video cards and other memory-heavy devices.
          
          2) If > 64MB of memory space is required, the IXP4xx can be 
	     configured to use indirect registers to access PCI This allows 
	     for up to 128MB (0x48000000 to 0x4fffffff) of memory on the bus. 
	     The disadvantage of this is that every PCI access requires 
	     three local register accesses plus a spinlock, but in some 
	     cases the performance hit is acceptable. In addition, you cannot 
	     mmap() PCI devices in this case due to the indirect nature
	     of the PCI window.

	  By default, the direct method is used. Choose this option if you
	  need to use the indirect method instead. If you don't know
	  what you need, leave this option unselected.

config IXP4XX_QMGR
	tristate "IXP4xx Queue Manager support"
	help
	  This driver supports IXP4xx built-in hardware queue manager
	  and is automatically selected by Ethernet and HSS drivers.

config IXP4XX_NPE
	tristate "IXP4xx Network Processor Engine support"
	select HOTPLUG
	select FW_LOADER
	help
	  This driver supports IXP4xx built-in network coprocessors
	  and is automatically selected by Ethernet and HSS drivers.

endmenu

endif
Commit	Line	Data
1da177e4 LT	1	if ARCH_IXP4XX
	2
	3	config ARCH_SUPPORTS_BIG_ENDIAN
	4	bool
	5	default y
	6
	7	menu "Intel IXP4xx Implementation Options"
	8
	9	comment "IXP4xx Platforms"
	10
a7918f39 AZ	11	config MACH_NSLU2
a7918f39 AZ	12	bool
e7fcdb79	13	prompt "Linksys NSLU2"
76bbb002	14	select PCI
a7918f39 AZ	15	help
	16	Say 'Y' here if you want your kernel to support Linksys's
	17	NSLU2 NAS device. For more information on this platform,
	18	see http://www.nslu2-linux.org
	19
0f185971	20	config MACH_AVILA
1da177e4	21	bool "Avila"
76bbb002	22	select PCI
1da177e4 LT	23	help
	24	Say 'Y' here if you want your kernel to support the Gateworks
	25	Avila Network Platform. For more information on this platform,
	26	see <file:Documentation/arm/IXP4xx>.
	27
0f185971 MLJ	28	config MACH_LOFT
	29	bool "Loft"
	30	depends on MACH_AVILA
	31	help
	32	Say 'Y' here if you want your kernel to support the Giant
	33	Shoulder Inc Loft board (a minor variation on the standard
	34	Gateworks Avila Network Platform).
	35
1da177e4 LT	36	config ARCH_ADI_COYOTE
1da177e4 LT	37	bool "Coyote"
76bbb002	38	select PCI
1da177e4 LT	39	help
	40	Say 'Y' here if you want your kernel to support the ADI
	41	Engineering Coyote Gateway Reference Platform. For more
	42	information on this platform, see <file:Documentation/arm/IXP4xx>.
	43
46918bd1 IK	44	config MACH_GATEWAY7001
	45	bool "Gateway 7001"
	46	select PCI
	47	help
	48	Say 'Y' here if you want your kernel to support Gateway's
	49	7001 Access Point. For more information on this platform,
	50	see http://openwrt.org
	51
dcdeeb21 IK	52	config MACH_WG302V2
	53	bool "Netgear WG302 v2 / WAG302 v2"
	54	select PCI
	55	help
	56	Say 'Y' here if you want your kernel to support Netgear's
	57	WG302 v2 or WAG302 v2 Access Points. For more information
	58	on this platform, see http://openwrt.org
	59
1da177e4 LT	60	config ARCH_IXDP425
	61	bool "IXDP425"
	62	help
	63	Say 'Y' here if you want your kernel to support Intel's
	64	IXDP425 Development Platform (Also known as Richfield).
	65	For more information on this platform, see <file:Documentation/arm/IXP4xx>.
	66
	67	config MACH_IXDPG425
	68	bool "IXDPG425"
	69	help
	70	Say 'Y' here if you want your kernel to support Intel's
	71	IXDPG425 Development Platform (Also known as Montajade).
	72	For more information on this platform, see <file:Documentation/arm/IXP4xx>.
	73
	74	config MACH_IXDP465
	75	bool "IXDP465"
	76	help
	77	Say 'Y' here if you want your kernel to support Intel's
	78	IXDP465 Development Platform (Also known as BMP).
7aa52f51	79	For more information on this platform, see <file:Documentation/arm/IXP4xx>.
1da177e4	80
45fba084 RS	81	config MACH_KIXRP435
	82	bool "KIXRP435"
	83	help
	84	Say 'Y' here if you want your kernel to support Intel's
	85	KIXRP435 Reference Platform.
	86	For more information on this platform, see <file:Documentation/arm/IXP4xx>.
1da177e4 LT	87
	88	#
	89	# IXCDP1100 is the exact same HW as IXDP425, but with a different machine
	90	# number from the bootloader due to marketing monkeys, so we just enable it
	91	# by default if IXDP425 is enabled.
	92	#
	93	config ARCH_IXCDP1100
	94	bool
	95	depends on ARCH_IXDP425
	96	default y
	97
	98	config ARCH_PRPMC1100
	99	bool "PrPMC1100"
	100	help
	101	Say 'Y' here if you want your kernel to support the Motorola
	102	PrPCM1100 Processor Mezanine Module. For more information on
	103	this platform, see <file:Documentation/arm/IXP4xx>.
	104
3145d8a6 RW	105	config MACH_NAS100D
	106	bool
	107	prompt "NAS100D"
76bbb002	108	select PCI
3145d8a6 RW	109	help
	110	Say 'Y' here if you want your kernel to support Iomega's
	111	NAS 100d device. For more information on this platform,
	112	see http://www.nslu2-linux.org/wiki/NAS100d/HomePage
	113
28bd3a0d MLJ	114	config MACH_DSMG600
	115	bool
	116	prompt "D-Link DSM-G600 RevA"
	117	select PCI
	118	help
	119	Say 'Y' here if you want your kernel to support D-Link's
	120	DSM-G600 RevA device. For more information on this platform,
	121	see http://www.nslu2-linux.org/wiki/DSMG600/HomePage
	122
1da177e4 LT	123	config ARCH_IXDP4XX
1da177e4 LT	124	bool
45fba084	125	depends on ARCH_IXDP425 \|\| MACH_IXDP465 \|\| MACH_KIXRP435
1da177e4 LT	126	default y
1da177e4 LT	127
7e36e2f5 RW	128	config MACH_FSG
	129	bool
	130	prompt "Freecom FSG-3"
	131	select PCI
	132	help
	133	Say 'Y' here if you want your kernel to support Freecom's
	134	FSG-3 device. For more information on this platform,
	135	see http://www.nslu2-linux.org/wiki/FSG3/HomePage
	136
1da177e4 LT	137	#
	138	# Certain registers and IRQs are only enabled if supporting IXP465 CPUs
	139	#
	140	config CPU_IXP46X
	141	bool
	142	depends on MACH_IXDP465
	143	default y
	144
45fba084 RS	145	config CPU_IXP43X
	146	bool
	147	depends on MACH_KIXRP435
	148	default y
	149
1da177e4 LT	150	config MACH_GTWX5715
	151	bool "Gemtek WX5715 (Linksys WRV54G)"
	152	depends on ARCH_IXP4XX
76bbb002	153	select PCI
1da177e4 LT	154	help
	155	This board is currently inside the Linksys WRV54G Gateways.
	156
	157	IXP425 - 266mhz
	158	32mb SDRAM
	159	8mb Flash
	160	miniPCI slot 0 does not have a card connector soldered to the board
	161	miniPCI slot 1 has an ISL3880 802.11g card (Prism54)
	162	npe0 is connected to a Kendin KS8995M Switch (4 ports)
	163	npe1 is the "wan" port
	164	"Console" UART is available on J11 as console
	165	"High Speed" UART is n/c (as far as I can tell)
	166	20 Pin ARM/Xscale JTAG interface on J2
	167
1da177e4 LT	168	comment "IXP4xx Options"
1da177e4 LT	169
76bbb002 DS	170	config DMABOUNCE
	171	bool
	172	default y
	173	depends on PCI
	174
1da177e4 LT	175	config IXP4XX_INDIRECT_PCI
1da177e4 LT	176	bool "Use indirect PCI memory access"
76bbb002	177	depends on PCI
1da177e4 LT	178	help
	179	IXP4xx provides two methods of accessing PCI memory space:
	180
	181	1) A direct mapped window from 0x48000000 to 0x4bffffff (64MB).
	182	To access PCI via this space, we simply ioremap() the BAR
	183	into the kernel and we can use the standard read[bwl]/write[bwl]
	184	macros. This is the preferred method due to speed but it
	185	limits the system to just 64MB of PCI memory. This can be
3cb2fccc	186	problematic if using video cards and other memory-heavy devices.
1da177e4 LT	187
	188	2) If > 64MB of memory space is required, the IXP4xx can be
	189	configured to use indirect registers to access PCI This allows
	190	for up to 128MB (0x48000000 to 0x4fffffff) of memory on the bus.
c41045a4	191	The disadvantage of this is that every PCI access requires
1da177e4 LT	192	three local register accesses plus a spinlock, but in some
	193	cases the performance hit is acceptable. In addition, you cannot
	194	mmap() PCI devices in this case due to the indirect nature
	195	of the PCI window.
	196
	197	By default, the direct method is used. Choose this option if you
	198	need to use the indirect method instead. If you don't know
	199	what you need, leave this option unselected.
	200
82a96f57 KH	201	config IXP4XX_QMGR
	202	tristate "IXP4xx Queue Manager support"
	203	help
	204	This driver supports IXP4xx built-in hardware queue manager
	205	and is automatically selected by Ethernet and HSS drivers.
	206
	207	config IXP4XX_NPE
	208	tristate "IXP4xx Network Processor Engine support"
	209	select HOTPLUG
	210	select FW_LOADER
	211	help
	212	This driver supports IXP4xx built-in network coprocessors
	213	and is automatically selected by Ethernet and HSS drivers.
	214
1da177e4 LT	215	endmenu
	216
	217	endif