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_KIXRP435 82 bool "KIXRP435" 83 help 84 Say 'Y' here if you want your kernel to support Intel's 85 KIXRP435 Reference Platform. 86 For more information on this platform, see <file:Documentation/arm/IXP4xx>. 87 88# 89# IXCDP1100 is the exact same HW as IXDP425, but with a different machine 90# number from the bootloader due to marketing monkeys, so we just enable it 91# by default if IXDP425 is enabled. 92# 93config ARCH_IXCDP1100 94 bool 95 depends on ARCH_IXDP425 96 default y 97 98config ARCH_PRPMC1100 99 bool "PrPMC1100" 100 help 101 Say 'Y' here if you want your kernel to support the Motorola 102 PrPCM1100 Processor Mezanine Module. For more information on 103 this platform, see <file:Documentation/arm/IXP4xx>. 104 105config MACH_NAS100D 106 bool 107 prompt "NAS100D" 108 select PCI 109 help 110 Say 'Y' here if you want your kernel to support Iomega's 111 NAS 100d device. For more information on this platform, 112 see http://www.nslu2-linux.org/wiki/NAS100d/HomePage 113 114config MACH_DSMG600 115 bool 116 prompt "D-Link DSM-G600 RevA" 117 select PCI 118 help 119 Say 'Y' here if you want your kernel to support D-Link's 120 DSM-G600 RevA device. For more information on this platform, 121 see http://www.nslu2-linux.org/wiki/DSMG600/HomePage 122 123config ARCH_IXDP4XX 124 bool 125 depends on ARCH_IXDP425 || MACH_IXDP465 || MACH_KIXRP435 126 default y 127 128config MACH_FSG 129 bool 130 prompt "Freecom FSG-3" 131 select PCI 132 help 133 Say 'Y' here if you want your kernel to support Freecom's 134 FSG-3 device. For more information on this platform, 135 see http://www.nslu2-linux.org/wiki/FSG3/HomePage 136 137# 138# Certain registers and IRQs are only enabled if supporting IXP465 CPUs 139# 140config CPU_IXP46X 141 bool 142 depends on MACH_IXDP465 143 default y 144 145config CPU_IXP43X 146 bool 147 depends on MACH_KIXRP435 148 default y 149 150config MACH_GTWX5715 151 bool "Gemtek WX5715 (Linksys WRV54G)" 152 depends on ARCH_IXP4XX 153 select PCI 154 help 155 This board is currently inside the Linksys WRV54G Gateways. 156 157 IXP425 - 266mhz 158 32mb SDRAM 159 8mb Flash 160 miniPCI slot 0 does not have a card connector soldered to the board 161 miniPCI slot 1 has an ISL3880 802.11g card (Prism54) 162 npe0 is connected to a Kendin KS8995M Switch (4 ports) 163 npe1 is the "wan" port 164 "Console" UART is available on J11 as console 165 "High Speed" UART is n/c (as far as I can tell) 166 20 Pin ARM/Xscale JTAG interface on J2 167 168comment "IXP4xx Options" 169 170config IXP4XX_INDIRECT_PCI 171 bool "Use indirect PCI memory access" 172 depends on PCI 173 help 174 IXP4xx provides two methods of accessing PCI memory space: 175 176 1) A direct mapped window from 0x48000000 to 0x4bffffff (64MB). 177 To access PCI via this space, we simply ioremap() the BAR 178 into the kernel and we can use the standard read[bwl]/write[bwl] 179 macros. This is the preferred method due to speed but it 180 limits the system to just 64MB of PCI memory. This can be 181 problematic if using video cards and other memory-heavy devices. 182 183 2) If > 64MB of memory space is required, the IXP4xx can be 184 configured to use indirect registers to access PCI This allows 185 for up to 128MB (0x48000000 to 0x4fffffff) of memory on the bus. 186 The disadvantage of this is that every PCI access requires 187 three local register accesses plus a spinlock, but in some 188 cases the performance hit is acceptable. In addition, you cannot 189 mmap() PCI devices in this case due to the indirect nature 190 of the PCI window. 191 192 By default, the direct method is used. Choose this option if you 193 need to use the indirect method instead. If you don't know 194 what you need, leave this option unselected. 195 196config IXP4XX_QMGR 197 tristate "IXP4xx Queue Manager support" 198 help 199 This driver supports IXP4xx built-in hardware queue manager 200 and is automatically selected by Ethernet and HSS drivers. 201 202config IXP4XX_NPE 203 tristate "IXP4xx Network Processor Engine support" 204 select HOTPLUG 205 select FW_LOADER 206 help 207 This driver supports IXP4xx built-in network coprocessors 208 and is automatically selected by Ethernet and HSS drivers. 209 210endmenu 211 212endif 213