Doug / smarc-fsl-linux-kernel

Download as
Browse Code ยป

Commit 8a335bc631ac9c43675821580c26ebf95a3044ba

Authored by Linus Torvalds
2 parents 1153742119 7b1fff7e4f
Exists in master and in 7 other branches imx_3.0.35_4.1.0, imx_3.10.17_1.0.1_ga, imx_3.10.53_1.1.0_ga, imx_3.14.28_1.0.0_ga, smarc-imx_3.10.53_1.1.0_ga, smarc-imx_3.14.28_1.0.0_ga, smarc-l5.0.0_1.0.0-ga

Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/nab/scsi-post-merge-2.6 

* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/nab/scsi-post-merge-2.6:
  ocfs2: Make OCFS2_FS depend on CONFIGFS_FS
  dlm: Make DLM depend on CONFIGFS_FS
  net: Make NETCONSOLE_DYNAMIC depend on CONFIGFS_FS
  configfs: change depends -> select SYSFS
  [SCSI] sd,sr: kill compat SDEV_MEDIA_CHANGE event
  [SCSI] sd: implement sd_check_events()

Showing 4 changed files Inline Diff

1 # 1 #
2 # Network device configuration 2 # Network device configuration
3 # 3 #
4 4
5 config HAVE_NET_MACB 5 config HAVE_NET_MACB
6 bool 6 bool
7 7
8 menuconfig NETDEVICES 8 menuconfig NETDEVICES
9 default y if UML 9 default y if UML
10 depends on NET 10 depends on NET
11 bool "Network device support" 11 bool "Network device support"
12 ---help--- 12 ---help---
13 You can say N here if you don't intend to connect your Linux box to 13 You can say N here if you don't intend to connect your Linux box to
14 any other computer at all. 14 any other computer at all.
15 15
16 You'll have to say Y if your computer contains a network card that 16 You'll have to say Y if your computer contains a network card that
17 you want to use under Linux. If you are going to run SLIP or PPP over 17 you want to use under Linux. If you are going to run SLIP or PPP over
18 telephone line or null modem cable you need say Y here. Connecting 18 telephone line or null modem cable you need say Y here. Connecting
19 two machines with parallel ports using PLIP needs this, as well as 19 two machines with parallel ports using PLIP needs this, as well as
20 AX.25/KISS for sending Internet traffic over amateur radio links. 20 AX.25/KISS for sending Internet traffic over amateur radio links.
21 21
22 See also "The Linux Network Administrator's Guide" by Olaf Kirch and 22 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
23 Terry Dawson. Available at <http://www.tldp.org/guides.html>. 23 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
24 24
25 If unsure, say Y. 25 If unsure, say Y.
26 26
27 # All the following symbols are dependent on NETDEVICES - do not repeat 27 # All the following symbols are dependent on NETDEVICES - do not repeat
28 # that for each of the symbols. 28 # that for each of the symbols.
29 if NETDEVICES 29 if NETDEVICES
30 30
31 config IFB 31 config IFB
32 tristate "Intermediate Functional Block support" 32 tristate "Intermediate Functional Block support"
33 depends on NET_CLS_ACT 33 depends on NET_CLS_ACT
34 ---help--- 34 ---help---
35 This is an intermediate driver that allows sharing of 35 This is an intermediate driver that allows sharing of
36 resources. 36 resources.
37 To compile this driver as a module, choose M here: the module 37 To compile this driver as a module, choose M here: the module
38 will be called ifb. If you want to use more than one ifb 38 will be called ifb. If you want to use more than one ifb
39 device at a time, you need to compile this driver as a module. 39 device at a time, you need to compile this driver as a module.
40 Instead of 'ifb', the devices will then be called 'ifb0', 40 Instead of 'ifb', the devices will then be called 'ifb0',
41 'ifb1' etc. 41 'ifb1' etc.
42 Look at the iproute2 documentation directory for usage etc 42 Look at the iproute2 documentation directory for usage etc
43 43
44 config DUMMY 44 config DUMMY
45 tristate "Dummy net driver support" 45 tristate "Dummy net driver support"
46 ---help--- 46 ---help---
47 This is essentially a bit-bucket device (i.e. traffic you send to 47 This is essentially a bit-bucket device (i.e. traffic you send to
48 this device is consigned into oblivion) with a configurable IP 48 this device is consigned into oblivion) with a configurable IP
49 address. It is most commonly used in order to make your currently 49 address. It is most commonly used in order to make your currently
50 inactive SLIP address seem like a real address for local programs. 50 inactive SLIP address seem like a real address for local programs.
51 If you use SLIP or PPP, you might want to say Y here. Since this 51 If you use SLIP or PPP, you might want to say Y here. Since this
52 thing often comes in handy, the default is Y. It won't enlarge your 52 thing often comes in handy, the default is Y. It won't enlarge your
53 kernel either. What a deal. Read about it in the Network 53 kernel either. What a deal. Read about it in the Network
54 Administrator's Guide, available from 54 Administrator's Guide, available from
55 <http://www.tldp.org/docs.html#guide>. 55 <http://www.tldp.org/docs.html#guide>.
56 56
57 To compile this driver as a module, choose M here: the module 57 To compile this driver as a module, choose M here: the module
58 will be called dummy. If you want to use more than one dummy 58 will be called dummy. If you want to use more than one dummy
59 device at a time, you need to compile this driver as a module. 59 device at a time, you need to compile this driver as a module.
60 Instead of 'dummy', the devices will then be called 'dummy0', 60 Instead of 'dummy', the devices will then be called 'dummy0',
61 'dummy1' etc. 61 'dummy1' etc.
62 62
63 config BONDING 63 config BONDING
64 tristate "Bonding driver support" 64 tristate "Bonding driver support"
65 depends on INET 65 depends on INET
66 depends on IPV6 || IPV6=n 66 depends on IPV6 || IPV6=n
67 ---help--- 67 ---help---
68 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet 68 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
69 Channels together. This is called 'Etherchannel' by Cisco, 69 Channels together. This is called 'Etherchannel' by Cisco,
70 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux. 70 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
71 71
72 The driver supports multiple bonding modes to allow for both high 72 The driver supports multiple bonding modes to allow for both high
73 performance and high availability operation. 73 performance and high availability operation.
74 74
75 Refer to <file:Documentation/networking/bonding.txt> for more 75 Refer to <file:Documentation/networking/bonding.txt> for more
76 information. 76 information.
77 77
78 To compile this driver as a module, choose M here: the module 78 To compile this driver as a module, choose M here: the module
79 will be called bonding. 79 will be called bonding.
80 80
81 config MACVLAN 81 config MACVLAN
82 tristate "MAC-VLAN support (EXPERIMENTAL)" 82 tristate "MAC-VLAN support (EXPERIMENTAL)"
83 depends on EXPERIMENTAL 83 depends on EXPERIMENTAL
84 ---help--- 84 ---help---
85 This allows one to create virtual interfaces that map packets to 85 This allows one to create virtual interfaces that map packets to
86 or from specific MAC addresses to a particular interface. 86 or from specific MAC addresses to a particular interface.
87 87
88 Macvlan devices can be added using the "ip" command from the 88 Macvlan devices can be added using the "ip" command from the
89 iproute2 package starting with the iproute2-2.6.23 release: 89 iproute2 package starting with the iproute2-2.6.23 release:
90 90
91 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan" 91 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
92 92
93 To compile this driver as a module, choose M here: the module 93 To compile this driver as a module, choose M here: the module
94 will be called macvlan. 94 will be called macvlan.
95 95
96 config MACVTAP 96 config MACVTAP
97 tristate "MAC-VLAN based tap driver (EXPERIMENTAL)" 97 tristate "MAC-VLAN based tap driver (EXPERIMENTAL)"
98 depends on MACVLAN 98 depends on MACVLAN
99 help 99 help
100 This adds a specialized tap character device driver that is based 100 This adds a specialized tap character device driver that is based
101 on the MAC-VLAN network interface, called macvtap. A macvtap device 101 on the MAC-VLAN network interface, called macvtap. A macvtap device
102 can be added in the same way as a macvlan device, using 'type 102 can be added in the same way as a macvlan device, using 'type
103 macvlan', and then be accessed through the tap user space interface. 103 macvlan', and then be accessed through the tap user space interface.
104 104
105 To compile this driver as a module, choose M here: the module 105 To compile this driver as a module, choose M here: the module
106 will be called macvtap. 106 will be called macvtap.
107 107
108 config EQUALIZER 108 config EQUALIZER
109 tristate "EQL (serial line load balancing) support" 109 tristate "EQL (serial line load balancing) support"
110 ---help--- 110 ---help---
111 If you have two serial connections to some other computer (this 111 If you have two serial connections to some other computer (this
112 usually requires two modems and two telephone lines) and you use 112 usually requires two modems and two telephone lines) and you use
113 SLIP (the protocol for sending Internet traffic over telephone 113 SLIP (the protocol for sending Internet traffic over telephone
114 lines) or PPP (a better SLIP) on them, you can make them behave like 114 lines) or PPP (a better SLIP) on them, you can make them behave like
115 one double speed connection using this driver. Naturally, this has 115 one double speed connection using this driver. Naturally, this has
116 to be supported at the other end as well, either with a similar EQL 116 to be supported at the other end as well, either with a similar EQL
117 Linux driver or with a Livingston Portmaster 2e. 117 Linux driver or with a Livingston Portmaster 2e.
118 118
119 Say Y if you want this and read 119 Say Y if you want this and read
120 <file:Documentation/networking/eql.txt>. You may also want to read 120 <file:Documentation/networking/eql.txt>. You may also want to read
121 section 6.2 of the NET-3-HOWTO, available from 121 section 6.2 of the NET-3-HOWTO, available from
122 <http://www.tldp.org/docs.html#howto>. 122 <http://www.tldp.org/docs.html#howto>.
123 123
124 To compile this driver as a module, choose M here: the module 124 To compile this driver as a module, choose M here: the module
125 will be called eql. If unsure, say N. 125 will be called eql. If unsure, say N.
126 126
127 config TUN 127 config TUN
128 tristate "Universal TUN/TAP device driver support" 128 tristate "Universal TUN/TAP device driver support"
129 select CRC32 129 select CRC32
130 ---help--- 130 ---help---
131 TUN/TAP provides packet reception and transmission for user space 131 TUN/TAP provides packet reception and transmission for user space
132 programs. It can be viewed as a simple Point-to-Point or Ethernet 132 programs. It can be viewed as a simple Point-to-Point or Ethernet
133 device, which instead of receiving packets from a physical media, 133 device, which instead of receiving packets from a physical media,
134 receives them from user space program and instead of sending packets 134 receives them from user space program and instead of sending packets
135 via physical media writes them to the user space program. 135 via physical media writes them to the user space program.
136 136
137 When a program opens /dev/net/tun, driver creates and registers 137 When a program opens /dev/net/tun, driver creates and registers
138 corresponding net device tunX or tapX. After a program closed above 138 corresponding net device tunX or tapX. After a program closed above
139 devices, driver will automatically delete tunXX or tapXX device and 139 devices, driver will automatically delete tunXX or tapXX device and
140 all routes corresponding to it. 140 all routes corresponding to it.
141 141
142 Please read <file:Documentation/networking/tuntap.txt> for more 142 Please read <file:Documentation/networking/tuntap.txt> for more
143 information. 143 information.
144 144
145 To compile this driver as a module, choose M here: the module 145 To compile this driver as a module, choose M here: the module
146 will be called tun. 146 will be called tun.
147 147
148 If you don't know what to use this for, you don't need it. 148 If you don't know what to use this for, you don't need it.
149 149
150 config VETH 150 config VETH
151 tristate "Virtual ethernet pair device" 151 tristate "Virtual ethernet pair device"
152 ---help--- 152 ---help---
153 This device is a local ethernet tunnel. Devices are created in pairs. 153 This device is a local ethernet tunnel. Devices are created in pairs.
154 When one end receives the packet it appears on its pair and vice 154 When one end receives the packet it appears on its pair and vice
155 versa. 155 versa.
156 156
157 config NET_SB1000 157 config NET_SB1000
158 tristate "General Instruments Surfboard 1000" 158 tristate "General Instruments Surfboard 1000"
159 depends on PNP 159 depends on PNP
160 ---help--- 160 ---help---
161 This is a driver for the General Instrument (also known as 161 This is a driver for the General Instrument (also known as
162 NextLevel) SURFboard 1000 internal 162 NextLevel) SURFboard 1000 internal
163 cable modem. This is an ISA card which is used by a number of cable 163 cable modem. This is an ISA card which is used by a number of cable
164 TV companies to provide cable modem access. It's a one-way 164 TV companies to provide cable modem access. It's a one-way
165 downstream-only cable modem, meaning that your upstream net link is 165 downstream-only cable modem, meaning that your upstream net link is
166 provided by your regular phone modem. 166 provided by your regular phone modem.
167 167
168 At present this driver only compiles as a module, so say M here if 168 At present this driver only compiles as a module, so say M here if
169 you have this card. The module will be called sb1000. Then read 169 you have this card. The module will be called sb1000. Then read
170 <file:Documentation/networking/README.sb1000> for information on how 170 <file:Documentation/networking/README.sb1000> for information on how
171 to use this module, as it needs special ppp scripts for establishing 171 to use this module, as it needs special ppp scripts for establishing
172 a connection. Further documentation and the necessary scripts can be 172 a connection. Further documentation and the necessary scripts can be
173 found at: 173 found at:
174 174
175 <http://www.jacksonville.net/~fventuri/> 175 <http://www.jacksonville.net/~fventuri/>
176 <http://home.adelphia.net/~siglercm/sb1000.html> 176 <http://home.adelphia.net/~siglercm/sb1000.html>
177 <http://linuxpower.cx/~cable/> 177 <http://linuxpower.cx/~cable/>
178 178
179 If you don't have this card, of course say N. 179 If you don't have this card, of course say N.
180 180
181 source "drivers/net/arcnet/Kconfig" 181 source "drivers/net/arcnet/Kconfig"
182 182
183 config MII 183 config MII
184 tristate "Generic Media Independent Interface device support" 184 tristate "Generic Media Independent Interface device support"
185 help 185 help
186 Most ethernet controllers have MII transceiver either as an external 186 Most ethernet controllers have MII transceiver either as an external
187 or internal device. It is safe to say Y or M here even if your 187 or internal device. It is safe to say Y or M here even if your
188 ethernet card lacks MII. 188 ethernet card lacks MII.
189 189
190 source "drivers/net/phy/Kconfig" 190 source "drivers/net/phy/Kconfig"
191 191
192 # 192 #
193 # Ethernet 193 # Ethernet
194 # 194 #
195 195
196 menuconfig NET_ETHERNET 196 menuconfig NET_ETHERNET
197 bool "Ethernet (10 or 100Mbit)" 197 bool "Ethernet (10 or 100Mbit)"
198 depends on !UML 198 depends on !UML
199 ---help--- 199 ---help---
200 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common 200 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
201 type of Local Area Network (LAN) in universities and companies. 201 type of Local Area Network (LAN) in universities and companies.
202 202
203 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over 203 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
204 coaxial cable, linking computers in a chain), 10BASE-T or twisted 204 coaxial cable, linking computers in a chain), 10BASE-T or twisted
205 pair (10 Mbps over twisted pair cable, linking computers to central 205 pair (10 Mbps over twisted pair cable, linking computers to central
206 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs), 206 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
207 100BASE-TX (100 Mbps over two twisted pair cables, using hubs), 207 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
208 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair 208 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
209 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links) 209 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
210 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit 210 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
211 Ethernet (1 Gbps over optical fiber or short copper links). 211 Ethernet (1 Gbps over optical fiber or short copper links).
212 212
213 If your Linux machine will be connected to an Ethernet and you have 213 If your Linux machine will be connected to an Ethernet and you have
214 an Ethernet network interface card (NIC) installed in your computer, 214 an Ethernet network interface card (NIC) installed in your computer,
215 say Y here and read the Ethernet-HOWTO, available from 215 say Y here and read the Ethernet-HOWTO, available from
216 <http://www.tldp.org/docs.html#howto>. You will then also have 216 <http://www.tldp.org/docs.html#howto>. You will then also have
217 to say Y to the driver for your particular NIC. 217 to say Y to the driver for your particular NIC.
218 218
219 Note that the answer to this question won't directly affect the 219 Note that the answer to this question won't directly affect the
220 kernel: saying N will just cause the configurator to skip all 220 kernel: saying N will just cause the configurator to skip all
221 the questions about Ethernet network cards. If unsure, say N. 221 the questions about Ethernet network cards. If unsure, say N.
222 222
223 if NET_ETHERNET 223 if NET_ETHERNET
224 224
225 config MACB 225 config MACB
226 tristate "Atmel MACB support" 226 tristate "Atmel MACB support"
227 depends on HAVE_NET_MACB 227 depends on HAVE_NET_MACB
228 select PHYLIB 228 select PHYLIB
229 help 229 help
230 The Atmel MACB ethernet interface is found on many AT32 and AT91 230 The Atmel MACB ethernet interface is found on many AT32 and AT91
231 parts. Say Y to include support for the MACB chip. 231 parts. Say Y to include support for the MACB chip.
232 232
233 To compile this driver as a module, choose M here: the module 233 To compile this driver as a module, choose M here: the module
234 will be called macb. 234 will be called macb.
235 235
236 source "drivers/net/arm/Kconfig" 236 source "drivers/net/arm/Kconfig"
237 237
238 config AX88796 238 config AX88796
239 tristate "ASIX AX88796 NE2000 clone support" 239 tristate "ASIX AX88796 NE2000 clone support"
240 depends on ARM || MIPS || SUPERH 240 depends on ARM || MIPS || SUPERH
241 select CRC32 241 select CRC32
242 select MII 242 select MII
243 help 243 help
244 AX88796 driver, using platform bus to provide 244 AX88796 driver, using platform bus to provide
245 chip detection and resources 245 chip detection and resources
246 246
247 config AX88796_93CX6 247 config AX88796_93CX6
248 bool "ASIX AX88796 external 93CX6 eeprom support" 248 bool "ASIX AX88796 external 93CX6 eeprom support"
249 depends on AX88796 249 depends on AX88796
250 select EEPROM_93CX6 250 select EEPROM_93CX6
251 help 251 help
252 Select this if your platform comes with an external 93CX6 eeprom. 252 Select this if your platform comes with an external 93CX6 eeprom.
253 253
254 config MACE 254 config MACE
255 tristate "MACE (Power Mac ethernet) support" 255 tristate "MACE (Power Mac ethernet) support"
256 depends on PPC_PMAC && PPC32 256 depends on PPC_PMAC && PPC32
257 select CRC32 257 select CRC32
258 help 258 help
259 Power Macintoshes and clones with Ethernet built-in on the 259 Power Macintoshes and clones with Ethernet built-in on the
260 motherboard will usually use a MACE (Medium Access Control for 260 motherboard will usually use a MACE (Medium Access Control for
261 Ethernet) interface. Say Y to include support for the MACE chip. 261 Ethernet) interface. Say Y to include support for the MACE chip.
262 262
263 To compile this driver as a module, choose M here: the module 263 To compile this driver as a module, choose M here: the module
264 will be called mace. 264 will be called mace.
265 265
266 config MACE_AAUI_PORT 266 config MACE_AAUI_PORT
267 bool "Use AAUI port instead of TP by default" 267 bool "Use AAUI port instead of TP by default"
268 depends on MACE 268 depends on MACE
269 help 269 help
270 Some Apple machines (notably the Apple Network Server) which use the 270 Some Apple machines (notably the Apple Network Server) which use the
271 MACE ethernet chip have an Apple AUI port (small 15-pin connector), 271 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
272 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say 272 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
273 Y here if you have such a machine. If unsure, say N. 273 Y here if you have such a machine. If unsure, say N.
274 The driver will default to AAUI on ANS anyway, and if you use it as 274 The driver will default to AAUI on ANS anyway, and if you use it as
275 a module, you can provide the port_aaui=0|1 to force the driver. 275 a module, you can provide the port_aaui=0|1 to force the driver.
276 276
277 config BMAC 277 config BMAC
278 tristate "BMAC (G3 ethernet) support" 278 tristate "BMAC (G3 ethernet) support"
279 depends on PPC_PMAC && PPC32 279 depends on PPC_PMAC && PPC32
280 select CRC32 280 select CRC32
281 help 281 help
282 Say Y for support of BMAC Ethernet interfaces. These are used on G3 282 Say Y for support of BMAC Ethernet interfaces. These are used on G3
283 computers. 283 computers.
284 284
285 To compile this driver as a module, choose M here: the module 285 To compile this driver as a module, choose M here: the module
286 will be called bmac. 286 will be called bmac.
287 287
288 config ARIADNE 288 config ARIADNE
289 tristate "Ariadne support" 289 tristate "Ariadne support"
290 depends on ZORRO 290 depends on ZORRO
291 help 291 help
292 If you have a Village Tronic Ariadne Ethernet adapter, say Y. 292 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
293 Otherwise, say N. 293 Otherwise, say N.
294 294
295 To compile this driver as a module, choose M here: the module 295 To compile this driver as a module, choose M here: the module
296 will be called ariadne. 296 will be called ariadne.
297 297
298 config A2065 298 config A2065
299 tristate "A2065 support" 299 tristate "A2065 support"
300 depends on ZORRO 300 depends on ZORRO
301 select CRC32 301 select CRC32
302 help 302 help
303 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise, 303 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
304 say N. 304 say N.
305 305
306 To compile this driver as a module, choose M here: the module 306 To compile this driver as a module, choose M here: the module
307 will be called a2065. 307 will be called a2065.
308 308
309 config HYDRA 309 config HYDRA
310 tristate "Hydra support" 310 tristate "Hydra support"
311 depends on ZORRO 311 depends on ZORRO
312 select CRC32 312 select CRC32
313 help 313 help
314 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N. 314 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
315 315
316 To compile this driver as a module, choose M here: the module 316 To compile this driver as a module, choose M here: the module
317 will be called hydra. 317 will be called hydra.
318 318
319 config ZORRO8390 319 config ZORRO8390
320 tristate "Zorro NS8390-based Ethernet support" 320 tristate "Zorro NS8390-based Ethernet support"
321 depends on ZORRO 321 depends on ZORRO
322 select CRC32 322 select CRC32
323 help 323 help
324 This driver is for Zorro Ethernet cards using an NS8390-compatible 324 This driver is for Zorro Ethernet cards using an NS8390-compatible
325 chipset, like the Village Tronic Ariadne II and the Individual 325 chipset, like the Village Tronic Ariadne II and the Individual
326 Computers X-Surf Ethernet cards. If you have such a card, say Y. 326 Computers X-Surf Ethernet cards. If you have such a card, say Y.
327 Otherwise, say N. 327 Otherwise, say N.
328 328
329 To compile this driver as a module, choose M here: the module 329 To compile this driver as a module, choose M here: the module
330 will be called zorro8390. 330 will be called zorro8390.
331 331
332 config APNE 332 config APNE
333 tristate "PCMCIA NE2000 support" 333 tristate "PCMCIA NE2000 support"
334 depends on AMIGA_PCMCIA 334 depends on AMIGA_PCMCIA
335 select CRC32 335 select CRC32
336 help 336 help
337 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise, 337 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
338 say N. 338 say N.
339 339
340 To compile this driver as a module, choose M here: the module 340 To compile this driver as a module, choose M here: the module
341 will be called apne. 341 will be called apne.
342 342
343 config MAC8390 343 config MAC8390
344 bool "Macintosh NS 8390 based ethernet cards" 344 bool "Macintosh NS 8390 based ethernet cards"
345 depends on MAC 345 depends on MAC
346 select CRC32 346 select CRC32
347 help 347 help
348 If you want to include a driver to support Nubus or LC-PDS 348 If you want to include a driver to support Nubus or LC-PDS
349 Ethernet cards using an NS8390 chipset or its equivalent, say Y 349 Ethernet cards using an NS8390 chipset or its equivalent, say Y
350 and read the Ethernet-HOWTO, available from 350 and read the Ethernet-HOWTO, available from
351 <http://www.tldp.org/docs.html#howto>. 351 <http://www.tldp.org/docs.html#howto>.
352 352
353 config MAC89x0 353 config MAC89x0
354 tristate "Macintosh CS89x0 based ethernet cards" 354 tristate "Macintosh CS89x0 based ethernet cards"
355 depends on MAC 355 depends on MAC
356 ---help--- 356 ---help---
357 Support for CS89x0 chipset based Ethernet cards. If you have a 357 Support for CS89x0 chipset based Ethernet cards. If you have a
358 Nubus or LC-PDS network (Ethernet) card of this type, say Y and 358 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
359 read the Ethernet-HOWTO, available from 359 read the Ethernet-HOWTO, available from
360 <http://www.tldp.org/docs.html#howto>. 360 <http://www.tldp.org/docs.html#howto>.
361 361
362 To compile this driver as a module, choose M here. This module will 362 To compile this driver as a module, choose M here. This module will
363 be called mac89x0. 363 be called mac89x0.
364 364
365 config MACSONIC 365 config MACSONIC
366 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)" 366 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
367 depends on MAC 367 depends on MAC
368 ---help--- 368 ---help---
369 Support for NatSemi SONIC based Ethernet devices. This includes 369 Support for NatSemi SONIC based Ethernet devices. This includes
370 the onboard Ethernet in many Quadras as well as some LC-PDS, 370 the onboard Ethernet in many Quadras as well as some LC-PDS,
371 a few Nubus and all known Comm Slot Ethernet cards. If you have 371 a few Nubus and all known Comm Slot Ethernet cards. If you have
372 one of these say Y and read the Ethernet-HOWTO, available from 372 one of these say Y and read the Ethernet-HOWTO, available from
373 <http://www.tldp.org/docs.html#howto>. 373 <http://www.tldp.org/docs.html#howto>.
374 374
375 To compile this driver as a module, choose M here. This module will 375 To compile this driver as a module, choose M here. This module will
376 be called macsonic. 376 be called macsonic.
377 377
378 config MACMACE 378 config MACMACE
379 bool "Macintosh (AV) onboard MACE ethernet" 379 bool "Macintosh (AV) onboard MACE ethernet"
380 depends on MAC 380 depends on MAC
381 select CRC32 381 select CRC32
382 help 382 help
383 Support for the onboard AMD 79C940 MACE Ethernet controller used in 383 Support for the onboard AMD 79C940 MACE Ethernet controller used in
384 the 660AV and 840AV Macintosh. If you have one of these Macintoshes 384 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
385 say Y and read the Ethernet-HOWTO, available from 385 say Y and read the Ethernet-HOWTO, available from
386 <http://www.tldp.org/docs.html#howto>. 386 <http://www.tldp.org/docs.html#howto>.
387 387
388 config MVME147_NET 388 config MVME147_NET
389 tristate "MVME147 (Lance) Ethernet support" 389 tristate "MVME147 (Lance) Ethernet support"
390 depends on MVME147 390 depends on MVME147
391 select CRC32 391 select CRC32
392 help 392 help
393 Support for the on-board Ethernet interface on the Motorola MVME147 393 Support for the on-board Ethernet interface on the Motorola MVME147
394 single-board computer. Say Y here to include the 394 single-board computer. Say Y here to include the
395 driver for this chip in your kernel. 395 driver for this chip in your kernel.
396 To compile this driver as a module, choose M here. 396 To compile this driver as a module, choose M here.
397 397
398 config MVME16x_NET 398 config MVME16x_NET
399 tristate "MVME16x Ethernet support" 399 tristate "MVME16x Ethernet support"
400 depends on MVME16x 400 depends on MVME16x
401 help 401 help
402 This is the driver for the Ethernet interface on the Motorola 402 This is the driver for the Ethernet interface on the Motorola
403 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the 403 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
404 driver for this chip in your kernel. 404 driver for this chip in your kernel.
405 To compile this driver as a module, choose M here. 405 To compile this driver as a module, choose M here.
406 406
407 config BVME6000_NET 407 config BVME6000_NET
408 tristate "BVME6000 Ethernet support" 408 tristate "BVME6000 Ethernet support"
409 depends on BVME6000 409 depends on BVME6000
410 help 410 help
411 This is the driver for the Ethernet interface on BVME4000 and 411 This is the driver for the Ethernet interface on BVME4000 and
412 BVME6000 VME boards. Say Y here to include the driver for this chip 412 BVME6000 VME boards. Say Y here to include the driver for this chip
413 in your kernel. 413 in your kernel.
414 To compile this driver as a module, choose M here. 414 To compile this driver as a module, choose M here.
415 415
416 config ATARILANCE 416 config ATARILANCE
417 tristate "Atari Lance support" 417 tristate "Atari Lance support"
418 depends on ATARI 418 depends on ATARI
419 help 419 help
420 Say Y to include support for several Atari Ethernet adapters based 420 Say Y to include support for several Atari Ethernet adapters based
421 on the AMD Lance chipset: RieblCard (with or without battery), or 421 on the AMD Lance chipset: RieblCard (with or without battery), or
422 PAMCard VME (also the version by Rhotron, with different addresses). 422 PAMCard VME (also the version by Rhotron, with different addresses).
423 423
424 config SUN3LANCE 424 config SUN3LANCE
425 tristate "Sun3/Sun3x on-board LANCE support" 425 tristate "Sun3/Sun3x on-board LANCE support"
426 depends on SUN3 || SUN3X 426 depends on SUN3 || SUN3X
427 help 427 help
428 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80) 428 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
429 featured an AMD Lance 10Mbit Ethernet controller on board; say Y 429 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
430 here to compile in the Linux driver for this and enable Ethernet. 430 here to compile in the Linux driver for this and enable Ethernet.
431 General Linux information on the Sun 3 and 3x series (now 431 General Linux information on the Sun 3 and 3x series (now
432 discontinued) is at 432 discontinued) is at
433 <http://www.angelfire.com/ca2/tech68k/sun3.html>. 433 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
434 434
435 If you're not building a kernel for a Sun 3, say N. 435 If you're not building a kernel for a Sun 3, say N.
436 436
437 config SUN3_82586 437 config SUN3_82586
438 bool "Sun3 on-board Intel 82586 support" 438 bool "Sun3 on-board Intel 82586 support"
439 depends on SUN3 439 depends on SUN3
440 help 440 help
441 This driver enables support for the on-board Intel 82586 based 441 This driver enables support for the on-board Intel 82586 based
442 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note 442 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
443 that this driver does not support 82586-based adapters on additional 443 that this driver does not support 82586-based adapters on additional
444 VME boards. 444 VME boards.
445 445
446 config HPLANCE 446 config HPLANCE
447 bool "HP on-board LANCE support" 447 bool "HP on-board LANCE support"
448 depends on DIO 448 depends on DIO
449 select CRC32 449 select CRC32
450 help 450 help
451 If you want to use the builtin "LANCE" Ethernet controller on an 451 If you want to use the builtin "LANCE" Ethernet controller on an
452 HP300 machine, say Y here. 452 HP300 machine, say Y here.
453 453
454 config LASI_82596 454 config LASI_82596
455 tristate "Lasi ethernet" 455 tristate "Lasi ethernet"
456 depends on GSC 456 depends on GSC
457 help 457 help
458 Say Y here to support the builtin Intel 82596 ethernet controller 458 Say Y here to support the builtin Intel 82596 ethernet controller
459 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet. 459 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
460 460
461 config SNI_82596 461 config SNI_82596
462 tristate "SNI RM ethernet" 462 tristate "SNI RM ethernet"
463 depends on NET_ETHERNET && SNI_RM 463 depends on NET_ETHERNET && SNI_RM
464 help 464 help
465 Say Y here to support the on-board Intel 82596 ethernet controller 465 Say Y here to support the on-board Intel 82596 ethernet controller
466 built into SNI RM machines. 466 built into SNI RM machines.
467 467
468 config KORINA 468 config KORINA
469 tristate "Korina (IDT RC32434) Ethernet support" 469 tristate "Korina (IDT RC32434) Ethernet support"
470 depends on NET_ETHERNET && MIKROTIK_RB532 470 depends on NET_ETHERNET && MIKROTIK_RB532
471 help 471 help
472 If you have a Mikrotik RouterBoard 500 or IDT RC32434 472 If you have a Mikrotik RouterBoard 500 or IDT RC32434
473 based system say Y. Otherwise say N. 473 based system say Y. Otherwise say N.
474 474
475 config MIPS_JAZZ_SONIC 475 config MIPS_JAZZ_SONIC
476 tristate "MIPS JAZZ onboard SONIC Ethernet support" 476 tristate "MIPS JAZZ onboard SONIC Ethernet support"
477 depends on MACH_JAZZ 477 depends on MACH_JAZZ
478 help 478 help
479 This is the driver for the onboard card of MIPS Magnum 4000, 479 This is the driver for the onboard card of MIPS Magnum 4000,
480 Acer PICA, Olivetti M700-10 and a few other identical OEM systems. 480 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
481 481
482 config XTENSA_XT2000_SONIC 482 config XTENSA_XT2000_SONIC
483 tristate "Xtensa XT2000 onboard SONIC Ethernet support" 483 tristate "Xtensa XT2000 onboard SONIC Ethernet support"
484 depends on XTENSA_PLATFORM_XT2000 484 depends on XTENSA_PLATFORM_XT2000
485 help 485 help
486 This is the driver for the onboard card of the Xtensa XT2000 board. 486 This is the driver for the onboard card of the Xtensa XT2000 board.
487 487
488 config MIPS_AU1X00_ENET 488 config MIPS_AU1X00_ENET
489 tristate "MIPS AU1000 Ethernet support" 489 tristate "MIPS AU1000 Ethernet support"
490 depends on MIPS_ALCHEMY 490 depends on MIPS_ALCHEMY
491 select PHYLIB 491 select PHYLIB
492 select CRC32 492 select CRC32
493 help 493 help
494 If you have an Alchemy Semi AU1X00 based system 494 If you have an Alchemy Semi AU1X00 based system
495 say Y. Otherwise, say N. 495 say Y. Otherwise, say N.
496 496
497 config SGI_IOC3_ETH 497 config SGI_IOC3_ETH
498 bool "SGI IOC3 Ethernet" 498 bool "SGI IOC3 Ethernet"
499 depends on PCI && SGI_IP27 499 depends on PCI && SGI_IP27
500 select CRC32 500 select CRC32
501 select MII 501 select MII
502 help 502 help
503 If you have a network (Ethernet) card of this type, say Y and read 503 If you have a network (Ethernet) card of this type, say Y and read
504 the Ethernet-HOWTO, available from 504 the Ethernet-HOWTO, available from
505 <http://www.tldp.org/docs.html#howto>. 505 <http://www.tldp.org/docs.html#howto>.
506 506
507 config MIPS_SIM_NET 507 config MIPS_SIM_NET
508 tristate "MIPS simulator Network device" 508 tristate "MIPS simulator Network device"
509 depends on MIPS_SIM 509 depends on MIPS_SIM
510 help 510 help
511 The MIPSNET device is a simple Ethernet network device which is 511 The MIPSNET device is a simple Ethernet network device which is
512 emulated by the MIPS Simulator. 512 emulated by the MIPS Simulator.
513 If you are not using a MIPSsim or are unsure, say N. 513 If you are not using a MIPSsim or are unsure, say N.
514 514
515 config SGI_O2MACE_ETH 515 config SGI_O2MACE_ETH
516 tristate "SGI O2 MACE Fast Ethernet support" 516 tristate "SGI O2 MACE Fast Ethernet support"
517 depends on SGI_IP32=y 517 depends on SGI_IP32=y
518 518
519 config STNIC 519 config STNIC
520 tristate "National DP83902AV support" 520 tristate "National DP83902AV support"
521 depends on SUPERH 521 depends on SUPERH
522 select CRC32 522 select CRC32
523 help 523 help
524 Support for cards based on the National Semiconductor DP83902AV 524 Support for cards based on the National Semiconductor DP83902AV
525 ST-NIC Serial Network Interface Controller for Twisted Pair. This 525 ST-NIC Serial Network Interface Controller for Twisted Pair. This
526 is a 10Mbit/sec Ethernet controller. Product overview and specs at 526 is a 10Mbit/sec Ethernet controller. Product overview and specs at
527 <http://www.national.com/pf/DP/DP83902A.html>. 527 <http://www.national.com/pf/DP/DP83902A.html>.
528 528
529 If unsure, say N. 529 If unsure, say N.
530 530
531 config SH_ETH 531 config SH_ETH
532 tristate "Renesas SuperH Ethernet support" 532 tristate "Renesas SuperH Ethernet support"
533 depends on SUPERH && \ 533 depends on SUPERH && \
534 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \ 534 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
535 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \ 535 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
536 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757) 536 CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
537 select CRC32 537 select CRC32
538 select MII 538 select MII
539 select MDIO_BITBANG 539 select MDIO_BITBANG
540 select PHYLIB 540 select PHYLIB
541 help 541 help
542 Renesas SuperH Ethernet device driver. 542 Renesas SuperH Ethernet device driver.
543 This driver supporting CPUs are: 543 This driver supporting CPUs are:
544 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757. 544 - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
545 545
546 config SUNLANCE 546 config SUNLANCE
547 tristate "Sun LANCE support" 547 tristate "Sun LANCE support"
548 depends on SBUS 548 depends on SBUS
549 select CRC32 549 select CRC32
550 help 550 help
551 This driver supports the "le" interface present on all 32-bit Sparc 551 This driver supports the "le" interface present on all 32-bit Sparc
552 systems, on some older Ultra systems and as an Sbus option. These 552 systems, on some older Ultra systems and as an Sbus option. These
553 cards are based on the AMD Lance chipset, which is better known 553 cards are based on the AMD Lance chipset, which is better known
554 via the NE2100 cards. 554 via the NE2100 cards.
555 555
556 To compile this driver as a module, choose M here: the module 556 To compile this driver as a module, choose M here: the module
557 will be called sunlance. 557 will be called sunlance.
558 558
559 config HAPPYMEAL 559 config HAPPYMEAL
560 tristate "Sun Happy Meal 10/100baseT support" 560 tristate "Sun Happy Meal 10/100baseT support"
561 depends on SBUS || PCI 561 depends on SBUS || PCI
562 select CRC32 562 select CRC32
563 help 563 help
564 This driver supports the "hme" interface present on most Ultra 564 This driver supports the "hme" interface present on most Ultra
565 systems and as an option on older Sbus systems. This driver supports 565 systems and as an option on older Sbus systems. This driver supports
566 both PCI and Sbus devices. This driver also supports the "qfe" quad 566 both PCI and Sbus devices. This driver also supports the "qfe" quad
567 100baseT device available in both PCI and Sbus configurations. 567 100baseT device available in both PCI and Sbus configurations.
568 568
569 To compile this driver as a module, choose M here: the module 569 To compile this driver as a module, choose M here: the module
570 will be called sunhme. 570 will be called sunhme.
571 571
572 config SUNBMAC 572 config SUNBMAC
573 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)" 573 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
574 depends on SBUS && EXPERIMENTAL 574 depends on SBUS && EXPERIMENTAL
575 select CRC32 575 select CRC32
576 help 576 help
577 This driver supports the "be" interface available as an Sbus option. 577 This driver supports the "be" interface available as an Sbus option.
578 This is Sun's older 100baseT Ethernet device. 578 This is Sun's older 100baseT Ethernet device.
579 579
580 To compile this driver as a module, choose M here: the module 580 To compile this driver as a module, choose M here: the module
581 will be called sunbmac. 581 will be called sunbmac.
582 582
583 config SUNQE 583 config SUNQE
584 tristate "Sun QuadEthernet support" 584 tristate "Sun QuadEthernet support"
585 depends on SBUS 585 depends on SBUS
586 select CRC32 586 select CRC32
587 help 587 help
588 This driver supports the "qe" 10baseT Ethernet device, available as 588 This driver supports the "qe" 10baseT Ethernet device, available as
589 an Sbus option. Note that this is not the same as Quad FastEthernet 589 an Sbus option. Note that this is not the same as Quad FastEthernet
590 "qfe" which is supported by the Happy Meal driver instead. 590 "qfe" which is supported by the Happy Meal driver instead.
591 591
592 To compile this driver as a module, choose M here: the module 592 To compile this driver as a module, choose M here: the module
593 will be called sunqe. 593 will be called sunqe.
594 594
595 config SUNGEM 595 config SUNGEM
596 tristate "Sun GEM support" 596 tristate "Sun GEM support"
597 depends on PCI 597 depends on PCI
598 select CRC32 598 select CRC32
599 help 599 help
600 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also 600 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
601 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>. 601 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
602 602
603 config CASSINI 603 config CASSINI
604 tristate "Sun Cassini support" 604 tristate "Sun Cassini support"
605 depends on PCI 605 depends on PCI
606 select CRC32 606 select CRC32
607 help 607 help
608 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also 608 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
609 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf> 609 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
610 610
611 config SUNVNET 611 config SUNVNET
612 tristate "Sun Virtual Network support" 612 tristate "Sun Virtual Network support"
613 depends on SUN_LDOMS 613 depends on SUN_LDOMS
614 help 614 help
615 Support for virtual network devices under Sun Logical Domains. 615 Support for virtual network devices under Sun Logical Domains.
616 616
617 config NET_VENDOR_3COM 617 config NET_VENDOR_3COM
618 bool "3COM cards" 618 bool "3COM cards"
619 depends on ISA || EISA || MCA || PCI 619 depends on ISA || EISA || MCA || PCI
620 help 620 help
621 If you have a network (Ethernet) card belonging to this class, say Y 621 If you have a network (Ethernet) card belonging to this class, say Y
622 and read the Ethernet-HOWTO, available from 622 and read the Ethernet-HOWTO, available from
623 <http://www.tldp.org/docs.html#howto>. 623 <http://www.tldp.org/docs.html#howto>.
624 624
625 Note that the answer to this question doesn't directly affect the 625 Note that the answer to this question doesn't directly affect the
626 kernel: saying N will just cause the configurator to skip all 626 kernel: saying N will just cause the configurator to skip all
627 the questions about 3COM cards. If you say Y, you will be asked for 627 the questions about 3COM cards. If you say Y, you will be asked for
628 your specific card in the following questions. 628 your specific card in the following questions.
629 629
630 config EL1 630 config EL1
631 tristate "3c501 \"EtherLink\" support" 631 tristate "3c501 \"EtherLink\" support"
632 depends on NET_VENDOR_3COM && ISA 632 depends on NET_VENDOR_3COM && ISA
633 ---help--- 633 ---help---
634 If you have a network (Ethernet) card of this type, say Y and read 634 If you have a network (Ethernet) card of this type, say Y and read
635 the Ethernet-HOWTO, available from 635 the Ethernet-HOWTO, available from
636 <http://www.tldp.org/docs.html#howto>. Also, consider buying a 636 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
637 new card, since the 3c501 is slow, broken, and obsolete: you will 637 new card, since the 3c501 is slow, broken, and obsolete: you will
638 have problems. Some people suggest to ping ("man ping") a nearby 638 have problems. Some people suggest to ping ("man ping") a nearby
639 machine every minute ("man cron") when using this card. 639 machine every minute ("man cron") when using this card.
640 640
641 To compile this driver as a module, choose M here. The module 641 To compile this driver as a module, choose M here. The module
642 will be called 3c501. 642 will be called 3c501.
643 643
644 config EL2 644 config EL2
645 tristate "3c503 \"EtherLink II\" support" 645 tristate "3c503 \"EtherLink II\" support"
646 depends on NET_VENDOR_3COM && ISA 646 depends on NET_VENDOR_3COM && ISA
647 select CRC32 647 select CRC32
648 help 648 help
649 If you have a network (Ethernet) card of this type, say Y and read 649 If you have a network (Ethernet) card of this type, say Y and read
650 the Ethernet-HOWTO, available from 650 the Ethernet-HOWTO, available from
651 <http://www.tldp.org/docs.html#howto>. 651 <http://www.tldp.org/docs.html#howto>.
652 652
653 To compile this driver as a module, choose M here. The module 653 To compile this driver as a module, choose M here. The module
654 will be called 3c503. 654 will be called 3c503.
655 655
656 config ELPLUS 656 config ELPLUS
657 tristate "3c505 \"EtherLink Plus\" support" 657 tristate "3c505 \"EtherLink Plus\" support"
658 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API 658 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
659 ---help--- 659 ---help---
660 Information about this network (Ethernet) card can be found in 660 Information about this network (Ethernet) card can be found in
661 <file:Documentation/networking/3c505.txt>. If you have a card of 661 <file:Documentation/networking/3c505.txt>. If you have a card of
662 this type, say Y and read the Ethernet-HOWTO, available from 662 this type, say Y and read the Ethernet-HOWTO, available from
663 <http://www.tldp.org/docs.html#howto>. 663 <http://www.tldp.org/docs.html#howto>.
664 664
665 To compile this driver as a module, choose M here. The module 665 To compile this driver as a module, choose M here. The module
666 will be called 3c505. 666 will be called 3c505.
667 667
668 config EL16 668 config EL16
669 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)" 669 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
670 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL 670 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
671 help 671 help
672 If you have a network (Ethernet) card of this type, say Y and read 672 If you have a network (Ethernet) card of this type, say Y and read
673 the Ethernet-HOWTO, available from 673 the Ethernet-HOWTO, available from
674 <http://www.tldp.org/docs.html#howto>. 674 <http://www.tldp.org/docs.html#howto>.
675 675
676 To compile this driver as a module, choose M here. The module 676 To compile this driver as a module, choose M here. The module
677 will be called 3c507. 677 will be called 3c507.
678 678
679 config EL3 679 config EL3
680 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support" 680 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
681 depends on NET_VENDOR_3COM && (ISA || EISA || MCA) 681 depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
682 ---help--- 682 ---help---
683 If you have a network (Ethernet) card belonging to the 3Com 683 If you have a network (Ethernet) card belonging to the 3Com
684 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available 684 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
685 from <http://www.tldp.org/docs.html#howto>. 685 from <http://www.tldp.org/docs.html#howto>.
686 686
687 If your card is not working you may need to use the DOS 687 If your card is not working you may need to use the DOS
688 setup disk to disable Plug & Play mode, and to select the default 688 setup disk to disable Plug & Play mode, and to select the default
689 media type. 689 media type.
690 690
691 To compile this driver as a module, choose M here. The module 691 To compile this driver as a module, choose M here. The module
692 will be called 3c509. 692 will be called 3c509.
693 693
694 config 3C515 694 config 3C515
695 tristate "3c515 ISA \"Fast EtherLink\"" 695 tristate "3c515 ISA \"Fast EtherLink\""
696 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API 696 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
697 help 697 help
698 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet 698 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
699 network card, say Y and read the Ethernet-HOWTO, available from 699 network card, say Y and read the Ethernet-HOWTO, available from
700 <http://www.tldp.org/docs.html#howto>. 700 <http://www.tldp.org/docs.html#howto>.
701 701
702 To compile this driver as a module, choose M here. The module 702 To compile this driver as a module, choose M here. The module
703 will be called 3c515. 703 will be called 3c515.
704 704
705 config ELMC 705 config ELMC
706 tristate "3c523 \"EtherLink/MC\" support" 706 tristate "3c523 \"EtherLink/MC\" support"
707 depends on NET_VENDOR_3COM && MCA_LEGACY 707 depends on NET_VENDOR_3COM && MCA_LEGACY
708 help 708 help
709 If you have a network (Ethernet) card of this type, say Y and read 709 If you have a network (Ethernet) card of this type, say Y and read
710 the Ethernet-HOWTO, available from 710 the Ethernet-HOWTO, available from
711 <http://www.tldp.org/docs.html#howto>. 711 <http://www.tldp.org/docs.html#howto>.
712 712
713 To compile this driver as a module, choose M here. The module 713 To compile this driver as a module, choose M here. The module
714 will be called 3c523. 714 will be called 3c523.
715 715
716 config ELMC_II 716 config ELMC_II
717 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)" 717 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
718 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY 718 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
719 help 719 help
720 If you have a network (Ethernet) card of this type, say Y and read 720 If you have a network (Ethernet) card of this type, say Y and read
721 the Ethernet-HOWTO, available from 721 the Ethernet-HOWTO, available from
722 <http://www.tldp.org/docs.html#howto>. 722 <http://www.tldp.org/docs.html#howto>.
723 723
724 To compile this driver as a module, choose M here. The module 724 To compile this driver as a module, choose M here. The module
725 will be called 3c527. 725 will be called 3c527.
726 726
727 config VORTEX 727 config VORTEX
728 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support" 728 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
729 depends on NET_VENDOR_3COM && (PCI || EISA) 729 depends on NET_VENDOR_3COM && (PCI || EISA)
730 select MII 730 select MII
731 ---help--- 731 ---help---
732 This option enables driver support for a large number of 10Mbps and 732 This option enables driver support for a large number of 10Mbps and
733 10/100Mbps EISA, PCI and PCMCIA 3Com network cards: 733 10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
734 734
735 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI 735 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
736 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI 736 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
737 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus 737 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
738 "Tornado" (3c905) PCI 738 "Tornado" (3c905) PCI
739 "Hurricane" (3c555/3cSOHO) PCI 739 "Hurricane" (3c555/3cSOHO) PCI
740 740
741 If you have such a card, say Y and read the Ethernet-HOWTO, 741 If you have such a card, say Y and read the Ethernet-HOWTO,
742 available from <http://www.tldp.org/docs.html#howto>. More 742 available from <http://www.tldp.org/docs.html#howto>. More
743 specific information is in 743 specific information is in
744 <file:Documentation/networking/vortex.txt> and in the comments at 744 <file:Documentation/networking/vortex.txt> and in the comments at
745 the beginning of <file:drivers/net/3c59x.c>. 745 the beginning of <file:drivers/net/3c59x.c>.
746 746
747 To compile this support as a module, choose M here. 747 To compile this support as a module, choose M here.
748 748
749 config TYPHOON 749 config TYPHOON
750 tristate "3cr990 series \"Typhoon\" support" 750 tristate "3cr990 series \"Typhoon\" support"
751 depends on NET_VENDOR_3COM && PCI 751 depends on NET_VENDOR_3COM && PCI
752 select CRC32 752 select CRC32
753 ---help--- 753 ---help---
754 This option enables driver support for the 3cr990 series of cards: 754 This option enables driver support for the 3cr990 series of cards:
755 755
756 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97, 756 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
757 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server, 757 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
758 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR 758 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
759 759
760 If you have a network (Ethernet) card of this type, say Y and read 760 If you have a network (Ethernet) card of this type, say Y and read
761 the Ethernet-HOWTO, available from 761 the Ethernet-HOWTO, available from
762 <http://www.tldp.org/docs.html#howto>. 762 <http://www.tldp.org/docs.html#howto>.
763 763
764 To compile this driver as a module, choose M here. The module 764 To compile this driver as a module, choose M here. The module
765 will be called typhoon. 765 will be called typhoon.
766 766
767 config LANCE 767 config LANCE
768 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support" 768 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
769 depends on ISA && ISA_DMA_API 769 depends on ISA && ISA_DMA_API
770 help 770 help
771 If you have a network (Ethernet) card of this type, say Y and read 771 If you have a network (Ethernet) card of this type, say Y and read
772 the Ethernet-HOWTO, available from 772 the Ethernet-HOWTO, available from
773 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are 773 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
774 of this type. 774 of this type.
775 775
776 To compile this driver as a module, choose M here: the module 776 To compile this driver as a module, choose M here: the module
777 will be called lance. This is recommended. 777 will be called lance. This is recommended.
778 778
779 config NET_VENDOR_SMC 779 config NET_VENDOR_SMC
780 bool "Western Digital/SMC cards" 780 bool "Western Digital/SMC cards"
781 depends on ISA || MCA || EISA || MAC 781 depends on ISA || MCA || EISA || MAC
782 help 782 help
783 If you have a network (Ethernet) card belonging to this class, say Y 783 If you have a network (Ethernet) card belonging to this class, say Y
784 and read the Ethernet-HOWTO, available from 784 and read the Ethernet-HOWTO, available from
785 <http://www.tldp.org/docs.html#howto>. 785 <http://www.tldp.org/docs.html#howto>.
786 786
787 Note that the answer to this question doesn't directly affect the 787 Note that the answer to this question doesn't directly affect the
788 kernel: saying N will just cause the configurator to skip all 788 kernel: saying N will just cause the configurator to skip all
789 the questions about Western Digital cards. If you say Y, you will be 789 the questions about Western Digital cards. If you say Y, you will be
790 asked for your specific card in the following questions. 790 asked for your specific card in the following questions.
791 791
792 config WD80x3 792 config WD80x3
793 tristate "WD80*3 support" 793 tristate "WD80*3 support"
794 depends on NET_VENDOR_SMC && ISA 794 depends on NET_VENDOR_SMC && ISA
795 select CRC32 795 select CRC32
796 help 796 help
797 If you have a network (Ethernet) card of this type, say Y and read 797 If you have a network (Ethernet) card of this type, say Y and read
798 the Ethernet-HOWTO, available from 798 the Ethernet-HOWTO, available from
799 <http://www.tldp.org/docs.html#howto>. 799 <http://www.tldp.org/docs.html#howto>.
800 800
801 To compile this driver as a module, choose M here. The module 801 To compile this driver as a module, choose M here. The module
802 will be called wd. 802 will be called wd.
803 803
804 config ULTRAMCA 804 config ULTRAMCA
805 tristate "SMC Ultra MCA support" 805 tristate "SMC Ultra MCA support"
806 depends on NET_VENDOR_SMC && MCA 806 depends on NET_VENDOR_SMC && MCA
807 select CRC32 807 select CRC32
808 help 808 help
809 If you have a network (Ethernet) card of this type and are running 809 If you have a network (Ethernet) card of this type and are running
810 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO, 810 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
811 available from <http://www.tldp.org/docs.html#howto>. 811 available from <http://www.tldp.org/docs.html#howto>.
812 812
813 To compile this driver as a module, choose M here. The module 813 To compile this driver as a module, choose M here. The module
814 will be called smc-mca. 814 will be called smc-mca.
815 815
816 config ULTRA 816 config ULTRA
817 tristate "SMC Ultra support" 817 tristate "SMC Ultra support"
818 depends on NET_VENDOR_SMC && ISA 818 depends on NET_VENDOR_SMC && ISA
819 select CRC32 819 select CRC32
820 ---help--- 820 ---help---
821 If you have a network (Ethernet) card of this type, say Y and read 821 If you have a network (Ethernet) card of this type, say Y and read
822 the Ethernet-HOWTO, available from 822 the Ethernet-HOWTO, available from
823 <http://www.tldp.org/docs.html#howto>. 823 <http://www.tldp.org/docs.html#howto>.
824 824
825 Important: There have been many reports that, with some motherboards 825 Important: There have been many reports that, with some motherboards
826 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible, 826 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
827 such as some BusLogic models) causes corruption problems with many 827 such as some BusLogic models) causes corruption problems with many
828 operating systems. The Linux smc-ultra driver has a work-around for 828 operating systems. The Linux smc-ultra driver has a work-around for
829 this but keep it in mind if you have such a SCSI card and have 829 this but keep it in mind if you have such a SCSI card and have
830 problems. 830 problems.
831 831
832 To compile this driver as a module, choose M here. The module 832 To compile this driver as a module, choose M here. The module
833 will be called smc-ultra. 833 will be called smc-ultra.
834 834
835 config ULTRA32 835 config ULTRA32
836 tristate "SMC Ultra32 EISA support" 836 tristate "SMC Ultra32 EISA support"
837 depends on NET_VENDOR_SMC && EISA 837 depends on NET_VENDOR_SMC && EISA
838 select CRC32 838 select CRC32
839 help 839 help
840 If you have a network (Ethernet) card of this type, say Y and read 840 If you have a network (Ethernet) card of this type, say Y and read
841 the Ethernet-HOWTO, available from 841 the Ethernet-HOWTO, available from
842 <http://www.tldp.org/docs.html#howto>. 842 <http://www.tldp.org/docs.html#howto>.
843 843
844 To compile this driver as a module, choose M here. The module 844 To compile this driver as a module, choose M here. The module
845 will be called smc-ultra32. 845 will be called smc-ultra32.
846 846
847 config BFIN_MAC 847 config BFIN_MAC
848 tristate "Blackfin on-chip MAC support" 848 tristate "Blackfin on-chip MAC support"
849 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537) 849 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
850 select CRC32 850 select CRC32
851 select MII 851 select MII
852 select PHYLIB 852 select PHYLIB
853 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE 853 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
854 help 854 help
855 This is the driver for Blackfin on-chip mac device. Say Y if you want it 855 This is the driver for Blackfin on-chip mac device. Say Y if you want it
856 compiled into the kernel. This driver is also available as a module 856 compiled into the kernel. This driver is also available as a module
857 ( = code which can be inserted in and removed from the running kernel 857 ( = code which can be inserted in and removed from the running kernel
858 whenever you want). The module will be called bfin_mac. 858 whenever you want). The module will be called bfin_mac.
859 859
860 config BFIN_MAC_USE_L1 860 config BFIN_MAC_USE_L1
861 bool "Use L1 memory for rx/tx packets" 861 bool "Use L1 memory for rx/tx packets"
862 depends on BFIN_MAC && (BF527 || BF537) 862 depends on BFIN_MAC && (BF527 || BF537)
863 default y 863 default y
864 help 864 help
865 To get maximum network performance, you should use L1 memory as rx/tx buffers. 865 To get maximum network performance, you should use L1 memory as rx/tx buffers.
866 Say N here if you want to reserve L1 memory for other uses. 866 Say N here if you want to reserve L1 memory for other uses.
867 867
868 config BFIN_TX_DESC_NUM 868 config BFIN_TX_DESC_NUM
869 int "Number of transmit buffer packets" 869 int "Number of transmit buffer packets"
870 depends on BFIN_MAC 870 depends on BFIN_MAC
871 range 6 10 if BFIN_MAC_USE_L1 871 range 6 10 if BFIN_MAC_USE_L1
872 range 10 100 872 range 10 100
873 default "10" 873 default "10"
874 help 874 help
875 Set the number of buffer packets used in driver. 875 Set the number of buffer packets used in driver.
876 876
877 config BFIN_RX_DESC_NUM 877 config BFIN_RX_DESC_NUM
878 int "Number of receive buffer packets" 878 int "Number of receive buffer packets"
879 depends on BFIN_MAC 879 depends on BFIN_MAC
880 range 20 100 if BFIN_MAC_USE_L1 880 range 20 100 if BFIN_MAC_USE_L1
881 range 20 800 881 range 20 800
882 default "20" 882 default "20"
883 help 883 help
884 Set the number of buffer packets used in driver. 884 Set the number of buffer packets used in driver.
885 885
886 config BFIN_MAC_USE_HWSTAMP 886 config BFIN_MAC_USE_HWSTAMP
887 bool "Use IEEE 1588 hwstamp" 887 bool "Use IEEE 1588 hwstamp"
888 depends on BFIN_MAC && BF518 888 depends on BFIN_MAC && BF518
889 default y 889 default y
890 help 890 help
891 To support the IEEE 1588 Precision Time Protocol (PTP), select y here 891 To support the IEEE 1588 Precision Time Protocol (PTP), select y here
892 892
893 config SMC9194 893 config SMC9194
894 tristate "SMC 9194 support" 894 tristate "SMC 9194 support"
895 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN) 895 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
896 select CRC32 896 select CRC32
897 ---help--- 897 ---help---
898 This is support for the SMC9xxx based Ethernet cards. Choose this 898 This is support for the SMC9xxx based Ethernet cards. Choose this
899 option if you have a DELL laptop with the docking station, or 899 option if you have a DELL laptop with the docking station, or
900 another SMC9192/9194 based chipset. Say Y if you want it compiled 900 another SMC9192/9194 based chipset. Say Y if you want it compiled
901 into the kernel, and read the file 901 into the kernel, and read the file
902 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO, 902 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
903 available from <http://www.tldp.org/docs.html#howto>. 903 available from <http://www.tldp.org/docs.html#howto>.
904 904
905 To compile this driver as a module, choose M here. The module 905 To compile this driver as a module, choose M here. The module
906 will be called smc9194. 906 will be called smc9194.
907 907
908 config SMC91X 908 config SMC91X
909 tristate "SMC 91C9x/91C1xxx support" 909 tristate "SMC 91C9x/91C1xxx support"
910 select CRC32 910 select CRC32
911 select MII 911 select MII
912 depends on ARM || M32R || SUPERH || \ 912 depends on ARM || M32R || SUPERH || \
913 MIPS || BLACKFIN || MN10300 || COLDFIRE 913 MIPS || BLACKFIN || MN10300 || COLDFIRE
914 help 914 help
915 This is a driver for SMC's 91x series of Ethernet chipsets, 915 This is a driver for SMC's 91x series of Ethernet chipsets,
916 including the SMC91C94 and the SMC91C111. Say Y if you want it 916 including the SMC91C94 and the SMC91C111. Say Y if you want it
917 compiled into the kernel, and read the file 917 compiled into the kernel, and read the file
918 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO, 918 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
919 available from <http://www.tldp.org/docs.html#howto>. 919 available from <http://www.tldp.org/docs.html#howto>.
920 920
921 This driver is also available as a module ( = code which can be 921 This driver is also available as a module ( = code which can be
922 inserted in and removed from the running kernel whenever you want). 922 inserted in and removed from the running kernel whenever you want).
923 The module will be called smc91x. If you want to compile it as a 923 The module will be called smc91x. If you want to compile it as a
924 module, say M here and read <file:Documentation/kbuild/modules.txt>. 924 module, say M here and read <file:Documentation/kbuild/modules.txt>.
925 925
926 config PXA168_ETH 926 config PXA168_ETH
927 tristate "Marvell pxa168 ethernet support" 927 tristate "Marvell pxa168 ethernet support"
928 depends on CPU_PXA168 928 depends on CPU_PXA168
929 select PHYLIB 929 select PHYLIB
930 help 930 help
931 This driver supports the pxa168 Ethernet ports. 931 This driver supports the pxa168 Ethernet ports.
932 932
933 To compile this driver as a module, choose M here. The module 933 To compile this driver as a module, choose M here. The module
934 will be called pxa168_eth. 934 will be called pxa168_eth.
935 935
936 config NET_NETX 936 config NET_NETX
937 tristate "NetX Ethernet support" 937 tristate "NetX Ethernet support"
938 select MII 938 select MII
939 depends on ARCH_NETX 939 depends on ARCH_NETX
940 help 940 help
941 This is support for the Hilscher netX builtin Ethernet ports 941 This is support for the Hilscher netX builtin Ethernet ports
942 942
943 To compile this driver as a module, choose M here. The module 943 To compile this driver as a module, choose M here. The module
944 will be called netx-eth. 944 will be called netx-eth.
945 945
946 config TI_DAVINCI_EMAC 946 config TI_DAVINCI_EMAC
947 tristate "TI DaVinci EMAC Support" 947 tristate "TI DaVinci EMAC Support"
948 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 ) 948 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
949 select TI_DAVINCI_MDIO 949 select TI_DAVINCI_MDIO
950 select TI_DAVINCI_CPDMA 950 select TI_DAVINCI_CPDMA
951 select PHYLIB 951 select PHYLIB
952 help 952 help
953 This driver supports TI's DaVinci Ethernet . 953 This driver supports TI's DaVinci Ethernet .
954 954
955 To compile this driver as a module, choose M here: the module 955 To compile this driver as a module, choose M here: the module
956 will be called davinci_emac_driver. This is recommended. 956 will be called davinci_emac_driver. This is recommended.
957 957
958 config TI_DAVINCI_MDIO 958 config TI_DAVINCI_MDIO
959 tristate "TI DaVinci MDIO Support" 959 tristate "TI DaVinci MDIO Support"
960 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 ) 960 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
961 select PHYLIB 961 select PHYLIB
962 help 962 help
963 This driver supports TI's DaVinci MDIO module. 963 This driver supports TI's DaVinci MDIO module.
964 964
965 To compile this driver as a module, choose M here: the module 965 To compile this driver as a module, choose M here: the module
966 will be called davinci_mdio. This is recommended. 966 will be called davinci_mdio. This is recommended.
967 967
968 config TI_DAVINCI_CPDMA 968 config TI_DAVINCI_CPDMA
969 tristate "TI DaVinci CPDMA Support" 969 tristate "TI DaVinci CPDMA Support"
970 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 ) 970 depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
971 help 971 help
972 This driver supports TI's DaVinci CPDMA dma engine. 972 This driver supports TI's DaVinci CPDMA dma engine.
973 973
974 To compile this driver as a module, choose M here: the module 974 To compile this driver as a module, choose M here: the module
975 will be called davinci_cpdma. This is recommended. 975 will be called davinci_cpdma. This is recommended.
976 976
977 config DM9000 977 config DM9000
978 tristate "DM9000 support" 978 tristate "DM9000 support"
979 depends on ARM || BLACKFIN || MIPS 979 depends on ARM || BLACKFIN || MIPS
980 select CRC32 980 select CRC32
981 select MII 981 select MII
982 ---help--- 982 ---help---
983 Support for DM9000 chipset. 983 Support for DM9000 chipset.
984 984
985 To compile this driver as a module, choose M here. The module 985 To compile this driver as a module, choose M here. The module
986 will be called dm9000. 986 will be called dm9000.
987 987
988 config DM9000_DEBUGLEVEL 988 config DM9000_DEBUGLEVEL
989 int "DM9000 maximum debug level" 989 int "DM9000 maximum debug level"
990 depends on DM9000 990 depends on DM9000
991 default 4 991 default 4
992 help 992 help
993 The maximum level of debugging code compiled into the DM9000 993 The maximum level of debugging code compiled into the DM9000
994 driver. 994 driver.
995 995
996 config DM9000_FORCE_SIMPLE_PHY_POLL 996 config DM9000_FORCE_SIMPLE_PHY_POLL
997 bool "Force simple NSR based PHY polling" 997 bool "Force simple NSR based PHY polling"
998 depends on DM9000 998 depends on DM9000
999 ---help--- 999 ---help---
1000 This configuration forces the DM9000 to use the NSR's LinkStatus 1000 This configuration forces the DM9000 to use the NSR's LinkStatus
1001 bit to determine if the link is up or down instead of the more 1001 bit to determine if the link is up or down instead of the more
1002 costly MII PHY reads. Note, this will not work if the chip is 1002 costly MII PHY reads. Note, this will not work if the chip is
1003 operating with an external PHY. 1003 operating with an external PHY.
1004 1004
1005 config ENC28J60 1005 config ENC28J60
1006 tristate "ENC28J60 support" 1006 tristate "ENC28J60 support"
1007 depends on EXPERIMENTAL && SPI && NET_ETHERNET 1007 depends on EXPERIMENTAL && SPI && NET_ETHERNET
1008 select CRC32 1008 select CRC32
1009 ---help--- 1009 ---help---
1010 Support for the Microchip EN28J60 ethernet chip. 1010 Support for the Microchip EN28J60 ethernet chip.
1011 1011
1012 To compile this driver as a module, choose M here. The module will be 1012 To compile this driver as a module, choose M here. The module will be
1013 called enc28j60. 1013 called enc28j60.
1014 1014
1015 config ENC28J60_WRITEVERIFY 1015 config ENC28J60_WRITEVERIFY
1016 bool "Enable write verify" 1016 bool "Enable write verify"
1017 depends on ENC28J60 1017 depends on ENC28J60
1018 ---help--- 1018 ---help---
1019 Enable the verify after the buffer write useful for debugging purpose. 1019 Enable the verify after the buffer write useful for debugging purpose.
1020 If unsure, say N. 1020 If unsure, say N.
1021 1021
1022 config ETHOC 1022 config ETHOC
1023 tristate "OpenCores 10/100 Mbps Ethernet MAC support" 1023 tristate "OpenCores 10/100 Mbps Ethernet MAC support"
1024 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA 1024 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
1025 select MII 1025 select MII
1026 select PHYLIB 1026 select PHYLIB
1027 select CRC32 1027 select CRC32
1028 select BITREVERSE 1028 select BITREVERSE
1029 help 1029 help
1030 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC. 1030 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
1031 1031
1032 config GRETH 1032 config GRETH
1033 tristate "Aeroflex Gaisler GRETH Ethernet MAC support" 1033 tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
1034 depends on SPARC 1034 depends on SPARC
1035 select PHYLIB 1035 select PHYLIB
1036 select CRC32 1036 select CRC32
1037 help 1037 help
1038 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC. 1038 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
1039 1039
1040 config SMC911X 1040 config SMC911X
1041 tristate "SMSC LAN911[5678] support" 1041 tristate "SMSC LAN911[5678] support"
1042 select CRC32 1042 select CRC32
1043 select MII 1043 select MII
1044 depends on ARM || SUPERH || MN10300 1044 depends on ARM || SUPERH || MN10300
1045 help 1045 help
1046 This is a driver for SMSC's LAN911x series of Ethernet chipsets 1046 This is a driver for SMSC's LAN911x series of Ethernet chipsets
1047 including the new LAN9115, LAN9116, LAN9117, and LAN9118. 1047 including the new LAN9115, LAN9116, LAN9117, and LAN9118.
1048 Say Y if you want it compiled into the kernel, 1048 Say Y if you want it compiled into the kernel,
1049 and read the Ethernet-HOWTO, available from 1049 and read the Ethernet-HOWTO, available from
1050 <http://www.tldp.org/docs.html#howto>. 1050 <http://www.tldp.org/docs.html#howto>.
1051 1051
1052 This driver is also available as a module. The module will be 1052 This driver is also available as a module. The module will be
1053 called smc911x. If you want to compile it as a module, say M 1053 called smc911x. If you want to compile it as a module, say M
1054 here and read <file:Documentation/kbuild/modules.txt> 1054 here and read <file:Documentation/kbuild/modules.txt>
1055 1055
1056 config SMSC911X 1056 config SMSC911X
1057 tristate "SMSC LAN911x/LAN921x families embedded ethernet support" 1057 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
1058 depends on ARM || SUPERH || BLACKFIN || MIPS || MN10300 1058 depends on ARM || SUPERH || BLACKFIN || MIPS || MN10300
1059 select CRC32 1059 select CRC32
1060 select MII 1060 select MII
1061 select PHYLIB 1061 select PHYLIB
1062 ---help--- 1062 ---help---
1063 Say Y here if you want support for SMSC LAN911x and LAN921x families 1063 Say Y here if you want support for SMSC LAN911x and LAN921x families
1064 of ethernet controllers. 1064 of ethernet controllers.
1065 1065
1066 To compile this driver as a module, choose M here and read 1066 To compile this driver as a module, choose M here and read
1067 <file:Documentation/networking/net-modules.txt>. The module 1067 <file:Documentation/networking/net-modules.txt>. The module
1068 will be called smsc911x. 1068 will be called smsc911x.
1069 1069
1070 config SMSC911X_ARCH_HOOKS 1070 config SMSC911X_ARCH_HOOKS
1071 def_bool n 1071 def_bool n
1072 depends on SMSC911X 1072 depends on SMSC911X
1073 help 1073 help
1074 If the arch enables this, it allows the arch to implement various 1074 If the arch enables this, it allows the arch to implement various
1075 hooks for more comprehensive interrupt control and also to override 1075 hooks for more comprehensive interrupt control and also to override
1076 the source of the MAC address. 1076 the source of the MAC address.
1077 1077
1078 config NET_VENDOR_RACAL 1078 config NET_VENDOR_RACAL
1079 bool "Racal-Interlan (Micom) NI cards" 1079 bool "Racal-Interlan (Micom) NI cards"
1080 depends on ISA 1080 depends on ISA
1081 help 1081 help
1082 If you have a network (Ethernet) card belonging to this class, such 1082 If you have a network (Ethernet) card belonging to this class, such
1083 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO, 1083 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
1084 available from <http://www.tldp.org/docs.html#howto>. 1084 available from <http://www.tldp.org/docs.html#howto>.
1085 1085
1086 Note that the answer to this question doesn't directly affect the 1086 Note that the answer to this question doesn't directly affect the
1087 kernel: saying N will just cause the configurator to skip all 1087 kernel: saying N will just cause the configurator to skip all
1088 the questions about NI cards. If you say Y, you will be asked for 1088 the questions about NI cards. If you say Y, you will be asked for
1089 your specific card in the following questions. 1089 your specific card in the following questions.
1090 1090
1091 config NI5010 1091 config NI5010
1092 tristate "NI5010 support (EXPERIMENTAL)" 1092 tristate "NI5010 support (EXPERIMENTAL)"
1093 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP 1093 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
1094 ---help--- 1094 ---help---
1095 If you have a network (Ethernet) card of this type, say Y and read 1095 If you have a network (Ethernet) card of this type, say Y and read
1096 the Ethernet-HOWTO, available from 1096 the Ethernet-HOWTO, available from
1097 <http://www.tldp.org/docs.html#howto>. Note that this is still 1097 <http://www.tldp.org/docs.html#howto>. Note that this is still
1098 experimental code. 1098 experimental code.
1099 1099
1100 To compile this driver as a module, choose M here. The module 1100 To compile this driver as a module, choose M here. The module
1101 will be called ni5010. 1101 will be called ni5010.
1102 1102
1103 config NI52 1103 config NI52
1104 tristate "NI5210 support" 1104 tristate "NI5210 support"
1105 depends on NET_VENDOR_RACAL && ISA 1105 depends on NET_VENDOR_RACAL && ISA
1106 help 1106 help
1107 If you have a network (Ethernet) card of this type, say Y and read 1107 If you have a network (Ethernet) card of this type, say Y and read
1108 the Ethernet-HOWTO, available from 1108 the Ethernet-HOWTO, available from
1109 <http://www.tldp.org/docs.html#howto>. 1109 <http://www.tldp.org/docs.html#howto>.
1110 1110
1111 To compile this driver as a module, choose M here. The module 1111 To compile this driver as a module, choose M here. The module
1112 will be called ni52. 1112 will be called ni52.
1113 1113
1114 config NI65 1114 config NI65
1115 tristate "NI6510 support" 1115 tristate "NI6510 support"
1116 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API 1116 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
1117 help 1117 help
1118 If you have a network (Ethernet) card of this type, say Y and read 1118 If you have a network (Ethernet) card of this type, say Y and read
1119 the Ethernet-HOWTO, available from 1119 the Ethernet-HOWTO, available from
1120 <http://www.tldp.org/docs.html#howto>. 1120 <http://www.tldp.org/docs.html#howto>.
1121 1121
1122 To compile this driver as a module, choose M here. The module 1122 To compile this driver as a module, choose M here. The module
1123 will be called ni65. 1123 will be called ni65.
1124 1124
1125 config DNET 1125 config DNET
1126 tristate "Dave ethernet support (DNET)" 1126 tristate "Dave ethernet support (DNET)"
1127 depends on NET_ETHERNET && HAS_IOMEM 1127 depends on NET_ETHERNET && HAS_IOMEM
1128 select PHYLIB 1128 select PHYLIB
1129 help 1129 help
1130 The Dave ethernet interface (DNET) is found on Qong Board FPGA. 1130 The Dave ethernet interface (DNET) is found on Qong Board FPGA.
1131 Say Y to include support for the DNET chip. 1131 Say Y to include support for the DNET chip.
1132 1132
1133 To compile this driver as a module, choose M here: the module 1133 To compile this driver as a module, choose M here: the module
1134 will be called dnet. 1134 will be called dnet.
1135 1135
1136 source "drivers/net/tulip/Kconfig" 1136 source "drivers/net/tulip/Kconfig"
1137 1137
1138 config AT1700 1138 config AT1700
1139 tristate "AT1700/1720 support (EXPERIMENTAL)" 1139 tristate "AT1700/1720 support (EXPERIMENTAL)"
1140 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL 1140 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
1141 select CRC32 1141 select CRC32
1142 ---help--- 1142 ---help---
1143 If you have a network (Ethernet) card of this type, say Y and read 1143 If you have a network (Ethernet) card of this type, say Y and read
1144 the Ethernet-HOWTO, available from 1144 the Ethernet-HOWTO, available from
1145 <http://www.tldp.org/docs.html#howto>. 1145 <http://www.tldp.org/docs.html#howto>.
1146 1146
1147 To compile this driver as a module, choose M here. The module 1147 To compile this driver as a module, choose M here. The module
1148 will be called at1700. 1148 will be called at1700.
1149 1149
1150 config DEPCA 1150 config DEPCA
1151 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support" 1151 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
1152 depends on ISA || EISA || MCA 1152 depends on ISA || EISA || MCA
1153 select CRC32 1153 select CRC32
1154 ---help--- 1154 ---help---
1155 If you have a network (Ethernet) card of this type, say Y and read 1155 If you have a network (Ethernet) card of this type, say Y and read
1156 the Ethernet-HOWTO, available from 1156 the Ethernet-HOWTO, available from
1157 <http://www.tldp.org/docs.html#howto> as well as 1157 <http://www.tldp.org/docs.html#howto> as well as
1158 <file:drivers/net/depca.c>. 1158 <file:drivers/net/depca.c>.
1159 1159
1160 To compile this driver as a module, choose M here. The module 1160 To compile this driver as a module, choose M here. The module
1161 will be called depca. 1161 will be called depca.
1162 1162
1163 config HP100 1163 config HP100
1164 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support" 1164 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
1165 depends on ISA || EISA || PCI 1165 depends on ISA || EISA || PCI
1166 help 1166 help
1167 If you have a network (Ethernet) card of this type, say Y and read 1167 If you have a network (Ethernet) card of this type, say Y and read
1168 the Ethernet-HOWTO, available from 1168 the Ethernet-HOWTO, available from
1169 <http://www.tldp.org/docs.html#howto>. 1169 <http://www.tldp.org/docs.html#howto>.
1170 1170
1171 To compile this driver as a module, choose M here. The module 1171 To compile this driver as a module, choose M here. The module
1172 will be called hp100. 1172 will be called hp100.
1173 1173
1174 config NET_ISA 1174 config NET_ISA
1175 bool "Other ISA cards" 1175 bool "Other ISA cards"
1176 depends on ISA 1176 depends on ISA
1177 ---help--- 1177 ---help---
1178 If your network (Ethernet) card hasn't been mentioned yet and its 1178 If your network (Ethernet) card hasn't been mentioned yet and its
1179 bus system (that's the way the cards talks to the other components 1179 bus system (that's the way the cards talks to the other components
1180 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y. 1180 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
1181 Make sure you know the name of your card. Read the Ethernet-HOWTO, 1181 Make sure you know the name of your card. Read the Ethernet-HOWTO,
1182 available from <http://www.tldp.org/docs.html#howto>. 1182 available from <http://www.tldp.org/docs.html#howto>.
1183 1183
1184 If unsure, say Y. 1184 If unsure, say Y.
1185 1185
1186 Note that the answer to this question doesn't directly affect the 1186 Note that the answer to this question doesn't directly affect the
1187 kernel: saying N will just cause the configurator to skip all 1187 kernel: saying N will just cause the configurator to skip all
1188 the remaining ISA network card questions. If you say Y, you will be 1188 the remaining ISA network card questions. If you say Y, you will be
1189 asked for your specific card in the following questions. 1189 asked for your specific card in the following questions.
1190 1190
1191 config E2100 1191 config E2100
1192 tristate "Cabletron E21xx support" 1192 tristate "Cabletron E21xx support"
1193 depends on NET_ISA 1193 depends on NET_ISA
1194 select CRC32 1194 select CRC32
1195 help 1195 help
1196 If you have a network (Ethernet) card of this type, say Y and read 1196 If you have a network (Ethernet) card of this type, say Y and read
1197 the Ethernet-HOWTO, available from 1197 the Ethernet-HOWTO, available from
1198 <http://www.tldp.org/docs.html#howto>. 1198 <http://www.tldp.org/docs.html#howto>.
1199 1199
1200 To compile this driver as a module, choose M here. The module 1200 To compile this driver as a module, choose M here. The module
1201 will be called e2100. 1201 will be called e2100.
1202 1202
1203 config EWRK3 1203 config EWRK3
1204 tristate "EtherWORKS 3 (DE203, DE204, DE205) support" 1204 tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
1205 depends on NET_ISA 1205 depends on NET_ISA
1206 select CRC32 1206 select CRC32
1207 ---help--- 1207 ---help---
1208 This driver supports the DE203, DE204 and DE205 network (Ethernet) 1208 This driver supports the DE203, DE204 and DE205 network (Ethernet)
1209 cards. If this is for you, say Y and read 1209 cards. If this is for you, say Y and read
1210 <file:Documentation/networking/ewrk3.txt> in the kernel source as 1210 <file:Documentation/networking/ewrk3.txt> in the kernel source as
1211 well as the Ethernet-HOWTO, available from 1211 well as the Ethernet-HOWTO, available from
1212 <http://www.tldp.org/docs.html#howto>. 1212 <http://www.tldp.org/docs.html#howto>.
1213 1213
1214 To compile this driver as a module, choose M here. The module 1214 To compile this driver as a module, choose M here. The module
1215 will be called ewrk3. 1215 will be called ewrk3.
1216 1216
1217 config EEXPRESS 1217 config EEXPRESS
1218 tristate "EtherExpress 16 support" 1218 tristate "EtherExpress 16 support"
1219 depends on NET_ISA 1219 depends on NET_ISA
1220 ---help--- 1220 ---help---
1221 If you have an EtherExpress16 network (Ethernet) card, say Y and 1221 If you have an EtherExpress16 network (Ethernet) card, say Y and
1222 read the Ethernet-HOWTO, available from 1222 read the Ethernet-HOWTO, available from
1223 <http://www.tldp.org/docs.html#howto>. Note that the Intel 1223 <http://www.tldp.org/docs.html#howto>. Note that the Intel
1224 EtherExpress16 card used to be regarded as a very poor choice 1224 EtherExpress16 card used to be regarded as a very poor choice
1225 because the driver was very unreliable. We now have a new driver 1225 because the driver was very unreliable. We now have a new driver
1226 that should do better. 1226 that should do better.
1227 1227
1228 To compile this driver as a module, choose M here. The module 1228 To compile this driver as a module, choose M here. The module
1229 will be called eexpress. 1229 will be called eexpress.
1230 1230
1231 config EEXPRESS_PRO 1231 config EEXPRESS_PRO
1232 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support" 1232 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
1233 depends on NET_ISA 1233 depends on NET_ISA
1234 ---help--- 1234 ---help---
1235 If you have a network (Ethernet) card of this type, say Y. This 1235 If you have a network (Ethernet) card of this type, say Y. This
1236 driver supports Intel i82595{FX,TX} based boards. Note however 1236 driver supports Intel i82595{FX,TX} based boards. Note however
1237 that the EtherExpress PRO/100 Ethernet card has its own separate 1237 that the EtherExpress PRO/100 Ethernet card has its own separate
1238 driver. Please read the Ethernet-HOWTO, available from 1238 driver. Please read the Ethernet-HOWTO, available from
1239 <http://www.tldp.org/docs.html#howto>. 1239 <http://www.tldp.org/docs.html#howto>.
1240 1240
1241 To compile this driver as a module, choose M here. The module 1241 To compile this driver as a module, choose M here. The module
1242 will be called eepro. 1242 will be called eepro.
1243 1243
1244 config HPLAN_PLUS 1244 config HPLAN_PLUS
1245 tristate "HP PCLAN+ (27247B and 27252A) support" 1245 tristate "HP PCLAN+ (27247B and 27252A) support"
1246 depends on NET_ISA 1246 depends on NET_ISA
1247 select CRC32 1247 select CRC32
1248 help 1248 help
1249 If you have a network (Ethernet) card of this type, say Y and read 1249 If you have a network (Ethernet) card of this type, say Y and read
1250 the Ethernet-HOWTO, available from 1250 the Ethernet-HOWTO, available from
1251 <http://www.tldp.org/docs.html#howto>. 1251 <http://www.tldp.org/docs.html#howto>.
1252 1252
1253 To compile this driver as a module, choose M here. The module 1253 To compile this driver as a module, choose M here. The module
1254 will be called hp-plus. 1254 will be called hp-plus.
1255 1255
1256 config HPLAN 1256 config HPLAN
1257 tristate "HP PCLAN (27245 and other 27xxx series) support" 1257 tristate "HP PCLAN (27245 and other 27xxx series) support"
1258 depends on NET_ISA 1258 depends on NET_ISA
1259 select CRC32 1259 select CRC32
1260 help 1260 help
1261 If you have a network (Ethernet) card of this type, say Y and read 1261 If you have a network (Ethernet) card of this type, say Y and read
1262 the Ethernet-HOWTO, available from 1262 the Ethernet-HOWTO, available from
1263 <http://www.tldp.org/docs.html#howto>. 1263 <http://www.tldp.org/docs.html#howto>.
1264 1264
1265 To compile this driver as a module, choose M here. The module 1265 To compile this driver as a module, choose M here. The module
1266 will be called hp. 1266 will be called hp.
1267 1267
1268 config LP486E 1268 config LP486E
1269 tristate "LP486E on board Ethernet" 1269 tristate "LP486E on board Ethernet"
1270 depends on NET_ISA 1270 depends on NET_ISA
1271 help 1271 help
1272 Say Y here to support the 82596-based on-board Ethernet controller 1272 Say Y here to support the 82596-based on-board Ethernet controller
1273 for the Panther motherboard, which is one of the two shipped in the 1273 for the Panther motherboard, which is one of the two shipped in the
1274 Intel Professional Workstation. 1274 Intel Professional Workstation.
1275 1275
1276 config ETH16I 1276 config ETH16I
1277 tristate "ICL EtherTeam 16i/32 support" 1277 tristate "ICL EtherTeam 16i/32 support"
1278 depends on NET_ISA 1278 depends on NET_ISA
1279 help 1279 help
1280 If you have a network (Ethernet) card of this type, say Y and read 1280 If you have a network (Ethernet) card of this type, say Y and read
1281 the Ethernet-HOWTO, available from 1281 the Ethernet-HOWTO, available from
1282 <http://www.tldp.org/docs.html#howto>. 1282 <http://www.tldp.org/docs.html#howto>.
1283 1283
1284 To compile this driver as a module, choose M here. The module 1284 To compile this driver as a module, choose M here. The module
1285 will be called eth16i. 1285 will be called eth16i.
1286 1286
1287 config NE2000 1287 config NE2000
1288 tristate "NE2000/NE1000 support" 1288 tristate "NE2000/NE1000 support"
1289 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX 1289 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX
1290 select CRC32 1290 select CRC32
1291 ---help--- 1291 ---help---
1292 If you have a network (Ethernet) card of this type, say Y and read 1292 If you have a network (Ethernet) card of this type, say Y and read
1293 the Ethernet-HOWTO, available from 1293 the Ethernet-HOWTO, available from
1294 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards 1294 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
1295 without a specific driver are compatible with NE2000. 1295 without a specific driver are compatible with NE2000.
1296 1296
1297 If you have a PCI NE2000 card however, say N here and Y to "PCI 1297 If you have a PCI NE2000 card however, say N here and Y to "PCI
1298 NE2000 and clone support" under "EISA, VLB, PCI and on board 1298 NE2000 and clone support" under "EISA, VLB, PCI and on board
1299 controllers" below. If you have a NE2000 card and are running on 1299 controllers" below. If you have a NE2000 card and are running on
1300 an MCA system (a bus system used on some IBM PS/2 computers and 1300 an MCA system (a bus system used on some IBM PS/2 computers and
1301 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support", 1301 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
1302 below. 1302 below.
1303 1303
1304 To compile this driver as a module, choose M here. The module 1304 To compile this driver as a module, choose M here. The module
1305 will be called ne. 1305 will be called ne.
1306 1306
1307 config ZNET 1307 config ZNET
1308 tristate "Zenith Z-Note support (EXPERIMENTAL)" 1308 tristate "Zenith Z-Note support (EXPERIMENTAL)"
1309 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API 1309 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
1310 help 1310 help
1311 The Zenith Z-Note notebook computer has a built-in network 1311 The Zenith Z-Note notebook computer has a built-in network
1312 (Ethernet) card, and this is the Linux driver for it. Note that the 1312 (Ethernet) card, and this is the Linux driver for it. Note that the
1313 IBM Thinkpad 300 is compatible with the Z-Note and is also supported 1313 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
1314 by this driver. Read the Ethernet-HOWTO, available from 1314 by this driver. Read the Ethernet-HOWTO, available from
1315 <http://www.tldp.org/docs.html#howto>. 1315 <http://www.tldp.org/docs.html#howto>.
1316 1316
1317 config SEEQ8005 1317 config SEEQ8005
1318 tristate "SEEQ8005 support (EXPERIMENTAL)" 1318 tristate "SEEQ8005 support (EXPERIMENTAL)"
1319 depends on NET_ISA && EXPERIMENTAL 1319 depends on NET_ISA && EXPERIMENTAL
1320 help 1320 help
1321 This is a driver for the SEEQ 8005 network (Ethernet) card. If this 1321 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
1322 is for you, read the Ethernet-HOWTO, available from 1322 is for you, read the Ethernet-HOWTO, available from
1323 <http://www.tldp.org/docs.html#howto>. 1323 <http://www.tldp.org/docs.html#howto>.
1324 1324
1325 To compile this driver as a module, choose M here. The module 1325 To compile this driver as a module, choose M here. The module
1326 will be called seeq8005. 1326 will be called seeq8005.
1327 1327
1328 config NE2_MCA 1328 config NE2_MCA
1329 tristate "NE/2 (ne2000 MCA version) support" 1329 tristate "NE/2 (ne2000 MCA version) support"
1330 depends on MCA_LEGACY 1330 depends on MCA_LEGACY
1331 select CRC32 1331 select CRC32
1332 help 1332 help
1333 If you have a network (Ethernet) card of this type, say Y and read 1333 If you have a network (Ethernet) card of this type, say Y and read
1334 the Ethernet-HOWTO, available from 1334 the Ethernet-HOWTO, available from
1335 <http://www.tldp.org/docs.html#howto>. 1335 <http://www.tldp.org/docs.html#howto>.
1336 1336
1337 To compile this driver as a module, choose M here. The module 1337 To compile this driver as a module, choose M here. The module
1338 will be called ne2. 1338 will be called ne2.
1339 1339
1340 config IBMLANA 1340 config IBMLANA
1341 tristate "IBM LAN Adapter/A support" 1341 tristate "IBM LAN Adapter/A support"
1342 depends on MCA 1342 depends on MCA
1343 ---help--- 1343 ---help---
1344 This is a Micro Channel Ethernet adapter. You need to set 1344 This is a Micro Channel Ethernet adapter. You need to set
1345 CONFIG_MCA to use this driver. It is both available as an in-kernel 1345 CONFIG_MCA to use this driver. It is both available as an in-kernel
1346 driver and as a module. 1346 driver and as a module.
1347 1347
1348 To compile this driver as a module, choose M here. The only 1348 To compile this driver as a module, choose M here. The only
1349 currently supported card is the IBM LAN Adapter/A for Ethernet. It 1349 currently supported card is the IBM LAN Adapter/A for Ethernet. It
1350 will both support 16K and 32K memory windows, however a 32K window 1350 will both support 16K and 32K memory windows, however a 32K window
1351 gives a better security against packet losses. Usage of multiple 1351 gives a better security against packet losses. Usage of multiple
1352 boards with this driver should be possible, but has not been tested 1352 boards with this driver should be possible, but has not been tested
1353 up to now due to lack of hardware. 1353 up to now due to lack of hardware.
1354 1354
1355 config IBMVETH 1355 config IBMVETH
1356 tristate "IBM LAN Virtual Ethernet support" 1356 tristate "IBM LAN Virtual Ethernet support"
1357 depends on PPC_PSERIES 1357 depends on PPC_PSERIES
1358 ---help--- 1358 ---help---
1359 This driver supports virtual ethernet adapters on newer IBM iSeries 1359 This driver supports virtual ethernet adapters on newer IBM iSeries
1360 and pSeries systems. 1360 and pSeries systems.
1361 1361
1362 To compile this driver as a module, choose M here. The module will 1362 To compile this driver as a module, choose M here. The module will
1363 be called ibmveth. 1363 be called ibmveth.
1364 1364
1365 source "drivers/net/ibm_newemac/Kconfig" 1365 source "drivers/net/ibm_newemac/Kconfig"
1366 1366
1367 config NET_PCI 1367 config NET_PCI
1368 bool "EISA, VLB, PCI and on board controllers" 1368 bool "EISA, VLB, PCI and on board controllers"
1369 depends on ISA || EISA || PCI 1369 depends on ISA || EISA || PCI
1370 help 1370 help
1371 This is another class of network cards which attach directly to the 1371 This is another class of network cards which attach directly to the
1372 bus. If you have one of those, say Y and read the Ethernet-HOWTO, 1372 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
1373 available from <http://www.tldp.org/docs.html#howto>. 1373 available from <http://www.tldp.org/docs.html#howto>.
1374 1374
1375 Note that the answer to this question doesn't directly affect the 1375 Note that the answer to this question doesn't directly affect the
1376 kernel: saying N will just cause the configurator to skip all 1376 kernel: saying N will just cause the configurator to skip all
1377 the questions about this class of network cards. If you say Y, you 1377 the questions about this class of network cards. If you say Y, you
1378 will be asked for your specific card in the following questions. If 1378 will be asked for your specific card in the following questions. If
1379 you are unsure, say Y. 1379 you are unsure, say Y.
1380 1380
1381 config PCNET32 1381 config PCNET32
1382 tristate "AMD PCnet32 PCI support" 1382 tristate "AMD PCnet32 PCI support"
1383 depends on NET_PCI && PCI 1383 depends on NET_PCI && PCI
1384 select CRC32 1384 select CRC32
1385 select MII 1385 select MII
1386 help 1386 help
1387 If you have a PCnet32 or PCnetPCI based network (Ethernet) card, 1387 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
1388 answer Y here and read the Ethernet-HOWTO, available from 1388 answer Y here and read the Ethernet-HOWTO, available from
1389 <http://www.tldp.org/docs.html#howto>. 1389 <http://www.tldp.org/docs.html#howto>.
1390 1390
1391 To compile this driver as a module, choose M here. The module 1391 To compile this driver as a module, choose M here. The module
1392 will be called pcnet32. 1392 will be called pcnet32.
1393 1393
1394 config AMD8111_ETH 1394 config AMD8111_ETH
1395 tristate "AMD 8111 (new PCI lance) support" 1395 tristate "AMD 8111 (new PCI lance) support"
1396 depends on NET_PCI && PCI 1396 depends on NET_PCI && PCI
1397 select CRC32 1397 select CRC32
1398 select MII 1398 select MII
1399 help 1399 help
1400 If you have an AMD 8111-based PCI lance ethernet card, 1400 If you have an AMD 8111-based PCI lance ethernet card,
1401 answer Y here and read the Ethernet-HOWTO, available from 1401 answer Y here and read the Ethernet-HOWTO, available from
1402 <http://www.tldp.org/docs.html#howto>. 1402 <http://www.tldp.org/docs.html#howto>.
1403 1403
1404 To compile this driver as a module, choose M here. The module 1404 To compile this driver as a module, choose M here. The module
1405 will be called amd8111e. 1405 will be called amd8111e.
1406 1406
1407 config ADAPTEC_STARFIRE 1407 config ADAPTEC_STARFIRE
1408 tristate "Adaptec Starfire/DuraLAN support" 1408 tristate "Adaptec Starfire/DuraLAN support"
1409 depends on NET_PCI && PCI 1409 depends on NET_PCI && PCI
1410 select CRC32 1410 select CRC32
1411 select MII 1411 select MII
1412 help 1412 help
1413 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network 1413 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
1414 adapter. The DuraLAN chip is used on the 64 bit PCI boards from 1414 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
1415 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip 1415 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
1416 driver. 1416 driver.
1417 1417
1418 To compile this driver as a module, choose M here: the module 1418 To compile this driver as a module, choose M here: the module
1419 will be called starfire. This is recommended. 1419 will be called starfire. This is recommended.
1420 1420
1421 config AC3200 1421 config AC3200
1422 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)" 1422 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
1423 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL 1423 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
1424 select CRC32 1424 select CRC32
1425 help 1425 help
1426 If you have a network (Ethernet) card of this type, say Y and read 1426 If you have a network (Ethernet) card of this type, say Y and read
1427 the Ethernet-HOWTO, available from 1427 the Ethernet-HOWTO, available from
1428 <http://www.tldp.org/docs.html#howto>. 1428 <http://www.tldp.org/docs.html#howto>.
1429 1429
1430 To compile this driver as a module, choose M here. The module 1430 To compile this driver as a module, choose M here. The module
1431 will be called ac3200. 1431 will be called ac3200.
1432 1432
1433 config KSZ884X_PCI 1433 config KSZ884X_PCI
1434 tristate "Micrel KSZ8841/2 PCI" 1434 tristate "Micrel KSZ8841/2 PCI"
1435 depends on NET_PCI && PCI 1435 depends on NET_PCI && PCI
1436 select MII 1436 select MII
1437 select CRC32 1437 select CRC32
1438 help 1438 help
1439 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip. 1439 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
1440 1440
1441 To compile this driver as a module, choose M here. The module 1441 To compile this driver as a module, choose M here. The module
1442 will be called ksz884x. 1442 will be called ksz884x.
1443 1443
1444 config APRICOT 1444 config APRICOT
1445 tristate "Apricot Xen-II on board Ethernet" 1445 tristate "Apricot Xen-II on board Ethernet"
1446 depends on NET_PCI && ISA 1446 depends on NET_PCI && ISA
1447 help 1447 help
1448 If you have a network (Ethernet) controller of this type, say Y and 1448 If you have a network (Ethernet) controller of this type, say Y and
1449 read the Ethernet-HOWTO, available from 1449 read the Ethernet-HOWTO, available from
1450 <http://www.tldp.org/docs.html#howto>. 1450 <http://www.tldp.org/docs.html#howto>.
1451 1451
1452 To compile this driver as a module, choose M here. The module 1452 To compile this driver as a module, choose M here. The module
1453 will be called apricot. 1453 will be called apricot.
1454 1454
1455 config B44 1455 config B44
1456 tristate "Broadcom 440x/47xx ethernet support" 1456 tristate "Broadcom 440x/47xx ethernet support"
1457 depends on SSB_POSSIBLE && HAS_DMA 1457 depends on SSB_POSSIBLE && HAS_DMA
1458 select SSB 1458 select SSB
1459 select MII 1459 select MII
1460 help 1460 help
1461 If you have a network (Ethernet) controller of this type, say Y 1461 If you have a network (Ethernet) controller of this type, say Y
1462 or M and read the Ethernet-HOWTO, available from 1462 or M and read the Ethernet-HOWTO, available from
1463 <http://www.tldp.org/docs.html#howto>. 1463 <http://www.tldp.org/docs.html#howto>.
1464 1464
1465 To compile this driver as a module, choose M here. The module 1465 To compile this driver as a module, choose M here. The module
1466 will be called b44. 1466 will be called b44.
1467 1467
1468 # Auto-select SSB PCI-HOST support, if possible 1468 # Auto-select SSB PCI-HOST support, if possible
1469 config B44_PCI_AUTOSELECT 1469 config B44_PCI_AUTOSELECT
1470 bool 1470 bool
1471 depends on B44 && SSB_PCIHOST_POSSIBLE 1471 depends on B44 && SSB_PCIHOST_POSSIBLE
1472 select SSB_PCIHOST 1472 select SSB_PCIHOST
1473 default y 1473 default y
1474 1474
1475 # Auto-select SSB PCICORE driver, if possible 1475 # Auto-select SSB PCICORE driver, if possible
1476 config B44_PCICORE_AUTOSELECT 1476 config B44_PCICORE_AUTOSELECT
1477 bool 1477 bool
1478 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE 1478 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
1479 select SSB_DRIVER_PCICORE 1479 select SSB_DRIVER_PCICORE
1480 default y 1480 default y
1481 1481
1482 config B44_PCI 1482 config B44_PCI
1483 bool 1483 bool
1484 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT 1484 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
1485 default y 1485 default y
1486 1486
1487 config FORCEDETH 1487 config FORCEDETH
1488 tristate "nForce Ethernet support" 1488 tristate "nForce Ethernet support"
1489 depends on NET_PCI && PCI 1489 depends on NET_PCI && PCI
1490 help 1490 help
1491 If you have a network (Ethernet) controller of this type, say Y and 1491 If you have a network (Ethernet) controller of this type, say Y and
1492 read the Ethernet-HOWTO, available from 1492 read the Ethernet-HOWTO, available from
1493 <http://www.tldp.org/docs.html#howto>. 1493 <http://www.tldp.org/docs.html#howto>.
1494 1494
1495 To compile this driver as a module, choose M here. The module 1495 To compile this driver as a module, choose M here. The module
1496 will be called forcedeth. 1496 will be called forcedeth.
1497 1497
1498 config CS89x0 1498 config CS89x0
1499 tristate "CS89x0 support" 1499 tristate "CS89x0 support"
1500 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \ 1500 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
1501 || ARCH_IXDP2X01 || MACH_MX31ADS) 1501 || ARCH_IXDP2X01 || MACH_MX31ADS)
1502 ---help--- 1502 ---help---
1503 Support for CS89x0 chipset based Ethernet cards. If you have a 1503 Support for CS89x0 chipset based Ethernet cards. If you have a
1504 network (Ethernet) card of this type, say Y and read the 1504 network (Ethernet) card of this type, say Y and read the
1505 Ethernet-HOWTO, available from 1505 Ethernet-HOWTO, available from
1506 <http://www.tldp.org/docs.html#howto> as well as 1506 <http://www.tldp.org/docs.html#howto> as well as
1507 <file:Documentation/networking/cs89x0.txt>. 1507 <file:Documentation/networking/cs89x0.txt>.
1508 1508
1509 To compile this driver as a module, choose M here. The module 1509 To compile this driver as a module, choose M here. The module
1510 will be called cs89x0. 1510 will be called cs89x0.
1511 1511
1512 config CS89x0_NONISA_IRQ 1512 config CS89x0_NONISA_IRQ
1513 def_bool y 1513 def_bool y
1514 depends on CS89x0 != n 1514 depends on CS89x0 != n
1515 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || MACH_MX31ADS 1515 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || MACH_MX31ADS
1516 1516
1517 config TC35815 1517 config TC35815
1518 tristate "TOSHIBA TC35815 Ethernet support" 1518 tristate "TOSHIBA TC35815 Ethernet support"
1519 depends on NET_PCI && PCI && MIPS 1519 depends on NET_PCI && PCI && MIPS
1520 select PHYLIB 1520 select PHYLIB
1521 1521
1522 config E100 1522 config E100
1523 tristate "Intel(R) PRO/100+ support" 1523 tristate "Intel(R) PRO/100+ support"
1524 depends on NET_PCI && PCI 1524 depends on NET_PCI && PCI
1525 select MII 1525 select MII
1526 ---help--- 1526 ---help---
1527 This driver supports Intel(R) PRO/100 family of adapters. 1527 This driver supports Intel(R) PRO/100 family of adapters.
1528 To verify that your adapter is supported, find the board ID number 1528 To verify that your adapter is supported, find the board ID number
1529 on the adapter. Look for a label that has a barcode and a number 1529 on the adapter. Look for a label that has a barcode and a number
1530 in the format 123456-001 (six digits hyphen three digits). 1530 in the format 123456-001 (six digits hyphen three digits).
1531 1531
1532 Use the above information and the Adapter & Driver ID Guide at: 1532 Use the above information and the Adapter & Driver ID Guide at:
1533 1533
1534 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 1534 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
1535 1535
1536 to identify the adapter. 1536 to identify the adapter.
1537 1537
1538 For the latest Intel PRO/100 network driver for Linux, see: 1538 For the latest Intel PRO/100 network driver for Linux, see:
1539 1539
1540 <http://www.intel.com/p/en_US/support/highlights/network/pro100plus> 1540 <http://www.intel.com/p/en_US/support/highlights/network/pro100plus>
1541 1541
1542 More specific information on configuring the driver is in 1542 More specific information on configuring the driver is in
1543 <file:Documentation/networking/e100.txt>. 1543 <file:Documentation/networking/e100.txt>.
1544 1544
1545 To compile this driver as a module, choose M here. The module 1545 To compile this driver as a module, choose M here. The module
1546 will be called e100. 1546 will be called e100.
1547 1547
1548 config LNE390 1548 config LNE390
1549 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)" 1549 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
1550 depends on NET_PCI && EISA && EXPERIMENTAL 1550 depends on NET_PCI && EISA && EXPERIMENTAL
1551 select CRC32 1551 select CRC32
1552 help 1552 help
1553 If you have a network (Ethernet) card of this type, say Y and read 1553 If you have a network (Ethernet) card of this type, say Y and read
1554 the Ethernet-HOWTO, available from 1554 the Ethernet-HOWTO, available from
1555 <http://www.tldp.org/docs.html#howto>. 1555 <http://www.tldp.org/docs.html#howto>.
1556 1556
1557 To compile this driver as a module, choose M here. The module 1557 To compile this driver as a module, choose M here. The module
1558 will be called lne390. 1558 will be called lne390.
1559 1559
1560 config FEALNX 1560 config FEALNX
1561 tristate "Myson MTD-8xx PCI Ethernet support" 1561 tristate "Myson MTD-8xx PCI Ethernet support"
1562 depends on NET_PCI && PCI 1562 depends on NET_PCI && PCI
1563 select CRC32 1563 select CRC32
1564 select MII 1564 select MII
1565 help 1565 help
1566 Say Y here to support the Myson MTD-800 family of PCI-based Ethernet 1566 Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
1567 cards. <http://www.myson.com.tw/> 1567 cards. <http://www.myson.com.tw/>
1568 1568
1569 config NATSEMI 1569 config NATSEMI
1570 tristate "National Semiconductor DP8381x series PCI Ethernet support" 1570 tristate "National Semiconductor DP8381x series PCI Ethernet support"
1571 depends on NET_PCI && PCI 1571 depends on NET_PCI && PCI
1572 select CRC32 1572 select CRC32
1573 help 1573 help
1574 This driver is for the National Semiconductor DP83810 series, 1574 This driver is for the National Semiconductor DP83810 series,
1575 which is used in cards from PureData, NetGear, Linksys 1575 which is used in cards from PureData, NetGear, Linksys
1576 and others, including the 83815 chip. 1576 and others, including the 83815 chip.
1577 More specific information and updates are available from 1577 More specific information and updates are available from
1578 <http://www.scyld.com/network/natsemi.html>. 1578 <http://www.scyld.com/network/natsemi.html>.
1579 1579
1580 config NE2K_PCI 1580 config NE2K_PCI
1581 tristate "PCI NE2000 and clones support (see help)" 1581 tristate "PCI NE2000 and clones support (see help)"
1582 depends on NET_PCI && PCI 1582 depends on NET_PCI && PCI
1583 select CRC32 1583 select CRC32
1584 ---help--- 1584 ---help---
1585 This driver is for NE2000 compatible PCI cards. It will not work 1585 This driver is for NE2000 compatible PCI cards. It will not work
1586 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000 1586 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
1587 support" below). If you have a PCI NE2000 network (Ethernet) card, 1587 support" below). If you have a PCI NE2000 network (Ethernet) card,
1588 say Y and read the Ethernet-HOWTO, available from 1588 say Y and read the Ethernet-HOWTO, available from
1589 <http://www.tldp.org/docs.html#howto>. 1589 <http://www.tldp.org/docs.html#howto>.
1590 1590
1591 This driver also works for the following NE2000 clone cards: 1591 This driver also works for the following NE2000 clone cards:
1592 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2 1592 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
1593 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond 1593 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
1594 Holtek HT80232 Holtek HT80229 1594 Holtek HT80232 Holtek HT80229
1595 1595
1596 To compile this driver as a module, choose M here. The module 1596 To compile this driver as a module, choose M here. The module
1597 will be called ne2k-pci. 1597 will be called ne2k-pci.
1598 1598
1599 config NE3210 1599 config NE3210
1600 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)" 1600 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
1601 depends on NET_PCI && EISA && EXPERIMENTAL 1601 depends on NET_PCI && EISA && EXPERIMENTAL
1602 select CRC32 1602 select CRC32
1603 ---help--- 1603 ---help---
1604 If you have a network (Ethernet) card of this type, say Y and read 1604 If you have a network (Ethernet) card of this type, say Y and read
1605 the Ethernet-HOWTO, available from 1605 the Ethernet-HOWTO, available from
1606 <http://www.tldp.org/docs.html#howto>. Note that this driver 1606 <http://www.tldp.org/docs.html#howto>. Note that this driver
1607 will NOT WORK for NE3200 cards as they are completely different. 1607 will NOT WORK for NE3200 cards as they are completely different.
1608 1608
1609 To compile this driver as a module, choose M here. The module 1609 To compile this driver as a module, choose M here. The module
1610 will be called ne3210. 1610 will be called ne3210.
1611 1611
1612 config ES3210 1612 config ES3210
1613 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)" 1613 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
1614 depends on NET_PCI && EISA && EXPERIMENTAL 1614 depends on NET_PCI && EISA && EXPERIMENTAL
1615 select CRC32 1615 select CRC32
1616 help 1616 help
1617 If you have a network (Ethernet) card of this type, say Y and read 1617 If you have a network (Ethernet) card of this type, say Y and read
1618 the Ethernet-HOWTO, available from 1618 the Ethernet-HOWTO, available from
1619 <http://www.tldp.org/docs.html#howto>. 1619 <http://www.tldp.org/docs.html#howto>.
1620 1620
1621 To compile this driver as a module, choose M here. The module 1621 To compile this driver as a module, choose M here. The module
1622 will be called es3210. 1622 will be called es3210.
1623 1623
1624 config 8139CP 1624 config 8139CP
1625 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)" 1625 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
1626 depends on NET_PCI && PCI && EXPERIMENTAL 1626 depends on NET_PCI && PCI && EXPERIMENTAL
1627 select CRC32 1627 select CRC32
1628 select MII 1628 select MII
1629 help 1629 help
1630 This is a driver for the Fast Ethernet PCI network cards based on 1630 This is a driver for the Fast Ethernet PCI network cards based on
1631 the RTL8139C+ chips. If you have one of those, say Y and read 1631 the RTL8139C+ chips. If you have one of those, say Y and read
1632 the Ethernet-HOWTO, available from 1632 the Ethernet-HOWTO, available from
1633 <http://www.tldp.org/docs.html#howto>. 1633 <http://www.tldp.org/docs.html#howto>.
1634 1634
1635 To compile this driver as a module, choose M here: the module 1635 To compile this driver as a module, choose M here: the module
1636 will be called 8139cp. This is recommended. 1636 will be called 8139cp. This is recommended.
1637 1637
1638 config 8139TOO 1638 config 8139TOO
1639 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support" 1639 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
1640 depends on NET_PCI && PCI 1640 depends on NET_PCI && PCI
1641 select CRC32 1641 select CRC32
1642 select MII 1642 select MII
1643 ---help--- 1643 ---help---
1644 This is a driver for the Fast Ethernet PCI network cards based on 1644 This is a driver for the Fast Ethernet PCI network cards based on
1645 the RTL 8129/8130/8139 chips. If you have one of those, say Y and 1645 the RTL 8129/8130/8139 chips. If you have one of those, say Y and
1646 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>. 1646 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
1647 1647
1648 To compile this driver as a module, choose M here: the module 1648 To compile this driver as a module, choose M here: the module
1649 will be called 8139too. This is recommended. 1649 will be called 8139too. This is recommended.
1650 1650
1651 config 8139TOO_PIO 1651 config 8139TOO_PIO
1652 bool "Use PIO instead of MMIO" 1652 bool "Use PIO instead of MMIO"
1653 default y 1653 default y
1654 depends on 8139TOO 1654 depends on 8139TOO
1655 help 1655 help
1656 This instructs the driver to use programmed I/O ports (PIO) instead 1656 This instructs the driver to use programmed I/O ports (PIO) instead
1657 of PCI shared memory (MMIO). This can possibly solve some problems 1657 of PCI shared memory (MMIO). This can possibly solve some problems
1658 in case your mainboard has memory consistency issues. If unsure, 1658 in case your mainboard has memory consistency issues. If unsure,
1659 say N. 1659 say N.
1660 1660
1661 config 8139TOO_TUNE_TWISTER 1661 config 8139TOO_TUNE_TWISTER
1662 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)" 1662 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
1663 depends on 8139TOO 1663 depends on 8139TOO
1664 help 1664 help
1665 This implements a function which might come in handy in case you 1665 This implements a function which might come in handy in case you
1666 are using low quality on long cabling. It is required for RealTek 1666 are using low quality on long cabling. It is required for RealTek
1667 RTL-8139 revision K boards, and totally unused otherwise. It tries 1667 RTL-8139 revision K boards, and totally unused otherwise. It tries
1668 to match the transceiver to the cable characteristics. This is 1668 to match the transceiver to the cable characteristics. This is
1669 experimental since hardly documented by the manufacturer. 1669 experimental since hardly documented by the manufacturer.
1670 If unsure, say Y. 1670 If unsure, say Y.
1671 1671
1672 config 8139TOO_8129 1672 config 8139TOO_8129
1673 bool "Support for older RTL-8129/8130 boards" 1673 bool "Support for older RTL-8129/8130 boards"
1674 depends on 8139TOO 1674 depends on 8139TOO
1675 help 1675 help
1676 This enables support for the older and uncommon RTL-8129 and 1676 This enables support for the older and uncommon RTL-8129 and
1677 RTL-8130 chips, which support MII via an external transceiver, 1677 RTL-8130 chips, which support MII via an external transceiver,
1678 instead of an internal one. Disabling this option will save some 1678 instead of an internal one. Disabling this option will save some
1679 memory by making the code size smaller. If unsure, say Y. 1679 memory by making the code size smaller. If unsure, say Y.
1680 1680
1681 config 8139_OLD_RX_RESET 1681 config 8139_OLD_RX_RESET
1682 bool "Use older RX-reset method" 1682 bool "Use older RX-reset method"
1683 depends on 8139TOO 1683 depends on 8139TOO
1684 help 1684 help
1685 The 8139too driver was recently updated to contain a more rapid 1685 The 8139too driver was recently updated to contain a more rapid
1686 reset sequence, in the face of severe receive errors. This "new" 1686 reset sequence, in the face of severe receive errors. This "new"
1687 RX-reset method should be adequate for all boards. But if you 1687 RX-reset method should be adequate for all boards. But if you
1688 experience problems, you can enable this option to restore the 1688 experience problems, you can enable this option to restore the
1689 old RX-reset behavior. If unsure, say N. 1689 old RX-reset behavior. If unsure, say N.
1690 1690
1691 config R6040 1691 config R6040
1692 tristate "RDC R6040 Fast Ethernet Adapter support" 1692 tristate "RDC R6040 Fast Ethernet Adapter support"
1693 depends on NET_PCI && PCI 1693 depends on NET_PCI && PCI
1694 select CRC32 1694 select CRC32
1695 select MII 1695 select MII
1696 select PHYLIB 1696 select PHYLIB
1697 help 1697 help
1698 This is a driver for the R6040 Fast Ethernet MACs found in the 1698 This is a driver for the R6040 Fast Ethernet MACs found in the
1699 the RDC R-321x System-on-chips. 1699 the RDC R-321x System-on-chips.
1700 1700
1701 To compile this driver as a module, choose M here: the module 1701 To compile this driver as a module, choose M here: the module
1702 will be called r6040. This is recommended. 1702 will be called r6040. This is recommended.
1703 1703
1704 config SIS900 1704 config SIS900
1705 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support" 1705 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
1706 depends on NET_PCI && PCI 1706 depends on NET_PCI && PCI
1707 select CRC32 1707 select CRC32
1708 select MII 1708 select MII
1709 ---help--- 1709 ---help---
1710 This is a driver for the Fast Ethernet PCI network cards based on 1710 This is a driver for the Fast Ethernet PCI network cards based on
1711 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in 1711 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
1712 SiS 630 and SiS 540 chipsets. 1712 SiS 630 and SiS 540 chipsets.
1713 1713
1714 This driver also supports AMD 79C901 HomePNA so that you can use 1714 This driver also supports AMD 79C901 HomePNA so that you can use
1715 your phone line as a network cable. 1715 your phone line as a network cable.
1716 1716
1717 To compile this driver as a module, choose M here: the module 1717 To compile this driver as a module, choose M here: the module
1718 will be called sis900. This is recommended. 1718 will be called sis900. This is recommended.
1719 1719
1720 config EPIC100 1720 config EPIC100
1721 tristate "SMC EtherPower II" 1721 tristate "SMC EtherPower II"
1722 depends on NET_PCI && PCI 1722 depends on NET_PCI && PCI
1723 select CRC32 1723 select CRC32
1724 select MII 1724 select MII
1725 help 1725 help
1726 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC, 1726 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
1727 which is based on the SMC83c17x (EPIC/100). 1727 which is based on the SMC83c17x (EPIC/100).
1728 More specific information and updates are available from 1728 More specific information and updates are available from
1729 <http://www.scyld.com/network/epic100.html>. 1729 <http://www.scyld.com/network/epic100.html>.
1730 1730
1731 config SMSC9420 1731 config SMSC9420
1732 tristate "SMSC LAN9420 PCI ethernet adapter support" 1732 tristate "SMSC LAN9420 PCI ethernet adapter support"
1733 depends on NET_PCI && PCI 1733 depends on NET_PCI && PCI
1734 select CRC32 1734 select CRC32
1735 select PHYLIB 1735 select PHYLIB
1736 select SMSC_PHY 1736 select SMSC_PHY
1737 help 1737 help
1738 This is a driver for SMSC's LAN9420 PCI ethernet adapter. 1738 This is a driver for SMSC's LAN9420 PCI ethernet adapter.
1739 Say Y if you want it compiled into the kernel, 1739 Say Y if you want it compiled into the kernel,
1740 and read the Ethernet-HOWTO, available from 1740 and read the Ethernet-HOWTO, available from
1741 <http://www.tldp.org/docs.html#howto>. 1741 <http://www.tldp.org/docs.html#howto>.
1742 1742
1743 This driver is also available as a module. The module will be 1743 This driver is also available as a module. The module will be
1744 called smsc9420. If you want to compile it as a module, say M 1744 called smsc9420. If you want to compile it as a module, say M
1745 here and read <file:Documentation/kbuild/modules.txt> 1745 here and read <file:Documentation/kbuild/modules.txt>
1746 1746
1747 config SUNDANCE 1747 config SUNDANCE
1748 tristate "Sundance Alta support" 1748 tristate "Sundance Alta support"
1749 depends on NET_PCI && PCI 1749 depends on NET_PCI && PCI
1750 select CRC32 1750 select CRC32
1751 select MII 1751 select MII
1752 help 1752 help
1753 This driver is for the Sundance "Alta" chip. 1753 This driver is for the Sundance "Alta" chip.
1754 More specific information and updates are available from 1754 More specific information and updates are available from
1755 <http://www.scyld.com/network/sundance.html>. 1755 <http://www.scyld.com/network/sundance.html>.
1756 1756
1757 config SUNDANCE_MMIO 1757 config SUNDANCE_MMIO
1758 bool "Use MMIO instead of PIO" 1758 bool "Use MMIO instead of PIO"
1759 depends on SUNDANCE 1759 depends on SUNDANCE
1760 help 1760 help
1761 Enable memory-mapped I/O for interaction with Sundance NIC registers. 1761 Enable memory-mapped I/O for interaction with Sundance NIC registers.
1762 Do NOT enable this by default, PIO (enabled when MMIO is disabled) 1762 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
1763 is known to solve bugs on certain chips. 1763 is known to solve bugs on certain chips.
1764 1764
1765 If unsure, say N. 1765 If unsure, say N.
1766 1766
1767 config TLAN 1767 config TLAN
1768 tristate "TI ThunderLAN support" 1768 tristate "TI ThunderLAN support"
1769 depends on NET_PCI && (PCI || EISA) 1769 depends on NET_PCI && (PCI || EISA)
1770 ---help--- 1770 ---help---
1771 If you have a PCI Ethernet network card based on the ThunderLAN chip 1771 If you have a PCI Ethernet network card based on the ThunderLAN chip
1772 which is supported by this driver, say Y and read the 1772 which is supported by this driver, say Y and read the
1773 Ethernet-HOWTO, available from 1773 Ethernet-HOWTO, available from
1774 <http://www.tldp.org/docs.html#howto>. 1774 <http://www.tldp.org/docs.html#howto>.
1775 1775
1776 Devices currently supported by this driver are Compaq Netelligent, 1776 Devices currently supported by this driver are Compaq Netelligent,
1777 Compaq NetFlex and Olicom cards. Please read the file 1777 Compaq NetFlex and Olicom cards. Please read the file
1778 <file:Documentation/networking/tlan.txt> for more details. 1778 <file:Documentation/networking/tlan.txt> for more details.
1779 1779
1780 To compile this driver as a module, choose M here. The module 1780 To compile this driver as a module, choose M here. The module
1781 will be called tlan. 1781 will be called tlan.
1782 1782
1783 Please email feedback to <torben.mathiasen@compaq.com>. 1783 Please email feedback to <torben.mathiasen@compaq.com>.
1784 1784
1785 config KS8842 1785 config KS8842
1786 tristate "Micrel KSZ8841/42 with generic bus interface" 1786 tristate "Micrel KSZ8841/42 with generic bus interface"
1787 depends on HAS_IOMEM && DMA_ENGINE 1787 depends on HAS_IOMEM && DMA_ENGINE
1788 help 1788 help
1789 This platform driver is for KSZ8841(1-port) / KS8842(2-port) 1789 This platform driver is for KSZ8841(1-port) / KS8842(2-port)
1790 ethernet switch chip (managed, VLAN, QoS) from Micrel or 1790 ethernet switch chip (managed, VLAN, QoS) from Micrel or
1791 Timberdale(FPGA). 1791 Timberdale(FPGA).
1792 1792
1793 config KS8851 1793 config KS8851
1794 tristate "Micrel KS8851 SPI" 1794 tristate "Micrel KS8851 SPI"
1795 depends on SPI 1795 depends on SPI
1796 select MII 1796 select MII
1797 select CRC32 1797 select CRC32
1798 help 1798 help
1799 SPI driver for Micrel KS8851 SPI attached network chip. 1799 SPI driver for Micrel KS8851 SPI attached network chip.
1800 1800
1801 config KS8851_MLL 1801 config KS8851_MLL
1802 tristate "Micrel KS8851 MLL" 1802 tristate "Micrel KS8851 MLL"
1803 depends on HAS_IOMEM 1803 depends on HAS_IOMEM
1804 select MII 1804 select MII
1805 help 1805 help
1806 This platform driver is for Micrel KS8851 Address/data bus 1806 This platform driver is for Micrel KS8851 Address/data bus
1807 multiplexed network chip. 1807 multiplexed network chip.
1808 1808
1809 config VIA_RHINE 1809 config VIA_RHINE
1810 tristate "VIA Rhine support" 1810 tristate "VIA Rhine support"
1811 depends on NET_PCI && PCI 1811 depends on NET_PCI && PCI
1812 select CRC32 1812 select CRC32
1813 select MII 1813 select MII
1814 help 1814 help
1815 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A), 1815 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
1816 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type 1816 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
1817 Ethernet functions can also be found integrated on South Bridges 1817 Ethernet functions can also be found integrated on South Bridges
1818 (e.g. VT8235). 1818 (e.g. VT8235).
1819 1819
1820 To compile this driver as a module, choose M here. The module 1820 To compile this driver as a module, choose M here. The module
1821 will be called via-rhine. 1821 will be called via-rhine.
1822 1822
1823 config VIA_RHINE_MMIO 1823 config VIA_RHINE_MMIO
1824 bool "Use MMIO instead of PIO" 1824 bool "Use MMIO instead of PIO"
1825 depends on VIA_RHINE 1825 depends on VIA_RHINE
1826 help 1826 help
1827 This instructs the driver to use PCI shared memory (MMIO) instead of 1827 This instructs the driver to use PCI shared memory (MMIO) instead of
1828 programmed I/O ports (PIO). Enabling this gives an improvement in 1828 programmed I/O ports (PIO). Enabling this gives an improvement in
1829 processing time in parts of the driver. 1829 processing time in parts of the driver.
1830 1830
1831 If unsure, say Y. 1831 If unsure, say Y.
1832 1832
1833 config SC92031 1833 config SC92031
1834 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)" 1834 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
1835 depends on NET_PCI && PCI && EXPERIMENTAL 1835 depends on NET_PCI && PCI && EXPERIMENTAL
1836 select CRC32 1836 select CRC32
1837 ---help--- 1837 ---help---
1838 This is a driver for the Fast Ethernet PCI network cards based on 1838 This is a driver for the Fast Ethernet PCI network cards based on
1839 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you 1839 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
1840 have one of these, say Y here. 1840 have one of these, say Y here.
1841 1841
1842 To compile this driver as a module, choose M here: the module 1842 To compile this driver as a module, choose M here: the module
1843 will be called sc92031. This is recommended. 1843 will be called sc92031. This is recommended.
1844 1844
1845 config CPMAC 1845 config CPMAC
1846 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)" 1846 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
1847 depends on NET_ETHERNET && EXPERIMENTAL && AR7 1847 depends on NET_ETHERNET && EXPERIMENTAL && AR7
1848 select PHYLIB 1848 select PHYLIB
1849 help 1849 help
1850 TI AR7 CPMAC Ethernet support 1850 TI AR7 CPMAC Ethernet support
1851 1851
1852 config NET_POCKET 1852 config NET_POCKET
1853 bool "Pocket and portable adapters" 1853 bool "Pocket and portable adapters"
1854 depends on PARPORT 1854 depends on PARPORT
1855 ---help--- 1855 ---help---
1856 Cute little network (Ethernet) devices which attach to the parallel 1856 Cute little network (Ethernet) devices which attach to the parallel
1857 port ("pocket adapters"), commonly used with laptops. If you have 1857 port ("pocket adapters"), commonly used with laptops. If you have
1858 one of those, say Y and read the Ethernet-HOWTO, available from 1858 one of those, say Y and read the Ethernet-HOWTO, available from
1859 <http://www.tldp.org/docs.html#howto>. 1859 <http://www.tldp.org/docs.html#howto>.
1860 1860
1861 If you want to plug a network (or some other) card into the PCMCIA 1861 If you want to plug a network (or some other) card into the PCMCIA
1862 (or PC-card) slot of your laptop instead (PCMCIA is the standard for 1862 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
1863 credit card size extension cards used by all modern laptops), you 1863 credit card size extension cards used by all modern laptops), you
1864 need the pcmcia-cs package (location contained in the file 1864 need the pcmcia-cs package (location contained in the file
1865 <file:Documentation/Changes>) and you can say N here. 1865 <file:Documentation/Changes>) and you can say N here.
1866 1866
1867 Laptop users should read the Linux Laptop home page at 1867 Laptop users should read the Linux Laptop home page at
1868 <http://www.linux-on-laptops.com/> or 1868 <http://www.linux-on-laptops.com/> or
1869 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>. 1869 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
1870 1870
1871 Note that the answer to this question doesn't directly affect the 1871 Note that the answer to this question doesn't directly affect the
1872 kernel: saying N will just cause the configurator to skip all 1872 kernel: saying N will just cause the configurator to skip all
1873 the questions about this class of network devices. If you say Y, you 1873 the questions about this class of network devices. If you say Y, you
1874 will be asked for your specific device in the following questions. 1874 will be asked for your specific device in the following questions.
1875 1875
1876 config ATP 1876 config ATP
1877 tristate "AT-LAN-TEC/RealTek pocket adapter support" 1877 tristate "AT-LAN-TEC/RealTek pocket adapter support"
1878 depends on NET_POCKET && PARPORT && X86 1878 depends on NET_POCKET && PARPORT && X86
1879 select CRC32 1879 select CRC32
1880 ---help--- 1880 ---help---
1881 This is a network (Ethernet) device which attaches to your parallel 1881 This is a network (Ethernet) device which attaches to your parallel
1882 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO, 1882 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
1883 available from <http://www.tldp.org/docs.html#howto>, if you 1883 available from <http://www.tldp.org/docs.html#howto>, if you
1884 want to use this. If you intend to use this driver, you should have 1884 want to use this. If you intend to use this driver, you should have
1885 said N to the "Parallel printer support", because the two drivers 1885 said N to the "Parallel printer support", because the two drivers
1886 don't like each other. 1886 don't like each other.
1887 1887
1888 To compile this driver as a module, choose M here: the module 1888 To compile this driver as a module, choose M here: the module
1889 will be called atp. 1889 will be called atp.
1890 1890
1891 config DE600 1891 config DE600
1892 tristate "D-Link DE600 pocket adapter support" 1892 tristate "D-Link DE600 pocket adapter support"
1893 depends on NET_POCKET && PARPORT 1893 depends on NET_POCKET && PARPORT
1894 ---help--- 1894 ---help---
1895 This is a network (Ethernet) device which attaches to your parallel 1895 This is a network (Ethernet) device which attaches to your parallel
1896 port. Read <file:Documentation/networking/DLINK.txt> as well as the 1896 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1897 Ethernet-HOWTO, available from 1897 Ethernet-HOWTO, available from
1898 <http://www.tldp.org/docs.html#howto>, if you want to use 1898 <http://www.tldp.org/docs.html#howto>, if you want to use
1899 this. It is possible to have several devices share a single parallel 1899 this. It is possible to have several devices share a single parallel
1900 port and it is safe to compile the corresponding drivers into the 1900 port and it is safe to compile the corresponding drivers into the
1901 kernel. 1901 kernel.
1902 1902
1903 To compile this driver as a module, choose M here: the module 1903 To compile this driver as a module, choose M here: the module
1904 will be called de600. 1904 will be called de600.
1905 1905
1906 config DE620 1906 config DE620
1907 tristate "D-Link DE620 pocket adapter support" 1907 tristate "D-Link DE620 pocket adapter support"
1908 depends on NET_POCKET && PARPORT 1908 depends on NET_POCKET && PARPORT
1909 ---help--- 1909 ---help---
1910 This is a network (Ethernet) device which attaches to your parallel 1910 This is a network (Ethernet) device which attaches to your parallel
1911 port. Read <file:Documentation/networking/DLINK.txt> as well as the 1911 port. Read <file:Documentation/networking/DLINK.txt> as well as the
1912 Ethernet-HOWTO, available from 1912 Ethernet-HOWTO, available from
1913 <http://www.tldp.org/docs.html#howto>, if you want to use 1913 <http://www.tldp.org/docs.html#howto>, if you want to use
1914 this. It is possible to have several devices share a single parallel 1914 this. It is possible to have several devices share a single parallel
1915 port and it is safe to compile the corresponding drivers into the 1915 port and it is safe to compile the corresponding drivers into the
1916 kernel. 1916 kernel.
1917 1917
1918 To compile this driver as a module, choose M here: the module 1918 To compile this driver as a module, choose M here: the module
1919 will be called de620. 1919 will be called de620.
1920 1920
1921 config SGISEEQ 1921 config SGISEEQ
1922 tristate "SGI Seeq ethernet controller support" 1922 tristate "SGI Seeq ethernet controller support"
1923 depends on SGI_HAS_SEEQ 1923 depends on SGI_HAS_SEEQ
1924 help 1924 help
1925 Say Y here if you have an Seeq based Ethernet network card. This is 1925 Say Y here if you have an Seeq based Ethernet network card. This is
1926 used in many Silicon Graphics machines. 1926 used in many Silicon Graphics machines.
1927 1927
1928 config DECLANCE 1928 config DECLANCE
1929 tristate "DEC LANCE ethernet controller support" 1929 tristate "DEC LANCE ethernet controller support"
1930 depends on MACH_DECSTATION 1930 depends on MACH_DECSTATION
1931 select CRC32 1931 select CRC32
1932 help 1932 help
1933 This driver is for the series of Ethernet controllers produced by 1933 This driver is for the series of Ethernet controllers produced by
1934 DEC (now Compaq) based on the AMD Lance chipset, including the 1934 DEC (now Compaq) based on the AMD Lance chipset, including the
1935 DEPCA series. (This chipset is better known via the NE2100 cards.) 1935 DEPCA series. (This chipset is better known via the NE2100 cards.)
1936 1936
1937 config 68360_ENET 1937 config 68360_ENET
1938 bool "Motorola 68360 ethernet controller" 1938 bool "Motorola 68360 ethernet controller"
1939 depends on M68360 1939 depends on M68360
1940 help 1940 help
1941 Say Y here if you want to use the built-in ethernet controller of 1941 Say Y here if you want to use the built-in ethernet controller of
1942 the Motorola 68360 processor. 1942 the Motorola 68360 processor.
1943 1943
1944 config FEC 1944 config FEC
1945 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)" 1945 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
1946 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \ 1946 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
1947 MACH_MX27 || ARCH_MX35 || ARCH_MX25 || ARCH_MX5 || SOC_IMX28 1947 MACH_MX27 || ARCH_MX35 || ARCH_MX25 || ARCH_MX5 || SOC_IMX28
1948 select PHYLIB 1948 select PHYLIB
1949 help 1949 help
1950 Say Y here if you want to use the built-in 10/100 Fast ethernet 1950 Say Y here if you want to use the built-in 10/100 Fast ethernet
1951 controller on some Motorola ColdFire and Freescale i.MX processors. 1951 controller on some Motorola ColdFire and Freescale i.MX processors.
1952 1952
1953 config FEC_MPC52xx 1953 config FEC_MPC52xx
1954 tristate "MPC52xx FEC driver" 1954 tristate "MPC52xx FEC driver"
1955 depends on PPC_MPC52xx && PPC_BESTCOMM 1955 depends on PPC_MPC52xx && PPC_BESTCOMM
1956 select CRC32 1956 select CRC32
1957 select PHYLIB 1957 select PHYLIB
1958 select PPC_BESTCOMM_FEC 1958 select PPC_BESTCOMM_FEC
1959 ---help--- 1959 ---help---
1960 This option enables support for the MPC5200's on-chip 1960 This option enables support for the MPC5200's on-chip
1961 Fast Ethernet Controller 1961 Fast Ethernet Controller
1962 If compiled as module, it will be called fec_mpc52xx. 1962 If compiled as module, it will be called fec_mpc52xx.
1963 1963
1964 config FEC_MPC52xx_MDIO 1964 config FEC_MPC52xx_MDIO
1965 bool "MPC52xx FEC MDIO bus driver" 1965 bool "MPC52xx FEC MDIO bus driver"
1966 depends on FEC_MPC52xx 1966 depends on FEC_MPC52xx
1967 default y 1967 default y
1968 ---help--- 1968 ---help---
1969 The MPC5200's FEC can connect to the Ethernet either with 1969 The MPC5200's FEC can connect to the Ethernet either with
1970 an external MII PHY chip or 10 Mbps 7-wire interface 1970 an external MII PHY chip or 10 Mbps 7-wire interface
1971 (Motorola? industry standard). 1971 (Motorola? industry standard).
1972 If your board uses an external PHY connected to FEC, enable this. 1972 If your board uses an external PHY connected to FEC, enable this.
1973 If not sure, enable. 1973 If not sure, enable.
1974 If compiled as module, it will be called fec_mpc52xx_phy. 1974 If compiled as module, it will be called fec_mpc52xx_phy.
1975 1975
1976 config NE_H8300 1976 config NE_H8300
1977 tristate "NE2000 compatible support for H8/300" 1977 tristate "NE2000 compatible support for H8/300"
1978 depends on H8300 1978 depends on H8300
1979 help 1979 help
1980 Say Y here if you want to use the NE2000 compatible 1980 Say Y here if you want to use the NE2000 compatible
1981 controller on the Renesas H8/300 processor. 1981 controller on the Renesas H8/300 processor.
1982 1982
1983 config ATL2 1983 config ATL2
1984 tristate "Atheros L2 Fast Ethernet support" 1984 tristate "Atheros L2 Fast Ethernet support"
1985 depends on PCI 1985 depends on PCI
1986 select CRC32 1986 select CRC32
1987 select MII 1987 select MII
1988 help 1988 help
1989 This driver supports the Atheros L2 fast ethernet adapter. 1989 This driver supports the Atheros L2 fast ethernet adapter.
1990 1990
1991 To compile this driver as a module, choose M here. The module 1991 To compile this driver as a module, choose M here. The module
1992 will be called atl2. 1992 will be called atl2.
1993 1993
1994 config XILINX_EMACLITE 1994 config XILINX_EMACLITE
1995 tristate "Xilinx 10/100 Ethernet Lite support" 1995 tristate "Xilinx 10/100 Ethernet Lite support"
1996 depends on PPC32 || MICROBLAZE 1996 depends on PPC32 || MICROBLAZE
1997 select PHYLIB 1997 select PHYLIB
1998 help 1998 help
1999 This driver supports the 10/100 Ethernet Lite from Xilinx. 1999 This driver supports the 10/100 Ethernet Lite from Xilinx.
2000 2000
2001 config BCM63XX_ENET 2001 config BCM63XX_ENET
2002 tristate "Broadcom 63xx internal mac support" 2002 tristate "Broadcom 63xx internal mac support"
2003 depends on BCM63XX 2003 depends on BCM63XX
2004 select MII 2004 select MII
2005 select PHYLIB 2005 select PHYLIB
2006 help 2006 help
2007 This driver supports the ethernet MACs in the Broadcom 63xx 2007 This driver supports the ethernet MACs in the Broadcom 63xx
2008 MIPS chipset family (BCM63XX). 2008 MIPS chipset family (BCM63XX).
2009 2009
2010 source "drivers/net/fs_enet/Kconfig" 2010 source "drivers/net/fs_enet/Kconfig"
2011 2011
2012 source "drivers/net/octeon/Kconfig" 2012 source "drivers/net/octeon/Kconfig"
2013 2013
2014 endif # NET_ETHERNET 2014 endif # NET_ETHERNET
2015 2015
2016 # 2016 #
2017 # Gigabit Ethernet 2017 # Gigabit Ethernet
2018 # 2018 #
2019 2019
2020 menuconfig NETDEV_1000 2020 menuconfig NETDEV_1000
2021 bool "Ethernet (1000 Mbit)" 2021 bool "Ethernet (1000 Mbit)"
2022 depends on !UML 2022 depends on !UML
2023 default y 2023 default y
2024 ---help--- 2024 ---help---
2025 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common 2025 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
2026 type of Local Area Network (LAN) in universities and companies. 2026 type of Local Area Network (LAN) in universities and companies.
2027 2027
2028 Say Y here to get to see options for Gigabit Ethernet drivers. 2028 Say Y here to get to see options for Gigabit Ethernet drivers.
2029 This option alone does not add any kernel code. 2029 This option alone does not add any kernel code.
2030 Note that drivers supporting both 100 and 1000 MBit may be listed 2030 Note that drivers supporting both 100 and 1000 MBit may be listed
2031 under "Ethernet (10 or 100MBit)" instead. 2031 under "Ethernet (10 or 100MBit)" instead.
2032 2032
2033 If you say N, all options in this submenu will be skipped and disabled. 2033 If you say N, all options in this submenu will be skipped and disabled.
2034 2034
2035 if NETDEV_1000 2035 if NETDEV_1000
2036 2036
2037 config ACENIC 2037 config ACENIC
2038 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support" 2038 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
2039 depends on PCI 2039 depends on PCI
2040 ---help--- 2040 ---help---
2041 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear 2041 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
2042 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet 2042 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
2043 adapter. The driver allows for using the Jumbo Frame option (9000 2043 adapter. The driver allows for using the Jumbo Frame option (9000
2044 bytes/frame) however it requires that your switches can handle this 2044 bytes/frame) however it requires that your switches can handle this
2045 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig 2045 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
2046 line. 2046 line.
2047 2047
2048 To compile this driver as a module, choose M here: the 2048 To compile this driver as a module, choose M here: the
2049 module will be called acenic. 2049 module will be called acenic.
2050 2050
2051 config ACENIC_OMIT_TIGON_I 2051 config ACENIC_OMIT_TIGON_I
2052 bool "Omit support for old Tigon I based AceNICs" 2052 bool "Omit support for old Tigon I based AceNICs"
2053 depends on ACENIC 2053 depends on ACENIC
2054 help 2054 help
2055 Say Y here if you only have Tigon II based AceNICs and want to leave 2055 Say Y here if you only have Tigon II based AceNICs and want to leave
2056 out support for the older Tigon I based cards which are no longer 2056 out support for the older Tigon I based cards which are no longer
2057 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B 2057 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
2058 version)). This will reduce the size of the driver object by 2058 version)). This will reduce the size of the driver object by
2059 app. 100KB. If you are not sure whether your card is a Tigon I or a 2059 app. 100KB. If you are not sure whether your card is a Tigon I or a
2060 Tigon II, say N here. 2060 Tigon II, say N here.
2061 2061
2062 The safe and default value for this is N. 2062 The safe and default value for this is N.
2063 2063
2064 config DL2K 2064 config DL2K
2065 tristate "DL2000/TC902x-based Gigabit Ethernet support" 2065 tristate "DL2000/TC902x-based Gigabit Ethernet support"
2066 depends on PCI 2066 depends on PCI
2067 select CRC32 2067 select CRC32
2068 help 2068 help
2069 This driver supports DL2000/TC902x-based Gigabit ethernet cards, 2069 This driver supports DL2000/TC902x-based Gigabit ethernet cards,
2070 which includes 2070 which includes
2071 D-Link DGE-550T Gigabit Ethernet Adapter. 2071 D-Link DGE-550T Gigabit Ethernet Adapter.
2072 D-Link DL2000-based Gigabit Ethernet Adapter. 2072 D-Link DL2000-based Gigabit Ethernet Adapter.
2073 Sundance/Tamarack TC902x Gigabit Ethernet Adapter. 2073 Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
2074 2074
2075 To compile this driver as a module, choose M here: the 2075 To compile this driver as a module, choose M here: the
2076 module will be called dl2k. 2076 module will be called dl2k.
2077 2077
2078 config E1000 2078 config E1000
2079 tristate "Intel(R) PRO/1000 Gigabit Ethernet support" 2079 tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
2080 depends on PCI 2080 depends on PCI
2081 ---help--- 2081 ---help---
2082 This driver supports Intel(R) PRO/1000 gigabit ethernet family of 2082 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
2083 adapters. For more information on how to identify your adapter, go 2083 adapters. For more information on how to identify your adapter, go
2084 to the Adapter & Driver ID Guide at: 2084 to the Adapter & Driver ID Guide at:
2085 2085
2086 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2086 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2087 2087
2088 For general information and support, go to the Intel support 2088 For general information and support, go to the Intel support
2089 website at: 2089 website at:
2090 2090
2091 <http://support.intel.com> 2091 <http://support.intel.com>
2092 2092
2093 More specific information on configuring the driver is in 2093 More specific information on configuring the driver is in
2094 <file:Documentation/networking/e1000.txt>. 2094 <file:Documentation/networking/e1000.txt>.
2095 2095
2096 To compile this driver as a module, choose M here. The module 2096 To compile this driver as a module, choose M here. The module
2097 will be called e1000. 2097 will be called e1000.
2098 2098
2099 config E1000E 2099 config E1000E
2100 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support" 2100 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
2101 depends on PCI && (!SPARC32 || BROKEN) 2101 depends on PCI && (!SPARC32 || BROKEN)
2102 ---help--- 2102 ---help---
2103 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit 2103 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
2104 ethernet family of adapters. For PCI or PCI-X e1000 adapters, 2104 ethernet family of adapters. For PCI or PCI-X e1000 adapters,
2105 use the regular e1000 driver For more information on how to 2105 use the regular e1000 driver For more information on how to
2106 identify your adapter, go to the Adapter & Driver ID Guide at: 2106 identify your adapter, go to the Adapter & Driver ID Guide at:
2107 2107
2108 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2108 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2109 2109
2110 For general information and support, go to the Intel support 2110 For general information and support, go to the Intel support
2111 website at: 2111 website at:
2112 2112
2113 <http://support.intel.com> 2113 <http://support.intel.com>
2114 2114
2115 To compile this driver as a module, choose M here. The module 2115 To compile this driver as a module, choose M here. The module
2116 will be called e1000e. 2116 will be called e1000e.
2117 2117
2118 config IP1000 2118 config IP1000
2119 tristate "IP1000 Gigabit Ethernet support" 2119 tristate "IP1000 Gigabit Ethernet support"
2120 depends on PCI && EXPERIMENTAL 2120 depends on PCI && EXPERIMENTAL
2121 select MII 2121 select MII
2122 ---help--- 2122 ---help---
2123 This driver supports IP1000 gigabit Ethernet cards. 2123 This driver supports IP1000 gigabit Ethernet cards.
2124 2124
2125 To compile this driver as a module, choose M here: the module 2125 To compile this driver as a module, choose M here: the module
2126 will be called ipg. This is recommended. 2126 will be called ipg. This is recommended.
2127 2127
2128 config IGB 2128 config IGB
2129 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support" 2129 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
2130 depends on PCI 2130 depends on PCI
2131 ---help--- 2131 ---help---
2132 This driver supports Intel(R) 82575/82576 gigabit ethernet family of 2132 This driver supports Intel(R) 82575/82576 gigabit ethernet family of
2133 adapters. For more information on how to identify your adapter, go 2133 adapters. For more information on how to identify your adapter, go
2134 to the Adapter & Driver ID Guide at: 2134 to the Adapter & Driver ID Guide at:
2135 2135
2136 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2136 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2137 2137
2138 For general information and support, go to the Intel support 2138 For general information and support, go to the Intel support
2139 website at: 2139 website at:
2140 2140
2141 <http://support.intel.com> 2141 <http://support.intel.com>
2142 2142
2143 More specific information on configuring the driver is in 2143 More specific information on configuring the driver is in
2144 <file:Documentation/networking/e1000.txt>. 2144 <file:Documentation/networking/e1000.txt>.
2145 2145
2146 To compile this driver as a module, choose M here. The module 2146 To compile this driver as a module, choose M here. The module
2147 will be called igb. 2147 will be called igb.
2148 2148
2149 config IGB_DCA 2149 config IGB_DCA
2150 bool "Direct Cache Access (DCA) Support" 2150 bool "Direct Cache Access (DCA) Support"
2151 default y 2151 default y
2152 depends on IGB && DCA && !(IGB=y && DCA=m) 2152 depends on IGB && DCA && !(IGB=y && DCA=m)
2153 ---help--- 2153 ---help---
2154 Say Y here if you want to use Direct Cache Access (DCA) in the 2154 Say Y here if you want to use Direct Cache Access (DCA) in the
2155 driver. DCA is a method for warming the CPU cache before data 2155 driver. DCA is a method for warming the CPU cache before data
2156 is used, with the intent of lessening the impact of cache misses. 2156 is used, with the intent of lessening the impact of cache misses.
2157 2157
2158 config IGBVF 2158 config IGBVF
2159 tristate "Intel(R) 82576 Virtual Function Ethernet support" 2159 tristate "Intel(R) 82576 Virtual Function Ethernet support"
2160 depends on PCI 2160 depends on PCI
2161 ---help--- 2161 ---help---
2162 This driver supports Intel(R) 82576 virtual functions. For more 2162 This driver supports Intel(R) 82576 virtual functions. For more
2163 information on how to identify your adapter, go to the Adapter & 2163 information on how to identify your adapter, go to the Adapter &
2164 Driver ID Guide at: 2164 Driver ID Guide at:
2165 2165
2166 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2166 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2167 2167
2168 For general information and support, go to the Intel support 2168 For general information and support, go to the Intel support
2169 website at: 2169 website at:
2170 2170
2171 <http://support.intel.com> 2171 <http://support.intel.com>
2172 2172
2173 More specific information on configuring the driver is in 2173 More specific information on configuring the driver is in
2174 <file:Documentation/networking/e1000.txt>. 2174 <file:Documentation/networking/e1000.txt>.
2175 2175
2176 To compile this driver as a module, choose M here. The module 2176 To compile this driver as a module, choose M here. The module
2177 will be called igbvf. 2177 will be called igbvf.
2178 2178
2179 source "drivers/net/ixp2000/Kconfig" 2179 source "drivers/net/ixp2000/Kconfig"
2180 2180
2181 config MYRI_SBUS 2181 config MYRI_SBUS
2182 tristate "MyriCOM Gigabit Ethernet support" 2182 tristate "MyriCOM Gigabit Ethernet support"
2183 depends on SBUS 2183 depends on SBUS
2184 help 2184 help
2185 This driver supports MyriCOM Sbus gigabit Ethernet cards. 2185 This driver supports MyriCOM Sbus gigabit Ethernet cards.
2186 2186
2187 To compile this driver as a module, choose M here: the module 2187 To compile this driver as a module, choose M here: the module
2188 will be called myri_sbus. This is recommended. 2188 will be called myri_sbus. This is recommended.
2189 2189
2190 config NS83820 2190 config NS83820
2191 tristate "National Semiconductor DP83820 support" 2191 tristate "National Semiconductor DP83820 support"
2192 depends on PCI 2192 depends on PCI
2193 help 2193 help
2194 This is a driver for the National Semiconductor DP83820 series 2194 This is a driver for the National Semiconductor DP83820 series
2195 of gigabit ethernet MACs. Cards using this chipset include 2195 of gigabit ethernet MACs. Cards using this chipset include
2196 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX, 2196 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
2197 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of 2197 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
2198 zero copy. 2198 zero copy.
2199 2199
2200 config HAMACHI 2200 config HAMACHI
2201 tristate "Packet Engines Hamachi GNIC-II support" 2201 tristate "Packet Engines Hamachi GNIC-II support"
2202 depends on PCI 2202 depends on PCI
2203 select MII 2203 select MII
2204 help 2204 help
2205 If you have a Gigabit Ethernet card of this type, say Y and read 2205 If you have a Gigabit Ethernet card of this type, say Y and read
2206 the Ethernet-HOWTO, available from 2206 the Ethernet-HOWTO, available from
2207 <http://www.tldp.org/docs.html#howto>. 2207 <http://www.tldp.org/docs.html#howto>.
2208 2208
2209 To compile this driver as a module, choose M here. The module will be 2209 To compile this driver as a module, choose M here. The module will be
2210 called hamachi. 2210 called hamachi.
2211 2211
2212 config YELLOWFIN 2212 config YELLOWFIN
2213 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)" 2213 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
2214 depends on PCI && EXPERIMENTAL 2214 depends on PCI && EXPERIMENTAL
2215 select CRC32 2215 select CRC32
2216 ---help--- 2216 ---help---
2217 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet 2217 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
2218 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is 2218 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
2219 used by the Beowulf Linux cluster project. See 2219 used by the Beowulf Linux cluster project. See
2220 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more 2220 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
2221 information about this driver in particular and Beowulf in general. 2221 information about this driver in particular and Beowulf in general.
2222 2222
2223 To compile this driver as a module, choose M here: the module 2223 To compile this driver as a module, choose M here: the module
2224 will be called yellowfin. This is recommended. 2224 will be called yellowfin. This is recommended.
2225 2225
2226 config R8169 2226 config R8169
2227 tristate "Realtek 8169 gigabit ethernet support" 2227 tristate "Realtek 8169 gigabit ethernet support"
2228 depends on PCI 2228 depends on PCI
2229 select FW_LOADER 2229 select FW_LOADER
2230 select CRC32 2230 select CRC32
2231 select MII 2231 select MII
2232 ---help--- 2232 ---help---
2233 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter. 2233 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
2234 2234
2235 To compile this driver as a module, choose M here: the module 2235 To compile this driver as a module, choose M here: the module
2236 will be called r8169. This is recommended. 2236 will be called r8169. This is recommended.
2237 2237
2238 config R8169_VLAN 2238 config R8169_VLAN
2239 bool "VLAN support" 2239 bool "VLAN support"
2240 depends on R8169 && VLAN_8021Q 2240 depends on R8169 && VLAN_8021Q
2241 ---help--- 2241 ---help---
2242 Say Y here for the r8169 driver to support the functions required 2242 Say Y here for the r8169 driver to support the functions required
2243 by the kernel 802.1Q code. 2243 by the kernel 802.1Q code.
2244 2244
2245 If in doubt, say Y. 2245 If in doubt, say Y.
2246 2246
2247 config SB1250_MAC 2247 config SB1250_MAC
2248 tristate "SB1250 Gigabit Ethernet support" 2248 tristate "SB1250 Gigabit Ethernet support"
2249 depends on SIBYTE_SB1xxx_SOC 2249 depends on SIBYTE_SB1xxx_SOC
2250 select PHYLIB 2250 select PHYLIB
2251 ---help--- 2251 ---help---
2252 This driver supports Gigabit Ethernet interfaces based on the 2252 This driver supports Gigabit Ethernet interfaces based on the
2253 Broadcom SiByte family of System-On-a-Chip parts. They include 2253 Broadcom SiByte family of System-On-a-Chip parts. They include
2254 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455 2254 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
2255 and BCM1480 chips. 2255 and BCM1480 chips.
2256 2256
2257 To compile this driver as a module, choose M here: the module 2257 To compile this driver as a module, choose M here: the module
2258 will be called sb1250-mac. 2258 will be called sb1250-mac.
2259 2259
2260 config SIS190 2260 config SIS190
2261 tristate "SiS190/SiS191 gigabit ethernet support" 2261 tristate "SiS190/SiS191 gigabit ethernet support"
2262 depends on PCI 2262 depends on PCI
2263 select CRC32 2263 select CRC32
2264 select MII 2264 select MII
2265 ---help--- 2265 ---help---
2266 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or 2266 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
2267 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to 2267 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
2268 appear in lan on motherboard designs which are based on SiS 965 2268 appear in lan on motherboard designs which are based on SiS 965
2269 and SiS 966 south bridge. 2269 and SiS 966 south bridge.
2270 2270
2271 To compile this driver as a module, choose M here: the module 2271 To compile this driver as a module, choose M here: the module
2272 will be called sis190. This is recommended. 2272 will be called sis190. This is recommended.
2273 2273
2274 config SKGE 2274 config SKGE
2275 tristate "New SysKonnect GigaEthernet support" 2275 tristate "New SysKonnect GigaEthernet support"
2276 depends on PCI 2276 depends on PCI
2277 select CRC32 2277 select CRC32
2278 ---help--- 2278 ---help---
2279 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx 2279 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
2280 and related Gigabit Ethernet adapters. It is a new smaller driver 2280 and related Gigabit Ethernet adapters. It is a new smaller driver
2281 with better performance and more complete ethtool support. 2281 with better performance and more complete ethtool support.
2282 2282
2283 It does not support the link failover and network management 2283 It does not support the link failover and network management
2284 features that "portable" vendor supplied sk98lin driver does. 2284 features that "portable" vendor supplied sk98lin driver does.
2285 2285
2286 This driver supports adapters based on the original Yukon chipset: 2286 This driver supports adapters based on the original Yukon chipset:
2287 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T, 2287 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
2288 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872. 2288 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
2289 2289
2290 It does not support the newer Yukon2 chipset: a separate driver, 2290 It does not support the newer Yukon2 chipset: a separate driver,
2291 sky2, is provided for Yukon2-based adapters. 2291 sky2, is provided for Yukon2-based adapters.
2292 2292
2293 To compile this driver as a module, choose M here: the module 2293 To compile this driver as a module, choose M here: the module
2294 will be called skge. This is recommended. 2294 will be called skge. This is recommended.
2295 2295
2296 config SKGE_DEBUG 2296 config SKGE_DEBUG
2297 bool "Debugging interface" 2297 bool "Debugging interface"
2298 depends on SKGE && DEBUG_FS 2298 depends on SKGE && DEBUG_FS
2299 help 2299 help
2300 This option adds the ability to dump driver state for debugging. 2300 This option adds the ability to dump driver state for debugging.
2301 The file /sys/kernel/debug/skge/ethX displays the state of the internal 2301 The file /sys/kernel/debug/skge/ethX displays the state of the internal
2302 transmit and receive rings. 2302 transmit and receive rings.
2303 2303
2304 If unsure, say N. 2304 If unsure, say N.
2305 2305
2306 config SKY2 2306 config SKY2
2307 tristate "SysKonnect Yukon2 support" 2307 tristate "SysKonnect Yukon2 support"
2308 depends on PCI 2308 depends on PCI
2309 select CRC32 2309 select CRC32
2310 ---help--- 2310 ---help---
2311 This driver supports Gigabit Ethernet adapters based on the 2311 This driver supports Gigabit Ethernet adapters based on the
2312 Marvell Yukon 2 chipset: 2312 Marvell Yukon 2 chipset:
2313 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/ 2313 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
2314 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21 2314 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
2315 2315
2316 There is companion driver for the older Marvell Yukon and 2316 There is companion driver for the older Marvell Yukon and
2317 Genesis based adapters: skge. 2317 Genesis based adapters: skge.
2318 2318
2319 To compile this driver as a module, choose M here: the module 2319 To compile this driver as a module, choose M here: the module
2320 will be called sky2. This is recommended. 2320 will be called sky2. This is recommended.
2321 2321
2322 config SKY2_DEBUG 2322 config SKY2_DEBUG
2323 bool "Debugging interface" 2323 bool "Debugging interface"
2324 depends on SKY2 && DEBUG_FS 2324 depends on SKY2 && DEBUG_FS
2325 help 2325 help
2326 This option adds the ability to dump driver state for debugging. 2326 This option adds the ability to dump driver state for debugging.
2327 The file /sys/kernel/debug/sky2/ethX displays the state of the internal 2327 The file /sys/kernel/debug/sky2/ethX displays the state of the internal
2328 transmit and receive rings. 2328 transmit and receive rings.
2329 2329
2330 If unsure, say N. 2330 If unsure, say N.
2331 2331
2332 config VIA_VELOCITY 2332 config VIA_VELOCITY
2333 tristate "VIA Velocity support" 2333 tristate "VIA Velocity support"
2334 depends on PCI 2334 depends on PCI
2335 select CRC32 2335 select CRC32
2336 select CRC_CCITT 2336 select CRC_CCITT
2337 select MII 2337 select MII
2338 help 2338 help
2339 If you have a VIA "Velocity" based network card say Y here. 2339 If you have a VIA "Velocity" based network card say Y here.
2340 2340
2341 To compile this driver as a module, choose M here. The module 2341 To compile this driver as a module, choose M here. The module
2342 will be called via-velocity. 2342 will be called via-velocity.
2343 2343
2344 config TIGON3 2344 config TIGON3
2345 tristate "Broadcom Tigon3 support" 2345 tristate "Broadcom Tigon3 support"
2346 depends on PCI 2346 depends on PCI
2347 select PHYLIB 2347 select PHYLIB
2348 help 2348 help
2349 This driver supports Broadcom Tigon3 based gigabit Ethernet cards. 2349 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
2350 2350
2351 To compile this driver as a module, choose M here: the module 2351 To compile this driver as a module, choose M here: the module
2352 will be called tg3. This is recommended. 2352 will be called tg3. This is recommended.
2353 2353
2354 config BNX2 2354 config BNX2
2355 tristate "Broadcom NetXtremeII support" 2355 tristate "Broadcom NetXtremeII support"
2356 depends on PCI 2356 depends on PCI
2357 select CRC32 2357 select CRC32
2358 select FW_LOADER 2358 select FW_LOADER
2359 help 2359 help
2360 This driver supports Broadcom NetXtremeII gigabit Ethernet cards. 2360 This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
2361 2361
2362 To compile this driver as a module, choose M here: the module 2362 To compile this driver as a module, choose M here: the module
2363 will be called bnx2. This is recommended. 2363 will be called bnx2. This is recommended.
2364 2364
2365 config CNIC 2365 config CNIC
2366 tristate "Broadcom CNIC support" 2366 tristate "Broadcom CNIC support"
2367 depends on PCI 2367 depends on PCI
2368 select BNX2 2368 select BNX2
2369 select UIO 2369 select UIO
2370 help 2370 help
2371 This driver supports offload features of Broadcom NetXtremeII 2371 This driver supports offload features of Broadcom NetXtremeII
2372 gigabit Ethernet cards. 2372 gigabit Ethernet cards.
2373 2373
2374 To compile this driver as a module, choose M here: the module 2374 To compile this driver as a module, choose M here: the module
2375 will be called cnic. This is recommended. 2375 will be called cnic. This is recommended.
2376 2376
2377 config SPIDER_NET 2377 config SPIDER_NET
2378 tristate "Spider Gigabit Ethernet driver" 2378 tristate "Spider Gigabit Ethernet driver"
2379 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB) 2379 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
2380 select FW_LOADER 2380 select FW_LOADER
2381 help 2381 help
2382 This driver supports the Gigabit Ethernet chips present on the 2382 This driver supports the Gigabit Ethernet chips present on the
2383 Cell Processor-Based Blades from IBM. 2383 Cell Processor-Based Blades from IBM.
2384 2384
2385 config TSI108_ETH 2385 config TSI108_ETH
2386 tristate "Tundra TSI108 gigabit Ethernet support" 2386 tristate "Tundra TSI108 gigabit Ethernet support"
2387 depends on TSI108_BRIDGE 2387 depends on TSI108_BRIDGE
2388 help 2388 help
2389 This driver supports Tundra TSI108 gigabit Ethernet ports. 2389 This driver supports Tundra TSI108 gigabit Ethernet ports.
2390 To compile this driver as a module, choose M here: the module 2390 To compile this driver as a module, choose M here: the module
2391 will be called tsi108_eth. 2391 will be called tsi108_eth.
2392 2392
2393 config GELIC_NET 2393 config GELIC_NET
2394 tristate "PS3 Gigabit Ethernet driver" 2394 tristate "PS3 Gigabit Ethernet driver"
2395 depends on PPC_PS3 2395 depends on PPC_PS3
2396 select PS3_SYS_MANAGER 2396 select PS3_SYS_MANAGER
2397 help 2397 help
2398 This driver supports the network device on the PS3 game 2398 This driver supports the network device on the PS3 game
2399 console. This driver has built-in support for Ethernet. 2399 console. This driver has built-in support for Ethernet.
2400 2400
2401 To compile this driver as a module, choose M here: the 2401 To compile this driver as a module, choose M here: the
2402 module will be called ps3_gelic. 2402 module will be called ps3_gelic.
2403 2403
2404 config GELIC_WIRELESS 2404 config GELIC_WIRELESS
2405 bool "PS3 Wireless support" 2405 bool "PS3 Wireless support"
2406 depends on WLAN 2406 depends on WLAN
2407 depends on GELIC_NET 2407 depends on GELIC_NET
2408 select WIRELESS_EXT 2408 select WIRELESS_EXT
2409 help 2409 help
2410 This option adds the support for the wireless feature of PS3. 2410 This option adds the support for the wireless feature of PS3.
2411 If you have the wireless-less model of PS3 or have no plan to 2411 If you have the wireless-less model of PS3 or have no plan to
2412 use wireless feature, disabling this option saves memory. As 2412 use wireless feature, disabling this option saves memory. As
2413 the driver automatically distinguishes the models, you can 2413 the driver automatically distinguishes the models, you can
2414 safely enable this option even if you have a wireless-less model. 2414 safely enable this option even if you have a wireless-less model.
2415 2415
2416 config FSL_PQ_MDIO 2416 config FSL_PQ_MDIO
2417 tristate "Freescale PQ MDIO" 2417 tristate "Freescale PQ MDIO"
2418 depends on FSL_SOC 2418 depends on FSL_SOC
2419 select PHYLIB 2419 select PHYLIB
2420 help 2420 help
2421 This driver supports the MDIO bus used by the gianfar and UCC drivers. 2421 This driver supports the MDIO bus used by the gianfar and UCC drivers.
2422 2422
2423 config GIANFAR 2423 config GIANFAR
2424 tristate "Gianfar Ethernet" 2424 tristate "Gianfar Ethernet"
2425 depends on FSL_SOC 2425 depends on FSL_SOC
2426 select FSL_PQ_MDIO 2426 select FSL_PQ_MDIO
2427 select PHYLIB 2427 select PHYLIB
2428 select CRC32 2428 select CRC32
2429 help 2429 help
2430 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx, 2430 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
2431 and MPC86xx family of chips, and the FEC on the 8540. 2431 and MPC86xx family of chips, and the FEC on the 8540.
2432 2432
2433 config UCC_GETH 2433 config UCC_GETH
2434 tristate "Freescale QE Gigabit Ethernet" 2434 tristate "Freescale QE Gigabit Ethernet"
2435 depends on QUICC_ENGINE 2435 depends on QUICC_ENGINE
2436 select FSL_PQ_MDIO 2436 select FSL_PQ_MDIO
2437 select PHYLIB 2437 select PHYLIB
2438 help 2438 help
2439 This driver supports the Gigabit Ethernet mode of the QUICC Engine, 2439 This driver supports the Gigabit Ethernet mode of the QUICC Engine,
2440 which is available on some Freescale SOCs. 2440 which is available on some Freescale SOCs.
2441 2441
2442 config UGETH_TX_ON_DEMAND 2442 config UGETH_TX_ON_DEMAND
2443 bool "Transmit on Demand support" 2443 bool "Transmit on Demand support"
2444 depends on UCC_GETH 2444 depends on UCC_GETH
2445 2445
2446 config MV643XX_ETH 2446 config MV643XX_ETH
2447 tristate "Marvell Discovery (643XX) and Orion ethernet support" 2447 tristate "Marvell Discovery (643XX) and Orion ethernet support"
2448 depends on (MV64X60 || PPC32 || PLAT_ORION) && INET 2448 depends on (MV64X60 || PPC32 || PLAT_ORION) && INET
2449 select INET_LRO 2449 select INET_LRO
2450 select PHYLIB 2450 select PHYLIB
2451 help 2451 help
2452 This driver supports the gigabit ethernet MACs in the 2452 This driver supports the gigabit ethernet MACs in the
2453 Marvell Discovery PPC/MIPS chipset family (MV643XX) and 2453 Marvell Discovery PPC/MIPS chipset family (MV643XX) and
2454 in the Marvell Orion ARM SoC family. 2454 in the Marvell Orion ARM SoC family.
2455 2455
2456 Some boards that use the Discovery chipset are the Momenco 2456 Some boards that use the Discovery chipset are the Momenco
2457 Ocelot C and Jaguar ATX and Pegasos II. 2457 Ocelot C and Jaguar ATX and Pegasos II.
2458 2458
2459 config XILINX_LL_TEMAC 2459 config XILINX_LL_TEMAC
2460 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver" 2460 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
2461 depends on PPC || MICROBLAZE 2461 depends on PPC || MICROBLAZE
2462 select PHYLIB 2462 select PHYLIB
2463 help 2463 help
2464 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC 2464 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
2465 core used in Xilinx Spartan and Virtex FPGAs 2465 core used in Xilinx Spartan and Virtex FPGAs
2466 2466
2467 config QLA3XXX 2467 config QLA3XXX
2468 tristate "QLogic QLA3XXX Network Driver Support" 2468 tristate "QLogic QLA3XXX Network Driver Support"
2469 depends on PCI 2469 depends on PCI
2470 help 2470 help
2471 This driver supports QLogic ISP3XXX gigabit Ethernet cards. 2471 This driver supports QLogic ISP3XXX gigabit Ethernet cards.
2472 2472
2473 To compile this driver as a module, choose M here: the module 2473 To compile this driver as a module, choose M here: the module
2474 will be called qla3xxx. 2474 will be called qla3xxx.
2475 2475
2476 config ATL1 2476 config ATL1
2477 tristate "Atheros/Attansic L1 Gigabit Ethernet support" 2477 tristate "Atheros/Attansic L1 Gigabit Ethernet support"
2478 depends on PCI 2478 depends on PCI
2479 select CRC32 2479 select CRC32
2480 select MII 2480 select MII
2481 help 2481 help
2482 This driver supports the Atheros/Attansic L1 gigabit ethernet 2482 This driver supports the Atheros/Attansic L1 gigabit ethernet
2483 adapter. 2483 adapter.
2484 2484
2485 To compile this driver as a module, choose M here. The module 2485 To compile this driver as a module, choose M here. The module
2486 will be called atl1. 2486 will be called atl1.
2487 2487
2488 config ATL1E 2488 config ATL1E
2489 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)" 2489 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
2490 depends on PCI && EXPERIMENTAL 2490 depends on PCI && EXPERIMENTAL
2491 select CRC32 2491 select CRC32
2492 select MII 2492 select MII
2493 help 2493 help
2494 This driver supports the Atheros L1E gigabit ethernet adapter. 2494 This driver supports the Atheros L1E gigabit ethernet adapter.
2495 2495
2496 To compile this driver as a module, choose M here. The module 2496 To compile this driver as a module, choose M here. The module
2497 will be called atl1e. 2497 will be called atl1e.
2498 2498
2499 config ATL1C 2499 config ATL1C
2500 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)" 2500 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
2501 depends on PCI && EXPERIMENTAL 2501 depends on PCI && EXPERIMENTAL
2502 select CRC32 2502 select CRC32
2503 select MII 2503 select MII
2504 help 2504 help
2505 This driver supports the Atheros L1C gigabit ethernet adapter. 2505 This driver supports the Atheros L1C gigabit ethernet adapter.
2506 2506
2507 To compile this driver as a module, choose M here. The module 2507 To compile this driver as a module, choose M here. The module
2508 will be called atl1c. 2508 will be called atl1c.
2509 2509
2510 config JME 2510 config JME
2511 tristate "JMicron(R) PCI-Express Gigabit Ethernet support" 2511 tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
2512 depends on PCI 2512 depends on PCI
2513 select CRC32 2513 select CRC32
2514 select MII 2514 select MII
2515 ---help--- 2515 ---help---
2516 This driver supports the PCI-Express gigabit ethernet adapters 2516 This driver supports the PCI-Express gigabit ethernet adapters
2517 based on JMicron JMC250 chipset. 2517 based on JMicron JMC250 chipset.
2518 2518
2519 To compile this driver as a module, choose M here. The module 2519 To compile this driver as a module, choose M here. The module
2520 will be called jme. 2520 will be called jme.
2521 2521
2522 config S6GMAC 2522 config S6GMAC
2523 tristate "S6105 GMAC ethernet support" 2523 tristate "S6105 GMAC ethernet support"
2524 depends on XTENSA_VARIANT_S6000 2524 depends on XTENSA_VARIANT_S6000
2525 select PHYLIB 2525 select PHYLIB
2526 help 2526 help
2527 This driver supports the on chip ethernet device on the 2527 This driver supports the on chip ethernet device on the
2528 S6105 xtensa processor. 2528 S6105 xtensa processor.
2529 2529
2530 To compile this driver as a module, choose M here. The module 2530 To compile this driver as a module, choose M here. The module
2531 will be called s6gmac. 2531 will be called s6gmac.
2532 2532
2533 source "drivers/net/stmmac/Kconfig" 2533 source "drivers/net/stmmac/Kconfig"
2534 2534
2535 config PCH_GBE 2535 config PCH_GBE
2536 tristate "PCH Gigabit Ethernet" 2536 tristate "PCH Gigabit Ethernet"
2537 depends on PCI 2537 depends on PCI
2538 select MII 2538 select MII
2539 ---help--- 2539 ---help---
2540 This is a gigabit ethernet driver for EG20T PCH. 2540 This is a gigabit ethernet driver for EG20T PCH.
2541 EG20T PCH is the platform controller hub that is used in Intel's 2541 EG20T PCH is the platform controller hub that is used in Intel's
2542 general embedded platform. 2542 general embedded platform.
2543 EG20T PCH has Gigabit Ethernet interface. 2543 EG20T PCH has Gigabit Ethernet interface.
2544 Using this interface, it is able to access system devices connected 2544 Using this interface, it is able to access system devices connected
2545 to Gigabit Ethernet. 2545 to Gigabit Ethernet.
2546 This driver enables Gigabit Ethernet function. 2546 This driver enables Gigabit Ethernet function.
2547 2547
2548 endif # NETDEV_1000 2548 endif # NETDEV_1000
2549 2549
2550 # 2550 #
2551 # 10 Gigabit Ethernet 2551 # 10 Gigabit Ethernet
2552 # 2552 #
2553 2553
2554 menuconfig NETDEV_10000 2554 menuconfig NETDEV_10000
2555 bool "Ethernet (10000 Mbit)" 2555 bool "Ethernet (10000 Mbit)"
2556 depends on !UML 2556 depends on !UML
2557 default y 2557 default y
2558 ---help--- 2558 ---help---
2559 Say Y here to get to see options for 10 Gigabit Ethernet drivers. 2559 Say Y here to get to see options for 10 Gigabit Ethernet drivers.
2560 This option alone does not add any kernel code. 2560 This option alone does not add any kernel code.
2561 2561
2562 If you say N, all options in this submenu will be skipped and disabled. 2562 If you say N, all options in this submenu will be skipped and disabled.
2563 2563
2564 if NETDEV_10000 2564 if NETDEV_10000
2565 2565
2566 config MDIO 2566 config MDIO
2567 tristate 2567 tristate
2568 2568
2569 config CHELSIO_T1 2569 config CHELSIO_T1
2570 tristate "Chelsio 10Gb Ethernet support" 2570 tristate "Chelsio 10Gb Ethernet support"
2571 depends on PCI 2571 depends on PCI
2572 select CRC32 2572 select CRC32
2573 select MDIO 2573 select MDIO
2574 help 2574 help
2575 This driver supports Chelsio gigabit and 10-gigabit 2575 This driver supports Chelsio gigabit and 10-gigabit
2576 Ethernet cards. More information about adapter features and 2576 Ethernet cards. More information about adapter features and
2577 performance tuning is in <file:Documentation/networking/cxgb.txt>. 2577 performance tuning is in <file:Documentation/networking/cxgb.txt>.
2578 2578
2579 For general information about Chelsio and our products, visit 2579 For general information about Chelsio and our products, visit
2580 our website at <http://www.chelsio.com>. 2580 our website at <http://www.chelsio.com>.
2581 2581
2582 For customer support, please visit our customer support page at 2582 For customer support, please visit our customer support page at
2583 <http://www.chelsio.com/support.html>. 2583 <http://www.chelsio.com/support.html>.
2584 2584
2585 Please send feedback to <linux-bugs@chelsio.com>. 2585 Please send feedback to <linux-bugs@chelsio.com>.
2586 2586
2587 To compile this driver as a module, choose M here: the module 2587 To compile this driver as a module, choose M here: the module
2588 will be called cxgb. 2588 will be called cxgb.
2589 2589
2590 config CHELSIO_T1_1G 2590 config CHELSIO_T1_1G
2591 bool "Chelsio gigabit Ethernet support" 2591 bool "Chelsio gigabit Ethernet support"
2592 depends on CHELSIO_T1 2592 depends on CHELSIO_T1
2593 help 2593 help
2594 Enables support for Chelsio's gigabit Ethernet PCI cards. If you 2594 Enables support for Chelsio's gigabit Ethernet PCI cards. If you
2595 are using only 10G cards say 'N' here. 2595 are using only 10G cards say 'N' here.
2596 2596
2597 config CHELSIO_T3_DEPENDS 2597 config CHELSIO_T3_DEPENDS
2598 tristate 2598 tristate
2599 depends on PCI && INET 2599 depends on PCI && INET
2600 default y 2600 default y
2601 2601
2602 config CHELSIO_T3 2602 config CHELSIO_T3
2603 tristate "Chelsio Communications T3 10Gb Ethernet support" 2603 tristate "Chelsio Communications T3 10Gb Ethernet support"
2604 depends on CHELSIO_T3_DEPENDS 2604 depends on CHELSIO_T3_DEPENDS
2605 select FW_LOADER 2605 select FW_LOADER
2606 select MDIO 2606 select MDIO
2607 help 2607 help
2608 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet 2608 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
2609 adapters. 2609 adapters.
2610 2610
2611 For general information about Chelsio and our products, visit 2611 For general information about Chelsio and our products, visit
2612 our website at <http://www.chelsio.com>. 2612 our website at <http://www.chelsio.com>.
2613 2613
2614 For customer support, please visit our customer support page at 2614 For customer support, please visit our customer support page at
2615 <http://www.chelsio.com/support.html>. 2615 <http://www.chelsio.com/support.html>.
2616 2616
2617 Please send feedback to <linux-bugs@chelsio.com>. 2617 Please send feedback to <linux-bugs@chelsio.com>.
2618 2618
2619 To compile this driver as a module, choose M here: the module 2619 To compile this driver as a module, choose M here: the module
2620 will be called cxgb3. 2620 will be called cxgb3.
2621 2621
2622 config CHELSIO_T4_DEPENDS 2622 config CHELSIO_T4_DEPENDS
2623 tristate 2623 tristate
2624 depends on PCI && INET 2624 depends on PCI && INET
2625 default y 2625 default y
2626 2626
2627 config CHELSIO_T4 2627 config CHELSIO_T4
2628 tristate "Chelsio Communications T4 Ethernet support" 2628 tristate "Chelsio Communications T4 Ethernet support"
2629 depends on CHELSIO_T4_DEPENDS 2629 depends on CHELSIO_T4_DEPENDS
2630 select FW_LOADER 2630 select FW_LOADER
2631 select MDIO 2631 select MDIO
2632 help 2632 help
2633 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet 2633 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
2634 adapters. 2634 adapters.
2635 2635
2636 For general information about Chelsio and our products, visit 2636 For general information about Chelsio and our products, visit
2637 our website at <http://www.chelsio.com>. 2637 our website at <http://www.chelsio.com>.
2638 2638
2639 For customer support, please visit our customer support page at 2639 For customer support, please visit our customer support page at
2640 <http://www.chelsio.com/support.html>. 2640 <http://www.chelsio.com/support.html>.
2641 2641
2642 Please send feedback to <linux-bugs@chelsio.com>. 2642 Please send feedback to <linux-bugs@chelsio.com>.
2643 2643
2644 To compile this driver as a module choose M here; the module 2644 To compile this driver as a module choose M here; the module
2645 will be called cxgb4. 2645 will be called cxgb4.
2646 2646
2647 config CHELSIO_T4VF_DEPENDS 2647 config CHELSIO_T4VF_DEPENDS
2648 tristate 2648 tristate
2649 depends on PCI && INET 2649 depends on PCI && INET
2650 default y 2650 default y
2651 2651
2652 config CHELSIO_T4VF 2652 config CHELSIO_T4VF
2653 tristate "Chelsio Communications T4 Virtual Function Ethernet support" 2653 tristate "Chelsio Communications T4 Virtual Function Ethernet support"
2654 depends on CHELSIO_T4VF_DEPENDS 2654 depends on CHELSIO_T4VF_DEPENDS
2655 help 2655 help
2656 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet 2656 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet
2657 adapters with PCI-E SR-IOV Virtual Functions. 2657 adapters with PCI-E SR-IOV Virtual Functions.
2658 2658
2659 For general information about Chelsio and our products, visit 2659 For general information about Chelsio and our products, visit
2660 our website at <http://www.chelsio.com>. 2660 our website at <http://www.chelsio.com>.
2661 2661
2662 For customer support, please visit our customer support page at 2662 For customer support, please visit our customer support page at
2663 <http://www.chelsio.com/support.html>. 2663 <http://www.chelsio.com/support.html>.
2664 2664
2665 Please send feedback to <linux-bugs@chelsio.com>. 2665 Please send feedback to <linux-bugs@chelsio.com>.
2666 2666
2667 To compile this driver as a module choose M here; the module 2667 To compile this driver as a module choose M here; the module
2668 will be called cxgb4vf. 2668 will be called cxgb4vf.
2669 2669
2670 config EHEA 2670 config EHEA
2671 tristate "eHEA Ethernet support" 2671 tristate "eHEA Ethernet support"
2672 depends on IBMEBUS && INET && SPARSEMEM 2672 depends on IBMEBUS && INET && SPARSEMEM
2673 select INET_LRO 2673 select INET_LRO
2674 ---help--- 2674 ---help---
2675 This driver supports the IBM pSeries eHEA ethernet adapter. 2675 This driver supports the IBM pSeries eHEA ethernet adapter.
2676 2676
2677 To compile the driver as a module, choose M here. The module 2677 To compile the driver as a module, choose M here. The module
2678 will be called ehea. 2678 will be called ehea.
2679 2679
2680 config ENIC 2680 config ENIC
2681 tristate "Cisco VIC Ethernet NIC Support" 2681 tristate "Cisco VIC Ethernet NIC Support"
2682 depends on PCI && INET 2682 depends on PCI && INET
2683 help 2683 help
2684 This enables the support for the Cisco VIC Ethernet card. 2684 This enables the support for the Cisco VIC Ethernet card.
2685 2685
2686 config IXGBE 2686 config IXGBE
2687 tristate "Intel(R) 10GbE PCI Express adapters support" 2687 tristate "Intel(R) 10GbE PCI Express adapters support"
2688 depends on PCI && INET 2688 depends on PCI && INET
2689 select MDIO 2689 select MDIO
2690 ---help--- 2690 ---help---
2691 This driver supports Intel(R) 10GbE PCI Express family of 2691 This driver supports Intel(R) 10GbE PCI Express family of
2692 adapters. For more information on how to identify your adapter, go 2692 adapters. For more information on how to identify your adapter, go
2693 to the Adapter & Driver ID Guide at: 2693 to the Adapter & Driver ID Guide at:
2694 2694
2695 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2695 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2696 2696
2697 For general information and support, go to the Intel support 2697 For general information and support, go to the Intel support
2698 website at: 2698 website at:
2699 2699
2700 <http://support.intel.com> 2700 <http://support.intel.com>
2701 2701
2702 To compile this driver as a module, choose M here. The module 2702 To compile this driver as a module, choose M here. The module
2703 will be called ixgbe. 2703 will be called ixgbe.
2704 2704
2705 config IXGBE_DCA 2705 config IXGBE_DCA
2706 bool "Direct Cache Access (DCA) Support" 2706 bool "Direct Cache Access (DCA) Support"
2707 default y 2707 default y
2708 depends on IXGBE && DCA && !(IXGBE=y && DCA=m) 2708 depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
2709 ---help--- 2709 ---help---
2710 Say Y here if you want to use Direct Cache Access (DCA) in the 2710 Say Y here if you want to use Direct Cache Access (DCA) in the
2711 driver. DCA is a method for warming the CPU cache before data 2711 driver. DCA is a method for warming the CPU cache before data
2712 is used, with the intent of lessening the impact of cache misses. 2712 is used, with the intent of lessening the impact of cache misses.
2713 2713
2714 config IXGBE_DCB 2714 config IXGBE_DCB
2715 bool "Data Center Bridging (DCB) Support" 2715 bool "Data Center Bridging (DCB) Support"
2716 default n 2716 default n
2717 depends on IXGBE && DCB 2717 depends on IXGBE && DCB
2718 ---help--- 2718 ---help---
2719 Say Y here if you want to use Data Center Bridging (DCB) in the 2719 Say Y here if you want to use Data Center Bridging (DCB) in the
2720 driver. 2720 driver.
2721 2721
2722 If unsure, say N. 2722 If unsure, say N.
2723 2723
2724 config IXGBEVF 2724 config IXGBEVF
2725 tristate "Intel(R) 82599 Virtual Function Ethernet support" 2725 tristate "Intel(R) 82599 Virtual Function Ethernet support"
2726 depends on PCI_MSI 2726 depends on PCI_MSI
2727 ---help--- 2727 ---help---
2728 This driver supports Intel(R) 82599 virtual functions. For more 2728 This driver supports Intel(R) 82599 virtual functions. For more
2729 information on how to identify your adapter, go to the Adapter & 2729 information on how to identify your adapter, go to the Adapter &
2730 Driver ID Guide at: 2730 Driver ID Guide at:
2731 2731
2732 <http://support.intel.com/support/network/sb/CS-008441.htm> 2732 <http://support.intel.com/support/network/sb/CS-008441.htm>
2733 2733
2734 For general information and support, go to the Intel support 2734 For general information and support, go to the Intel support
2735 website at: 2735 website at:
2736 2736
2737 <http://support.intel.com> 2737 <http://support.intel.com>
2738 2738
2739 More specific information on configuring the driver is in 2739 More specific information on configuring the driver is in
2740 <file:Documentation/networking/ixgbevf.txt>. 2740 <file:Documentation/networking/ixgbevf.txt>.
2741 2741
2742 To compile this driver as a module, choose M here. The module 2742 To compile this driver as a module, choose M here. The module
2743 will be called ixgbevf. MSI-X interrupt support is required 2743 will be called ixgbevf. MSI-X interrupt support is required
2744 for this driver to work correctly. 2744 for this driver to work correctly.
2745 2745
2746 config IXGB 2746 config IXGB
2747 tristate "Intel(R) PRO/10GbE support" 2747 tristate "Intel(R) PRO/10GbE support"
2748 depends on PCI 2748 depends on PCI
2749 ---help--- 2749 ---help---
2750 This driver supports Intel(R) PRO/10GbE family of adapters for 2750 This driver supports Intel(R) PRO/10GbE family of adapters for
2751 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver 2751 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
2752 instead. For more information on how to identify your adapter, go 2752 instead. For more information on how to identify your adapter, go
2753 to the Adapter & Driver ID Guide at: 2753 to the Adapter & Driver ID Guide at:
2754 2754
2755 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2755 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
2756 2756
2757 For general information and support, go to the Intel support 2757 For general information and support, go to the Intel support
2758 website at: 2758 website at:
2759 2759
2760 <http://support.intel.com> 2760 <http://support.intel.com>
2761 2761
2762 More specific information on configuring the driver is in 2762 More specific information on configuring the driver is in
2763 <file:Documentation/networking/ixgb.txt>. 2763 <file:Documentation/networking/ixgb.txt>.
2764 2764
2765 To compile this driver as a module, choose M here. The module 2765 To compile this driver as a module, choose M here. The module
2766 will be called ixgb. 2766 will be called ixgb.
2767 2767
2768 config S2IO 2768 config S2IO
2769 tristate "Exar Xframe 10Gb Ethernet Adapter" 2769 tristate "Exar Xframe 10Gb Ethernet Adapter"
2770 depends on PCI 2770 depends on PCI
2771 ---help--- 2771 ---help---
2772 This driver supports Exar Corp's Xframe Series 10Gb Ethernet Adapters. 2772 This driver supports Exar Corp's Xframe Series 10Gb Ethernet Adapters.
2773 2773
2774 More specific information on configuring the driver is in 2774 More specific information on configuring the driver is in
2775 <file:Documentation/networking/s2io.txt>. 2775 <file:Documentation/networking/s2io.txt>.
2776 2776
2777 To compile this driver as a module, choose M here. The module 2777 To compile this driver as a module, choose M here. The module
2778 will be called s2io. 2778 will be called s2io.
2779 2779
2780 config VXGE 2780 config VXGE
2781 tristate "Exar X3100 Series 10GbE PCIe Server Adapter" 2781 tristate "Exar X3100 Series 10GbE PCIe Server Adapter"
2782 depends on PCI && INET 2782 depends on PCI && INET
2783 ---help--- 2783 ---help---
2784 This driver supports Exar Corp's X3100 Series 10 GbE PCIe 2784 This driver supports Exar Corp's X3100 Series 10 GbE PCIe
2785 I/O Virtualized Server Adapter. 2785 I/O Virtualized Server Adapter.
2786 2786
2787 More specific information on configuring the driver is in 2787 More specific information on configuring the driver is in
2788 <file:Documentation/networking/vxge.txt>. 2788 <file:Documentation/networking/vxge.txt>.
2789 2789
2790 To compile this driver as a module, choose M here. The module 2790 To compile this driver as a module, choose M here. The module
2791 will be called vxge. 2791 will be called vxge.
2792 2792
2793 config VXGE_DEBUG_TRACE_ALL 2793 config VXGE_DEBUG_TRACE_ALL
2794 bool "Enabling All Debug trace statments in driver" 2794 bool "Enabling All Debug trace statments in driver"
2795 default n 2795 default n
2796 depends on VXGE 2796 depends on VXGE
2797 ---help--- 2797 ---help---
2798 Say Y here if you want to enabling all the debug trace statements in 2798 Say Y here if you want to enabling all the debug trace statements in
2799 the vxge driver. By default only few debug trace statements are 2799 the vxge driver. By default only few debug trace statements are
2800 enabled. 2800 enabled.
2801 2801
2802 config MYRI10GE 2802 config MYRI10GE
2803 tristate "Myricom Myri-10G Ethernet support" 2803 tristate "Myricom Myri-10G Ethernet support"
2804 depends on PCI && INET 2804 depends on PCI && INET
2805 select FW_LOADER 2805 select FW_LOADER
2806 select CRC32 2806 select CRC32
2807 select INET_LRO 2807 select INET_LRO
2808 ---help--- 2808 ---help---
2809 This driver supports Myricom Myri-10G Dual Protocol interface in 2809 This driver supports Myricom Myri-10G Dual Protocol interface in
2810 Ethernet mode. If the eeprom on your board is not recent enough, 2810 Ethernet mode. If the eeprom on your board is not recent enough,
2811 you will need a newer firmware image. 2811 you will need a newer firmware image.
2812 You may get this image or more information, at: 2812 You may get this image or more information, at:
2813 2813
2814 <http://www.myri.com/scs/download-Myri10GE.html> 2814 <http://www.myri.com/scs/download-Myri10GE.html>
2815 2815
2816 To compile this driver as a module, choose M here. The module 2816 To compile this driver as a module, choose M here. The module
2817 will be called myri10ge. 2817 will be called myri10ge.
2818 2818
2819 config MYRI10GE_DCA 2819 config MYRI10GE_DCA
2820 bool "Direct Cache Access (DCA) Support" 2820 bool "Direct Cache Access (DCA) Support"
2821 default y 2821 default y
2822 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m) 2822 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
2823 ---help--- 2823 ---help---
2824 Say Y here if you want to use Direct Cache Access (DCA) in the 2824 Say Y here if you want to use Direct Cache Access (DCA) in the
2825 driver. DCA is a method for warming the CPU cache before data 2825 driver. DCA is a method for warming the CPU cache before data
2826 is used, with the intent of lessening the impact of cache misses. 2826 is used, with the intent of lessening the impact of cache misses.
2827 2827
2828 config NETXEN_NIC 2828 config NETXEN_NIC
2829 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC" 2829 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
2830 depends on PCI 2830 depends on PCI
2831 select FW_LOADER 2831 select FW_LOADER
2832 help 2832 help
2833 This enables the support for NetXen's Gigabit Ethernet card. 2833 This enables the support for NetXen's Gigabit Ethernet card.
2834 2834
2835 config NIU 2835 config NIU
2836 tristate "Sun Neptune 10Gbit Ethernet support" 2836 tristate "Sun Neptune 10Gbit Ethernet support"
2837 depends on PCI 2837 depends on PCI
2838 select CRC32 2838 select CRC32
2839 help 2839 help
2840 This enables support for cards based upon Sun's 2840 This enables support for cards based upon Sun's
2841 Neptune chipset. 2841 Neptune chipset.
2842 2842
2843 config PASEMI_MAC 2843 config PASEMI_MAC
2844 tristate "PA Semi 1/10Gbit MAC" 2844 tristate "PA Semi 1/10Gbit MAC"
2845 depends on PPC_PASEMI && PCI && INET 2845 depends on PPC_PASEMI && PCI && INET
2846 select PHYLIB 2846 select PHYLIB
2847 select INET_LRO 2847 select INET_LRO
2848 help 2848 help
2849 This driver supports the on-chip 1/10Gbit Ethernet controller on 2849 This driver supports the on-chip 1/10Gbit Ethernet controller on
2850 PA Semi's PWRficient line of chips. 2850 PA Semi's PWRficient line of chips.
2851 2851
2852 config MLX4_EN 2852 config MLX4_EN
2853 tristate "Mellanox Technologies 10Gbit Ethernet support" 2853 tristate "Mellanox Technologies 10Gbit Ethernet support"
2854 depends on PCI && INET 2854 depends on PCI && INET
2855 select MLX4_CORE 2855 select MLX4_CORE
2856 select INET_LRO 2856 select INET_LRO
2857 help 2857 help
2858 This driver supports Mellanox Technologies ConnectX Ethernet 2858 This driver supports Mellanox Technologies ConnectX Ethernet
2859 devices. 2859 devices.
2860 2860
2861 config MLX4_CORE 2861 config MLX4_CORE
2862 tristate 2862 tristate
2863 depends on PCI 2863 depends on PCI
2864 default n 2864 default n
2865 2865
2866 config MLX4_DEBUG 2866 config MLX4_DEBUG
2867 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED) 2867 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
2868 depends on MLX4_CORE 2868 depends on MLX4_CORE
2869 default y 2869 default y
2870 ---help--- 2870 ---help---
2871 This option causes debugging code to be compiled into the 2871 This option causes debugging code to be compiled into the
2872 mlx4_core driver. The output can be turned on via the 2872 mlx4_core driver. The output can be turned on via the
2873 debug_level module parameter (which can also be set after 2873 debug_level module parameter (which can also be set after
2874 the driver is loaded through sysfs). 2874 the driver is loaded through sysfs).
2875 2875
2876 config TEHUTI 2876 config TEHUTI
2877 tristate "Tehuti Networks 10G Ethernet" 2877 tristate "Tehuti Networks 10G Ethernet"
2878 depends on PCI 2878 depends on PCI
2879 help 2879 help
2880 Tehuti Networks 10G Ethernet NIC 2880 Tehuti Networks 10G Ethernet NIC
2881 2881
2882 config BNX2X 2882 config BNX2X
2883 tristate "Broadcom NetXtremeII 10Gb support" 2883 tristate "Broadcom NetXtremeII 10Gb support"
2884 depends on PCI 2884 depends on PCI
2885 select FW_LOADER 2885 select FW_LOADER
2886 select ZLIB_INFLATE 2886 select ZLIB_INFLATE
2887 select LIBCRC32C 2887 select LIBCRC32C
2888 select MDIO 2888 select MDIO
2889 help 2889 help
2890 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards. 2890 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
2891 To compile this driver as a module, choose M here: the module 2891 To compile this driver as a module, choose M here: the module
2892 will be called bnx2x. This is recommended. 2892 will be called bnx2x. This is recommended.
2893 2893
2894 config QLCNIC 2894 config QLCNIC
2895 tristate "QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support" 2895 tristate "QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support"
2896 depends on PCI 2896 depends on PCI
2897 select FW_LOADER 2897 select FW_LOADER
2898 help 2898 help
2899 This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet 2899 This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet
2900 devices. 2900 devices.
2901 2901
2902 config QLGE 2902 config QLGE
2903 tristate "QLogic QLGE 10Gb Ethernet Driver Support" 2903 tristate "QLogic QLGE 10Gb Ethernet Driver Support"
2904 depends on PCI 2904 depends on PCI
2905 help 2905 help
2906 This driver supports QLogic ISP8XXX 10Gb Ethernet cards. 2906 This driver supports QLogic ISP8XXX 10Gb Ethernet cards.
2907 2907
2908 To compile this driver as a module, choose M here: the module 2908 To compile this driver as a module, choose M here: the module
2909 will be called qlge. 2909 will be called qlge.
2910 2910
2911 config BNA 2911 config BNA
2912 tristate "Brocade 1010/1020 10Gb Ethernet Driver support" 2912 tristate "Brocade 1010/1020 10Gb Ethernet Driver support"
2913 depends on PCI 2913 depends on PCI
2914 ---help--- 2914 ---help---
2915 This driver supports Brocade 1010/1020 10Gb CEE capable Ethernet 2915 This driver supports Brocade 1010/1020 10Gb CEE capable Ethernet
2916 cards. 2916 cards.
2917 To compile this driver as a module, choose M here: the module 2917 To compile this driver as a module, choose M here: the module
2918 will be called bna. 2918 will be called bna.
2919 2919
2920 For general information and support, go to the Brocade support 2920 For general information and support, go to the Brocade support
2921 website at: 2921 website at:
2922 2922
2923 <http://support.brocade.com> 2923 <http://support.brocade.com>
2924 2924
2925 source "drivers/net/sfc/Kconfig" 2925 source "drivers/net/sfc/Kconfig"
2926 2926
2927 source "drivers/net/benet/Kconfig" 2927 source "drivers/net/benet/Kconfig"
2928 2928
2929 endif # NETDEV_10000 2929 endif # NETDEV_10000
2930 2930
2931 source "drivers/net/tokenring/Kconfig" 2931 source "drivers/net/tokenring/Kconfig"
2932 2932
2933 source "drivers/net/wireless/Kconfig" 2933 source "drivers/net/wireless/Kconfig"
2934 2934
2935 source "drivers/net/wimax/Kconfig" 2935 source "drivers/net/wimax/Kconfig"
2936 2936
2937 source "drivers/net/usb/Kconfig" 2937 source "drivers/net/usb/Kconfig"
2938 2938
2939 source "drivers/net/pcmcia/Kconfig" 2939 source "drivers/net/pcmcia/Kconfig"
2940 2940
2941 source "drivers/net/wan/Kconfig" 2941 source "drivers/net/wan/Kconfig"
2942 2942
2943 source "drivers/atm/Kconfig" 2943 source "drivers/atm/Kconfig"
2944 2944
2945 source "drivers/ieee802154/Kconfig" 2945 source "drivers/ieee802154/Kconfig"
2946 2946
2947 source "drivers/s390/net/Kconfig" 2947 source "drivers/s390/net/Kconfig"
2948 2948
2949 source "drivers/net/caif/Kconfig" 2949 source "drivers/net/caif/Kconfig"
2950 2950
2951 config TILE_NET 2951 config TILE_NET
2952 tristate "Tilera GBE/XGBE network driver support" 2952 tristate "Tilera GBE/XGBE network driver support"
2953 depends on TILE 2953 depends on TILE
2954 default y 2954 default y
2955 select CRC32 2955 select CRC32
2956 help 2956 help
2957 This is a standard Linux network device driver for the 2957 This is a standard Linux network device driver for the
2958 on-chip Tilera Gigabit Ethernet and XAUI interfaces. 2958 on-chip Tilera Gigabit Ethernet and XAUI interfaces.
2959 2959
2960 To compile this driver as a module, choose M here: the module 2960 To compile this driver as a module, choose M here: the module
2961 will be called tile_net. 2961 will be called tile_net.
2962 2962
2963 config XEN_NETDEV_FRONTEND 2963 config XEN_NETDEV_FRONTEND
2964 tristate "Xen network device frontend driver" 2964 tristate "Xen network device frontend driver"
2965 depends on XEN 2965 depends on XEN
2966 select XEN_XENBUS_FRONTEND 2966 select XEN_XENBUS_FRONTEND
2967 default y 2967 default y
2968 help 2968 help
2969 The network device frontend driver allows the kernel to 2969 The network device frontend driver allows the kernel to
2970 access network devices exported exported by a virtual 2970 access network devices exported exported by a virtual
2971 machine containing a physical network device driver. The 2971 machine containing a physical network device driver. The
2972 frontend driver is intended for unprivileged guest domains; 2972 frontend driver is intended for unprivileged guest domains;
2973 if you are compiling a kernel for a Xen guest, you almost 2973 if you are compiling a kernel for a Xen guest, you almost
2974 certainly want to enable this. 2974 certainly want to enable this.
2975 2975
2976 config ISERIES_VETH 2976 config ISERIES_VETH
2977 tristate "iSeries Virtual Ethernet driver support" 2977 tristate "iSeries Virtual Ethernet driver support"
2978 depends on PPC_ISERIES 2978 depends on PPC_ISERIES
2979 2979
2980 config RIONET 2980 config RIONET
2981 tristate "RapidIO Ethernet over messaging driver support" 2981 tristate "RapidIO Ethernet over messaging driver support"
2982 depends on RAPIDIO 2982 depends on RAPIDIO
2983 2983
2984 config RIONET_TX_SIZE 2984 config RIONET_TX_SIZE
2985 int "Number of outbound queue entries" 2985 int "Number of outbound queue entries"
2986 depends on RIONET 2986 depends on RIONET
2987 default "128" 2987 default "128"
2988 2988
2989 config RIONET_RX_SIZE 2989 config RIONET_RX_SIZE
2990 int "Number of inbound queue entries" 2990 int "Number of inbound queue entries"
2991 depends on RIONET 2991 depends on RIONET
2992 default "128" 2992 default "128"
2993 2993
2994 config FDDI 2994 config FDDI
2995 tristate "FDDI driver support" 2995 tristate "FDDI driver support"
2996 depends on (PCI || EISA || TC) 2996 depends on (PCI || EISA || TC)
2997 help 2997 help
2998 Fiber Distributed Data Interface is a high speed local area network 2998 Fiber Distributed Data Interface is a high speed local area network
2999 design; essentially a replacement for high speed Ethernet. FDDI can 2999 design; essentially a replacement for high speed Ethernet. FDDI can
3000 run over copper or fiber. If you are connected to such a network and 3000 run over copper or fiber. If you are connected to such a network and
3001 want a driver for the FDDI card in your computer, say Y here (and 3001 want a driver for the FDDI card in your computer, say Y here (and
3002 then also Y to the driver for your FDDI card, below). Most people 3002 then also Y to the driver for your FDDI card, below). Most people
3003 will say N. 3003 will say N.
3004 3004
3005 config DEFXX 3005 config DEFXX
3006 tristate "Digital DEFTA/DEFEA/DEFPA adapter support" 3006 tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
3007 depends on FDDI && (PCI || EISA || TC) 3007 depends on FDDI && (PCI || EISA || TC)
3008 ---help--- 3008 ---help---
3009 This is support for the DIGITAL series of TURBOchannel (DEFTA), 3009 This is support for the DIGITAL series of TURBOchannel (DEFTA),
3010 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you 3010 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
3011 to a local FDDI network. 3011 to a local FDDI network.
3012 3012
3013 To compile this driver as a module, choose M here: the module 3013 To compile this driver as a module, choose M here: the module
3014 will be called defxx. If unsure, say N. 3014 will be called defxx. If unsure, say N.
3015 3015
3016 config DEFXX_MMIO 3016 config DEFXX_MMIO
3017 bool 3017 bool
3018 prompt "Use MMIO instead of PIO" if PCI || EISA 3018 prompt "Use MMIO instead of PIO" if PCI || EISA
3019 depends on DEFXX 3019 depends on DEFXX
3020 default n if PCI || EISA 3020 default n if PCI || EISA
3021 default y 3021 default y
3022 ---help--- 3022 ---help---
3023 This instructs the driver to use EISA or PCI memory-mapped I/O 3023 This instructs the driver to use EISA or PCI memory-mapped I/O
3024 (MMIO) as appropriate instead of programmed I/O ports (PIO). 3024 (MMIO) as appropriate instead of programmed I/O ports (PIO).
3025 Enabling this gives an improvement in processing time in parts 3025 Enabling this gives an improvement in processing time in parts
3026 of the driver, but it may cause problems with EISA (DEFEA) 3026 of the driver, but it may cause problems with EISA (DEFEA)
3027 adapters. TURBOchannel does not have the concept of I/O ports, 3027 adapters. TURBOchannel does not have the concept of I/O ports,
3028 so MMIO is always used for these (DEFTA) adapters. 3028 so MMIO is always used for these (DEFTA) adapters.
3029 3029
3030 If unsure, say N. 3030 If unsure, say N.
3031 3031
3032 config SKFP 3032 config SKFP
3033 tristate "SysKonnect FDDI PCI support" 3033 tristate "SysKonnect FDDI PCI support"
3034 depends on FDDI && PCI 3034 depends on FDDI && PCI
3035 select BITREVERSE 3035 select BITREVERSE
3036 ---help--- 3036 ---help---
3037 Say Y here if you have a SysKonnect FDDI PCI adapter. 3037 Say Y here if you have a SysKonnect FDDI PCI adapter.
3038 The following adapters are supported by this driver: 3038 The following adapters are supported by this driver:
3039 - SK-5521 (SK-NET FDDI-UP) 3039 - SK-5521 (SK-NET FDDI-UP)
3040 - SK-5522 (SK-NET FDDI-UP DAS) 3040 - SK-5522 (SK-NET FDDI-UP DAS)
3041 - SK-5541 (SK-NET FDDI-FP) 3041 - SK-5541 (SK-NET FDDI-FP)
3042 - SK-5543 (SK-NET FDDI-LP) 3042 - SK-5543 (SK-NET FDDI-LP)
3043 - SK-5544 (SK-NET FDDI-LP DAS) 3043 - SK-5544 (SK-NET FDDI-LP DAS)
3044 - SK-5821 (SK-NET FDDI-UP64) 3044 - SK-5821 (SK-NET FDDI-UP64)
3045 - SK-5822 (SK-NET FDDI-UP64 DAS) 3045 - SK-5822 (SK-NET FDDI-UP64 DAS)
3046 - SK-5841 (SK-NET FDDI-FP64) 3046 - SK-5841 (SK-NET FDDI-FP64)
3047 - SK-5843 (SK-NET FDDI-LP64) 3047 - SK-5843 (SK-NET FDDI-LP64)
3048 - SK-5844 (SK-NET FDDI-LP64 DAS) 3048 - SK-5844 (SK-NET FDDI-LP64 DAS)
3049 - Netelligent 100 FDDI DAS Fibre SC 3049 - Netelligent 100 FDDI DAS Fibre SC
3050 - Netelligent 100 FDDI SAS Fibre SC 3050 - Netelligent 100 FDDI SAS Fibre SC
3051 - Netelligent 100 FDDI DAS UTP 3051 - Netelligent 100 FDDI DAS UTP
3052 - Netelligent 100 FDDI SAS UTP 3052 - Netelligent 100 FDDI SAS UTP
3053 - Netelligent 100 FDDI SAS Fibre MIC 3053 - Netelligent 100 FDDI SAS Fibre MIC
3054 3054
3055 Read <file:Documentation/networking/skfp.txt> for information about 3055 Read <file:Documentation/networking/skfp.txt> for information about
3056 the driver. 3056 the driver.
3057 3057
3058 Questions concerning this driver can be addressed to: 3058 Questions concerning this driver can be addressed to:
3059 <linux@syskonnect.de> 3059 <linux@syskonnect.de>
3060 3060
3061 To compile this driver as a module, choose M here: the module 3061 To compile this driver as a module, choose M here: the module
3062 will be called skfp. This is recommended. 3062 will be called skfp. This is recommended.
3063 3063
3064 config HIPPI 3064 config HIPPI
3065 bool "HIPPI driver support (EXPERIMENTAL)" 3065 bool "HIPPI driver support (EXPERIMENTAL)"
3066 depends on EXPERIMENTAL && INET && PCI 3066 depends on EXPERIMENTAL && INET && PCI
3067 help 3067 help
3068 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and 3068 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
3069 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI 3069 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
3070 can run over copper (25m) or fiber (300m on multi-mode or 10km on 3070 can run over copper (25m) or fiber (300m on multi-mode or 10km on
3071 single-mode). HIPPI networks are commonly used for clusters and to 3071 single-mode). HIPPI networks are commonly used for clusters and to
3072 connect to super computers. If you are connected to a HIPPI network 3072 connect to super computers. If you are connected to a HIPPI network
3073 and have a HIPPI network card in your computer that you want to use 3073 and have a HIPPI network card in your computer that you want to use
3074 under Linux, say Y here (you must also remember to enable the driver 3074 under Linux, say Y here (you must also remember to enable the driver
3075 for your HIPPI card below). Most people will say N here. 3075 for your HIPPI card below). Most people will say N here.
3076 3076
3077 config ROADRUNNER 3077 config ROADRUNNER
3078 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)" 3078 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
3079 depends on HIPPI && PCI 3079 depends on HIPPI && PCI
3080 help 3080 help
3081 Say Y here if this is your PCI HIPPI network card. 3081 Say Y here if this is your PCI HIPPI network card.
3082 3082
3083 To compile this driver as a module, choose M here: the module 3083 To compile this driver as a module, choose M here: the module
3084 will be called rrunner. If unsure, say N. 3084 will be called rrunner. If unsure, say N.
3085 3085
3086 config ROADRUNNER_LARGE_RINGS 3086 config ROADRUNNER_LARGE_RINGS
3087 bool "Use large TX/RX rings (EXPERIMENTAL)" 3087 bool "Use large TX/RX rings (EXPERIMENTAL)"
3088 depends on ROADRUNNER 3088 depends on ROADRUNNER
3089 help 3089 help
3090 If you say Y here, the RoadRunner driver will preallocate up to 2 MB 3090 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
3091 of additional memory to allow for fastest operation, both for 3091 of additional memory to allow for fastest operation, both for
3092 transmitting and receiving. This memory cannot be used by any other 3092 transmitting and receiving. This memory cannot be used by any other
3093 kernel code or by user space programs. Say Y here only if you have 3093 kernel code or by user space programs. Say Y here only if you have
3094 the memory. 3094 the memory.
3095 3095
3096 config PLIP 3096 config PLIP
3097 tristate "PLIP (parallel port) support" 3097 tristate "PLIP (parallel port) support"
3098 depends on PARPORT 3098 depends on PARPORT
3099 ---help--- 3099 ---help---
3100 PLIP (Parallel Line Internet Protocol) is used to create a 3100 PLIP (Parallel Line Internet Protocol) is used to create a
3101 reasonably fast mini network consisting of two (or, rarely, more) 3101 reasonably fast mini network consisting of two (or, rarely, more)
3102 local machines. A PLIP link from a Linux box is a popular means to 3102 local machines. A PLIP link from a Linux box is a popular means to
3103 install a Linux distribution on a machine which doesn't have a 3103 install a Linux distribution on a machine which doesn't have a
3104 CD-ROM drive (a minimal system has to be transferred with floppies 3104 CD-ROM drive (a minimal system has to be transferred with floppies
3105 first). The kernels on both machines need to have this PLIP option 3105 first). The kernels on both machines need to have this PLIP option
3106 enabled for this to work. 3106 enabled for this to work.
3107 3107
3108 The PLIP driver has two modes, mode 0 and mode 1. The parallel 3108 The PLIP driver has two modes, mode 0 and mode 1. The parallel
3109 ports (the connectors at the computers with 25 holes) are connected 3109 ports (the connectors at the computers with 25 holes) are connected
3110 with "null printer" or "Turbo Laplink" cables which can transmit 4 3110 with "null printer" or "Turbo Laplink" cables which can transmit 4
3111 bits at a time (mode 0) or with special PLIP cables, to be used on 3111 bits at a time (mode 0) or with special PLIP cables, to be used on
3112 bidirectional parallel ports only, which can transmit 8 bits at a 3112 bidirectional parallel ports only, which can transmit 8 bits at a
3113 time (mode 1); you can find the wiring of these cables in 3113 time (mode 1); you can find the wiring of these cables in
3114 <file:Documentation/networking/PLIP.txt>. The cables can be up to 3114 <file:Documentation/networking/PLIP.txt>. The cables can be up to
3115 15m long. Mode 0 works also if one of the machines runs DOS/Windows 3115 15m long. Mode 0 works also if one of the machines runs DOS/Windows
3116 and has some PLIP software installed, e.g. the Crynwr PLIP packet 3116 and has some PLIP software installed, e.g. the Crynwr PLIP packet
3117 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>) 3117 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
3118 and winsock or NCSA's telnet. 3118 and winsock or NCSA's telnet.
3119 3119
3120 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well 3120 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
3121 as the NET-3-HOWTO, both available from 3121 as the NET-3-HOWTO, both available from
3122 <http://www.tldp.org/docs.html#howto>. Note that the PLIP 3122 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
3123 protocol has been changed and this PLIP driver won't work together 3123 protocol has been changed and this PLIP driver won't work together
3124 with the PLIP support in Linux versions 1.0.x. This option enlarges 3124 with the PLIP support in Linux versions 1.0.x. This option enlarges
3125 your kernel by about 8 KB. 3125 your kernel by about 8 KB.
3126 3126
3127 To compile this driver as a module, choose M here. The module 3127 To compile this driver as a module, choose M here. The module
3128 will be called plip. If unsure, say Y or M, in case you buy 3128 will be called plip. If unsure, say Y or M, in case you buy
3129 a laptop later. 3129 a laptop later.
3130 3130
3131 config PPP 3131 config PPP
3132 tristate "PPP (point-to-point protocol) support" 3132 tristate "PPP (point-to-point protocol) support"
3133 select SLHC 3133 select SLHC
3134 ---help--- 3134 ---help---
3135 PPP (Point to Point Protocol) is a newer and better SLIP. It serves 3135 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
3136 the same purpose: sending Internet traffic over telephone (and other 3136 the same purpose: sending Internet traffic over telephone (and other
3137 serial) lines. Ask your access provider if they support it, because 3137 serial) lines. Ask your access provider if they support it, because
3138 otherwise you can't use it; most Internet access providers these 3138 otherwise you can't use it; most Internet access providers these
3139 days support PPP rather than SLIP. 3139 days support PPP rather than SLIP.
3140 3140
3141 To use PPP, you need an additional program called pppd as described 3141 To use PPP, you need an additional program called pppd as described
3142 in the PPP-HOWTO, available at 3142 in the PPP-HOWTO, available at
3143 <http://www.tldp.org/docs.html#howto>. Make sure that you have 3143 <http://www.tldp.org/docs.html#howto>. Make sure that you have
3144 the version of pppd recommended in <file:Documentation/Changes>. 3144 the version of pppd recommended in <file:Documentation/Changes>.
3145 The PPP option enlarges your kernel by about 16 KB. 3145 The PPP option enlarges your kernel by about 16 KB.
3146 3146
3147 There are actually two versions of PPP: the traditional PPP for 3147 There are actually two versions of PPP: the traditional PPP for
3148 asynchronous lines, such as regular analog phone lines, and 3148 asynchronous lines, such as regular analog phone lines, and
3149 synchronous PPP which can be used over digital ISDN lines for 3149 synchronous PPP which can be used over digital ISDN lines for
3150 example. If you want to use PPP over phone lines or other 3150 example. If you want to use PPP over phone lines or other
3151 asynchronous serial lines, you need to say Y (or M) here and also to 3151 asynchronous serial lines, you need to say Y (or M) here and also to
3152 the next option, "PPP support for async serial ports". For PPP over 3152 the next option, "PPP support for async serial ports". For PPP over
3153 synchronous lines, you should say Y (or M) here and to "Support 3153 synchronous lines, you should say Y (or M) here and to "Support
3154 synchronous PPP", below. 3154 synchronous PPP", below.
3155 3155
3156 If you said Y to "Version information on all symbols" above, then 3156 If you said Y to "Version information on all symbols" above, then
3157 you cannot compile the PPP driver into the kernel; you can then only 3157 you cannot compile the PPP driver into the kernel; you can then only
3158 compile it as a module. To compile this driver as a module, choose M 3158 compile it as a module. To compile this driver as a module, choose M
3159 here. The module will be called ppp_generic. 3159 here. The module will be called ppp_generic.
3160 3160
3161 config PPP_MULTILINK 3161 config PPP_MULTILINK
3162 bool "PPP multilink support (EXPERIMENTAL)" 3162 bool "PPP multilink support (EXPERIMENTAL)"
3163 depends on PPP && EXPERIMENTAL 3163 depends on PPP && EXPERIMENTAL
3164 help 3164 help
3165 PPP multilink is a protocol (defined in RFC 1990) which allows you 3165 PPP multilink is a protocol (defined in RFC 1990) which allows you
3166 to combine several (logical or physical) lines into one logical PPP 3166 to combine several (logical or physical) lines into one logical PPP
3167 connection, so that you can utilize your full bandwidth. 3167 connection, so that you can utilize your full bandwidth.
3168 3168
3169 This has to be supported at the other end as well and you need a 3169 This has to be supported at the other end as well and you need a
3170 version of the pppd daemon which understands the multilink protocol. 3170 version of the pppd daemon which understands the multilink protocol.
3171 3171
3172 If unsure, say N. 3172 If unsure, say N.
3173 3173
3174 config PPP_FILTER 3174 config PPP_FILTER
3175 bool "PPP filtering" 3175 bool "PPP filtering"
3176 depends on PPP 3176 depends on PPP
3177 help 3177 help
3178 Say Y here if you want to be able to filter the packets passing over 3178 Say Y here if you want to be able to filter the packets passing over
3179 PPP interfaces. This allows you to control which packets count as 3179 PPP interfaces. This allows you to control which packets count as
3180 activity (i.e. which packets will reset the idle timer or bring up 3180 activity (i.e. which packets will reset the idle timer or bring up
3181 a demand-dialed link) and which packets are to be dropped entirely. 3181 a demand-dialed link) and which packets are to be dropped entirely.
3182 You need to say Y here if you wish to use the pass-filter and 3182 You need to say Y here if you wish to use the pass-filter and
3183 active-filter options to pppd. 3183 active-filter options to pppd.
3184 3184
3185 If unsure, say N. 3185 If unsure, say N.
3186 3186
3187 config PPP_ASYNC 3187 config PPP_ASYNC
3188 tristate "PPP support for async serial ports" 3188 tristate "PPP support for async serial ports"
3189 depends on PPP 3189 depends on PPP
3190 select CRC_CCITT 3190 select CRC_CCITT
3191 ---help--- 3191 ---help---
3192 Say Y (or M) here if you want to be able to use PPP over standard 3192 Say Y (or M) here if you want to be able to use PPP over standard
3193 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use 3193 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
3194 a modem (not a synchronous or ISDN modem) to contact your ISP, you 3194 a modem (not a synchronous or ISDN modem) to contact your ISP, you
3195 need this option. 3195 need this option.
3196 3196
3197 To compile this driver as a module, choose M here. 3197 To compile this driver as a module, choose M here.
3198 3198
3199 If unsure, say Y. 3199 If unsure, say Y.
3200 3200
3201 config PPP_SYNC_TTY 3201 config PPP_SYNC_TTY
3202 tristate "PPP support for sync tty ports" 3202 tristate "PPP support for sync tty ports"
3203 depends on PPP 3203 depends on PPP
3204 help 3204 help
3205 Say Y (or M) here if you want to be able to use PPP over synchronous 3205 Say Y (or M) here if you want to be able to use PPP over synchronous
3206 (HDLC) tty devices, such as the SyncLink adapter. These devices 3206 (HDLC) tty devices, such as the SyncLink adapter. These devices
3207 are often used for high-speed leased lines like T1/E1. 3207 are often used for high-speed leased lines like T1/E1.
3208 3208
3209 To compile this driver as a module, choose M here. 3209 To compile this driver as a module, choose M here.
3210 3210
3211 config PPP_DEFLATE 3211 config PPP_DEFLATE
3212 tristate "PPP Deflate compression" 3212 tristate "PPP Deflate compression"
3213 depends on PPP 3213 depends on PPP
3214 select ZLIB_INFLATE 3214 select ZLIB_INFLATE
3215 select ZLIB_DEFLATE 3215 select ZLIB_DEFLATE
3216 ---help--- 3216 ---help---
3217 Support for the Deflate compression method for PPP, which uses the 3217 Support for the Deflate compression method for PPP, which uses the
3218 Deflate algorithm (the same algorithm that gzip uses) to compress 3218 Deflate algorithm (the same algorithm that gzip uses) to compress
3219 each PPP packet before it is sent over the wire. The machine at the 3219 each PPP packet before it is sent over the wire. The machine at the
3220 other end of the PPP link (usually your ISP) has to support the 3220 other end of the PPP link (usually your ISP) has to support the
3221 Deflate compression method as well for this to be useful. Even if 3221 Deflate compression method as well for this to be useful. Even if
3222 they don't support it, it is safe to say Y here. 3222 they don't support it, it is safe to say Y here.
3223 3223
3224 To compile this driver as a module, choose M here. 3224 To compile this driver as a module, choose M here.
3225 3225
3226 config PPP_BSDCOMP 3226 config PPP_BSDCOMP
3227 tristate "PPP BSD-Compress compression" 3227 tristate "PPP BSD-Compress compression"
3228 depends on PPP 3228 depends on PPP
3229 ---help--- 3229 ---help---
3230 Support for the BSD-Compress compression method for PPP, which uses 3230 Support for the BSD-Compress compression method for PPP, which uses
3231 the LZW compression method to compress each PPP packet before it is 3231 the LZW compression method to compress each PPP packet before it is
3232 sent over the wire. The machine at the other end of the PPP link 3232 sent over the wire. The machine at the other end of the PPP link
3233 (usually your ISP) has to support the BSD-Compress compression 3233 (usually your ISP) has to support the BSD-Compress compression
3234 method as well for this to be useful. Even if they don't support it, 3234 method as well for this to be useful. Even if they don't support it,
3235 it is safe to say Y here. 3235 it is safe to say Y here.
3236 3236
3237 The PPP Deflate compression method ("PPP Deflate compression", 3237 The PPP Deflate compression method ("PPP Deflate compression",
3238 above) is preferable to BSD-Compress, because it compresses better 3238 above) is preferable to BSD-Compress, because it compresses better
3239 and is patent-free. 3239 and is patent-free.
3240 3240
3241 Note that the BSD compression code will always be compiled as a 3241 Note that the BSD compression code will always be compiled as a
3242 module; it is called bsd_comp and will show up in the directory 3242 module; it is called bsd_comp and will show up in the directory
3243 modules once you have said "make modules". If unsure, say N. 3243 modules once you have said "make modules". If unsure, say N.
3244 3244
3245 config PPP_MPPE 3245 config PPP_MPPE
3246 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)" 3246 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
3247 depends on PPP && EXPERIMENTAL 3247 depends on PPP && EXPERIMENTAL
3248 select CRYPTO 3248 select CRYPTO
3249 select CRYPTO_SHA1 3249 select CRYPTO_SHA1
3250 select CRYPTO_ARC4 3250 select CRYPTO_ARC4
3251 select CRYPTO_ECB 3251 select CRYPTO_ECB
3252 ---help--- 3252 ---help---
3253 Support for the MPPE Encryption protocol, as employed by the 3253 Support for the MPPE Encryption protocol, as employed by the
3254 Microsoft Point-to-Point Tunneling Protocol. 3254 Microsoft Point-to-Point Tunneling Protocol.
3255 3255
3256 See http://pptpclient.sourceforge.net/ for information on 3256 See http://pptpclient.sourceforge.net/ for information on
3257 configuring PPTP clients and servers to utilize this method. 3257 configuring PPTP clients and servers to utilize this method.
3258 3258
3259 config PPPOE 3259 config PPPOE
3260 tristate "PPP over Ethernet (EXPERIMENTAL)" 3260 tristate "PPP over Ethernet (EXPERIMENTAL)"
3261 depends on EXPERIMENTAL && PPP 3261 depends on EXPERIMENTAL && PPP
3262 help 3262 help
3263 Support for PPP over Ethernet. 3263 Support for PPP over Ethernet.
3264 3264
3265 This driver requires the latest version of pppd from the CVS 3265 This driver requires the latest version of pppd from the CVS
3266 repository at cvs.samba.org. Alternatively, see the 3266 repository at cvs.samba.org. Alternatively, see the
3267 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>) 3267 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
3268 which contains instruction on how to use this driver (under 3268 which contains instruction on how to use this driver (under
3269 the heading "Kernel mode PPPoE"). 3269 the heading "Kernel mode PPPoE").
3270 3270
3271 config PPTP 3271 config PPTP
3272 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)" 3272 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
3273 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX 3273 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
3274 help 3274 help
3275 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol) 3275 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
3276 3276
3277 This driver requires pppd plugin to work in client mode or 3277 This driver requires pppd plugin to work in client mode or
3278 modified pptpd (poptop) to work in server mode. 3278 modified pptpd (poptop) to work in server mode.
3279 See http://accel-pptp.sourceforge.net/ for information how to 3279 See http://accel-pptp.sourceforge.net/ for information how to
3280 utilize this module. 3280 utilize this module.
3281 3281
3282 config PPPOATM 3282 config PPPOATM
3283 tristate "PPP over ATM" 3283 tristate "PPP over ATM"
3284 depends on ATM && PPP 3284 depends on ATM && PPP
3285 help 3285 help
3286 Support PPP (Point to Point Protocol) encapsulated in ATM frames. 3286 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
3287 This implementation does not yet comply with section 8 of RFC2364, 3287 This implementation does not yet comply with section 8 of RFC2364,
3288 which can lead to bad results if the ATM peer loses state and 3288 which can lead to bad results if the ATM peer loses state and
3289 changes its encapsulation unilaterally. 3289 changes its encapsulation unilaterally.
3290 3290
3291 config PPPOL2TP 3291 config PPPOL2TP
3292 tristate "PPP over L2TP (EXPERIMENTAL)" 3292 tristate "PPP over L2TP (EXPERIMENTAL)"
3293 depends on EXPERIMENTAL && L2TP && PPP 3293 depends on EXPERIMENTAL && L2TP && PPP
3294 help 3294 help
3295 Support for PPP-over-L2TP socket family. L2TP is a protocol 3295 Support for PPP-over-L2TP socket family. L2TP is a protocol
3296 used by ISPs and enterprises to tunnel PPP traffic over UDP 3296 used by ISPs and enterprises to tunnel PPP traffic over UDP
3297 tunnels. L2TP is replacing PPTP for VPN uses. 3297 tunnels. L2TP is replacing PPTP for VPN uses.
3298 3298
3299 config SLIP 3299 config SLIP
3300 tristate "SLIP (serial line) support" 3300 tristate "SLIP (serial line) support"
3301 ---help--- 3301 ---help---
3302 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to 3302 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
3303 connect to your Internet service provider or to connect to some 3303 connect to your Internet service provider or to connect to some
3304 other local Unix box or if you want to configure your Linux box as a 3304 other local Unix box or if you want to configure your Linux box as a
3305 Slip/CSlip server for other people to dial in. SLIP (Serial Line 3305 Slip/CSlip server for other people to dial in. SLIP (Serial Line
3306 Internet Protocol) is a protocol used to send Internet traffic over 3306 Internet Protocol) is a protocol used to send Internet traffic over
3307 serial connections such as telephone lines or null modem cables; 3307 serial connections such as telephone lines or null modem cables;
3308 nowadays, the protocol PPP is more commonly used for this same 3308 nowadays, the protocol PPP is more commonly used for this same
3309 purpose. 3309 purpose.
3310 3310
3311 Normally, your access provider has to support SLIP in order for you 3311 Normally, your access provider has to support SLIP in order for you
3312 to be able to use it, but there is now a SLIP emulator called SLiRP 3312 to be able to use it, but there is now a SLIP emulator called SLiRP
3313 around (available from 3313 around (available from
3314 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which 3314 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3315 allows you to use SLIP over a regular dial up shell connection. If 3315 allows you to use SLIP over a regular dial up shell connection. If
3316 you plan to use SLiRP, make sure to say Y to CSLIP, below. The 3316 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
3317 NET-3-HOWTO, available from 3317 NET-3-HOWTO, available from
3318 <http://www.tldp.org/docs.html#howto>, explains how to 3318 <http://www.tldp.org/docs.html#howto>, explains how to
3319 configure SLIP. Note that you don't need this option if you just 3319 configure SLIP. Note that you don't need this option if you just
3320 want to run term (term is a program which gives you almost full 3320 want to run term (term is a program which gives you almost full
3321 Internet connectivity if you have a regular dial up shell account on 3321 Internet connectivity if you have a regular dial up shell account on
3322 some Internet connected Unix computer. Read 3322 some Internet connected Unix computer. Read
3323 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP 3323 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
3324 support will enlarge your kernel by about 4 KB. If unsure, say N. 3324 support will enlarge your kernel by about 4 KB. If unsure, say N.
3325 3325
3326 To compile this driver as a module, choose M here. The module 3326 To compile this driver as a module, choose M here. The module
3327 will be called slip. 3327 will be called slip.
3328 3328
3329 config SLIP_COMPRESSED 3329 config SLIP_COMPRESSED
3330 bool "CSLIP compressed headers" 3330 bool "CSLIP compressed headers"
3331 depends on SLIP 3331 depends on SLIP
3332 select SLHC 3332 select SLHC
3333 ---help--- 3333 ---help---
3334 This protocol is faster than SLIP because it uses compression on the 3334 This protocol is faster than SLIP because it uses compression on the
3335 TCP/IP headers (not on the data itself), but it has to be supported 3335 TCP/IP headers (not on the data itself), but it has to be supported
3336 on both ends. Ask your access provider if you are not sure and 3336 on both ends. Ask your access provider if you are not sure and
3337 answer Y, just in case. You will still be able to use plain SLIP. If 3337 answer Y, just in case. You will still be able to use plain SLIP. If
3338 you plan to use SLiRP, the SLIP emulator (available from 3338 you plan to use SLiRP, the SLIP emulator (available from
3339 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which 3339 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
3340 allows you to use SLIP over a regular dial up shell connection, you 3340 allows you to use SLIP over a regular dial up shell connection, you
3341 definitely want to say Y here. The NET-3-HOWTO, available from 3341 definitely want to say Y here. The NET-3-HOWTO, available from
3342 <http://www.tldp.org/docs.html#howto>, explains how to configure 3342 <http://www.tldp.org/docs.html#howto>, explains how to configure
3343 CSLIP. This won't enlarge your kernel. 3343 CSLIP. This won't enlarge your kernel.
3344 3344
3345 config SLHC 3345 config SLHC
3346 tristate 3346 tristate
3347 help 3347 help
3348 This option enables Van Jacobsen serial line header compression 3348 This option enables Van Jacobsen serial line header compression
3349 routines. 3349 routines.
3350 3350
3351 config SLIP_SMART 3351 config SLIP_SMART
3352 bool "Keepalive and linefill" 3352 bool "Keepalive and linefill"
3353 depends on SLIP 3353 depends on SLIP
3354 help 3354 help
3355 Adds additional capabilities to the SLIP driver to support the 3355 Adds additional capabilities to the SLIP driver to support the
3356 RELCOM line fill and keepalive monitoring. Ideal on poor quality 3356 RELCOM line fill and keepalive monitoring. Ideal on poor quality
3357 analogue lines. 3357 analogue lines.
3358 3358
3359 config SLIP_MODE_SLIP6 3359 config SLIP_MODE_SLIP6
3360 bool "Six bit SLIP encapsulation" 3360 bool "Six bit SLIP encapsulation"
3361 depends on SLIP 3361 depends on SLIP
3362 help 3362 help
3363 Just occasionally you may need to run IP over hostile serial 3363 Just occasionally you may need to run IP over hostile serial
3364 networks that don't pass all control characters or are only seven 3364 networks that don't pass all control characters or are only seven
3365 bit. Saying Y here adds an extra mode you can use with SLIP: 3365 bit. Saying Y here adds an extra mode you can use with SLIP:
3366 "slip6". In this mode, SLIP will only send normal ASCII symbols over 3366 "slip6". In this mode, SLIP will only send normal ASCII symbols over
3367 the serial device. Naturally, this has to be supported at the other 3367 the serial device. Naturally, this has to be supported at the other
3368 end of the link as well. It's good enough, for example, to run IP 3368 end of the link as well. It's good enough, for example, to run IP
3369 over the async ports of a Camtec JNT Pad. If unsure, say N. 3369 over the async ports of a Camtec JNT Pad. If unsure, say N.
3370 3370
3371 config NET_FC 3371 config NET_FC
3372 bool "Fibre Channel driver support" 3372 bool "Fibre Channel driver support"
3373 depends on SCSI && PCI 3373 depends on SCSI && PCI
3374 help 3374 help
3375 Fibre Channel is a high speed serial protocol mainly used to connect 3375 Fibre Channel is a high speed serial protocol mainly used to connect
3376 large storage devices to the computer; it is compatible with and 3376 large storage devices to the computer; it is compatible with and
3377 intended to replace SCSI. 3377 intended to replace SCSI.
3378 3378
3379 If you intend to use Fibre Channel, you need to have a Fibre channel 3379 If you intend to use Fibre Channel, you need to have a Fibre channel
3380 adaptor card in your computer; say Y here and to the driver for your 3380 adaptor card in your computer; say Y here and to the driver for your
3381 adaptor below. You also should have said Y to "SCSI support" and 3381 adaptor below. You also should have said Y to "SCSI support" and
3382 "SCSI generic support". 3382 "SCSI generic support".
3383 3383
3384 config NETCONSOLE 3384 config NETCONSOLE
3385 tristate "Network console logging support" 3385 tristate "Network console logging support"
3386 ---help--- 3386 ---help---
3387 If you want to log kernel messages over the network, enable this. 3387 If you want to log kernel messages over the network, enable this.
3388 See <file:Documentation/networking/netconsole.txt> for details. 3388 See <file:Documentation/networking/netconsole.txt> for details.
3389 3389
3390 config NETCONSOLE_DYNAMIC 3390 config NETCONSOLE_DYNAMIC
3391 bool "Dynamic reconfiguration of logging targets" 3391 bool "Dynamic reconfiguration of logging targets"
3392 depends on NETCONSOLE && SYSFS 3392 depends on NETCONSOLE && SYSFS && CONFIGFS_FS
3393 select CONFIGFS_FS
3394 help 3393 help
3395 This option enables the ability to dynamically reconfigure target 3394 This option enables the ability to dynamically reconfigure target
3396 parameters (interface, IP addresses, port numbers, MAC addresses) 3395 parameters (interface, IP addresses, port numbers, MAC addresses)
3397 at runtime through a userspace interface exported using configfs. 3396 at runtime through a userspace interface exported using configfs.
3398 See <file:Documentation/networking/netconsole.txt> for details. 3397 See <file:Documentation/networking/netconsole.txt> for details.
3399 3398
3400 config NETPOLL 3399 config NETPOLL
3401 def_bool NETCONSOLE 3400 def_bool NETCONSOLE
3402 3401
3403 config NETPOLL_TRAP 3402 config NETPOLL_TRAP
3404 bool "Netpoll traffic trapping" 3403 bool "Netpoll traffic trapping"
3405 default n 3404 default n
3406 depends on NETPOLL 3405 depends on NETPOLL
3407 3406
3408 config NET_POLL_CONTROLLER 3407 config NET_POLL_CONTROLLER
3409 def_bool NETPOLL 3408 def_bool NETPOLL
3410 3409
3411 config VIRTIO_NET 3410 config VIRTIO_NET
3412 tristate "Virtio network driver (EXPERIMENTAL)" 3411 tristate "Virtio network driver (EXPERIMENTAL)"
3413 depends on EXPERIMENTAL && VIRTIO 3412 depends on EXPERIMENTAL && VIRTIO
3414 ---help--- 3413 ---help---
3415 This is the virtual network driver for virtio. It can be used with 3414 This is the virtual network driver for virtio. It can be used with
3416 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M. 3415 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
3417 3416
3418 config VMXNET3 3417 config VMXNET3
3419 tristate "VMware VMXNET3 ethernet driver" 3418 tristate "VMware VMXNET3 ethernet driver"
3420 depends on PCI && INET 3419 depends on PCI && INET
3421 help 3420 help
3422 This driver supports VMware's vmxnet3 virtual ethernet NIC. 3421 This driver supports VMware's vmxnet3 virtual ethernet NIC.
3423 To compile this driver as a module, choose M here: the 3422 To compile this driver as a module, choose M here: the
3424 module will be called vmxnet3. 3423 module will be called vmxnet3.
3425 3424
3426 endif # NETDEVICES 3425 endif # NETDEVICES
3427 3426
1 config CONFIGFS_FS 1 config CONFIGFS_FS
2 tristate "Userspace-driven configuration filesystem" 2 tristate "Userspace-driven configuration filesystem"
3 depends on SYSFS 3 select SYSFS
4 help 4 help
5 configfs is a ram-based filesystem that provides the converse 5 configfs is a RAM-based filesystem that provides the converse
6 of sysfs's functionality. Where sysfs is a filesystem-based 6 of sysfs's functionality. Where sysfs is a filesystem-based
7 view of kernel objects, configfs is a filesystem-based manager 7 view of kernel objects, configfs is a filesystem-based manager
8 of kernel objects, or config_items. 8 of kernel objects, or config_items.
9 9
10 Both sysfs and configfs can and should exist together on the 10 Both sysfs and configfs can and should exist together on the
11 same system. One is not a replacement for the other. 11 same system. One is not a replacement for the other.
12 12
1 menuconfig DLM 1 menuconfig DLM
2 tristate "Distributed Lock Manager (DLM)" 2 tristate "Distributed Lock Manager (DLM)"
3 depends on EXPERIMENTAL && INET 3 depends on EXPERIMENTAL && INET
4 depends on SYSFS && (IPV6 || IPV6=n) 4 depends on SYSFS && CONFIGFS_FS && (IPV6 || IPV6=n)
5 select CONFIGFS_FS
6 select IP_SCTP 5 select IP_SCTP
7 help 6 help
8 A general purpose distributed lock manager for kernel or userspace 7 A general purpose distributed lock manager for kernel or userspace
9 applications. 8 applications.
10 9
11 config DLM_DEBUG 10 config DLM_DEBUG
12 bool "DLM debugging" 11 bool "DLM debugging"
13 depends on DLM 12 depends on DLM
14 help 13 help
15 Under the debugfs mount point, the name of each lockspace will 14 Under the debugfs mount point, the name of each lockspace will
16 appear as a file in the "dlm" directory. The output is the 15 appear as a file in the "dlm" directory. The output is the
17 list of resource and locks the local node knows about. 16 list of resource and locks the local node knows about.
18 17
1 config OCFS2_FS 1 config OCFS2_FS
2 tristate "OCFS2 file system support" 2 tristate "OCFS2 file system support"
3 depends on NET && SYSFS 3 depends on NET && SYSFS && CONFIGFS_FS
4 select CONFIGFS_FS
5 select JBD2 4 select JBD2
6 select CRC32 5 select CRC32
7 select QUOTA 6 select QUOTA
8 select QUOTA_TREE 7 select QUOTA_TREE
9 select FS_POSIX_ACL 8 select FS_POSIX_ACL
10 help 9 help
11 OCFS2 is a general purpose extent based shared disk cluster file 10 OCFS2 is a general purpose extent based shared disk cluster file
12 system with many similarities to ext3. It supports 64 bit inode 11 system with many similarities to ext3. It supports 64 bit inode
13 numbers, and has automatically extending metadata groups which may 12 numbers, and has automatically extending metadata groups which may
14 also make it attractive for non-clustered use. 13 also make it attractive for non-clustered use.
15 14
16 You'll want to install the ocfs2-tools package in order to at least 15 You'll want to install the ocfs2-tools package in order to at least
17 get "mount.ocfs2". 16 get "mount.ocfs2".
18 17
19 Project web page: http://oss.oracle.com/projects/ocfs2 18 Project web page: http://oss.oracle.com/projects/ocfs2
20 Tools web page: http://oss.oracle.com/projects/ocfs2-tools 19 Tools web page: http://oss.oracle.com/projects/ocfs2-tools
21 OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/ 20 OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
22 21
23 For more information on OCFS2, see the file 22 For more information on OCFS2, see the file
24 <file:Documentation/filesystems/ocfs2.txt>. 23 <file:Documentation/filesystems/ocfs2.txt>.
25 24
26 config OCFS2_FS_O2CB 25 config OCFS2_FS_O2CB
27 tristate "O2CB Kernelspace Clustering" 26 tristate "O2CB Kernelspace Clustering"
28 depends on OCFS2_FS 27 depends on OCFS2_FS
29 default y 28 default y
30 help 29 help
31 OCFS2 includes a simple kernelspace clustering package, the OCFS2 30 OCFS2 includes a simple kernelspace clustering package, the OCFS2
32 Cluster Base. It only requires a very small userspace component 31 Cluster Base. It only requires a very small userspace component
33 to configure it. This comes with the standard ocfs2-tools package. 32 to configure it. This comes with the standard ocfs2-tools package.
34 O2CB is limited to maintaining a cluster for OCFS2 file systems. 33 O2CB is limited to maintaining a cluster for OCFS2 file systems.
35 It cannot manage any other cluster applications. 34 It cannot manage any other cluster applications.
36 35
37 It is always safe to say Y here, as the clustering method is 36 It is always safe to say Y here, as the clustering method is
38 run-time selectable. 37 run-time selectable.
39 38
40 config OCFS2_FS_USERSPACE_CLUSTER 39 config OCFS2_FS_USERSPACE_CLUSTER
41 tristate "OCFS2 Userspace Clustering" 40 tristate "OCFS2 Userspace Clustering"
42 depends on OCFS2_FS && DLM 41 depends on OCFS2_FS && DLM
43 default y 42 default y
44 help 43 help
45 This option will allow OCFS2 to use userspace clustering services 44 This option will allow OCFS2 to use userspace clustering services
46 in conjunction with the DLM in fs/dlm. If you are using a 45 in conjunction with the DLM in fs/dlm. If you are using a
47 userspace cluster manager, say Y here. 46 userspace cluster manager, say Y here.
48 47
49 It is safe to say Y, as the clustering method is run-time 48 It is safe to say Y, as the clustering method is run-time
50 selectable. 49 selectable.
51 50
52 config OCFS2_FS_STATS 51 config OCFS2_FS_STATS
53 bool "OCFS2 statistics" 52 bool "OCFS2 statistics"
54 depends on OCFS2_FS && DEBUG_FS 53 depends on OCFS2_FS && DEBUG_FS
55 default y 54 default y
56 help 55 help
57 This option allows some fs statistics to be captured. Enabling 56 This option allows some fs statistics to be captured. Enabling
58 this option may increase the memory consumption. 57 this option may increase the memory consumption.
59 58
60 config OCFS2_DEBUG_MASKLOG 59 config OCFS2_DEBUG_MASKLOG
61 bool "OCFS2 logging support" 60 bool "OCFS2 logging support"
62 depends on OCFS2_FS 61 depends on OCFS2_FS
63 default y 62 default y
64 help 63 help
65 The ocfs2 filesystem has an extensive logging system. The system 64 The ocfs2 filesystem has an extensive logging system. The system
66 allows selection of events to log via files in /sys/o2cb/logmask/. 65 allows selection of events to log via files in /sys/o2cb/logmask/.
67 This option will enlarge your kernel, but it allows debugging of 66 This option will enlarge your kernel, but it allows debugging of
68 ocfs2 filesystem issues. 67 ocfs2 filesystem issues.
69 68
70 config OCFS2_DEBUG_FS 69 config OCFS2_DEBUG_FS
71 bool "OCFS2 expensive checks" 70 bool "OCFS2 expensive checks"
72 depends on OCFS2_FS 71 depends on OCFS2_FS
73 default n 72 default n
74 help 73 help
75 This option will enable expensive consistency checks. Enable 74 This option will enable expensive consistency checks. Enable
76 this option for debugging only as it is likely to decrease 75 this option for debugging only as it is likely to decrease
77 performance of the filesystem. 76 performance of the filesystem.
78 77