xref: /openbmc/linux/arch/arm/mach-ixp4xx/Kconfig (revision 77d84ff8) 
1if ARCH_IXP4XX
2
3menu "Intel IXP4xx Implementation Options"
4
5comment "IXP4xx Platforms"
6
7config MACH_NSLU2
8	bool
9	prompt "Linksys NSLU2"
10	select PCI
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
16config MACH_AVILA
17	bool "Avila"
18	select PCI
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
24config 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
32config ARCH_ADI_COYOTE
33	bool "Coyote"
34	select PCI
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
40config 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
48config 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
56config 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
63config 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
70config 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).
75	  For more information on this platform, see <file:Documentation/arm/IXP4xx>.
76
77config 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
83config 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>.
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#
95config ARCH_IXCDP1100
96	bool
97	depends on ARCH_IXDP425
98	default y
99
100config 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
107config MACH_NAS100D
108	bool
109	prompt "NAS100D"
110	select PCI
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
116config 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
125config	ARCH_IXDP4XX
126	bool
127	depends on ARCH_IXDP425 || MACH_IXDP465 || MACH_KIXRP435
128	default y
129
130config 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
139config 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
147#
148# Certain registers and IRQs are only enabled if supporting IXP465 CPUs
149#
150config CPU_IXP46X
151	bool
152	depends on MACH_IXDP465
153	default y
154
155config CPU_IXP43X
156	bool
157	depends on MACH_KIXRP435
158	default y
159
160config MACH_GTWX5715
161	bool "Gemtek WX5715 (Linksys WRV54G)"
162	depends on ARCH_IXP4XX
163	select PCI
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
178config 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
184config 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
191config 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
197comment "IXP4xx Options"
198
199config IXP4XX_INDIRECT_PCI
200	bool "Use indirect PCI memory access"
201	depends on PCI
202	help
203          IXP4xx provides two methods of accessing PCI memory space:
204
205          1) A direct mapped window from 0x48000000 to 0x4BFFFFFF (64MB).
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
209             limits the system to just 64MB of PCI memory. This can be
210             problematic if using video cards and other memory-heavy devices.
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.
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
225config 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
231config IXP4XX_NPE
232	tristate "IXP4xx Network Processor Engine support"
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
238endmenu
239
240endif
241