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

if ARCH_IXP4XX

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