[mirror_ubuntu-artful-kernel.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_GORAMO_MLR
	bool "GORAMO Multi Link Router"
	help
	  Say 'Y' here if you want your kernel to support GORAMO
	  MultiLink router.

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

config MACH_ARCOM_VULCAN
	bool
	prompt "Arcom/Eurotech Vulcan"
	select PCI
	help
	  Say 'Y' here if you want your kernel to support Arcom's
	  Vulcan board.

#
# 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

config MACH_DEVIXP
	bool "Omicron DEVIXP"
	help
	  Say 'Y' here if you want your kernel to support the DEVIXP
	  board from OMICRON electronics GmbH.

config MACH_MICCPT
	bool "Omicron MICCPT"
	select PCI
	help
	  Say 'Y' here if you want your kernel to support the MICCPT
	  board from OMICRON electronics GmbH.

config MACH_MIC256
	bool "Omicron MIC256"
	help
	  Say 'Y' here if you want your kernel to support the MIC256
	  board from OMICRON electronics GmbH.

comment "IXP4xx Options"

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 the whole PCI
	     memory space. This currently allows for up to 1 GB (0x10000000
	     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 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
11c79740 KH	81	config MACH_GORAMO_MLR
	82	bool "GORAMO Multi Link Router"
	83	help
	84	Say 'Y' here if you want your kernel to support GORAMO
	85	MultiLink router.
	86
45fba084 RS	87	config MACH_KIXRP435
	88	bool "KIXRP435"
	89	help
	90	Say 'Y' here if you want your kernel to support Intel's
	91	KIXRP435 Reference Platform.
	92	For more information on this platform, see <file:Documentation/arm/IXP4xx>.
1da177e4 LT	93
	94	#
	95	# IXCDP1100 is the exact same HW as IXDP425, but with a different machine
	96	# number from the bootloader due to marketing monkeys, so we just enable it
	97	# by default if IXDP425 is enabled.
	98	#
	99	config ARCH_IXCDP1100
	100	bool
	101	depends on ARCH_IXDP425
	102	default y
	103
	104	config ARCH_PRPMC1100
	105	bool "PrPMC1100"
	106	help
	107	Say 'Y' here if you want your kernel to support the Motorola
	108	PrPCM1100 Processor Mezanine Module. For more information on
	109	this platform, see <file:Documentation/arm/IXP4xx>.
	110
3145d8a6 RW	111	config MACH_NAS100D
	112	bool
	113	prompt "NAS100D"
76bbb002	114	select PCI
3145d8a6 RW	115	help
	116	Say 'Y' here if you want your kernel to support Iomega's
	117	NAS 100d device. For more information on this platform,
	118	see http://www.nslu2-linux.org/wiki/NAS100d/HomePage
	119
28bd3a0d MLJ	120	config MACH_DSMG600
	121	bool
	122	prompt "D-Link DSM-G600 RevA"
	123	select PCI
	124	help
	125	Say 'Y' here if you want your kernel to support D-Link's
	126	DSM-G600 RevA device. For more information on this platform,
	127	see http://www.nslu2-linux.org/wiki/DSMG600/HomePage
	128
1da177e4 LT	129	config ARCH_IXDP4XX
1da177e4 LT	130	bool
45fba084	131	depends on ARCH_IXDP425 \|\| MACH_IXDP465 \|\| MACH_KIXRP435
1da177e4 LT	132	default y
1da177e4 LT	133
7e36e2f5 RW	134	config MACH_FSG
	135	bool
	136	prompt "Freecom FSG-3"
	137	select PCI
	138	help
	139	Say 'Y' here if you want your kernel to support Freecom's
	140	FSG-3 device. For more information on this platform,
	141	see http://www.nslu2-linux.org/wiki/FSG3/HomePage
	142
4d9be47f MZ	143	config MACH_ARCOM_VULCAN
	144	bool
	145	prompt "Arcom/Eurotech Vulcan"
	146	select PCI
	147	help
	148	Say 'Y' here if you want your kernel to support Arcom's
	149	Vulcan board.
	150
1da177e4 LT	151	#
	152	# Certain registers and IRQs are only enabled if supporting IXP465 CPUs
	153	#
	154	config CPU_IXP46X
	155	bool
	156	depends on MACH_IXDP465
	157	default y
	158
45fba084 RS	159	config CPU_IXP43X
	160	bool
	161	depends on MACH_KIXRP435
	162	default y
	163
1da177e4 LT	164	config MACH_GTWX5715
	165	bool "Gemtek WX5715 (Linksys WRV54G)"
	166	depends on ARCH_IXP4XX
76bbb002	167	select PCI
1da177e4 LT	168	help
	169	This board is currently inside the Linksys WRV54G Gateways.
	170
	171	IXP425 - 266mhz
	172	32mb SDRAM
	173	8mb Flash
	174	miniPCI slot 0 does not have a card connector soldered to the board
	175	miniPCI slot 1 has an ISL3880 802.11g card (Prism54)
	176	npe0 is connected to a Kendin KS8995M Switch (4 ports)
	177	npe1 is the "wan" port
	178	"Console" UART is available on J11 as console
	179	"High Speed" UART is n/c (as far as I can tell)
	180	20 Pin ARM/Xscale JTAG interface on J2
	181
2b8f0119 RC	182	config MACH_DEVIXP
	183	bool "Omicron DEVIXP"
	184	help
	185	Say 'Y' here if you want your kernel to support the DEVIXP
	186	board from OMICRON electronics GmbH.
	187
	188	config MACH_MICCPT
	189	bool "Omicron MICCPT"
	190	select PCI
	191	help
	192	Say 'Y' here if you want your kernel to support the MICCPT
	193	board from OMICRON electronics GmbH.
	194
	195	config MACH_MIC256
	196	bool "Omicron MIC256"
	197	help
	198	Say 'Y' here if you want your kernel to support the MIC256
	199	board from OMICRON electronics GmbH.
	200
1da177e4 LT	201	comment "IXP4xx Options"
	202
	203	config IXP4XX_INDIRECT_PCI
	204	bool "Use indirect PCI memory access"
76bbb002	205	depends on PCI
1da177e4 LT	206	help
	207	IXP4xx provides two methods of accessing PCI memory space:
	208
ed5b9fa0	209	1) A direct mapped window from 0x48000000 to 0x4BFFFFFF (64MB).
1da177e4 LT	210	To access PCI via this space, we simply ioremap() the BAR
	211	into the kernel and we can use the standard read[bwl]/write[bwl]
	212	macros. This is the preferred method due to speed but it
ed5b9fa0	213	limits the system to just 64MB of PCI memory. This can be
3cb2fccc	214	problematic if using video cards and other memory-heavy devices.
ed5b9fa0 KH	215
	216	2) If > 64MB of memory space is required, the IXP4xx can be
	217	configured to use indirect registers to access the whole PCI
	218	memory space. This currently allows for up to 1 GB (0x10000000
	219	to 0x4FFFFFFF) of memory on the bus. The disadvantage of this
	220	is that every PCI access requires three local register accesses
	221	plus a spinlock, but in some cases the performance hit is
	222	acceptable. In addition, you cannot mmap() PCI devices in this
	223	case due to the indirect nature of the PCI window.
1da177e4 LT	224
	225	By default, the direct method is used. Choose this option if you
	226	need to use the indirect method instead. If you don't know
	227	what you need, leave this option unselected.
	228
82a96f57 KH	229	config IXP4XX_QMGR
	230	tristate "IXP4xx Queue Manager support"
	231	help
	232	This driver supports IXP4xx built-in hardware queue manager
	233	and is automatically selected by Ethernet and HSS drivers.
	234
	235	config IXP4XX_NPE
	236	tristate "IXP4xx Network Processor Engine support"
82a96f57 KH	237	select FW_LOADER
	238	help
	239	This driver supports IXP4xx built-in network coprocessors
	240	and is automatically selected by Ethernet and HSS drivers.
	241
1da177e4 LT	242	endmenu
	243
	244	endif