Lines Matching refs:driver

33 	bool "Network core driver support"
41 	tristate "Bonding driver support"
49 	  The driver supports multiple bonding modes to allow for both high
55 	  To compile this driver as a module, choose M here: the module
59 	tristate "Dummy net driver support"
71 	  To compile this driver as a module, choose M here: the module
81 	  one double speed connection using this driver.  Naturally, this has
83 	  Linux driver or with a Livingston Portmaster 2e.
90 	  To compile this driver as a module, choose M here: the module
94 	bool "Fibre Channel driver support"
102 	  adaptor card in your computer; say Y here and to the driver for your
110 	  This is an intermediate driver that allows sharing of
112 	  To compile this driver as a module, choose M here: the module
114 	  device at a time, you need to compile this driver as a module.
132 	  To compile this driver as a module, choose M here: the module
136 	tristate "MAC-VLAN based tap driver"
140 	  This adds a specialized tap character device driver that is based
145 	  To compile this driver as a module, choose M here: the module
164       To compile this driver as a module, choose M here: the module
179 	  To compile this driver as a module, choose M here: the module
193 	  To compile this driver as a module, choose M here: the module
224 	tristate "RapidIO Ethernet over messaging driver support"
238 	tristate "Universal TUN/TAP device driver support"
248 	  When a program opens /dev/net/tun, driver creates and registers
250 	  devices, driver will automatically delete tunXX or tapXX device and
256 	  To compile this driver as a module, choose M here: the module
283 	tristate "Virtio network driver"
286 	  This is the virtual network driver for virtio.  It can be used with
332 	  This is a driver for the General Instrument (also known as
339 	  At present this driver only compiles as a module, so say M here if
373 	tristate "Xen network device frontend driver"
378 	  This driver provides support for Xen paravirtual network
379 	  devices exported by a Xen network driver domain (often
382 	  The corresponding Linux backend driver is enabled by the
386 	  should say Y here. To compile this driver as a module, chose
393 	  This driver allows the kernel to act as a Xen network driver
398 	  The corresponding Linux frontend driver is enabled by the
401 	  The backend driver presents a standard network device
402 	  endpoint for each paravirtual network device to the driver
406 	  If you are compiling a kernel to run in a Xen network driver
408 	  compile this driver as a module, chose M here: the module
412 	tristate "VMware VMXNET3 ethernet driver"
415 	  This driver supports VMware's vmxnet3 virtual ethernet NIC.
416 	  To compile this driver as a module, choose M here: the
420 	tristate "FUJITSU Extended Socket Network Device driver"
423 	  This driver provides support for Extended Socket network device