3 config ARCH_SUPPORTS_BIG_ENDIAN
7 menu "Intel IXP4xx Implementation Options"
9 comment "IXP4xx Platforms"
13 prompt "Linksys NSLU2"
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
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>.
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).
36 config ARCH_ADI_COYOTE
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>.
44 config MACH_GATEWAY7001
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
55 Say 'Y' here if you want your kernel to support Intel's
56 IXDP425 Development Platform (Also known as Richfield).
57 For more information on this platform, see <file:Documentation/arm/IXP4xx>.
62 Say 'Y' here if you want your kernel to support Intel's
63 IXDPG425 Development Platform (Also known as Montajade).
64 For more information on this platform, see <file:Documentation/arm/IXP4xx>.
69 Say 'Y' here if you want your kernel to support Intel's
70 IXDP465 Development Platform (Also known as BMP).
71 For more information on this platform, see <file:Documentation/arm/IXP4xx>.
76 Say 'Y' here if you want your kernel to support Intel's
77 KIXRP435 Reference Platform.
78 For more information on this platform, see <file:Documentation/arm/IXP4xx>.
81 # IXCDP1100 is the exact same HW as IXDP425, but with a different machine
82 # number from the bootloader due to marketing monkeys, so we just enable it
83 # by default if IXDP425 is enabled.
87 depends on ARCH_IXDP425
93 Say 'Y' here if you want your kernel to support the Motorola
94 PrPCM1100 Processor Mezanine Module. For more information on
95 this platform, see <file:Documentation/arm/IXP4xx>.
102 Say 'Y' here if you want your kernel to support Iomega's
103 NAS 100d device. For more information on this platform,
104 see http://www.nslu2-linux.org/wiki/NAS100d/HomePage
108 prompt "D-Link DSM-G600 RevA"
111 Say 'Y' here if you want your kernel to support D-Link's
112 DSM-G600 RevA device. For more information on this platform,
113 see http://www.nslu2-linux.org/wiki/DSMG600/HomePage
117 depends on ARCH_IXDP425 || MACH_IXDP465 || MACH_KIXRP435
121 # Certain registers and IRQs are only enabled if supporting IXP465 CPUs
125 depends on MACH_IXDP465
130 depends on MACH_KIXRP435
134 bool "Gemtek WX5715 (Linksys WRV54G)"
135 depends on ARCH_IXP4XX
138 This board is currently inside the Linksys WRV54G Gateways.
143 miniPCI slot 0 does not have a card connector soldered to the board
144 miniPCI slot 1 has an ISL3880 802.11g card (Prism54)
145 npe0 is connected to a Kendin KS8995M Switch (4 ports)
146 npe1 is the "wan" port
147 "Console" UART is available on J11 as console
148 "High Speed" UART is n/c (as far as I can tell)
149 20 Pin ARM/Xscale JTAG interface on J2
151 comment "IXP4xx Options"
158 config IXP4XX_INDIRECT_PCI
159 bool "Use indirect PCI memory access"
162 IXP4xx provides two methods of accessing PCI memory space:
164 1) A direct mapped window from 0x48000000 to 0x4bffffff (64MB).
165 To access PCI via this space, we simply ioremap() the BAR
166 into the kernel and we can use the standard read[bwl]/write[bwl]
167 macros. This is the preferred method due to speed but it
168 limits the system to just 64MB of PCI memory. This can be
169 problematic if using video cards and other memory-heavy devices.
171 2) If > 64MB of memory space is required, the IXP4xx can be
172 configured to use indirect registers to access PCI This allows
173 for up to 128MB (0x48000000 to 0x4fffffff) of memory on the bus.
174 The disadvantage of this is that every PCI access requires
175 three local register accesses plus a spinlock, but in some
176 cases the performance hit is acceptable. In addition, you cannot
177 mmap() PCI devices in this case due to the indirect nature
180 By default, the direct method is used. Choose this option if you
181 need to use the indirect method instead. If you don't know
182 what you need, leave this option unselected.