4 config ARCH_SUPPORTS_BIG_ENDIAN
8 menu "Intel IXP4xx Implementation Options"
10 comment "IXP4xx Platforms"
14 prompt "Linksys NSLU2"
17 Say 'Y' here if you want your kernel to support Linksys's
18 NSLU2 NAS device. For more information on this platform,
19 see http://www.nslu2-linux.org
25 Say 'Y' here if you want your kernel to support the Gateworks
26 Avila Network Platform. For more information on this platform,
27 see <file:Documentation/arm/IXP4xx>.
29 config ARCH_ADI_COYOTE
33 Say 'Y' here if you want your kernel to support the ADI
34 Engineering Coyote Gateway Reference Platform. For more
35 information on this platform, see <file:Documentation/arm/IXP4xx>.
40 Say 'Y' here if you want your kernel to support Intel's
41 IXDP425 Development Platform (Also known as Richfield).
42 For more information on this platform, see <file:Documentation/arm/IXP4xx>.
47 Say 'Y' here if you want your kernel to support Intel's
48 IXDPG425 Development Platform (Also known as Montajade).
49 For more information on this platform, see <file:Documentation/arm/IXP4xx>.
54 Say 'Y' here if you want your kernel to support Intel's
55 IXDP465 Development Platform (Also known as BMP).
56 For more information on this platform, see <file:Documentation/arm/IXP4xx>.
60 # IXCDP1100 is the exact same HW as IXDP425, but with a different machine
61 # number from the bootloader due to marketing monkeys, so we just enable it
62 # by default if IXDP425 is enabled.
66 depends on ARCH_IXDP425
76 Say 'Y' here if you want your kernel to support the Motorola
77 PrPCM1100 Processor Mezanine Module. For more information on
78 this platform, see <file:Documentation/arm/IXP4xx>.
81 bool "SnapGear SE4000"
84 depends on ARCH_IXP4XX
86 Support for SnapGear SE4000 VPN Router.
90 depends on ARCH_IXP4XX
92 Support for SnapGear SG560 VPN Router.
98 depends on ARCH_IXP4XX
100 Support for SnapGear SG565 VPN Router.
103 bool "SnapGear SG580"
104 depends on ARCH_IXP4XX
106 Support for SnapGear SG580 VPN Router.
109 bool "SecureComputing SG590"
112 depends on ARCH_IXP4XX
114 Support for Secure Computing SG590 VPN Router.
117 bool "SecureComputing SG640"
118 depends on ARCH_IXP4XX
120 Support for SecureComputing SG640 PCI Router.
122 config MACH_SGARMAUTO
123 bool "SecureComputing 'AutoSelect' ARM Platform"
124 depends on ARCH_IXP4XX
126 Support for SecureComputing generic ARM platform based on IXP4XX.
129 bool "SnapGear SG710"
132 depends on ARCH_IXP4XX
134 Support for SnapGear SG710 VPN Router.
137 bool "SnapGear SG720"
140 depends on ARCH_IXP4XX
142 Support for SnapGear SG720 VPN Router.
145 bool "SecureComputing SG8100"
147 depends on ARCH_IXP4XX
149 Support for Secure Computing SG8100 Internet VPN Router.
156 Say 'Y' here if you want your kernel to support Iomega's
157 NAS 100d device. For more information on this platform,
158 see http://www.nslu2-linux.org/wiki/NAS100d/HomePage
161 # Avila and IXDP share the same source for now. Will change in future
165 depends on ARCH_IXDP425 || ARCH_AVILA || MACH_IXDP465
171 # Certain registers and IRQs are only enabled if supporting IXP465 CPUs
175 depends on MACH_IXDP465 || MACH_SG590 || MACH_SG720
179 bool "Gemtek WX5715 (Linksys WRV54G)"
180 depends on ARCH_IXP4XX
183 This board is currently inside the Linksys WRV54G Gateways.
188 miniPCI slot 0 does not have a card connector soldered to the board
189 miniPCI slot 1 has an ISL3880 802.11g card (Prism54)
190 npe0 is connected to a Kendin KS8995M Switch (4 ports)
191 npe1 is the "wan" port
192 "Console" UART is available on J11 as console
193 "High Speed" UART is n/c (as far as I can tell)
194 20 Pin ARM/Xscale JTAG interface on J2
196 comment "IXP4xx Options"
203 config IXP4XX_INDIRECT_PCI
204 bool "Use indirect PCI memory access"
207 IXP4xx provides two methods of accessing PCI memory space:
209 1) A direct mapped window from 0x48000000 to 0x4bffffff (64MB).
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
213 limits the system to just 64MB of PCI memory. This can be
214 problamatic if using video cards and other memory-heavy devices.
216 2) If > 64MB of memory space is required, the IXP4xx can be
217 configured to use indirect registers to access PCI This allows
218 for up to 128MB (0x48000000 to 0x4fffffff) of memory on the bus.
219 The disadvantage of this is that every PCI access requires
220 three local register accesses plus a spinlock, but in some
221 cases the performance hit is acceptable. In addition, you cannot
222 mmap() PCI devices in this case due to the indirect nature
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.
229 config IXP4XX_CLOCK_FORCE
230 bool "Select the master clock frequency"
231 depends on ARCH_IXP4XX
233 Some hardware platforms using the IXP4XX CPU family use a non-
234 standard clock frequency. Select this option so you can specify
235 the actual clock frequency input to the CPU.
238 int "Select the core clock frequency"
240 depends on IXP4XX_CLOCK_FORCE
242 You can set the actual CPU master clock frequency here, so that
243 you get accurate kernel timing. For example some platforms use a
244 66MHz crystal instead of a 66.666666MHz.