blob: 9715ef506c24b363f09164ac2cde59c4acba9e92 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001if ARCH_IXP4XX
2
3config ARCH_SUPPORTS_BIG_ENDIAN
4 bool
5 default y
6
7menu "Intel IXP4xx Implementation Options"
8
9comment "IXP4xx Platforms"
10
Alessandro Zummoa7918f32005-11-10 14:05:04 +000011config MACH_NSLU2
12 bool
Alessandro Zummoe7fcdb72006-03-08 23:45:12 +000013 prompt "Linksys NSLU2"
Deepak Saxena76bbb002006-04-30 15:34:29 +010014 select PCI
Alessandro Zummoa7918f32005-11-10 14:05:04 +000015 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
Michael-Luke Jones0f185972006-12-16 23:04:05 +010020config MACH_AVILA
Linus Torvalds1da177e2005-04-16 15:20:36 -070021 bool "Avila"
Deepak Saxena76bbb002006-04-30 15:34:29 +010022 select PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070023 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
Michael-Luke Jones0f185972006-12-16 23:04:05 +010028config 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
Linus Torvalds1da177e2005-04-16 15:20:36 -070036config ARCH_ADI_COYOTE
37 bool "Coyote"
Deepak Saxena76bbb002006-04-30 15:34:29 +010038 select PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070039 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 ARCH_IXDP425
45 bool "IXDP425"
46 help
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>.
50
51config MACH_IXDPG425
52 bool "IXDPG425"
53 help
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>.
57
58config MACH_IXDP465
59 bool "IXDP465"
60 help
61 Say 'Y' here if you want your kernel to support Intel's
62 IXDP465 Development Platform (Also known as BMP).
akpm@osdl.org7aa52f52005-04-16 15:23:56 -070063 For more information on this platform, see <file:Documentation/arm/IXP4xx>.
Linus Torvalds1da177e2005-04-16 15:20:36 -070064
Ruslan V. Sushko45fba082007-04-06 15:00:31 +010065config MACH_KIXRP435
66 bool "KIXRP435"
67 help
68 Say 'Y' here if you want your kernel to support Intel's
69 KIXRP435 Reference Platform.
70 For more information on this platform, see <file:Documentation/arm/IXP4xx>.
Linus Torvalds1da177e2005-04-16 15:20:36 -070071
72#
73# IXCDP1100 is the exact same HW as IXDP425, but with a different machine
74# number from the bootloader due to marketing monkeys, so we just enable it
75# by default if IXDP425 is enabled.
76#
77config ARCH_IXCDP1100
78 bool
79 depends on ARCH_IXDP425
80 default y
81
82config ARCH_PRPMC1100
83 bool "PrPMC1100"
84 help
85 Say 'Y' here if you want your kernel to support the Motorola
86 PrPCM1100 Processor Mezanine Module. For more information on
87 this platform, see <file:Documentation/arm/IXP4xx>.
88
Rod Whitby3145d8a2006-01-04 17:17:11 +000089config MACH_NAS100D
90 bool
91 prompt "NAS100D"
Deepak Saxena76bbb002006-04-30 15:34:29 +010092 select PCI
Rod Whitby3145d8a2006-01-04 17:17:11 +000093 help
94 Say 'Y' here if you want your kernel to support Iomega's
95 NAS 100d device. For more information on this platform,
96 see http://www.nslu2-linux.org/wiki/NAS100d/HomePage
97
Michael-Luke Jones28bd3a02007-04-28 08:31:40 +010098config MACH_DSMG600
99 bool
100 prompt "D-Link DSM-G600 RevA"
101 select PCI
102 help
103 Say 'Y' here if you want your kernel to support D-Link's
104 DSM-G600 RevA device. For more information on this platform,
105 see http://www.nslu2-linux.org/wiki/DSMG600/HomePage
106
Linus Torvalds1da177e2005-04-16 15:20:36 -0700107#
108# Avila and IXDP share the same source for now. Will change in future
109#
110config ARCH_IXDP4XX
111 bool
Ruslan V. Sushko45fba082007-04-06 15:00:31 +0100112 depends on ARCH_IXDP425 || MACH_IXDP465 || MACH_KIXRP435
Linus Torvalds1da177e2005-04-16 15:20:36 -0700113 default y
114
115#
116# Certain registers and IRQs are only enabled if supporting IXP465 CPUs
117#
118config CPU_IXP46X
119 bool
120 depends on MACH_IXDP465
121 default y
122
Ruslan V. Sushko45fba082007-04-06 15:00:31 +0100123config CPU_IXP43X
124 bool
125 depends on MACH_KIXRP435
126 default y
127
Linus Torvalds1da177e2005-04-16 15:20:36 -0700128config MACH_GTWX5715
129 bool "Gemtek WX5715 (Linksys WRV54G)"
130 depends on ARCH_IXP4XX
Deepak Saxena76bbb002006-04-30 15:34:29 +0100131 select PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700132 help
133 This board is currently inside the Linksys WRV54G Gateways.
134
135 IXP425 - 266mhz
136 32mb SDRAM
137 8mb Flash
138 miniPCI slot 0 does not have a card connector soldered to the board
139 miniPCI slot 1 has an ISL3880 802.11g card (Prism54)
140 npe0 is connected to a Kendin KS8995M Switch (4 ports)
141 npe1 is the "wan" port
142 "Console" UART is available on J11 as console
143 "High Speed" UART is n/c (as far as I can tell)
144 20 Pin ARM/Xscale JTAG interface on J2
145
Linus Torvalds1da177e2005-04-16 15:20:36 -0700146comment "IXP4xx Options"
147
Deepak Saxena76bbb002006-04-30 15:34:29 +0100148config DMABOUNCE
149 bool
150 default y
151 depends on PCI
152
Linus Torvalds1da177e2005-04-16 15:20:36 -0700153config IXP4XX_INDIRECT_PCI
154 bool "Use indirect PCI memory access"
Deepak Saxena76bbb002006-04-30 15:34:29 +0100155 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700156 help
157 IXP4xx provides two methods of accessing PCI memory space:
158
159 1) A direct mapped window from 0x48000000 to 0x4bffffff (64MB).
160 To access PCI via this space, we simply ioremap() the BAR
161 into the kernel and we can use the standard read[bwl]/write[bwl]
162 macros. This is the preferred method due to speed but it
163 limits the system to just 64MB of PCI memory. This can be
Matt LaPlante3cb2fcc2006-11-30 05:22:59 +0100164 problematic if using video cards and other memory-heavy devices.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700165
166 2) If > 64MB of memory space is required, the IXP4xx can be
167 configured to use indirect registers to access PCI This allows
168 for up to 128MB (0x48000000 to 0x4fffffff) of memory on the bus.
Egry Gaborc41045a2006-06-04 21:22:11 +0100169 The disadvantage of this is that every PCI access requires
Linus Torvalds1da177e2005-04-16 15:20:36 -0700170 three local register accesses plus a spinlock, but in some
171 cases the performance hit is acceptable. In addition, you cannot
172 mmap() PCI devices in this case due to the indirect nature
173 of the PCI window.
174
175 By default, the direct method is used. Choose this option if you
176 need to use the indirect method instead. If you don't know
177 what you need, leave this option unselected.
178
179endmenu
180
181endif