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_AVILA 21 bool "Avila" 22 depends on IXP4XX_PCI_LEGACY 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.rst>. 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 depends on IXP4XX_PCI_LEGACY 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.rst>. 43 44config MACH_GATEWAY7001 45 bool "Gateway 7001" 46 depends on IXP4XX_PCI_LEGACY 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 depends on IXP4XX_PCI_LEGACY 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 depends on IXP4XX_PCI_LEGACY 63 help 64 Say 'Y' here if you want your kernel to support Intel's 65 IXDP425 Development Platform (Also known as Richfield). 66 For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>. 67 68config MACH_IXDPG425 69 bool "IXDPG425" 70 depends on IXP4XX_PCI_LEGACY 71 help 72 Say 'Y' here if you want your kernel to support Intel's 73 IXDPG425 Development Platform (Also known as Montajade). 74 For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>. 75 76config MACH_IXDP465 77 bool "IXDP465" 78 help 79 Say 'Y' here if you want your kernel to support Intel's 80 IXDP465 Development Platform (Also known as BMP). 81 For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>. 82 83config MACH_GORAMO_MLR 84 bool "GORAMO Multi Link Router" 85 help 86 Say 'Y' here if you want your kernel to support GORAMO 87 MultiLink router. 88 89config MACH_KIXRP435 90 bool "KIXRP435" 91 help 92 Say 'Y' here if you want your kernel to support Intel's 93 KIXRP435 Reference Platform. 94 For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>. 95 96# 97# IXCDP1100 is the exact same HW as IXDP425, but with a different machine 98# number from the bootloader due to marketing monkeys, so we just enable it 99# by default if IXDP425 is enabled. 100# 101config ARCH_IXCDP1100 102 bool 103 depends on ARCH_IXDP425 104 default y 105 106config ARCH_PRPMC1100 107 bool "PrPMC1100" 108 help 109 Say 'Y' here if you want your kernel to support the Motorola 110 PrPCM1100 Processor Mezanine Module. For more information on 111 this platform, see <file:Documentation/arm/ixp4xx.rst>. 112 113config ARCH_IXDP4XX 114 bool 115 depends on ARCH_IXDP425 || MACH_IXDP465 || MACH_KIXRP435 116 default y 117 118config MACH_FSG 119 bool 120 prompt "Freecom FSG-3" 121 depends on IXP4XX_PCI_LEGACY 122 help 123 Say 'Y' here if you want your kernel to support Freecom's 124 FSG-3 device. For more information on this platform, 125 see http://www.nslu2-linux.org/wiki/FSG3/HomePage 126 127config MACH_ARCOM_VULCAN 128 bool 129 prompt "Arcom/Eurotech Vulcan" 130 depends on IXP4XX_PCI_LEGACY 131 help 132 Say 'Y' here if you want your kernel to support Arcom's 133 Vulcan board. 134 135# 136# Certain registers and IRQs are only enabled if supporting IXP465 CPUs 137# 138config CPU_IXP46X 139 bool 140 depends on MACH_IXDP465 141 default y 142 143config CPU_IXP43X 144 bool 145 depends on MACH_KIXRP435 146 default y 147 148config MACH_GTWX5715 149 bool "Gemtek WX5715 (Linksys WRV54G)" 150 depends on ARCH_IXP4XX 151 depends on IXP4XX_PCI_LEGACY 152 help 153 This board is currently inside the Linksys WRV54G Gateways. 154 155 IXP425 - 266mhz 156 32mb SDRAM 157 8mb Flash 158 miniPCI slot 0 does not have a card connector soldered to the board 159 miniPCI slot 1 has an ISL3880 802.11g card (Prism54) 160 npe0 is connected to a Kendin KS8995M Switch (4 ports) 161 npe1 is the "wan" port 162 "Console" UART is available on J11 as console 163 "High Speed" UART is n/c (as far as I can tell) 164 20 Pin ARM/Xscale JTAG interface on J2 165 166comment "IXP4xx Options" 167 168config IXP4XX_PCI_LEGACY 169 bool "IXP4xx legacy PCI driver support" 170 depends on PCI 171 help 172 Selects legacy PCI driver. 173 Not recommended for new development. 174 175config IXP4XX_INDIRECT_PCI 176 bool "Use indirect PCI memory access" 177 depends on IXP4XX_PCI_LEGACY 178 help 179 IXP4xx provides two methods of accessing PCI memory space: 180 181 1) A direct mapped window from 0x48000000 to 0x4BFFFFFF (64MB). 182 To access PCI via this space, we simply ioremap() the BAR 183 into the kernel and we can use the standard read[bwl]/write[bwl] 184 macros. This is the preferred method due to speed but it 185 limits the system to just 64MB of PCI memory. This can be 186 problematic if using video cards and other memory-heavy devices. 187 188 2) If > 64MB of memory space is required, the IXP4xx can be 189 configured to use indirect registers to access the whole PCI 190 memory space. This currently allows for up to 1 GB (0x10000000 191 to 0x4FFFFFFF) of memory on the bus. The disadvantage of this 192 is that every PCI access requires three local register accesses 193 plus a spinlock, but in some cases the performance hit is 194 acceptable. In addition, you cannot mmap() PCI devices in this 195 case due to the indirect nature of the PCI window. 196 197 By default, the direct method is used. Choose this option if you 198 need to use the indirect method instead. If you don't know 199 what you need, leave this option unselected. 200 201endmenu 202 203endif 204