xref: /openbmc/linux/arch/arm/mach-ixp4xx/Kconfig (revision ed5b9fa0) 
1if ARCH_IXP4XX
2
3config ARCH_SUPPORTS_BIG_ENDIAN
4	bool
5	default y
6
7menu "Intel IXP4xx Implementation Options"
8
9comment "IXP4xx Platforms"
10
11config MACH_NSLU2
12	bool
13	prompt "Linksys NSLU2"
14	select PCI
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
20config MACH_AVILA
21	bool "Avila"
22	select PCI
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
28config 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
36config ARCH_ADI_COYOTE
37	bool "Coyote"
38	select PCI
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
44config 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
52config 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
60config 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
67config 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
74config 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).
79	  For more information on this platform, see <file:Documentation/arm/IXP4xx>.
80
81config 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
87config 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>.
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#
99config ARCH_IXCDP1100
100	bool
101	depends on ARCH_IXDP425
102	default y
103
104config 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
111config MACH_NAS100D
112	bool
113	prompt "NAS100D"
114	select PCI
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
120config 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
129config	ARCH_IXDP4XX
130	bool
131	depends on ARCH_IXDP425 || MACH_IXDP465 || MACH_KIXRP435
132	default y
133
134config 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
143#
144# Certain registers and IRQs are only enabled if supporting IXP465 CPUs
145#
146config CPU_IXP46X
147	bool
148	depends on MACH_IXDP465
149	default y
150
151config CPU_IXP43X
152	bool
153	depends on MACH_KIXRP435
154	default y
155
156config MACH_GTWX5715
157	bool "Gemtek WX5715 (Linksys WRV54G)"
158	depends on ARCH_IXP4XX
159	select PCI
160	help
161		This board is currently inside the Linksys WRV54G Gateways.
162
163		IXP425 - 266mhz
164		32mb SDRAM
165		8mb Flash
166		miniPCI slot 0 does not have a card connector soldered to the board
167		miniPCI slot 1 has an ISL3880 802.11g card (Prism54)
168		npe0 is connected to a Kendin KS8995M Switch (4 ports)
169		npe1 is the "wan" port
170		"Console" UART is available on J11 as console
171		"High Speed" UART is n/c (as far as I can tell)
172		20 Pin ARM/Xscale JTAG interface on J2
173
174comment "IXP4xx Options"
175
176config IXP4XX_INDIRECT_PCI
177	bool "Use indirect PCI memory access"
178	depends on PCI
179	help
180          IXP4xx provides two methods of accessing PCI memory space:
181
182          1) A direct mapped window from 0x48000000 to 0x4BFFFFFF (64MB).
183             To access PCI via this space, we simply ioremap() the BAR
184             into the kernel and we can use the standard read[bwl]/write[bwl]
185             macros. This is the preferred method due to speed but it
186             limits the system to just 64MB of PCI memory. This can be
187             problematic if using video cards and other memory-heavy devices.
188
189	  2) If > 64MB of memory space is required, the IXP4xx can be
190	     configured to use indirect registers to access the whole PCI
191	     memory space. This currently allows for up to 1 GB (0x10000000
192	     to 0x4FFFFFFF) of memory on the bus. The disadvantage of this
193	     is that every PCI access requires three local register accesses
194	     plus a spinlock, but in some cases the performance hit is
195	     acceptable. In addition, you cannot mmap() PCI devices in this
196	     case due to the indirect nature of the PCI window.
197
198	  By default, the direct method is used. Choose this option if you
199	  need to use the indirect method instead. If you don't know
200	  what you need, leave this option unselected.
201
202config IXP4XX_QMGR
203	tristate "IXP4xx Queue Manager support"
204	help
205	  This driver supports IXP4xx built-in hardware queue manager
206	  and is automatically selected by Ethernet and HSS drivers.
207
208config IXP4XX_NPE
209	tristate "IXP4xx Network Processor Engine support"
210	select HOTPLUG
211	select FW_LOADER
212	help
213	  This driver supports IXP4xx built-in network coprocessors
214	  and is automatically selected by Ethernet and HSS drivers.
215
216endmenu
217
218endif
219