blob: c342dc4e8a45c43097f6c28e1e45ba848e57a7f3 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001if ARCH_IXP4XX
2
Linus Torvalds1da177e2005-04-16 15:20:36 -07003menu "Intel IXP4xx Implementation Options"
4
5comment "IXP4xx Platforms"
6
Alessandro Zummoa7918f32005-11-10 14:05:04 +00007config MACH_NSLU2
8 bool
Alessandro Zummoe7fcdb72006-03-08 23:45:12 +00009 prompt "Linksys NSLU2"
Deepak Saxena76bbb002006-04-30 15:34:29 +010010 select PCI
Alessandro Zummoa7918f32005-11-10 14:05:04 +000011 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
Michael-Luke Jones0f185972006-12-16 23:04:05 +010016config MACH_AVILA
Linus Torvalds1da177e2005-04-16 15:20:36 -070017 bool "Avila"
Deepak Saxena76bbb002006-04-30 15:34:29 +010018 select PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070019 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
Michael-Luke Jones0f185972006-12-16 23:04:05 +010024config 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
Linus Torvalds1da177e2005-04-16 15:20:36 -070032config ARCH_ADI_COYOTE
33 bool "Coyote"
Deepak Saxena76bbb002006-04-30 15:34:29 +010034 select PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070035 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
Imre Kaloz46918bd12007-06-02 15:44:08 +010040config 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
Imre Kalozdcdeeb22007-06-02 15:47:51 +010048config 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
Linus Torvalds1da177e2005-04-16 15:20:36 -070056config 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).
akpm@osdl.org7aa52f52005-04-16 15:23:56 -070075 For more information on this platform, see <file:Documentation/arm/IXP4xx>.
Linus Torvalds1da177e2005-04-16 15:20:36 -070076
Krzysztof Hałasa11c79742009-05-23 23:58:30 +020077config 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
Ruslan V. Sushko45fba082007-04-06 15:00:31 +010083config 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>.
Linus Torvalds1da177e2005-04-16 15:20:36 -070089
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
Rod Whitby3145d8a2006-01-04 17:17:11 +0000107config MACH_NAS100D
108 bool
109 prompt "NAS100D"
Deepak Saxena76bbb002006-04-30 15:34:29 +0100110 select PCI
Rod Whitby3145d8a2006-01-04 17:17:11 +0000111 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
Michael-Luke Jones28bd3a02007-04-28 08:31:40 +0100116config 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
Linus Torvalds1da177e2005-04-16 15:20:36 -0700125config ARCH_IXDP4XX
126 bool
Ruslan V. Sushko45fba082007-04-06 15:00:31 +0100127 depends on ARCH_IXDP425 || MACH_IXDP465 || MACH_KIXRP435
Linus Torvalds1da177e2005-04-16 15:20:36 -0700128 default y
129
Rod Whitby7e36e2f2008-04-01 10:53:23 +0100130config 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
Marc Zyngier4d9be472010-04-10 21:32:38 +0100139config 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
Linus Torvalds1da177e2005-04-16 15:20:36 -0700147#
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
Ruslan V. Sushko45fba082007-04-06 15:00:31 +0100155config CPU_IXP43X
156 bool
157 depends on MACH_KIXRP435
158 default y
159
Linus Torvalds1da177e2005-04-16 15:20:36 -0700160config MACH_GTWX5715
161 bool "Gemtek WX5715 (Linksys WRV54G)"
162 depends on ARCH_IXP4XX
Deepak Saxena76bbb002006-04-30 15:34:29 +0100163 select PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700164 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
Richard Cochran2b8f0112011-09-28 15:16:41 +0200178config 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
Linus Torvalds1da177e2005-04-16 15:20:36 -0700197comment "IXP4xx Options"
198
199config IXP4XX_INDIRECT_PCI
200 bool "Use indirect PCI memory access"
Deepak Saxena76bbb002006-04-30 15:34:29 +0100201 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700202 help
203 IXP4xx provides two methods of accessing PCI memory space:
204
Krzysztof Hałasaed5b9fa2009-11-15 18:02:10 +0100205 1) A direct mapped window from 0x48000000 to 0x4BFFFFFF (64MB).
Linus Torvalds1da177e2005-04-16 15:20:36 -0700206 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
Krzysztof Hałasaed5b9fa2009-11-15 18:02:10 +0100209 limits the system to just 64MB of PCI memory. This can be
Matt LaPlante3cb2fcc2006-11-30 05:22:59 +0100210 problematic if using video cards and other memory-heavy devices.
Krzysztof Hałasaed5b9fa2009-11-15 18:02:10 +0100211
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.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700220
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
Krzysztof Halasa82a96f52008-01-01 21:55:23 +0100225config 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"
Krzysztof Halasa82a96f52008-01-01 21:55:23 +0100233 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
Linus Torvalds1da177e2005-04-16 15:20:36 -0700238endmenu
239
240endif