1# SPDX-License-Identifier: GPL-2.0-only 2if ARCH_IXP4XX 3 4menu "Intel IXP4xx Implementation Options" 5 6comment "IXP4xx Platforms" 7 8config MACH_IXP4XX_OF 9 bool 10 prompt "Device Tree IXP4xx boards" 11 default y 12 select ARM_APPENDED_DTB # Old Redboot bootloaders deployed 13 select I2C 14 select I2C_IOP3XX 15 select PCI 16 select USE_OF 17 help 18 Say 'Y' here to support Device Tree-based IXP4xx platforms. 19 20config MACH_NSLU2 21 bool 22 prompt "Linksys NSLU2" 23 depends on IXP4XX_PCI_LEGACY 24 help 25 Say 'Y' here if you want your kernel to support Linksys's 26 NSLU2 NAS device. For more information on this platform, 27 see http://www.nslu2-linux.org 28 29config MACH_AVILA 30 bool "Avila" 31 depends on IXP4XX_PCI_LEGACY 32 help 33 Say 'Y' here if you want your kernel to support the Gateworks 34 Avila Network Platform. For more information on this platform, 35 see <file:Documentation/arm/ixp4xx.rst>. 36 37config MACH_LOFT 38 bool "Loft" 39 depends on MACH_AVILA 40 help 41 Say 'Y' here if you want your kernel to support the Giant 42 Shoulder Inc Loft board (a minor variation on the standard 43 Gateworks Avila Network Platform). 44 45config ARCH_ADI_COYOTE 46 bool "Coyote" 47 depends on IXP4XX_PCI_LEGACY 48 help 49 Say 'Y' here if you want your kernel to support the ADI 50 Engineering Coyote Gateway Reference Platform. For more 51 information on this platform, see <file:Documentation/arm/ixp4xx.rst>. 52 53config MACH_GATEWAY7001 54 bool "Gateway 7001" 55 depends on IXP4XX_PCI_LEGACY 56 help 57 Say 'Y' here if you want your kernel to support Gateway's 58 7001 Access Point. For more information on this platform, 59 see http://openwrt.org 60 61config MACH_WG302V2 62 bool "Netgear WG302 v2 / WAG302 v2" 63 depends on IXP4XX_PCI_LEGACY 64 help 65 Say 'Y' here if you want your kernel to support Netgear's 66 WG302 v2 or WAG302 v2 Access Points. For more information 67 on this platform, see http://openwrt.org 68 69config ARCH_IXDP425 70 bool "IXDP425" 71 depends on IXP4XX_PCI_LEGACY 72 help 73 Say 'Y' here if you want your kernel to support Intel's 74 IXDP425 Development Platform (Also known as Richfield). 75 For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>. 76 77config MACH_IXDPG425 78 bool "IXDPG425" 79 depends on IXP4XX_PCI_LEGACY 80 help 81 Say 'Y' here if you want your kernel to support Intel's 82 IXDPG425 Development Platform (Also known as Montajade). 83 For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>. 84 85config MACH_IXDP465 86 bool "IXDP465" 87 help 88 Say 'Y' here if you want your kernel to support Intel's 89 IXDP465 Development Platform (Also known as BMP). 90 For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>. 91 92config MACH_GORAMO_MLR 93 bool "GORAMO Multi Link Router" 94 help 95 Say 'Y' here if you want your kernel to support GORAMO 96 MultiLink router. 97 98config MACH_KIXRP435 99 bool "KIXRP435" 100 help 101 Say 'Y' here if you want your kernel to support Intel's 102 KIXRP435 Reference Platform. 103 For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>. 104 105# 106# IXCDP1100 is the exact same HW as IXDP425, but with a different machine 107# number from the bootloader due to marketing monkeys, so we just enable it 108# by default if IXDP425 is enabled. 109# 110config ARCH_IXCDP1100 111 bool 112 depends on ARCH_IXDP425 113 default y 114 115config ARCH_PRPMC1100 116 bool "PrPMC1100" 117 help 118 Say 'Y' here if you want your kernel to support the Motorola 119 PrPCM1100 Processor Mezanine Module. For more information on 120 this platform, see <file:Documentation/arm/ixp4xx.rst>. 121 122config MACH_NAS100D 123 bool 124 prompt "NAS100D" 125 depends on IXP4XX_PCI_LEGACY 126 help 127 Say 'Y' here if you want your kernel to support Iomega's 128 NAS 100d device. For more information on this platform, 129 see http://www.nslu2-linux.org/wiki/NAS100d/HomePage 130 131config MACH_DSMG600 132 bool 133 prompt "D-Link DSM-G600 RevA" 134 depends on IXP4XX_PCI_LEGACY 135 help 136 Say 'Y' here if you want your kernel to support D-Link's 137 DSM-G600 RevA device. For more information on this platform, 138 see http://www.nslu2-linux.org/wiki/DSMG600/HomePage 139 140config ARCH_IXDP4XX 141 bool 142 depends on ARCH_IXDP425 || MACH_IXDP465 || MACH_KIXRP435 143 default y 144 145config MACH_FSG 146 bool 147 prompt "Freecom FSG-3" 148 depends on IXP4XX_PCI_LEGACY 149 help 150 Say 'Y' here if you want your kernel to support Freecom's 151 FSG-3 device. For more information on this platform, 152 see http://www.nslu2-linux.org/wiki/FSG3/HomePage 153 154config MACH_ARCOM_VULCAN 155 bool 156 prompt "Arcom/Eurotech Vulcan" 157 depends on IXP4XX_PCI_LEGACY 158 help 159 Say 'Y' here if you want your kernel to support Arcom's 160 Vulcan board. 161 162# 163# Certain registers and IRQs are only enabled if supporting IXP465 CPUs 164# 165config CPU_IXP46X 166 bool 167 depends on MACH_IXDP465 168 default y 169 170config CPU_IXP43X 171 bool 172 depends on MACH_KIXRP435 173 default y 174 175config MACH_GTWX5715 176 bool "Gemtek WX5715 (Linksys WRV54G)" 177 depends on ARCH_IXP4XX 178 depends on IXP4XX_PCI_LEGACY 179 help 180 This board is currently inside the Linksys WRV54G Gateways. 181 182 IXP425 - 266mhz 183 32mb SDRAM 184 8mb Flash 185 miniPCI slot 0 does not have a card connector soldered to the board 186 miniPCI slot 1 has an ISL3880 802.11g card (Prism54) 187 npe0 is connected to a Kendin KS8995M Switch (4 ports) 188 npe1 is the "wan" port 189 "Console" UART is available on J11 as console 190 "High Speed" UART is n/c (as far as I can tell) 191 20 Pin ARM/Xscale JTAG interface on J2 192 193config MACH_DEVIXP 194 bool "Omicron DEVIXP" 195 help 196 Say 'Y' here if you want your kernel to support the DEVIXP 197 board from OMICRON electronics GmbH. 198 199config MACH_MICCPT 200 bool "Omicron MICCPT" 201 depends on IXP4XX_PCI_LEGACY 202 help 203 Say 'Y' here if you want your kernel to support the MICCPT 204 board from OMICRON electronics GmbH. 205 206config MACH_MIC256 207 bool "Omicron MIC256" 208 help 209 Say 'Y' here if you want your kernel to support the MIC256 210 board from OMICRON electronics GmbH. 211 212comment "IXP4xx Options" 213 214config IXP4XX_PCI_LEGACY 215 bool "IXP4xx legacy PCI driver support" 216 depends on PCI 217 help 218 Selects legacy PCI driver. 219 Not recommended for new development. 220 221config IXP4XX_INDIRECT_PCI 222 bool "Use indirect PCI memory access" 223 depends on IXP4XX_PCI_LEGACY 224 help 225 IXP4xx provides two methods of accessing PCI memory space: 226 227 1) A direct mapped window from 0x48000000 to 0x4BFFFFFF (64MB). 228 To access PCI via this space, we simply ioremap() the BAR 229 into the kernel and we can use the standard read[bwl]/write[bwl] 230 macros. This is the preferred method due to speed but it 231 limits the system to just 64MB of PCI memory. This can be 232 problematic if using video cards and other memory-heavy devices. 233 234 2) If > 64MB of memory space is required, the IXP4xx can be 235 configured to use indirect registers to access the whole PCI 236 memory space. This currently allows for up to 1 GB (0x10000000 237 to 0x4FFFFFFF) of memory on the bus. The disadvantage of this 238 is that every PCI access requires three local register accesses 239 plus a spinlock, but in some cases the performance hit is 240 acceptable. In addition, you cannot mmap() PCI devices in this 241 case due to the indirect nature of the PCI window. 242 243 By default, the direct method is used. Choose this option if you 244 need to use the indirect method instead. If you don't know 245 what you need, leave this option unselected. 246 247endmenu 248 249endif 250