[ARM] 4712/2: Adds functions to read and write IXP4xx "feature" bits
[deliverable/linux.git] / arch / arm / mach-ixp4xx / Kconfig
CommitLineData
1da177e4
LT
1if ARCH_IXP4XX
2
3config ARCH_SUPPORTS_BIG_ENDIAN
4 bool
5 default y
6
7menu "Intel IXP4xx Implementation Options"
8
9comment "IXP4xx Platforms"
10
a7918f39
AZ
11config MACH_NSLU2
12 bool
e7fcdb79 13 prompt "Linksys NSLU2"
76bbb002 14 select PCI
a7918f39
AZ
15 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
0f185971 20config MACH_AVILA
1da177e4 21 bool "Avila"
76bbb002 22 select PCI
1da177e4
LT
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>.
27
0f185971
MLJ
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
1da177e4
LT
36config ARCH_ADI_COYOTE
37 bool "Coyote"
76bbb002 38 select PCI
1da177e4
LT
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>.
43
46918bd1
IK
44config MACH_GATEWAY7001
45 bool "Gateway 7001"
46 select PCI
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
dcdeeb21
IK
52config MACH_WG302V2
53 bool "Netgear WG302 v2 / WAG302 v2"
54 select PCI
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
1da177e4
LT
60config ARCH_IXDP425
61 bool "IXDP425"
62 help
63 Say 'Y' here if you want your kernel to support Intel's
64 IXDP425 Development Platform (Also known as Richfield).
65 For more information on this platform, see <file:Documentation/arm/IXP4xx>.
66
67config MACH_IXDPG425
68 bool "IXDPG425"
69 help
70 Say 'Y' here if you want your kernel to support Intel's
71 IXDPG425 Development Platform (Also known as Montajade).
72 For more information on this platform, see <file:Documentation/arm/IXP4xx>.
73
74config MACH_IXDP465
75 bool "IXDP465"
76 help
77 Say 'Y' here if you want your kernel to support Intel's
78 IXDP465 Development Platform (Also known as BMP).
7aa52f51 79 For more information on this platform, see <file:Documentation/arm/IXP4xx>.
1da177e4 80
45fba084
RS
81config MACH_KIXRP435
82 bool "KIXRP435"
83 help
84 Say 'Y' here if you want your kernel to support Intel's
85 KIXRP435 Reference Platform.
86 For more information on this platform, see <file:Documentation/arm/IXP4xx>.
1da177e4
LT
87
88#
89# IXCDP1100 is the exact same HW as IXDP425, but with a different machine
90# number from the bootloader due to marketing monkeys, so we just enable it
91# by default if IXDP425 is enabled.
92#
93config ARCH_IXCDP1100
94 bool
95 depends on ARCH_IXDP425
96 default y
97
98config ARCH_PRPMC1100
99 bool "PrPMC1100"
100 help
101 Say 'Y' here if you want your kernel to support the Motorola
102 PrPCM1100 Processor Mezanine Module. For more information on
103 this platform, see <file:Documentation/arm/IXP4xx>.
104
3145d8a6
RW
105config MACH_NAS100D
106 bool
107 prompt "NAS100D"
76bbb002 108 select PCI
3145d8a6
RW
109 help
110 Say 'Y' here if you want your kernel to support Iomega's
111 NAS 100d device. For more information on this platform,
112 see http://www.nslu2-linux.org/wiki/NAS100d/HomePage
113
28bd3a0d
MLJ
114config MACH_DSMG600
115 bool
116 prompt "D-Link DSM-G600 RevA"
117 select PCI
118 help
119 Say 'Y' here if you want your kernel to support D-Link's
120 DSM-G600 RevA device. For more information on this platform,
121 see http://www.nslu2-linux.org/wiki/DSMG600/HomePage
122
1da177e4
LT
123config ARCH_IXDP4XX
124 bool
45fba084 125 depends on ARCH_IXDP425 || MACH_IXDP465 || MACH_KIXRP435
1da177e4
LT
126 default y
127
128#
129# Certain registers and IRQs are only enabled if supporting IXP465 CPUs
130#
131config CPU_IXP46X
132 bool
133 depends on MACH_IXDP465
134 default y
135
45fba084
RS
136config CPU_IXP43X
137 bool
138 depends on MACH_KIXRP435
139 default y
140
1da177e4
LT
141config MACH_GTWX5715
142 bool "Gemtek WX5715 (Linksys WRV54G)"
143 depends on ARCH_IXP4XX
76bbb002 144 select PCI
1da177e4
LT
145 help
146 This board is currently inside the Linksys WRV54G Gateways.
147
148 IXP425 - 266mhz
149 32mb SDRAM
150 8mb Flash
151 miniPCI slot 0 does not have a card connector soldered to the board
152 miniPCI slot 1 has an ISL3880 802.11g card (Prism54)
153 npe0 is connected to a Kendin KS8995M Switch (4 ports)
154 npe1 is the "wan" port
155 "Console" UART is available on J11 as console
156 "High Speed" UART is n/c (as far as I can tell)
157 20 Pin ARM/Xscale JTAG interface on J2
158
1da177e4
LT
159comment "IXP4xx Options"
160
76bbb002
DS
161config DMABOUNCE
162 bool
163 default y
164 depends on PCI
165
1da177e4
LT
166config IXP4XX_INDIRECT_PCI
167 bool "Use indirect PCI memory access"
76bbb002 168 depends on PCI
1da177e4
LT
169 help
170 IXP4xx provides two methods of accessing PCI memory space:
171
172 1) A direct mapped window from 0x48000000 to 0x4bffffff (64MB).
173 To access PCI via this space, we simply ioremap() the BAR
174 into the kernel and we can use the standard read[bwl]/write[bwl]
175 macros. This is the preferred method due to speed but it
176 limits the system to just 64MB of PCI memory. This can be
3cb2fccc 177 problematic if using video cards and other memory-heavy devices.
1da177e4
LT
178
179 2) If > 64MB of memory space is required, the IXP4xx can be
180 configured to use indirect registers to access PCI This allows
181 for up to 128MB (0x48000000 to 0x4fffffff) of memory on the bus.
c41045a4 182 The disadvantage of this is that every PCI access requires
1da177e4
LT
183 three local register accesses plus a spinlock, but in some
184 cases the performance hit is acceptable. In addition, you cannot
185 mmap() PCI devices in this case due to the indirect nature
186 of the PCI window.
187
188 By default, the direct method is used. Choose this option if you
189 need to use the indirect method instead. If you don't know
190 what you need, leave this option unselected.
191
192endmenu
193
194endif
This page took 0.282214 seconds and 5 git commands to generate.