Loading...
1#
2# Network device configuration
3#
4
5menuconfig NETDEVICES
6 default y if UML
7 depends on NET
8 bool "Network device support"
9 ---help---
10 You can say N here if you don't intend to connect your Linux box to
11 any other computer at all.
12
13 You'll have to say Y if your computer contains a network card that
14 you want to use under Linux. If you are going to run SLIP or PPP over
15 telephone line or null modem cable you need say Y here. Connecting
16 two machines with parallel ports using PLIP needs this, as well as
17 AX.25/KISS for sending Internet traffic over amateur radio links.
18
19 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
20 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
21
22 If unsure, say Y.
23
24# All the following symbols are dependent on NETDEVICES - do not repeat
25# that for each of the symbols.
26if NETDEVICES
27
28config MII
29 tristate
30
31config NET_CORE
32 default y
33 bool "Network core driver support"
34 ---help---
35 You can say N here if you do not intend to use any of the
36 networking core drivers (i.e. VLAN, bridging, bonding, etc.)
37
38if NET_CORE
39
40config BONDING
41 tristate "Bonding driver support"
42 depends on INET
43 depends on IPV6 || IPV6=n
44 ---help---
45 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
46 Channels together. This is called 'Etherchannel' by Cisco,
47 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
48
49 The driver supports multiple bonding modes to allow for both high
50 performance and high availability operation.
51
52 Refer to <file:Documentation/networking/bonding.txt> for more
53 information.
54
55 To compile this driver as a module, choose M here: the module
56 will be called bonding.
57
58config DUMMY
59 tristate "Dummy net driver support"
60 ---help---
61 This is essentially a bit-bucket device (i.e. traffic you send to
62 this device is consigned into oblivion) with a configurable IP
63 address. It is most commonly used in order to make your currently
64 inactive SLIP address seem like a real address for local programs.
65 If you use SLIP or PPP, you might want to say Y here. Since this
66 thing often comes in handy, the default is Y. It won't enlarge your
67 kernel either. What a deal. Read about it in the Network
68 Administrator's Guide, available from
69 <http://www.tldp.org/docs.html#guide>.
70
71 To compile this driver as a module, choose M here: the module
72 will be called dummy.
73
74config EQUALIZER
75 tristate "EQL (serial line load balancing) support"
76 ---help---
77 If you have two serial connections to some other computer (this
78 usually requires two modems and two telephone lines) and you use
79 SLIP (the protocol for sending Internet traffic over telephone
80 lines) or PPP (a better SLIP) on them, you can make them behave like
81 one double speed connection using this driver. Naturally, this has
82 to be supported at the other end as well, either with a similar EQL
83 Linux driver or with a Livingston Portmaster 2e.
84
85 Say Y if you want this and read
86 <file:Documentation/networking/eql.txt>. You may also want to read
87 section 6.2 of the NET-3-HOWTO, available from
88 <http://www.tldp.org/docs.html#howto>.
89
90 To compile this driver as a module, choose M here: the module
91 will be called eql. If unsure, say N.
92
93config NET_FC
94 bool "Fibre Channel driver support"
95 depends on SCSI && PCI
96 help
97 Fibre Channel is a high speed serial protocol mainly used to connect
98 large storage devices to the computer; it is compatible with and
99 intended to replace SCSI.
100
101 If you intend to use Fibre Channel, you need to have a Fibre channel
102 adaptor card in your computer; say Y here and to the driver for your
103 adaptor below. You also should have said Y to "SCSI support" and
104 "SCSI generic support".
105
106config IFB
107 tristate "Intermediate Functional Block support"
108 depends on NET_CLS_ACT
109 ---help---
110 This is an intermediate driver that allows sharing of
111 resources.
112 To compile this driver as a module, choose M here: the module
113 will be called ifb. If you want to use more than one ifb
114 device at a time, you need to compile this driver as a module.
115 Instead of 'ifb', the devices will then be called 'ifb0',
116 'ifb1' etc.
117 Look at the iproute2 documentation directory for usage etc
118
119source "drivers/net/team/Kconfig"
120
121config MACVLAN
122 tristate "MAC-VLAN support"
123 ---help---
124 This allows one to create virtual interfaces that map packets to
125 or from specific MAC addresses to a particular interface.
126
127 Macvlan devices can be added using the "ip" command from the
128 iproute2 package starting with the iproute2-2.6.23 release:
129
130 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
131
132 To compile this driver as a module, choose M here: the module
133 will be called macvlan.
134
135config MACVTAP
136 tristate "MAC-VLAN based tap driver"
137 depends on MACVLAN
138 help
139 This adds a specialized tap character device driver that is based
140 on the MAC-VLAN network interface, called macvtap. A macvtap device
141 can be added in the same way as a macvlan device, using 'type
142 macvtap', and then be accessed through the tap user space interface.
143
144 To compile this driver as a module, choose M here: the module
145 will be called macvtap.
146
147config VXLAN
148 tristate "Virtual eXtensible Local Area Network (VXLAN)"
149 depends on INET
150 select NET_IP_TUNNEL
151 ---help---
152 This allows one to create vxlan virtual interfaces that provide
153 Layer 2 Networks over Layer 3 Networks. VXLAN is often used
154 to tunnel virtual network infrastructure in virtualized environments.
155 For more information see:
156 http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
157
158 To compile this driver as a module, choose M here: the module
159 will be called vxlan.
160
161config NETCONSOLE
162 tristate "Network console logging support"
163 ---help---
164 If you want to log kernel messages over the network, enable this.
165 See <file:Documentation/networking/netconsole.txt> for details.
166
167config NETCONSOLE_DYNAMIC
168 bool "Dynamic reconfiguration of logging targets"
169 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
170 !(NETCONSOLE=y && CONFIGFS_FS=m)
171 help
172 This option enables the ability to dynamically reconfigure target
173 parameters (interface, IP addresses, port numbers, MAC addresses)
174 at runtime through a userspace interface exported using configfs.
175 See <file:Documentation/networking/netconsole.txt> for details.
176
177config NETPOLL
178 def_bool NETCONSOLE
179
180config NET_POLL_CONTROLLER
181 def_bool NETPOLL
182
183config NTB_NETDEV
184 tristate "Virtual Ethernet over NTB"
185 depends on NTB
186
187config RIONET
188 tristate "RapidIO Ethernet over messaging driver support"
189 depends on RAPIDIO
190
191config RIONET_TX_SIZE
192 int "Number of outbound queue entries"
193 depends on RIONET
194 default "128"
195
196config RIONET_RX_SIZE
197 int "Number of inbound queue entries"
198 depends on RIONET
199 default "128"
200
201config TUN
202 tristate "Universal TUN/TAP device driver support"
203 select CRC32
204 ---help---
205 TUN/TAP provides packet reception and transmission for user space
206 programs. It can be viewed as a simple Point-to-Point or Ethernet
207 device, which instead of receiving packets from a physical media,
208 receives them from user space program and instead of sending packets
209 via physical media writes them to the user space program.
210
211 When a program opens /dev/net/tun, driver creates and registers
212 corresponding net device tunX or tapX. After a program closed above
213 devices, driver will automatically delete tunXX or tapXX device and
214 all routes corresponding to it.
215
216 Please read <file:Documentation/networking/tuntap.txt> for more
217 information.
218
219 To compile this driver as a module, choose M here: the module
220 will be called tun.
221
222 If you don't know what to use this for, you don't need it.
223
224config VETH
225 tristate "Virtual ethernet pair device"
226 ---help---
227 This device is a local ethernet tunnel. Devices are created in pairs.
228 When one end receives the packet it appears on its pair and vice
229 versa.
230
231config VIRTIO_NET
232 tristate "Virtio network driver"
233 depends on VIRTIO
234 select AVERAGE
235 ---help---
236 This is the virtual network driver for virtio. It can be used with
237 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
238
239config NLMON
240 tristate "Virtual netlink monitoring device"
241 ---help---
242 This option enables a monitoring net device for netlink skbs. The
243 purpose of this is to analyze netlink messages with packet sockets.
244 Thus applications like tcpdump will be able to see local netlink
245 messages if they tap into the netlink device, record pcaps for further
246 diagnostics, etc. This is mostly intended for developers or support
247 to debug netlink issues. If unsure, say N.
248
249endif # NET_CORE
250
251config SUNGEM_PHY
252 tristate
253
254source "drivers/net/arcnet/Kconfig"
255
256source "drivers/atm/Kconfig"
257
258source "drivers/net/caif/Kconfig"
259
260source "drivers/net/dsa/Kconfig"
261
262source "drivers/net/ethernet/Kconfig"
263
264source "drivers/net/fddi/Kconfig"
265
266source "drivers/net/hippi/Kconfig"
267
268config NET_SB1000
269 tristate "General Instruments Surfboard 1000"
270 depends on PNP
271 ---help---
272 This is a driver for the General Instrument (also known as
273 NextLevel) SURFboard 1000 internal
274 cable modem. This is an ISA card which is used by a number of cable
275 TV companies to provide cable modem access. It's a one-way
276 downstream-only cable modem, meaning that your upstream net link is
277 provided by your regular phone modem.
278
279 At present this driver only compiles as a module, so say M here if
280 you have this card. The module will be called sb1000. Then read
281 <file:Documentation/networking/README.sb1000> for information on how
282 to use this module, as it needs special ppp scripts for establishing
283 a connection. Further documentation and the necessary scripts can be
284 found at:
285
286 <http://www.jacksonville.net/~fventuri/>
287 <http://home.adelphia.net/~siglercm/sb1000.html>
288 <http://linuxpower.cx/~cable/>
289
290 If you don't have this card, of course say N.
291
292source "drivers/net/phy/Kconfig"
293
294source "drivers/net/plip/Kconfig"
295
296source "drivers/net/ppp/Kconfig"
297
298source "drivers/net/slip/Kconfig"
299
300source "drivers/s390/net/Kconfig"
301
302source "drivers/net/usb/Kconfig"
303
304source "drivers/net/wireless/Kconfig"
305
306source "drivers/net/wimax/Kconfig"
307
308source "drivers/net/wan/Kconfig"
309
310source "drivers/net/ieee802154/Kconfig"
311
312config XEN_NETDEV_FRONTEND
313 tristate "Xen network device frontend driver"
314 depends on XEN
315 select XEN_XENBUS_FRONTEND
316 default y
317 help
318 This driver provides support for Xen paravirtual network
319 devices exported by a Xen network driver domain (often
320 domain 0).
321
322 The corresponding Linux backend driver is enabled by the
323 CONFIG_XEN_NETDEV_BACKEND option.
324
325 If you are compiling a kernel for use as Xen guest, you
326 should say Y here. To compile this driver as a module, chose
327 M here: the module will be called xen-netfront.
328
329config XEN_NETDEV_BACKEND
330 tristate "Xen backend network device"
331 depends on XEN_BACKEND
332 help
333 This driver allows the kernel to act as a Xen network driver
334 domain which exports paravirtual network devices to other
335 Xen domains. These devices can be accessed by any operating
336 system that implements a compatible front end.
337
338 The corresponding Linux frontend driver is enabled by the
339 CONFIG_XEN_NETDEV_FRONTEND configuration option.
340
341 The backend driver presents a standard network device
342 endpoint for each paravirtual network device to the driver
343 domain network stack. These can then be bridged or routed
344 etc in order to provide full network connectivity.
345
346 If you are compiling a kernel to run in a Xen network driver
347 domain (often this is domain 0) you should say Y here. To
348 compile this driver as a module, chose M here: the module
349 will be called xen-netback.
350
351config VMXNET3
352 tristate "VMware VMXNET3 ethernet driver"
353 depends on PCI && INET
354 help
355 This driver supports VMware's vmxnet3 virtual ethernet NIC.
356 To compile this driver as a module, choose M here: the
357 module will be called vmxnet3.
358
359source "drivers/net/hyperv/Kconfig"
360
361endif # NETDEVICES
1#
2# Network device configuration
3#
4
5menuconfig NETDEVICES
6 default y if UML
7 depends on NET
8 bool "Network device support"
9 ---help---
10 You can say N here if you don't intend to connect your Linux box to
11 any other computer at all.
12
13 You'll have to say Y if your computer contains a network card that
14 you want to use under Linux. If you are going to run SLIP or PPP over
15 telephone line or null modem cable you need say Y here. Connecting
16 two machines with parallel ports using PLIP needs this, as well as
17 AX.25/KISS for sending Internet traffic over amateur radio links.
18
19 See also "The Linux Network Administrator's Guide" by Olaf Kirch and
20 Terry Dawson. Available at <http://www.tldp.org/guides.html>.
21
22 If unsure, say Y.
23
24# All the following symbols are dependent on NETDEVICES - do not repeat
25# that for each of the symbols.
26if NETDEVICES
27
28config MII
29 tristate
30
31config NET_CORE
32 default y
33 bool "Network core driver support"
34 ---help---
35 You can say N here if you do not intend to use any of the
36 networking core drivers (i.e. VLAN, bridging, bonding, etc.)
37
38if NET_CORE
39
40config BONDING
41 tristate "Bonding driver support"
42 depends on INET
43 depends on IPV6 || IPV6=n
44 ---help---
45 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
46 Channels together. This is called 'Etherchannel' by Cisco,
47 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
48
49 The driver supports multiple bonding modes to allow for both high
50 performance and high availability operation.
51
52 Refer to <file:Documentation/networking/bonding.txt> for more
53 information.
54
55 To compile this driver as a module, choose M here: the module
56 will be called bonding.
57
58config DUMMY
59 tristate "Dummy net driver support"
60 ---help---
61 This is essentially a bit-bucket device (i.e. traffic you send to
62 this device is consigned into oblivion) with a configurable IP
63 address. It is most commonly used in order to make your currently
64 inactive SLIP address seem like a real address for local programs.
65 If you use SLIP or PPP, you might want to say Y here. It won't
66 enlarge your kernel. What a deal. Read about it in the Network
67 Administrator's Guide, available from
68 <http://www.tldp.org/docs.html#guide>.
69
70 To compile this driver as a module, choose M here: the module
71 will be called dummy.
72
73config EQUALIZER
74 tristate "EQL (serial line load balancing) support"
75 ---help---
76 If you have two serial connections to some other computer (this
77 usually requires two modems and two telephone lines) and you use
78 SLIP (the protocol for sending Internet traffic over telephone
79 lines) or PPP (a better SLIP) on them, you can make them behave like
80 one double speed connection using this driver. Naturally, this has
81 to be supported at the other end as well, either with a similar EQL
82 Linux driver or with a Livingston Portmaster 2e.
83
84 Say Y if you want this and read
85 <file:Documentation/networking/eql.txt>. You may also want to read
86 section 6.2 of the NET-3-HOWTO, available from
87 <http://www.tldp.org/docs.html#howto>.
88
89 To compile this driver as a module, choose M here: the module
90 will be called eql. If unsure, say N.
91
92config NET_FC
93 bool "Fibre Channel driver support"
94 depends on SCSI && PCI
95 help
96 Fibre Channel is a high speed serial protocol mainly used to connect
97 large storage devices to the computer; it is compatible with and
98 intended to replace SCSI.
99
100 If you intend to use Fibre Channel, you need to have a Fibre channel
101 adaptor card in your computer; say Y here and to the driver for your
102 adaptor below. You also should have said Y to "SCSI support" and
103 "SCSI generic support".
104
105config IFB
106 tristate "Intermediate Functional Block support"
107 depends on NET_CLS_ACT
108 ---help---
109 This is an intermediate driver that allows sharing of
110 resources.
111 To compile this driver as a module, choose M here: the module
112 will be called ifb. If you want to use more than one ifb
113 device at a time, you need to compile this driver as a module.
114 Instead of 'ifb', the devices will then be called 'ifb0',
115 'ifb1' etc.
116 Look at the iproute2 documentation directory for usage etc
117
118source "drivers/net/team/Kconfig"
119
120config MACVLAN
121 tristate "MAC-VLAN support"
122 ---help---
123 This allows one to create virtual interfaces that map packets to
124 or from specific MAC addresses to a particular interface.
125
126 Macvlan devices can be added using the "ip" command from the
127 iproute2 package starting with the iproute2-2.6.23 release:
128
129 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
130
131 To compile this driver as a module, choose M here: the module
132 will be called macvlan.
133
134config MACVTAP
135 tristate "MAC-VLAN based tap driver"
136 depends on MACVLAN
137 depends on INET
138 help
139 This adds a specialized tap character device driver that is based
140 on the MAC-VLAN network interface, called macvtap. A macvtap device
141 can be added in the same way as a macvlan device, using 'type
142 macvtap', and then be accessed through the tap user space interface.
143
144 To compile this driver as a module, choose M here: the module
145 will be called macvtap.
146
147
148config IPVLAN
149 tristate "IP-VLAN support"
150 depends on INET
151 depends on IPV6
152 ---help---
153 This allows one to create virtual devices off of a main interface
154 and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)
155 on packets. All interfaces (including the main interface) share L2
156 making it transparent to the connected L2 switch.
157
158 Ipvlan devices can be added using the "ip" command from the
159 iproute2 package starting with the iproute2-3.19 release:
160
161 "ip link add link <main-dev> [ NAME ] type ipvlan"
162
163 To compile this driver as a module, choose M here: the module
164 will be called ipvlan.
165
166
167config VXLAN
168 tristate "Virtual eXtensible Local Area Network (VXLAN)"
169 depends on INET
170 select NET_UDP_TUNNEL
171 ---help---
172 This allows one to create vxlan virtual interfaces that provide
173 Layer 2 Networks over Layer 3 Networks. VXLAN is often used
174 to tunnel virtual network infrastructure in virtualized environments.
175 For more information see:
176 http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
177
178 To compile this driver as a module, choose M here: the module
179 will be called vxlan.
180
181config GENEVE
182 tristate "Generic Network Virtualization Encapsulation"
183 depends on INET && NET_UDP_TUNNEL
184 select NET_IP_TUNNEL
185 ---help---
186 This allows one to create geneve virtual interfaces that provide
187 Layer 2 Networks over Layer 3 Networks. GENEVE is often used
188 to tunnel virtual network infrastructure in virtualized environments.
189 For more information see:
190 http://tools.ietf.org/html/draft-gross-geneve-02
191
192 To compile this driver as a module, choose M here: the module
193 will be called geneve.
194
195config MACSEC
196 tristate "IEEE 802.1AE MAC-level encryption (MACsec)"
197 select CRYPTO
198 select CRYPTO_AES
199 select CRYPTO_GCM
200 ---help---
201 MACsec is an encryption standard for Ethernet.
202
203config NETCONSOLE
204 tristate "Network console logging support"
205 ---help---
206 If you want to log kernel messages over the network, enable this.
207 See <file:Documentation/networking/netconsole.txt> for details.
208
209config NETCONSOLE_DYNAMIC
210 bool "Dynamic reconfiguration of logging targets"
211 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
212 !(NETCONSOLE=y && CONFIGFS_FS=m)
213 help
214 This option enables the ability to dynamically reconfigure target
215 parameters (interface, IP addresses, port numbers, MAC addresses)
216 at runtime through a userspace interface exported using configfs.
217 See <file:Documentation/networking/netconsole.txt> for details.
218
219config NETPOLL
220 def_bool NETCONSOLE
221 select SRCU
222
223config NET_POLL_CONTROLLER
224 def_bool NETPOLL
225
226config NTB_NETDEV
227 tristate "Virtual Ethernet over NTB Transport"
228 depends on NTB_TRANSPORT
229
230config RIONET
231 tristate "RapidIO Ethernet over messaging driver support"
232 depends on RAPIDIO
233
234config RIONET_TX_SIZE
235 int "Number of outbound queue entries"
236 depends on RIONET
237 default "128"
238
239config RIONET_RX_SIZE
240 int "Number of inbound queue entries"
241 depends on RIONET
242 default "128"
243
244config TUN
245 tristate "Universal TUN/TAP device driver support"
246 depends on INET
247 select CRC32
248 ---help---
249 TUN/TAP provides packet reception and transmission for user space
250 programs. It can be viewed as a simple Point-to-Point or Ethernet
251 device, which instead of receiving packets from a physical media,
252 receives them from user space program and instead of sending packets
253 via physical media writes them to the user space program.
254
255 When a program opens /dev/net/tun, driver creates and registers
256 corresponding net device tunX or tapX. After a program closed above
257 devices, driver will automatically delete tunXX or tapXX device and
258 all routes corresponding to it.
259
260 Please read <file:Documentation/networking/tuntap.txt> for more
261 information.
262
263 To compile this driver as a module, choose M here: the module
264 will be called tun.
265
266 If you don't know what to use this for, you don't need it.
267
268config TUN_VNET_CROSS_LE
269 bool "Support for cross-endian vnet headers on little-endian kernels"
270 default n
271 ---help---
272 This option allows TUN/TAP and MACVTAP device drivers in a
273 little-endian kernel to parse vnet headers that come from a
274 big-endian legacy virtio device.
275
276 Userspace programs can control the feature using the TUNSETVNETBE
277 and TUNGETVNETBE ioctls.
278
279 Unless you have a little-endian system hosting a big-endian virtual
280 machine with a legacy virtio NIC, you should say N.
281
282config VETH
283 tristate "Virtual ethernet pair device"
284 ---help---
285 This device is a local ethernet tunnel. Devices are created in pairs.
286 When one end receives the packet it appears on its pair and vice
287 versa.
288
289config VIRTIO_NET
290 tristate "Virtio network driver"
291 depends on VIRTIO
292 ---help---
293 This is the virtual network driver for virtio. It can be used with
294 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
295
296config NLMON
297 tristate "Virtual netlink monitoring device"
298 ---help---
299 This option enables a monitoring net device for netlink skbs. The
300 purpose of this is to analyze netlink messages with packet sockets.
301 Thus applications like tcpdump will be able to see local netlink
302 messages if they tap into the netlink device, record pcaps for further
303 diagnostics, etc. This is mostly intended for developers or support
304 to debug netlink issues. If unsure, say N.
305
306config NET_VRF
307 tristate "Virtual Routing and Forwarding (Lite)"
308 depends on IP_MULTIPLE_TABLES
309 depends on NET_L3_MASTER_DEV
310 depends on IPV6 || IPV6=n
311 depends on IPV6_MULTIPLE_TABLES || IPV6=n
312 ---help---
313 This option enables the support for mapping interfaces into VRF's. The
314 support enables VRF devices.
315
316endif # NET_CORE
317
318config SUNGEM_PHY
319 tristate
320
321source "drivers/net/arcnet/Kconfig"
322
323source "drivers/atm/Kconfig"
324
325source "drivers/net/caif/Kconfig"
326
327source "drivers/net/dsa/Kconfig"
328
329source "drivers/net/ethernet/Kconfig"
330
331source "drivers/net/fddi/Kconfig"
332
333source "drivers/net/hippi/Kconfig"
334
335config NET_SB1000
336 tristate "General Instruments Surfboard 1000"
337 depends on PNP
338 ---help---
339 This is a driver for the General Instrument (also known as
340 NextLevel) SURFboard 1000 internal
341 cable modem. This is an ISA card which is used by a number of cable
342 TV companies to provide cable modem access. It's a one-way
343 downstream-only cable modem, meaning that your upstream net link is
344 provided by your regular phone modem.
345
346 At present this driver only compiles as a module, so say M here if
347 you have this card. The module will be called sb1000. Then read
348 <file:Documentation/networking/README.sb1000> for information on how
349 to use this module, as it needs special ppp scripts for establishing
350 a connection. Further documentation and the necessary scripts can be
351 found at:
352
353 <http://www.jacksonville.net/~fventuri/>
354 <http://home.adelphia.net/~siglercm/sb1000.html>
355 <http://linuxpower.cx/~cable/>
356
357 If you don't have this card, of course say N.
358
359source "drivers/net/phy/Kconfig"
360
361source "drivers/net/plip/Kconfig"
362
363source "drivers/net/ppp/Kconfig"
364
365source "drivers/net/slip/Kconfig"
366
367source "drivers/s390/net/Kconfig"
368
369source "drivers/net/usb/Kconfig"
370
371source "drivers/net/wireless/Kconfig"
372
373source "drivers/net/wimax/Kconfig"
374
375source "drivers/net/wan/Kconfig"
376
377source "drivers/net/ieee802154/Kconfig"
378
379config XEN_NETDEV_FRONTEND
380 tristate "Xen network device frontend driver"
381 depends on XEN
382 select XEN_XENBUS_FRONTEND
383 default y
384 help
385 This driver provides support for Xen paravirtual network
386 devices exported by a Xen network driver domain (often
387 domain 0).
388
389 The corresponding Linux backend driver is enabled by the
390 CONFIG_XEN_NETDEV_BACKEND option.
391
392 If you are compiling a kernel for use as Xen guest, you
393 should say Y here. To compile this driver as a module, chose
394 M here: the module will be called xen-netfront.
395
396config XEN_NETDEV_BACKEND
397 tristate "Xen backend network device"
398 depends on XEN_BACKEND
399 help
400 This driver allows the kernel to act as a Xen network driver
401 domain which exports paravirtual network devices to other
402 Xen domains. These devices can be accessed by any operating
403 system that implements a compatible front end.
404
405 The corresponding Linux frontend driver is enabled by the
406 CONFIG_XEN_NETDEV_FRONTEND configuration option.
407
408 The backend driver presents a standard network device
409 endpoint for each paravirtual network device to the driver
410 domain network stack. These can then be bridged or routed
411 etc in order to provide full network connectivity.
412
413 If you are compiling a kernel to run in a Xen network driver
414 domain (often this is domain 0) you should say Y here. To
415 compile this driver as a module, chose M here: the module
416 will be called xen-netback.
417
418config VMXNET3
419 tristate "VMware VMXNET3 ethernet driver"
420 depends on PCI && INET
421 help
422 This driver supports VMware's vmxnet3 virtual ethernet NIC.
423 To compile this driver as a module, choose M here: the
424 module will be called vmxnet3.
425
426config FUJITSU_ES
427 tristate "FUJITSU Extended Socket Network Device driver"
428 depends on ACPI
429 help
430 This driver provides support for Extended Socket network device
431 on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series.
432
433source "drivers/net/hyperv/Kconfig"
434
435endif # NETDEVICES