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>.
47 Say 'Y' here if you want your kernel to support Intel's
48 IXDP425 Development Platform (Also known as Richfield).
49 For more information on this platform, see <file:Documentation/arm/IXP4xx>.
54 Say 'Y' here if you want your kernel to support Intel's
55 IXDPG425 Development Platform (Also known as Montajade).
56 For more information on this platform, see <file:Documentation/arm/IXP4xx>.
61 Say 'Y' here if you want your kernel to support Intel's
62 IXDP465 Development Platform (Also known as BMP).
63 For more information on this platform, see <file:Documentation/arm/IXP4xx>.
67 # IXCDP1100 is the exact same HW as IXDP425, but with a different machine
68 # number from the bootloader due to marketing monkeys, so we just enable it
69 # by default if IXDP425 is enabled.
73 depends on ARCH_IXDP425
79 Say 'Y' here if you want your kernel to support the Motorola
80 PrPCM1100 Processor Mezanine Module. For more information on
81 this platform, see <file:Documentation/arm/IXP4xx>.
88 Say 'Y' here if you want your kernel to support Iomega's
89 NAS 100d device. For more information on this platform,
90 see http://www.nslu2-linux.org/wiki/NAS100d/HomePage
93 # Avila and IXDP share the same source for now. Will change in future
97 depends on ARCH_IXDP425 || MACH_IXDP465
101 # Certain registers and IRQs are only enabled if supporting IXP465 CPUs
105 depends on MACH_IXDP465
109 bool "Gemtek WX5715 (Linksys WRV54G)"
110 depends on ARCH_IXP4XX
113 This board is currently inside the Linksys WRV54G Gateways.
118 miniPCI slot 0 does not have a card connector soldered to the board
119 miniPCI slot 1 has an ISL3880 802.11g card (Prism54)
120 npe0 is connected to a Kendin KS8995M Switch (4 ports)
121 npe1 is the "wan" port
122 "Console" UART is available on J11 as console
123 "High Speed" UART is n/c (as far as I can tell)
124 20 Pin ARM/Xscale JTAG interface on J2
126 comment "IXP4xx Options"
133 config IXP4XX_INDIRECT_PCI
134 bool "Use indirect PCI memory access"
137 IXP4xx provides two methods of accessing PCI memory space:
139 1) A direct mapped window from 0x48000000 to 0x4bffffff (64MB).
140 To access PCI via this space, we simply ioremap() the BAR
141 into the kernel and we can use the standard read[bwl]/write[bwl]
142 macros. This is the preferred method due to speed but it
143 limits the system to just 64MB of PCI memory. This can be
144 problematic if using video cards and other memory-heavy devices.
146 2) If > 64MB of memory space is required, the IXP4xx can be
147 configured to use indirect registers to access PCI This allows
148 for up to 128MB (0x48000000 to 0x4fffffff) of memory on the bus.
149 The disadvantage of this is that every PCI access requires
150 three local register accesses plus a spinlock, but in some
151 cases the performance hit is acceptable. In addition, you cannot
152 mmap() PCI devices in this case due to the indirect nature
155 By default, the direct method is used. Choose this option if you
156 need to use the indirect method instead. If you don't know
157 what you need, leave this option unselected.