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 143config MACH_ARCOM_VULCAN 144 bool 145 prompt "Arcom/Eurotech Vulcan" 146 select PCI 147 help 148 Say 'Y' here if you want your kernel to support Arcom's 149 Vulcan board. 150 151# 152# Certain registers and IRQs are only enabled if supporting IXP465 CPUs 153# 154config CPU_IXP46X 155 bool 156 depends on MACH_IXDP465 157 default y 158 159config CPU_IXP43X 160 bool 161 depends on MACH_KIXRP435 162 default y 163 164config MACH_GTWX5715 165 bool "Gemtek WX5715 (Linksys WRV54G)" 166 depends on ARCH_IXP4XX 167 select PCI 168 help 169 This board is currently inside the Linksys WRV54G Gateways. 170 171 IXP425 - 266mhz 172 32mb SDRAM 173 8mb Flash 174 miniPCI slot 0 does not have a card connector soldered to the board 175 miniPCI slot 1 has an ISL3880 802.11g card (Prism54) 176 npe0 is connected to a Kendin KS8995M Switch (4 ports) 177 npe1 is the "wan" port 178 "Console" UART is available on J11 as console 179 "High Speed" UART is n/c (as far as I can tell) 180 20 Pin ARM/Xscale JTAG interface on J2 181 182config MACH_DEVIXP 183 bool "Omicron DEVIXP" 184 help 185 Say 'Y' here if you want your kernel to support the DEVIXP 186 board from OMICRON electronics GmbH. 187 188config MACH_MICCPT 189 bool "Omicron MICCPT" 190 select PCI 191 help 192 Say 'Y' here if you want your kernel to support the MICCPT 193 board from OMICRON electronics GmbH. 194 195config MACH_MIC256 196 bool "Omicron MIC256" 197 help 198 Say 'Y' here if you want your kernel to support the MIC256 199 board from OMICRON electronics GmbH. 200 201comment "IXP4xx Options" 202 203config IXP4XX_INDIRECT_PCI 204 bool "Use indirect PCI memory access" 205 depends on PCI 206 help 207 IXP4xx provides two methods of accessing PCI memory space: 208 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 problematic if using video cards and other memory-heavy devices. 215 216 2) If > 64MB of memory space is required, the IXP4xx can be 217 configured to use indirect registers to access the whole PCI 218 memory space. This currently allows for up to 1 GB (0x10000000 219 to 0x4FFFFFFF) of memory on the bus. The disadvantage of this 220 is that every PCI access requires three local register accesses 221 plus a spinlock, but in some cases the performance hit is 222 acceptable. In addition, you cannot mmap() PCI devices in this 223 case due to the indirect nature of the PCI window. 224 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. 228 229config IXP4XX_QMGR 230 tristate "IXP4xx Queue Manager support" 231 help 232 This driver supports IXP4xx built-in hardware queue manager 233 and is automatically selected by Ethernet and HSS drivers. 234 235config IXP4XX_NPE 236 tristate "IXP4xx Network Processor Engine support" 237 select FW_LOADER 238 help 239 This driver supports IXP4xx built-in network coprocessors 240 and is automatically selected by Ethernet and HSS drivers. 241 242endmenu 243 244endif 245