2005-04-16 16:20:36 -06:00
|
|
|
#
|
|
|
|
# Network device configuration
|
|
|
|
#
|
|
|
|
|
2010-08-07 22:21:33 -06:00
|
|
|
config HAVE_NET_MACB
|
|
|
|
bool
|
|
|
|
|
2007-06-13 13:48:53 -06:00
|
|
|
menuconfig NETDEVICES
|
2006-01-18 18:42:59 -07:00
|
|
|
default y if UML
|
2007-07-21 20:11:35 -06:00
|
|
|
depends on NET
|
2005-04-16 16:20:36 -06:00
|
|
|
bool "Network device support"
|
|
|
|
---help---
|
|
|
|
You can say N here if you don't intend to connect your Linux box to
|
|
|
|
any other computer at all.
|
|
|
|
|
|
|
|
You'll have to say Y if your computer contains a network card that
|
|
|
|
you want to use under Linux. If you are going to run SLIP or PPP over
|
|
|
|
telephone line or null modem cable you need say Y here. Connecting
|
|
|
|
two machines with parallel ports using PLIP needs this, as well as
|
|
|
|
AX.25/KISS for sending Internet traffic over amateur radio links.
|
|
|
|
|
|
|
|
See also "The Linux Network Administrator's Guide" by Olaf Kirch and
|
|
|
|
Terry Dawson. Available at <http://www.tldp.org/guides.html>.
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
2006-09-26 00:11:21 -06:00
|
|
|
# All the following symbols are dependent on NETDEVICES - do not repeat
|
|
|
|
# that for each of the symbols.
|
|
|
|
if NETDEVICES
|
2005-07-27 14:04:35 -06:00
|
|
|
|
2006-01-08 23:34:25 -07:00
|
|
|
config IFB
|
|
|
|
tristate "Intermediate Functional Block support"
|
|
|
|
depends on NET_CLS_ACT
|
|
|
|
---help---
|
2006-11-29 21:22:59 -07:00
|
|
|
This is an intermediate driver that allows sharing of
|
2006-01-08 23:34:25 -07:00
|
|
|
resources.
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called ifb. If you want to use more than one ifb
|
|
|
|
device at a time, you need to compile this driver as a module.
|
|
|
|
Instead of 'ifb', the devices will then be called 'ifb0',
|
|
|
|
'ifb1' etc.
|
|
|
|
Look at the iproute2 documentation directory for usage etc
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config DUMMY
|
|
|
|
tristate "Dummy net driver support"
|
|
|
|
---help---
|
|
|
|
This is essentially a bit-bucket device (i.e. traffic you send to
|
|
|
|
this device is consigned into oblivion) with a configurable IP
|
|
|
|
address. It is most commonly used in order to make your currently
|
|
|
|
inactive SLIP address seem like a real address for local programs.
|
|
|
|
If you use SLIP or PPP, you might want to say Y here. Since this
|
|
|
|
thing often comes in handy, the default is Y. It won't enlarge your
|
|
|
|
kernel either. What a deal. Read about it in the Network
|
|
|
|
Administrator's Guide, available from
|
|
|
|
<http://www.tldp.org/docs.html#guide>.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called dummy. If you want to use more than one dummy
|
|
|
|
device at a time, you need to compile this driver as a module.
|
|
|
|
Instead of 'dummy', the devices will then be called 'dummy0',
|
|
|
|
'dummy1' etc.
|
|
|
|
|
|
|
|
config BONDING
|
|
|
|
tristate "Bonding driver support"
|
|
|
|
depends on INET
|
bonding: send IPv6 neighbor advertisement on failover
This patch adds better IPv6 failover support for bonding devices,
especially when in active-backup mode and there are only IPv6 addresses
configured, as reported by Alex Sidorenko.
- Creates a new file, net/drivers/bonding/bond_ipv6.c, for the
IPv6-specific routines. Both regular bonds and VLANs over bonds
are supported.
- Adds a new tunable, num_unsol_na, to limit the number of unsolicited
IPv6 Neighbor Advertisements that are sent on a failover event.
Default is 1.
- Creates two new IPv6 neighbor discovery functions:
ndisc_build_skb()
ndisc_send_skb()
These were required to support VLANs since we have to be able to
add the VLAN id to the skb since ndisc_send_na() and friends
shouldn't be asked to do this. These two routines are basically
__ndisc_send() split into two pieces, in a slightly different order.
- Updates Documentation/networking/bonding.txt and bumps the rev of bond
support to 3.4.0.
On failover, this new code will generate one packet:
- An unsolicited IPv6 Neighbor Advertisement, which helps the switch
learn that the address has moved to the new slave.
Testing has shown that sending just the NA results in pretty good
behavior when in active-back mode, I saw no lost ping packets for example.
Signed-off-by: Brian Haley <brian.haley@hp.com>
Signed-off-by: Jay Vosburgh <fubar@us.ibm.com>
Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
2008-11-04 18:51:14 -07:00
|
|
|
depends on IPV6 || IPV6=n
|
2005-04-16 16:20:36 -06:00
|
|
|
---help---
|
|
|
|
Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
|
|
|
|
Channels together. This is called 'Etherchannel' by Cisco,
|
|
|
|
'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
|
|
|
|
|
|
|
|
The driver supports multiple bonding modes to allow for both high
|
2006-02-12 10:53:04 -07:00
|
|
|
performance and high availability operation.
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
Refer to <file:Documentation/networking/bonding.txt> for more
|
|
|
|
information.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called bonding.
|
|
|
|
|
2007-07-14 19:55:06 -06:00
|
|
|
config MACVLAN
|
|
|
|
tristate "MAC-VLAN support (EXPERIMENTAL)"
|
|
|
|
depends on EXPERIMENTAL
|
|
|
|
---help---
|
|
|
|
This allows one to create virtual interfaces that map packets to
|
|
|
|
or from specific MAC addresses to a particular interface.
|
|
|
|
|
2008-02-26 18:52:05 -07:00
|
|
|
Macvlan devices can be added using the "ip" command from the
|
|
|
|
iproute2 package starting with the iproute2-2.6.23 release:
|
|
|
|
|
|
|
|
"ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
|
|
|
|
|
2007-07-14 19:55:06 -06:00
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called macvlan.
|
|
|
|
|
2010-01-30 05:24:26 -07:00
|
|
|
config MACVTAP
|
|
|
|
tristate "MAC-VLAN based tap driver (EXPERIMENTAL)"
|
|
|
|
depends on MACVLAN
|
|
|
|
help
|
|
|
|
This adds a specialized tap character device driver that is based
|
|
|
|
on the MAC-VLAN network interface, called macvtap. A macvtap device
|
|
|
|
can be added in the same way as a macvlan device, using 'type
|
|
|
|
macvlan', and then be accessed through the tap user space interface.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called macvtap.
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config EQUALIZER
|
|
|
|
tristate "EQL (serial line load balancing) support"
|
|
|
|
---help---
|
|
|
|
If you have two serial connections to some other computer (this
|
|
|
|
usually requires two modems and two telephone lines) and you use
|
|
|
|
SLIP (the protocol for sending Internet traffic over telephone
|
|
|
|
lines) or PPP (a better SLIP) on them, you can make them behave like
|
|
|
|
one double speed connection using this driver. Naturally, this has
|
|
|
|
to be supported at the other end as well, either with a similar EQL
|
|
|
|
Linux driver or with a Livingston Portmaster 2e.
|
|
|
|
|
|
|
|
Say Y if you want this and read
|
|
|
|
<file:Documentation/networking/eql.txt>. You may also want to read
|
|
|
|
section 6.2 of the NET-3-HOWTO, available from
|
|
|
|
<http://www.tldp.org/docs.html#howto>.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called eql. If unsure, say N.
|
|
|
|
|
|
|
|
config TUN
|
|
|
|
tristate "Universal TUN/TAP device driver support"
|
|
|
|
select CRC32
|
|
|
|
---help---
|
|
|
|
TUN/TAP provides packet reception and transmission for user space
|
|
|
|
programs. It can be viewed as a simple Point-to-Point or Ethernet
|
|
|
|
device, which instead of receiving packets from a physical media,
|
|
|
|
receives them from user space program and instead of sending packets
|
|
|
|
via physical media writes them to the user space program.
|
|
|
|
|
|
|
|
When a program opens /dev/net/tun, driver creates and registers
|
|
|
|
corresponding net device tunX or tapX. After a program closed above
|
|
|
|
devices, driver will automatically delete tunXX or tapXX device and
|
|
|
|
all routes corresponding to it.
|
|
|
|
|
|
|
|
Please read <file:Documentation/networking/tuntap.txt> for more
|
|
|
|
information.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called tun.
|
|
|
|
|
|
|
|
If you don't know what to use this for, you don't need it.
|
|
|
|
|
2007-09-25 17:14:46 -06:00
|
|
|
config VETH
|
2007-11-06 21:35:55 -07:00
|
|
|
tristate "Virtual ethernet pair device"
|
2007-09-25 17:14:46 -06:00
|
|
|
---help---
|
2007-11-06 21:35:55 -07:00
|
|
|
This device is a local ethernet tunnel. Devices are created in pairs.
|
|
|
|
When one end receives the packet it appears on its pair and vice
|
|
|
|
versa.
|
2007-09-25 17:14:46 -06:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config NET_SB1000
|
|
|
|
tristate "General Instruments Surfboard 1000"
|
2005-07-27 14:04:35 -06:00
|
|
|
depends on PNP
|
2005-04-16 16:20:36 -06:00
|
|
|
---help---
|
|
|
|
This is a driver for the General Instrument (also known as
|
|
|
|
NextLevel) SURFboard 1000 internal
|
|
|
|
cable modem. This is an ISA card which is used by a number of cable
|
|
|
|
TV companies to provide cable modem access. It's a one-way
|
|
|
|
downstream-only cable modem, meaning that your upstream net link is
|
|
|
|
provided by your regular phone modem.
|
|
|
|
|
|
|
|
At present this driver only compiles as a module, so say M here if
|
|
|
|
you have this card. The module will be called sb1000. Then read
|
|
|
|
<file:Documentation/networking/README.sb1000> for information on how
|
|
|
|
to use this module, as it needs special ppp scripts for establishing
|
|
|
|
a connection. Further documentation and the necessary scripts can be
|
|
|
|
found at:
|
|
|
|
|
|
|
|
<http://www.jacksonville.net/~fventuri/>
|
|
|
|
<http://home.adelphia.net/~siglercm/sb1000.html>
|
|
|
|
<http://linuxpower.cx/~cable/>
|
|
|
|
|
|
|
|
If you don't have this card, of course say N.
|
|
|
|
|
2006-01-05 23:45:41 -07:00
|
|
|
source "drivers/net/arcnet/Kconfig"
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2010-10-13 09:18:59 -06:00
|
|
|
config MII
|
|
|
|
tristate "Generic Media Independent Interface device support"
|
|
|
|
help
|
|
|
|
Most ethernet controllers have MII transceiver either as an external
|
|
|
|
or internal device. It is safe to say Y or M here even if your
|
|
|
|
ethernet card lacks MII.
|
|
|
|
|
2005-07-30 17:31:23 -06:00
|
|
|
source "drivers/net/phy/Kconfig"
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
#
|
|
|
|
# Ethernet
|
|
|
|
#
|
|
|
|
|
2011-03-29 19:25:21 -06:00
|
|
|
source "drivers/net/ethernet/Kconfig"
|
|
|
|
|
2007-06-13 13:48:53 -06:00
|
|
|
menuconfig NET_ETHERNET
|
2005-04-16 16:20:36 -06:00
|
|
|
bool "Ethernet (10 or 100Mbit)"
|
2007-06-13 13:48:53 -06:00
|
|
|
depends on !UML
|
2005-04-16 16:20:36 -06:00
|
|
|
---help---
|
|
|
|
Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
|
|
|
|
type of Local Area Network (LAN) in universities and companies.
|
|
|
|
|
|
|
|
Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
|
|
|
|
coaxial cable, linking computers in a chain), 10BASE-T or twisted
|
|
|
|
pair (10 Mbps over twisted pair cable, linking computers to central
|
|
|
|
hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
|
|
|
|
100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
|
|
|
|
100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
|
|
|
|
cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
|
|
|
|
[the 100BASE varieties are also known as Fast Ethernet], and Gigabit
|
|
|
|
Ethernet (1 Gbps over optical fiber or short copper links).
|
|
|
|
|
|
|
|
If your Linux machine will be connected to an Ethernet and you have
|
|
|
|
an Ethernet network interface card (NIC) installed in your computer,
|
|
|
|
say Y here and read the Ethernet-HOWTO, available from
|
|
|
|
<http://www.tldp.org/docs.html#howto>. You will then also have
|
|
|
|
to say Y to the driver for your particular NIC.
|
|
|
|
|
|
|
|
Note that the answer to this question won't directly affect the
|
|
|
|
kernel: saying N will just cause the configurator to skip all
|
|
|
|
the questions about Ethernet network cards. If unsure, say N.
|
|
|
|
|
2007-06-13 13:48:53 -06:00
|
|
|
if NET_ETHERNET
|
|
|
|
|
2006-11-09 06:51:17 -07:00
|
|
|
config MACB
|
|
|
|
tristate "Atmel MACB support"
|
2010-08-07 22:21:33 -06:00
|
|
|
depends on HAVE_NET_MACB
|
2007-07-12 11:07:24 -06:00
|
|
|
select PHYLIB
|
2006-11-09 06:51:17 -07:00
|
|
|
help
|
|
|
|
The Atmel MACB ethernet interface is found on many AT32 and AT91
|
|
|
|
parts. Say Y to include support for the MACB chip.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called macb.
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
source "drivers/net/arm/Kconfig"
|
|
|
|
|
2008-03-19 10:14:51 -06:00
|
|
|
config KORINA
|
|
|
|
tristate "Korina (IDT RC32434) Ethernet support"
|
2008-04-28 05:48:40 -06:00
|
|
|
depends on NET_ETHERNET && MIKROTIK_RB532
|
2008-03-19 10:14:51 -06:00
|
|
|
help
|
|
|
|
If you have a Mikrotik RouterBoard 500 or IDT RC32434
|
|
|
|
based system say Y. Otherwise say N.
|
|
|
|
|
2005-10-10 07:51:27 -06:00
|
|
|
config MIPS_SIM_NET
|
2007-03-18 17:21:22 -06:00
|
|
|
tristate "MIPS simulator Network device"
|
2007-06-13 13:48:53 -06:00
|
|
|
depends on MIPS_SIM
|
2005-10-10 07:51:27 -06:00
|
|
|
help
|
|
|
|
The MIPSNET device is a simple Ethernet network device which is
|
|
|
|
emulated by the MIPS Simulator.
|
|
|
|
If you are not using a MIPSsim or are unsure, say N.
|
|
|
|
|
2008-06-09 17:33:56 -06:00
|
|
|
config SH_ETH
|
|
|
|
tristate "Renesas SuperH Ethernet support"
|
|
|
|
depends on SUPERH && \
|
2009-05-24 17:54:30 -06:00
|
|
|
(CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
|
|
|
|
CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
|
2010-07-05 12:32:50 -06:00
|
|
|
CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
|
2008-06-09 17:33:56 -06:00
|
|
|
select CRC32
|
|
|
|
select MII
|
|
|
|
select MDIO_BITBANG
|
|
|
|
select PHYLIB
|
|
|
|
help
|
|
|
|
Renesas SuperH Ethernet device driver.
|
2010-07-05 12:32:50 -06:00
|
|
|
This driver supporting CPUs are:
|
|
|
|
- SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
|
2008-06-09 17:33:56 -06:00
|
|
|
|
2007-07-17 00:43:44 -06:00
|
|
|
config BFIN_MAC
|
2008-08-26 21:47:57 -06:00
|
|
|
tristate "Blackfin on-chip MAC support"
|
2009-01-08 11:52:26 -07:00
|
|
|
depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
|
2007-07-17 00:43:44 -06:00
|
|
|
select CRC32
|
2007-09-19 09:37:41 -06:00
|
|
|
select MII
|
|
|
|
select PHYLIB
|
2007-07-17 00:43:44 -06:00
|
|
|
select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
|
|
|
|
help
|
2008-08-26 21:47:57 -06:00
|
|
|
This is the driver for Blackfin on-chip mac device. Say Y if you want it
|
2007-07-17 00:43:44 -06:00
|
|
|
compiled into the kernel. This driver is also available as a module
|
|
|
|
( = code which can be inserted in and removed from the running kernel
|
|
|
|
whenever you want). The module will be called bfin_mac.
|
|
|
|
|
|
|
|
config BFIN_MAC_USE_L1
|
|
|
|
bool "Use L1 memory for rx/tx packets"
|
2008-01-30 01:52:25 -07:00
|
|
|
depends on BFIN_MAC && (BF527 || BF537)
|
2007-07-17 00:43:44 -06:00
|
|
|
default y
|
|
|
|
help
|
2007-10-19 17:34:40 -06:00
|
|
|
To get maximum network performance, you should use L1 memory as rx/tx buffers.
|
2007-07-17 00:43:44 -06:00
|
|
|
Say N here if you want to reserve L1 memory for other uses.
|
|
|
|
|
|
|
|
config BFIN_TX_DESC_NUM
|
|
|
|
int "Number of transmit buffer packets"
|
|
|
|
depends on BFIN_MAC
|
|
|
|
range 6 10 if BFIN_MAC_USE_L1
|
|
|
|
range 10 100
|
|
|
|
default "10"
|
|
|
|
help
|
|
|
|
Set the number of buffer packets used in driver.
|
|
|
|
|
|
|
|
config BFIN_RX_DESC_NUM
|
|
|
|
int "Number of receive buffer packets"
|
|
|
|
depends on BFIN_MAC
|
|
|
|
range 20 100 if BFIN_MAC_USE_L1
|
|
|
|
range 20 800
|
|
|
|
default "20"
|
|
|
|
help
|
|
|
|
Set the number of buffer packets used in driver.
|
|
|
|
|
2010-05-17 18:19:40 -06:00
|
|
|
config BFIN_MAC_USE_HWSTAMP
|
|
|
|
bool "Use IEEE 1588 hwstamp"
|
|
|
|
depends on BFIN_MAC && BF518
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
To support the IEEE 1588 Precision Time Protocol (PTP), select y here
|
|
|
|
|
2006-06-21 23:11:13 -06:00
|
|
|
config NET_NETX
|
|
|
|
tristate "NetX Ethernet support"
|
|
|
|
select MII
|
2007-06-13 13:48:53 -06:00
|
|
|
depends on ARCH_NETX
|
2006-06-21 23:11:13 -06:00
|
|
|
help
|
|
|
|
This is support for the Hilscher netX builtin Ethernet ports
|
|
|
|
|
2007-11-12 22:03:58 -07:00
|
|
|
To compile this driver as a module, choose M here. The module
|
2006-06-21 23:11:13 -06:00
|
|
|
will be called netx-eth.
|
|
|
|
|
2009-05-18 16:19:01 -06:00
|
|
|
config TI_DAVINCI_EMAC
|
|
|
|
tristate "TI DaVinci EMAC Support"
|
2009-11-19 03:28:25 -07:00
|
|
|
depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
|
2010-09-15 08:11:24 -06:00
|
|
|
select TI_DAVINCI_MDIO
|
2010-09-15 08:11:28 -06:00
|
|
|
select TI_DAVINCI_CPDMA
|
2009-05-18 16:19:01 -06:00
|
|
|
select PHYLIB
|
|
|
|
help
|
|
|
|
This driver supports TI's DaVinci Ethernet .
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called davinci_emac_driver. This is recommended.
|
|
|
|
|
2010-09-15 08:11:21 -06:00
|
|
|
config TI_DAVINCI_MDIO
|
|
|
|
tristate "TI DaVinci MDIO Support"
|
|
|
|
depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
|
|
|
|
select PHYLIB
|
|
|
|
help
|
|
|
|
This driver supports TI's DaVinci MDIO module.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called davinci_mdio. This is recommended.
|
|
|
|
|
2010-09-15 08:11:28 -06:00
|
|
|
config TI_DAVINCI_CPDMA
|
|
|
|
tristate "TI DaVinci CPDMA Support"
|
|
|
|
depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
|
|
|
|
help
|
|
|
|
This driver supports TI's DaVinci CPDMA dma engine.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called davinci_cpdma. This is recommended.
|
|
|
|
|
2005-05-05 16:14:15 -06:00
|
|
|
config DM9000
|
|
|
|
tristate "DM9000 support"
|
2007-07-11 22:11:48 -06:00
|
|
|
depends on ARM || BLACKFIN || MIPS
|
2005-05-05 16:14:15 -06:00
|
|
|
select CRC32
|
|
|
|
select MII
|
|
|
|
---help---
|
|
|
|
Support for DM9000 chipset.
|
|
|
|
|
2007-11-12 22:03:58 -07:00
|
|
|
To compile this driver as a module, choose M here. The module
|
|
|
|
will be called dm9000.
|
2005-05-05 16:14:15 -06:00
|
|
|
|
2008-06-24 15:16:06 -06:00
|
|
|
config DM9000_DEBUGLEVEL
|
|
|
|
int "DM9000 maximum debug level"
|
|
|
|
depends on DM9000
|
|
|
|
default 4
|
|
|
|
help
|
|
|
|
The maximum level of debugging code compiled into the DM9000
|
|
|
|
driver.
|
|
|
|
|
2008-06-24 15:16:04 -06:00
|
|
|
config DM9000_FORCE_SIMPLE_PHY_POLL
|
|
|
|
bool "Force simple NSR based PHY polling"
|
|
|
|
depends on DM9000
|
|
|
|
---help---
|
|
|
|
This configuration forces the DM9000 to use the NSR's LinkStatus
|
|
|
|
bit to determine if the link is up or down instead of the more
|
|
|
|
costly MII PHY reads. Note, this will not work if the chip is
|
|
|
|
operating with an external PHY.
|
|
|
|
|
2008-01-14 03:00:28 -07:00
|
|
|
config ENC28J60
|
|
|
|
tristate "ENC28J60 support"
|
|
|
|
depends on EXPERIMENTAL && SPI && NET_ETHERNET
|
|
|
|
select CRC32
|
|
|
|
---help---
|
|
|
|
Support for the Microchip EN28J60 ethernet chip.
|
|
|
|
|
2008-02-05 04:13:58 -07:00
|
|
|
To compile this driver as a module, choose M here. The module will be
|
2008-01-14 03:00:28 -07:00
|
|
|
called enc28j60.
|
|
|
|
|
|
|
|
config ENC28J60_WRITEVERIFY
|
|
|
|
bool "Enable write verify"
|
|
|
|
depends on ENC28J60
|
|
|
|
---help---
|
|
|
|
Enable the verify after the buffer write useful for debugging purpose.
|
|
|
|
If unsure, say N.
|
|
|
|
|
2009-03-27 01:12:24 -06:00
|
|
|
config ETHOC
|
|
|
|
tristate "OpenCores 10/100 Mbps Ethernet MAC support"
|
2009-11-20 02:19:10 -07:00
|
|
|
depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
|
2009-03-27 01:12:24 -06:00
|
|
|
select MII
|
|
|
|
select PHYLIB
|
2009-04-08 16:41:25 -06:00
|
|
|
select CRC32
|
|
|
|
select BITREVERSE
|
2009-03-27 01:12:24 -06:00
|
|
|
help
|
|
|
|
Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
|
|
|
|
|
2010-02-14 20:33:44 -07:00
|
|
|
config GRETH
|
|
|
|
tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
|
2010-02-19 00:32:26 -07:00
|
|
|
depends on SPARC
|
2010-02-14 20:33:44 -07:00
|
|
|
select PHYLIB
|
|
|
|
select CRC32
|
|
|
|
help
|
|
|
|
Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
|
|
|
|
|
2009-03-12 00:26:02 -06:00
|
|
|
config DNET
|
|
|
|
tristate "Dave ethernet support (DNET)"
|
2009-03-21 17:58:47 -06:00
|
|
|
depends on NET_ETHERNET && HAS_IOMEM
|
2009-03-12 00:26:02 -06:00
|
|
|
select PHYLIB
|
|
|
|
help
|
|
|
|
The Dave ethernet interface (DNET) is found on Qong Board FPGA.
|
|
|
|
Say Y to include support for the DNET chip.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called dnet.
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config HP100
|
|
|
|
tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
|
2007-06-13 13:48:53 -06:00
|
|
|
depends on ISA || EISA || PCI
|
2005-04-16 16:20:36 -06:00
|
|
|
help
|
|
|
|
If you have a network (Ethernet) card of this type, say Y and read
|
|
|
|
the Ethernet-HOWTO, available from
|
|
|
|
<http://www.tldp.org/docs.html#howto>.
|
|
|
|
|
2007-11-12 22:03:58 -07:00
|
|
|
To compile this driver as a module, choose M here. The module
|
2005-04-16 16:20:36 -06:00
|
|
|
will be called hp100.
|
|
|
|
|
|
|
|
config NET_PCI
|
|
|
|
bool "EISA, VLB, PCI and on board controllers"
|
2007-06-13 13:48:53 -06:00
|
|
|
depends on ISA || EISA || PCI
|
2005-04-16 16:20:36 -06:00
|
|
|
help
|
|
|
|
This is another class of network cards which attach directly to the
|
|
|
|
bus. If you have one of those, say Y and read the Ethernet-HOWTO,
|
|
|
|
available from <http://www.tldp.org/docs.html#howto>.
|
|
|
|
|
|
|
|
Note that the answer to this question doesn't directly affect the
|
|
|
|
kernel: saying N will just cause the configurator to skip all
|
|
|
|
the questions about this class of network cards. If you say Y, you
|
|
|
|
will be asked for your specific card in the following questions. If
|
|
|
|
you are unsure, say Y.
|
|
|
|
|
|
|
|
config ADAPTEC_STARFIRE
|
|
|
|
tristate "Adaptec Starfire/DuraLAN support"
|
|
|
|
depends on NET_PCI && PCI
|
|
|
|
select CRC32
|
|
|
|
select MII
|
|
|
|
help
|
|
|
|
Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
|
|
|
|
adapter. The DuraLAN chip is used on the 64 bit PCI boards from
|
|
|
|
Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
|
|
|
|
driver.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called starfire. This is recommended.
|
|
|
|
|
2010-02-08 04:38:28 -07:00
|
|
|
config KSZ884X_PCI
|
|
|
|
tristate "Micrel KSZ8841/2 PCI"
|
|
|
|
depends on NET_PCI && PCI
|
|
|
|
select MII
|
|
|
|
select CRC32
|
|
|
|
help
|
|
|
|
This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
|
|
will be called ksz884x.
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config FORCEDETH
|
2006-03-08 01:06:30 -07:00
|
|
|
tristate "nForce Ethernet support"
|
|
|
|
depends on NET_PCI && PCI
|
2005-04-16 16:20:36 -06:00
|
|
|
help
|
|
|
|
If you have a network (Ethernet) controller of this type, say Y and
|
|
|
|
read the Ethernet-HOWTO, available from
|
|
|
|
<http://www.tldp.org/docs.html#howto>.
|
|
|
|
|
2007-11-12 22:03:58 -07:00
|
|
|
To compile this driver as a module, choose M here. The module
|
|
|
|
will be called forcedeth.
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
config TC35815
|
|
|
|
tristate "TOSHIBA TC35815 Ethernet support"
|
2007-03-03 07:54:59 -07:00
|
|
|
depends on NET_PCI && PCI && MIPS
|
2008-04-11 09:47:46 -06:00
|
|
|
select PHYLIB
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
config FEALNX
|
|
|
|
tristate "Myson MTD-8xx PCI Ethernet support"
|
|
|
|
depends on NET_PCI && PCI
|
|
|
|
select CRC32
|
|
|
|
select MII
|
|
|
|
help
|
2010-10-18 03:03:14 -06:00
|
|
|
Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
|
|
|
|
cards. <http://www.myson.com.tw/>
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2007-11-12 22:31:11 -07:00
|
|
|
config R6040
|
2009-01-08 08:04:50 -07:00
|
|
|
tristate "RDC R6040 Fast Ethernet Adapter support"
|
2007-11-12 22:31:11 -07:00
|
|
|
depends on NET_PCI && PCI
|
|
|
|
select CRC32
|
|
|
|
select MII
|
2010-05-31 03:18:57 -06:00
|
|
|
select PHYLIB
|
2007-11-12 22:31:11 -07:00
|
|
|
help
|
|
|
|
This is a driver for the R6040 Fast Ethernet MACs found in the
|
|
|
|
the RDC R-321x System-on-chips.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called r6040. This is recommended.
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config SIS900
|
|
|
|
tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
|
|
|
|
depends on NET_PCI && PCI
|
|
|
|
select CRC32
|
2005-04-30 05:52:49 -06:00
|
|
|
select MII
|
2005-04-16 16:20:36 -06:00
|
|
|
---help---
|
|
|
|
This is a driver for the Fast Ethernet PCI network cards based on
|
|
|
|
the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
|
2006-03-04 09:07:57 -07:00
|
|
|
SiS 630 and SiS 540 chipsets.
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
This driver also supports AMD 79C901 HomePNA so that you can use
|
|
|
|
your phone line as a network cable.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called sis900. This is recommended.
|
|
|
|
|
|
|
|
config TLAN
|
|
|
|
tristate "TI ThunderLAN support"
|
2008-05-30 10:49:55 -06:00
|
|
|
depends on NET_PCI && (PCI || EISA)
|
2005-04-16 16:20:36 -06:00
|
|
|
---help---
|
|
|
|
If you have a PCI Ethernet network card based on the ThunderLAN chip
|
|
|
|
which is supported by this driver, say Y and read the
|
|
|
|
Ethernet-HOWTO, available from
|
|
|
|
<http://www.tldp.org/docs.html#howto>.
|
|
|
|
|
|
|
|
Devices currently supported by this driver are Compaq Netelligent,
|
|
|
|
Compaq NetFlex and Olicom cards. Please read the file
|
|
|
|
<file:Documentation/networking/tlan.txt> for more details.
|
|
|
|
|
2007-11-12 22:03:58 -07:00
|
|
|
To compile this driver as a module, choose M here. The module
|
2005-04-16 16:20:36 -06:00
|
|
|
will be called tlan.
|
|
|
|
|
|
|
|
Please email feedback to <torben.mathiasen@compaq.com>.
|
|
|
|
|
2009-06-03 21:35:55 -06:00
|
|
|
config KS8842
|
2010-07-13 11:09:19 -06:00
|
|
|
tristate "Micrel KSZ8841/42 with generic bus interface"
|
2010-07-29 01:14:27 -06:00
|
|
|
depends on HAS_IOMEM && DMA_ENGINE
|
2009-06-03 21:35:55 -06:00
|
|
|
help
|
2010-11-11 05:31:21 -07:00
|
|
|
This platform driver is for KSZ8841(1-port) / KS8842(2-port)
|
|
|
|
ethernet switch chip (managed, VLAN, QoS) from Micrel or
|
|
|
|
Timberdale(FPGA).
|
2009-06-03 21:35:55 -06:00
|
|
|
|
2009-07-15 23:24:08 -06:00
|
|
|
config KS8851
|
2010-11-11 05:31:21 -07:00
|
|
|
tristate "Micrel KS8851 SPI"
|
|
|
|
depends on SPI
|
|
|
|
select MII
|
2009-08-19 13:13:31 -06:00
|
|
|
select CRC32
|
2010-11-11 05:31:21 -07:00
|
|
|
help
|
|
|
|
SPI driver for Micrel KS8851 SPI attached network chip.
|
2009-07-15 23:24:08 -06:00
|
|
|
|
2009-09-25 08:42:12 -06:00
|
|
|
config KS8851_MLL
|
|
|
|
tristate "Micrel KS8851 MLL"
|
|
|
|
depends on HAS_IOMEM
|
2009-10-14 16:10:58 -06:00
|
|
|
select MII
|
2009-09-25 08:42:12 -06:00
|
|
|
help
|
|
|
|
This platform driver is for Micrel KS8851 Address/data bus
|
|
|
|
multiplexed network chip.
|
|
|
|
|
2007-10-14 10:10:13 -06:00
|
|
|
config CPMAC
|
|
|
|
tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
|
2009-08-04 05:17:49 -06:00
|
|
|
depends on NET_ETHERNET && EXPERIMENTAL && AR7
|
2007-10-14 10:10:13 -06:00
|
|
|
select PHYLIB
|
|
|
|
help
|
|
|
|
TI AR7 CPMAC Ethernet support
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config NET_POCKET
|
|
|
|
bool "Pocket and portable adapters"
|
2007-06-13 13:48:53 -06:00
|
|
|
depends on PARPORT
|
2005-04-16 16:20:36 -06:00
|
|
|
---help---
|
|
|
|
Cute little network (Ethernet) devices which attach to the parallel
|
|
|
|
port ("pocket adapters"), commonly used with laptops. If you have
|
|
|
|
one of those, say Y and read the Ethernet-HOWTO, available from
|
|
|
|
<http://www.tldp.org/docs.html#howto>.
|
|
|
|
|
|
|
|
If you want to plug a network (or some other) card into the PCMCIA
|
|
|
|
(or PC-card) slot of your laptop instead (PCMCIA is the standard for
|
|
|
|
credit card size extension cards used by all modern laptops), you
|
|
|
|
need the pcmcia-cs package (location contained in the file
|
|
|
|
<file:Documentation/Changes>) and you can say N here.
|
|
|
|
|
|
|
|
Laptop users should read the Linux Laptop home page at
|
|
|
|
<http://www.linux-on-laptops.com/> or
|
|
|
|
Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
|
|
|
|
|
|
|
|
Note that the answer to this question doesn't directly affect the
|
|
|
|
kernel: saying N will just cause the configurator to skip all
|
|
|
|
the questions about this class of network devices. If you say Y, you
|
|
|
|
will be asked for your specific device in the following questions.
|
|
|
|
|
|
|
|
config FEC
|
2009-05-26 21:41:39 -06:00
|
|
|
bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
|
2010-02-05 01:56:22 -07:00
|
|
|
depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
|
2011-01-17 01:52:18 -07:00
|
|
|
IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC
|
|
|
|
default IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC if ARM
|
2010-03-30 20:10:44 -06:00
|
|
|
select PHYLIB
|
2005-04-16 16:20:36 -06:00
|
|
|
help
|
|
|
|
Say Y here if you want to use the built-in 10/100 Fast ethernet
|
2009-01-28 16:03:10 -07:00
|
|
|
controller on some Motorola ColdFire and Freescale i.MX processors.
|
2005-09-11 19:18:10 -06:00
|
|
|
|
2007-10-26 10:07:49 -06:00
|
|
|
config FEC_MPC52xx
|
|
|
|
tristate "MPC52xx FEC driver"
|
2008-11-14 05:19:00 -07:00
|
|
|
depends on PPC_MPC52xx && PPC_BESTCOMM
|
2007-10-26 10:07:49 -06:00
|
|
|
select CRC32
|
|
|
|
select PHYLIB
|
2008-11-14 05:19:00 -07:00
|
|
|
select PPC_BESTCOMM_FEC
|
2007-10-26 10:07:49 -06:00
|
|
|
---help---
|
|
|
|
This option enables support for the MPC5200's on-chip
|
|
|
|
Fast Ethernet Controller
|
2009-06-04 16:44:53 -06:00
|
|
|
If compiled as module, it will be called fec_mpc52xx.
|
2007-10-26 10:07:49 -06:00
|
|
|
|
|
|
|
config FEC_MPC52xx_MDIO
|
|
|
|
bool "MPC52xx FEC MDIO bus driver"
|
|
|
|
depends on FEC_MPC52xx
|
|
|
|
default y
|
|
|
|
---help---
|
|
|
|
The MPC5200's FEC can connect to the Ethernet either with
|
|
|
|
an external MII PHY chip or 10 Mbps 7-wire interface
|
|
|
|
(Motorola? industry standard).
|
|
|
|
If your board uses an external PHY connected to FEC, enable this.
|
|
|
|
If not sure, enable.
|
2009-06-04 16:44:53 -06:00
|
|
|
If compiled as module, it will be called fec_mpc52xx_phy.
|
2007-10-26 10:07:49 -06:00
|
|
|
|
2009-08-20 03:52:16 -06:00
|
|
|
config XILINX_EMACLITE
|
|
|
|
tristate "Xilinx 10/100 Ethernet Lite support"
|
|
|
|
depends on PPC32 || MICROBLAZE
|
2010-02-15 22:51:00 -07:00
|
|
|
select PHYLIB
|
2009-08-20 03:52:16 -06:00
|
|
|
help
|
|
|
|
This driver supports the 10/100 Ethernet Lite from Xilinx.
|
|
|
|
|
2011-05-05 16:10:01 -06:00
|
|
|
config LANTIQ_ETOP
|
|
|
|
tristate "Lantiq SoC ETOP driver"
|
|
|
|
depends on SOC_TYPE_XWAY
|
|
|
|
help
|
|
|
|
Support for the MII0 inside the Lantiq SoC
|
|
|
|
|
|
|
|
|
2005-10-28 14:25:58 -06:00
|
|
|
source "drivers/net/fs_enet/Kconfig"
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2009-10-14 13:04:41 -06:00
|
|
|
source "drivers/net/octeon/Kconfig"
|
|
|
|
|
2007-06-13 13:48:53 -06:00
|
|
|
endif # NET_ETHERNET
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
#
|
|
|
|
# Gigabit Ethernet
|
|
|
|
#
|
|
|
|
|
2007-05-10 23:52:56 -06:00
|
|
|
menuconfig NETDEV_1000
|
|
|
|
bool "Ethernet (1000 Mbit)"
|
2005-07-27 14:04:35 -06:00
|
|
|
depends on !UML
|
2007-05-10 23:52:56 -06:00
|
|
|
default y
|
2007-08-18 04:56:21 -06:00
|
|
|
---help---
|
|
|
|
Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
|
|
|
|
type of Local Area Network (LAN) in universities and companies.
|
|
|
|
|
|
|
|
Say Y here to get to see options for Gigabit Ethernet drivers.
|
|
|
|
This option alone does not add any kernel code.
|
|
|
|
Note that drivers supporting both 100 and 1000 MBit may be listed
|
|
|
|
under "Ethernet (10 or 100MBit)" instead.
|
|
|
|
|
|
|
|
If you say N, all options in this submenu will be skipped and disabled.
|
2007-05-10 23:52:56 -06:00
|
|
|
|
|
|
|
if NETDEV_1000
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2008-01-01 10:27:58 -07:00
|
|
|
config IP1000
|
|
|
|
tristate "IP1000 Gigabit Ethernet support"
|
|
|
|
depends on PCI && EXPERIMENTAL
|
|
|
|
select MII
|
|
|
|
---help---
|
|
|
|
This driver supports IP1000 gigabit Ethernet cards.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called ipg. This is recommended.
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config HAMACHI
|
|
|
|
tristate "Packet Engines Hamachi GNIC-II support"
|
|
|
|
depends on PCI
|
|
|
|
select MII
|
|
|
|
help
|
|
|
|
If you have a Gigabit Ethernet card of this type, say Y and read
|
|
|
|
the Ethernet-HOWTO, available from
|
|
|
|
<http://www.tldp.org/docs.html#howto>.
|
|
|
|
|
2007-11-12 22:03:58 -07:00
|
|
|
To compile this driver as a module, choose M here. The module will be
|
2005-04-16 16:20:36 -06:00
|
|
|
called hamachi.
|
|
|
|
|
|
|
|
config YELLOWFIN
|
|
|
|
tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
|
|
|
|
depends on PCI && EXPERIMENTAL
|
|
|
|
select CRC32
|
|
|
|
---help---
|
|
|
|
Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
|
|
|
|
adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
|
|
|
|
used by the Beowulf Linux cluster project. See
|
|
|
|
<http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
|
|
|
|
information about this driver in particular and Beowulf in general.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called yellowfin. This is recommended.
|
|
|
|
|
2005-07-30 05:08:43 -06:00
|
|
|
config SIS190
|
2005-09-02 16:57:51 -06:00
|
|
|
tristate "SiS190/SiS191 gigabit ethernet support"
|
2005-08-08 18:41:00 -06:00
|
|
|
depends on PCI
|
|
|
|
select CRC32
|
|
|
|
select MII
|
|
|
|
---help---
|
2005-09-02 16:57:51 -06:00
|
|
|
Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
|
|
|
|
a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
|
|
|
|
appear in lan on motherboard designs which are based on SiS 965
|
|
|
|
and SiS 966 south bridge.
|
2005-08-08 18:41:00 -06:00
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called sis190. This is recommended.
|
2005-07-30 05:08:43 -06:00
|
|
|
|
2005-09-05 16:19:29 -06:00
|
|
|
config SPIDER_NET
|
|
|
|
tristate "Spider Gigabit Ethernet driver"
|
2007-02-20 15:36:14 -07:00
|
|
|
depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
|
2006-03-15 03:30:44 -07:00
|
|
|
select FW_LOADER
|
2011-08-12 00:06:28 -06:00
|
|
|
select SUNGEM_PHY
|
2005-09-05 16:19:29 -06:00
|
|
|
help
|
|
|
|
This driver supports the Gigabit Ethernet chips present on the
|
|
|
|
Cell Processor-Based Blades from IBM.
|
|
|
|
|
2006-11-08 20:49:13 -07:00
|
|
|
config TSI108_ETH
|
2010-11-13 01:43:29 -07:00
|
|
|
tristate "Tundra TSI108 gigabit Ethernet support"
|
|
|
|
depends on TSI108_BRIDGE
|
|
|
|
help
|
|
|
|
This driver supports Tundra TSI108 gigabit Ethernet ports.
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called tsi108_eth.
|
2006-11-08 20:49:13 -07:00
|
|
|
|
2007-07-05 05:11:16 -06:00
|
|
|
config GELIC_NET
|
|
|
|
tristate "PS3 Gigabit Ethernet driver"
|
|
|
|
depends on PPC_PS3
|
2008-04-09 15:01:53 -06:00
|
|
|
select PS3_SYS_MANAGER
|
2007-07-05 05:11:16 -06:00
|
|
|
help
|
|
|
|
This driver supports the network device on the PS3 game
|
|
|
|
console. This driver has built-in support for Ethernet.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
module will be called ps3_gelic.
|
|
|
|
|
2008-02-07 03:58:57 -07:00
|
|
|
config GELIC_WIRELESS
|
2008-03-06 11:08:09 -07:00
|
|
|
bool "PS3 Wireless support"
|
2009-12-18 12:19:32 -07:00
|
|
|
depends on WLAN
|
2008-03-06 11:08:09 -07:00
|
|
|
depends on GELIC_NET
|
|
|
|
select WIRELESS_EXT
|
|
|
|
help
|
|
|
|
This option adds the support for the wireless feature of PS3.
|
|
|
|
If you have the wireless-less model of PS3 or have no plan to
|
|
|
|
use wireless feature, disabling this option saves memory. As
|
|
|
|
the driver automatically distinguishes the models, you can
|
|
|
|
safely enable this option even if you have a wireless-less model.
|
2008-02-07 03:58:57 -07:00
|
|
|
|
2009-02-04 17:42:12 -07:00
|
|
|
config FSL_PQ_MDIO
|
|
|
|
tristate "Freescale PQ MDIO"
|
|
|
|
depends on FSL_SOC
|
|
|
|
select PHYLIB
|
|
|
|
help
|
|
|
|
This driver supports the MDIO bus used by the gianfar and UCC drivers.
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config GIANFAR
|
|
|
|
tristate "Gianfar Ethernet"
|
2008-01-28 09:24:30 -07:00
|
|
|
depends on FSL_SOC
|
2009-02-04 17:42:12 -07:00
|
|
|
select FSL_PQ_MDIO
|
2005-09-23 20:54:21 -06:00
|
|
|
select PHYLIB
|
2007-04-12 11:57:06 -06:00
|
|
|
select CRC32
|
2005-04-16 16:20:36 -06:00
|
|
|
help
|
2006-06-17 16:52:55 -06:00
|
|
|
This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
|
|
|
|
and MPC86xx family of chips, and the FEC on the 8540.
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2006-08-15 00:00:11 -06:00
|
|
|
config UCC_GETH
|
2007-03-12 14:40:27 -06:00
|
|
|
tristate "Freescale QE Gigabit Ethernet"
|
|
|
|
depends on QUICC_ENGINE
|
2009-02-04 17:42:12 -07:00
|
|
|
select FSL_PQ_MDIO
|
2007-06-01 01:46:29 -06:00
|
|
|
select PHYLIB
|
2006-08-15 00:00:11 -06:00
|
|
|
help
|
2007-03-12 14:40:27 -06:00
|
|
|
This driver supports the Gigabit Ethernet mode of the QUICC Engine,
|
|
|
|
which is available on some Freescale SOCs.
|
2006-08-15 00:00:11 -06:00
|
|
|
|
2007-04-13 00:26:19 -06:00
|
|
|
config UGETH_TX_ON_DEMAND
|
|
|
|
bool "Transmit on Demand support"
|
2006-08-15 00:00:11 -06:00
|
|
|
depends on UCC_GETH
|
|
|
|
|
2009-04-25 06:53:39 -06:00
|
|
|
config XILINX_LL_TEMAC
|
|
|
|
tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
|
2010-04-08 01:08:02 -06:00
|
|
|
depends on PPC || MICROBLAZE
|
2009-04-25 06:53:39 -06:00
|
|
|
select PHYLIB
|
|
|
|
help
|
|
|
|
This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
|
|
|
|
core used in Xilinx Spartan and Virtex FPGAs
|
|
|
|
|
2008-09-15 11:00:11 -06:00
|
|
|
config JME
|
|
|
|
tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
|
|
|
|
depends on PCI
|
|
|
|
select CRC32
|
|
|
|
select MII
|
|
|
|
---help---
|
|
|
|
This driver supports the PCI-Express gigabit ethernet adapters
|
|
|
|
based on JMicron JMC250 chipset.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
|
|
will be called jme.
|
|
|
|
|
2009-06-10 13:58:48 -06:00
|
|
|
config S6GMAC
|
|
|
|
tristate "S6105 GMAC ethernet support"
|
|
|
|
depends on XTENSA_VARIANT_S6000
|
|
|
|
select PHYLIB
|
|
|
|
help
|
|
|
|
This driver supports the on chip ethernet device on the
|
|
|
|
S6105 xtensa processor.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
|
|
will be called s6gmac.
|
|
|
|
|
2007-05-10 23:52:56 -06:00
|
|
|
endif # NETDEV_1000
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
#
|
|
|
|
# 10 Gigabit Ethernet
|
|
|
|
#
|
|
|
|
|
2007-05-10 23:52:56 -06:00
|
|
|
menuconfig NETDEV_10000
|
|
|
|
bool "Ethernet (10000 Mbit)"
|
2005-07-27 14:04:35 -06:00
|
|
|
depends on !UML
|
2007-05-10 23:52:56 -06:00
|
|
|
default y
|
2007-08-18 04:56:21 -06:00
|
|
|
---help---
|
|
|
|
Say Y here to get to see options for 10 Gigabit Ethernet drivers.
|
|
|
|
This option alone does not add any kernel code.
|
|
|
|
|
|
|
|
If you say N, all options in this submenu will be skipped and disabled.
|
2007-05-10 23:52:56 -06:00
|
|
|
|
|
|
|
if NETDEV_10000
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2009-04-29 02:04:46 -06:00
|
|
|
config MDIO
|
|
|
|
tristate
|
|
|
|
|
2011-08-12 00:06:28 -06:00
|
|
|
config SUNGEM_PHY
|
|
|
|
tristate
|
|
|
|
|
2007-05-10 23:52:56 -06:00
|
|
|
endif # NETDEV_10000
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
source "drivers/net/tokenring/Kconfig"
|
|
|
|
|
|
|
|
source "drivers/net/wireless/Kconfig"
|
|
|
|
|
2008-12-23 17:18:48 -07:00
|
|
|
source "drivers/net/wimax/Kconfig"
|
|
|
|
|
2007-05-09 19:31:55 -06:00
|
|
|
source "drivers/net/usb/Kconfig"
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
source "drivers/net/pcmcia/Kconfig"
|
|
|
|
|
|
|
|
source "drivers/net/wan/Kconfig"
|
|
|
|
|
|
|
|
source "drivers/atm/Kconfig"
|
|
|
|
|
2009-06-08 06:18:51 -06:00
|
|
|
source "drivers/ieee802154/Kconfig"
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
source "drivers/s390/net/Kconfig"
|
|
|
|
|
2010-03-30 07:56:30 -06:00
|
|
|
source "drivers/net/caif/Kconfig"
|
|
|
|
|
2010-11-01 15:00:37 -06:00
|
|
|
config TILE_NET
|
|
|
|
tristate "Tilera GBE/XGBE network driver support"
|
|
|
|
depends on TILE
|
|
|
|
default y
|
|
|
|
select CRC32
|
|
|
|
help
|
|
|
|
This is a standard Linux network device driver for the
|
|
|
|
on-chip Tilera Gigabit Ethernet and XAUI interfaces.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called tile_net.
|
|
|
|
|
2007-07-17 19:37:06 -06:00
|
|
|
config XEN_NETDEV_FRONTEND
|
|
|
|
tristate "Xen network device frontend driver"
|
|
|
|
depends on XEN
|
2009-03-27 17:28:34 -06:00
|
|
|
select XEN_XENBUS_FRONTEND
|
2007-07-17 19:37:06 -06:00
|
|
|
default y
|
|
|
|
help
|
2011-03-14 18:06:18 -06:00
|
|
|
This driver provides support for Xen paravirtual network
|
|
|
|
devices exported by a Xen network driver domain (often
|
|
|
|
domain 0).
|
|
|
|
|
|
|
|
The corresponding Linux backend driver is enabled by the
|
|
|
|
CONFIG_XEN_NETDEV_BACKEND option.
|
|
|
|
|
|
|
|
If you are compiling a kernel for use as Xen guest, you
|
|
|
|
should say Y here. To compile this driver as a module, chose
|
|
|
|
M here: the module will be called xen-netfront.
|
|
|
|
|
|
|
|
config XEN_NETDEV_BACKEND
|
|
|
|
tristate "Xen backend network device"
|
|
|
|
depends on XEN_BACKEND
|
|
|
|
help
|
|
|
|
This driver allows the kernel to act as a Xen network driver
|
|
|
|
domain which exports paravirtual network devices to other
|
|
|
|
Xen domains. These devices can be accessed by any operating
|
|
|
|
system that implements a compatible front end.
|
|
|
|
|
|
|
|
The corresponding Linux frontend driver is enabled by the
|
|
|
|
CONFIG_XEN_NETDEV_FRONTEND configuration option.
|
|
|
|
|
|
|
|
The backend driver presents a standard network device
|
|
|
|
endpoint for each paravirtual network device to the driver
|
|
|
|
domain network stack. These can then be bridged or routed
|
|
|
|
etc in order to provide full network connectivity.
|
|
|
|
|
|
|
|
If you are compiling a kernel to run in a Xen network driver
|
|
|
|
domain (often this is domain 0) you should say Y here. To
|
|
|
|
compile this driver as a module, chose M here: the module
|
|
|
|
will be called xen-netback.
|
2007-07-17 19:37:06 -06:00
|
|
|
|
2005-09-09 13:10:10 -06:00
|
|
|
config RIONET
|
|
|
|
tristate "RapidIO Ethernet over messaging driver support"
|
2006-11-01 22:18:58 -07:00
|
|
|
depends on RAPIDIO
|
2005-09-09 13:10:10 -06:00
|
|
|
|
|
|
|
config RIONET_TX_SIZE
|
|
|
|
int "Number of outbound queue entries"
|
|
|
|
depends on RIONET
|
|
|
|
default "128"
|
|
|
|
|
|
|
|
config RIONET_RX_SIZE
|
|
|
|
int "Number of inbound queue entries"
|
|
|
|
depends on RIONET
|
|
|
|
default "128"
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config FDDI
|
2008-12-27 21:43:48 -07:00
|
|
|
tristate "FDDI driver support"
|
2007-02-05 17:28:27 -07:00
|
|
|
depends on (PCI || EISA || TC)
|
2005-04-16 16:20:36 -06:00
|
|
|
help
|
|
|
|
Fiber Distributed Data Interface is a high speed local area network
|
|
|
|
design; essentially a replacement for high speed Ethernet. FDDI can
|
|
|
|
run over copper or fiber. If you are connected to such a network and
|
|
|
|
want a driver for the FDDI card in your computer, say Y here (and
|
|
|
|
then also Y to the driver for your FDDI card, below). Most people
|
|
|
|
will say N.
|
|
|
|
|
|
|
|
config DEFXX
|
2007-02-05 17:28:27 -07:00
|
|
|
tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
|
|
|
|
depends on FDDI && (PCI || EISA || TC)
|
|
|
|
---help---
|
|
|
|
This is support for the DIGITAL series of TURBOchannel (DEFTA),
|
|
|
|
EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
|
|
|
|
to a local FDDI network.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called defxx. If unsure, say N.
|
|
|
|
|
|
|
|
config DEFXX_MMIO
|
|
|
|
bool
|
|
|
|
prompt "Use MMIO instead of PIO" if PCI || EISA
|
|
|
|
depends on DEFXX
|
|
|
|
default n if PCI || EISA
|
|
|
|
default y
|
|
|
|
---help---
|
|
|
|
This instructs the driver to use EISA or PCI memory-mapped I/O
|
|
|
|
(MMIO) as appropriate instead of programmed I/O ports (PIO).
|
|
|
|
Enabling this gives an improvement in processing time in parts
|
|
|
|
of the driver, but it may cause problems with EISA (DEFEA)
|
|
|
|
adapters. TURBOchannel does not have the concept of I/O ports,
|
|
|
|
so MMIO is always used for these (DEFTA) adapters.
|
|
|
|
|
|
|
|
If unsure, say N.
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
config SKFP
|
|
|
|
tristate "SysKonnect FDDI PCI support"
|
|
|
|
depends on FDDI && PCI
|
2006-12-19 14:09:08 -07:00
|
|
|
select BITREVERSE
|
2005-04-16 16:20:36 -06:00
|
|
|
---help---
|
|
|
|
Say Y here if you have a SysKonnect FDDI PCI adapter.
|
|
|
|
The following adapters are supported by this driver:
|
|
|
|
- SK-5521 (SK-NET FDDI-UP)
|
|
|
|
- SK-5522 (SK-NET FDDI-UP DAS)
|
|
|
|
- SK-5541 (SK-NET FDDI-FP)
|
|
|
|
- SK-5543 (SK-NET FDDI-LP)
|
|
|
|
- SK-5544 (SK-NET FDDI-LP DAS)
|
|
|
|
- SK-5821 (SK-NET FDDI-UP64)
|
|
|
|
- SK-5822 (SK-NET FDDI-UP64 DAS)
|
|
|
|
- SK-5841 (SK-NET FDDI-FP64)
|
|
|
|
- SK-5843 (SK-NET FDDI-LP64)
|
|
|
|
- SK-5844 (SK-NET FDDI-LP64 DAS)
|
|
|
|
- Netelligent 100 FDDI DAS Fibre SC
|
|
|
|
- Netelligent 100 FDDI SAS Fibre SC
|
|
|
|
- Netelligent 100 FDDI DAS UTP
|
|
|
|
- Netelligent 100 FDDI SAS UTP
|
|
|
|
- Netelligent 100 FDDI SAS Fibre MIC
|
|
|
|
|
|
|
|
Read <file:Documentation/networking/skfp.txt> for information about
|
|
|
|
the driver.
|
|
|
|
|
|
|
|
Questions concerning this driver can be addressed to:
|
|
|
|
<linux@syskonnect.de>
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called skfp. This is recommended.
|
|
|
|
|
|
|
|
config HIPPI
|
|
|
|
bool "HIPPI driver support (EXPERIMENTAL)"
|
2005-07-27 14:04:35 -06:00
|
|
|
depends on EXPERIMENTAL && INET && PCI
|
2005-04-16 16:20:36 -06:00
|
|
|
help
|
|
|
|
HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
|
|
|
|
1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
|
|
|
|
can run over copper (25m) or fiber (300m on multi-mode or 10km on
|
|
|
|
single-mode). HIPPI networks are commonly used for clusters and to
|
|
|
|
connect to super computers. If you are connected to a HIPPI network
|
|
|
|
and have a HIPPI network card in your computer that you want to use
|
|
|
|
under Linux, say Y here (you must also remember to enable the driver
|
|
|
|
for your HIPPI card below). Most people will say N here.
|
|
|
|
|
|
|
|
config ROADRUNNER
|
|
|
|
tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
|
|
|
|
depends on HIPPI && PCI
|
|
|
|
help
|
|
|
|
Say Y here if this is your PCI HIPPI network card.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
will be called rrunner. If unsure, say N.
|
|
|
|
|
|
|
|
config ROADRUNNER_LARGE_RINGS
|
|
|
|
bool "Use large TX/RX rings (EXPERIMENTAL)"
|
|
|
|
depends on ROADRUNNER
|
|
|
|
help
|
|
|
|
If you say Y here, the RoadRunner driver will preallocate up to 2 MB
|
|
|
|
of additional memory to allow for fastest operation, both for
|
|
|
|
transmitting and receiving. This memory cannot be used by any other
|
|
|
|
kernel code or by user space programs. Say Y here only if you have
|
|
|
|
the memory.
|
|
|
|
|
|
|
|
config PLIP
|
|
|
|
tristate "PLIP (parallel port) support"
|
2005-07-27 14:04:35 -06:00
|
|
|
depends on PARPORT
|
2005-04-16 16:20:36 -06:00
|
|
|
---help---
|
|
|
|
PLIP (Parallel Line Internet Protocol) is used to create a
|
|
|
|
reasonably fast mini network consisting of two (or, rarely, more)
|
|
|
|
local machines. A PLIP link from a Linux box is a popular means to
|
|
|
|
install a Linux distribution on a machine which doesn't have a
|
|
|
|
CD-ROM drive (a minimal system has to be transferred with floppies
|
|
|
|
first). The kernels on both machines need to have this PLIP option
|
|
|
|
enabled for this to work.
|
|
|
|
|
|
|
|
The PLIP driver has two modes, mode 0 and mode 1. The parallel
|
|
|
|
ports (the connectors at the computers with 25 holes) are connected
|
|
|
|
with "null printer" or "Turbo Laplink" cables which can transmit 4
|
|
|
|
bits at a time (mode 0) or with special PLIP cables, to be used on
|
|
|
|
bidirectional parallel ports only, which can transmit 8 bits at a
|
|
|
|
time (mode 1); you can find the wiring of these cables in
|
|
|
|
<file:Documentation/networking/PLIP.txt>. The cables can be up to
|
|
|
|
15m long. Mode 0 works also if one of the machines runs DOS/Windows
|
|
|
|
and has some PLIP software installed, e.g. the Crynwr PLIP packet
|
|
|
|
driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
|
|
|
|
and winsock or NCSA's telnet.
|
|
|
|
|
|
|
|
If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
|
|
|
|
as the NET-3-HOWTO, both available from
|
|
|
|
<http://www.tldp.org/docs.html#howto>. Note that the PLIP
|
|
|
|
protocol has been changed and this PLIP driver won't work together
|
|
|
|
with the PLIP support in Linux versions 1.0.x. This option enlarges
|
|
|
|
your kernel by about 8 KB.
|
|
|
|
|
2007-11-12 22:03:58 -07:00
|
|
|
To compile this driver as a module, choose M here. The module
|
|
|
|
will be called plip. If unsure, say Y or M, in case you buy
|
|
|
|
a laptop later.
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
config PPP
|
|
|
|
tristate "PPP (point-to-point protocol) support"
|
2006-07-14 05:15:40 -06:00
|
|
|
select SLHC
|
2005-04-16 16:20:36 -06:00
|
|
|
---help---
|
|
|
|
PPP (Point to Point Protocol) is a newer and better SLIP. It serves
|
|
|
|
the same purpose: sending Internet traffic over telephone (and other
|
|
|
|
serial) lines. Ask your access provider if they support it, because
|
|
|
|
otherwise you can't use it; most Internet access providers these
|
|
|
|
days support PPP rather than SLIP.
|
|
|
|
|
|
|
|
To use PPP, you need an additional program called pppd as described
|
|
|
|
in the PPP-HOWTO, available at
|
|
|
|
<http://www.tldp.org/docs.html#howto>. Make sure that you have
|
|
|
|
the version of pppd recommended in <file:Documentation/Changes>.
|
|
|
|
The PPP option enlarges your kernel by about 16 KB.
|
|
|
|
|
|
|
|
There are actually two versions of PPP: the traditional PPP for
|
|
|
|
asynchronous lines, such as regular analog phone lines, and
|
|
|
|
synchronous PPP which can be used over digital ISDN lines for
|
|
|
|
example. If you want to use PPP over phone lines or other
|
|
|
|
asynchronous serial lines, you need to say Y (or M) here and also to
|
|
|
|
the next option, "PPP support for async serial ports". For PPP over
|
|
|
|
synchronous lines, you should say Y (or M) here and to "Support
|
|
|
|
synchronous PPP", below.
|
|
|
|
|
|
|
|
If you said Y to "Version information on all symbols" above, then
|
|
|
|
you cannot compile the PPP driver into the kernel; you can then only
|
|
|
|
compile it as a module. To compile this driver as a module, choose M
|
2007-11-12 22:03:58 -07:00
|
|
|
here. The module will be called ppp_generic.
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
config PPP_MULTILINK
|
|
|
|
bool "PPP multilink support (EXPERIMENTAL)"
|
|
|
|
depends on PPP && EXPERIMENTAL
|
|
|
|
help
|
|
|
|
PPP multilink is a protocol (defined in RFC 1990) which allows you
|
|
|
|
to combine several (logical or physical) lines into one logical PPP
|
|
|
|
connection, so that you can utilize your full bandwidth.
|
|
|
|
|
|
|
|
This has to be supported at the other end as well and you need a
|
|
|
|
version of the pppd daemon which understands the multilink protocol.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
config PPP_FILTER
|
|
|
|
bool "PPP filtering"
|
|
|
|
depends on PPP
|
|
|
|
help
|
|
|
|
Say Y here if you want to be able to filter the packets passing over
|
|
|
|
PPP interfaces. This allows you to control which packets count as
|
|
|
|
activity (i.e. which packets will reset the idle timer or bring up
|
2006-02-12 10:53:04 -07:00
|
|
|
a demand-dialed link) and which packets are to be dropped entirely.
|
2005-04-16 16:20:36 -06:00
|
|
|
You need to say Y here if you wish to use the pass-filter and
|
|
|
|
active-filter options to pppd.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
config PPP_ASYNC
|
|
|
|
tristate "PPP support for async serial ports"
|
|
|
|
depends on PPP
|
|
|
|
select CRC_CCITT
|
|
|
|
---help---
|
|
|
|
Say Y (or M) here if you want to be able to use PPP over standard
|
|
|
|
asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
|
|
|
|
a modem (not a synchronous or ISDN modem) to contact your ISP, you
|
|
|
|
need this option.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here.
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
|
|
config PPP_SYNC_TTY
|
|
|
|
tristate "PPP support for sync tty ports"
|
|
|
|
depends on PPP
|
|
|
|
help
|
|
|
|
Say Y (or M) here if you want to be able to use PPP over synchronous
|
|
|
|
(HDLC) tty devices, such as the SyncLink adapter. These devices
|
|
|
|
are often used for high-speed leased lines like T1/E1.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here.
|
|
|
|
|
|
|
|
config PPP_DEFLATE
|
|
|
|
tristate "PPP Deflate compression"
|
|
|
|
depends on PPP
|
|
|
|
select ZLIB_INFLATE
|
|
|
|
select ZLIB_DEFLATE
|
|
|
|
---help---
|
|
|
|
Support for the Deflate compression method for PPP, which uses the
|
|
|
|
Deflate algorithm (the same algorithm that gzip uses) to compress
|
|
|
|
each PPP packet before it is sent over the wire. The machine at the
|
|
|
|
other end of the PPP link (usually your ISP) has to support the
|
|
|
|
Deflate compression method as well for this to be useful. Even if
|
|
|
|
they don't support it, it is safe to say Y here.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here.
|
|
|
|
|
|
|
|
config PPP_BSDCOMP
|
|
|
|
tristate "PPP BSD-Compress compression"
|
|
|
|
depends on PPP
|
|
|
|
---help---
|
|
|
|
Support for the BSD-Compress compression method for PPP, which uses
|
|
|
|
the LZW compression method to compress each PPP packet before it is
|
|
|
|
sent over the wire. The machine at the other end of the PPP link
|
|
|
|
(usually your ISP) has to support the BSD-Compress compression
|
|
|
|
method as well for this to be useful. Even if they don't support it,
|
|
|
|
it is safe to say Y here.
|
|
|
|
|
|
|
|
The PPP Deflate compression method ("PPP Deflate compression",
|
|
|
|
above) is preferable to BSD-Compress, because it compresses better
|
|
|
|
and is patent-free.
|
|
|
|
|
|
|
|
Note that the BSD compression code will always be compiled as a
|
|
|
|
module; it is called bsd_comp and will show up in the directory
|
|
|
|
modules once you have said "make modules". If unsure, say N.
|
|
|
|
|
2005-11-08 10:40:47 -07:00
|
|
|
config PPP_MPPE
|
2010-11-11 05:31:21 -07:00
|
|
|
tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
|
|
|
|
depends on PPP && EXPERIMENTAL
|
|
|
|
select CRYPTO
|
|
|
|
select CRYPTO_SHA1
|
|
|
|
select CRYPTO_ARC4
|
|
|
|
select CRYPTO_ECB
|
|
|
|
---help---
|
|
|
|
Support for the MPPE Encryption protocol, as employed by the
|
|
|
|
Microsoft Point-to-Point Tunneling Protocol.
|
|
|
|
|
|
|
|
See http://pptpclient.sourceforge.net/ for information on
|
|
|
|
configuring PPTP clients and servers to utilize this method.
|
2005-11-08 10:40:47 -07:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config PPPOE
|
|
|
|
tristate "PPP over Ethernet (EXPERIMENTAL)"
|
|
|
|
depends on EXPERIMENTAL && PPP
|
|
|
|
help
|
|
|
|
Support for PPP over Ethernet.
|
|
|
|
|
|
|
|
This driver requires the latest version of pppd from the CVS
|
|
|
|
repository at cvs.samba.org. Alternatively, see the
|
|
|
|
RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
|
|
|
|
which contains instruction on how to use this driver (under
|
|
|
|
the heading "Kernel mode PPPoE").
|
|
|
|
|
2010-08-22 00:05:39 -06:00
|
|
|
config PPTP
|
|
|
|
tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
|
|
|
|
depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
|
|
|
|
help
|
|
|
|
Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
|
|
|
|
|
|
|
|
This driver requires pppd plugin to work in client mode or
|
|
|
|
modified pptpd (poptop) to work in server mode.
|
|
|
|
See http://accel-pptp.sourceforge.net/ for information how to
|
|
|
|
utilize this module.
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config PPPOATM
|
|
|
|
tristate "PPP over ATM"
|
|
|
|
depends on ATM && PPP
|
|
|
|
help
|
|
|
|
Support PPP (Point to Point Protocol) encapsulated in ATM frames.
|
|
|
|
This implementation does not yet comply with section 8 of RFC2364,
|
|
|
|
which can lead to bad results if the ATM peer loses state and
|
|
|
|
changes its encapsulation unilaterally.
|
|
|
|
|
2007-06-27 16:49:24 -06:00
|
|
|
config PPPOL2TP
|
|
|
|
tristate "PPP over L2TP (EXPERIMENTAL)"
|
2010-04-02 00:18:33 -06:00
|
|
|
depends on EXPERIMENTAL && L2TP && PPP
|
2007-06-27 16:49:24 -06:00
|
|
|
help
|
|
|
|
Support for PPP-over-L2TP socket family. L2TP is a protocol
|
|
|
|
used by ISPs and enterprises to tunnel PPP traffic over UDP
|
|
|
|
tunnels. L2TP is replacing PPTP for VPN uses.
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config SLIP
|
|
|
|
tristate "SLIP (serial line) support"
|
|
|
|
---help---
|
|
|
|
Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
|
|
|
|
connect to your Internet service provider or to connect to some
|
|
|
|
other local Unix box or if you want to configure your Linux box as a
|
|
|
|
Slip/CSlip server for other people to dial in. SLIP (Serial Line
|
|
|
|
Internet Protocol) is a protocol used to send Internet traffic over
|
|
|
|
serial connections such as telephone lines or null modem cables;
|
|
|
|
nowadays, the protocol PPP is more commonly used for this same
|
|
|
|
purpose.
|
|
|
|
|
|
|
|
Normally, your access provider has to support SLIP in order for you
|
|
|
|
to be able to use it, but there is now a SLIP emulator called SLiRP
|
|
|
|
around (available from
|
|
|
|
<ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
|
|
|
|
allows you to use SLIP over a regular dial up shell connection. If
|
|
|
|
you plan to use SLiRP, make sure to say Y to CSLIP, below. The
|
|
|
|
NET-3-HOWTO, available from
|
|
|
|
<http://www.tldp.org/docs.html#howto>, explains how to
|
|
|
|
configure SLIP. Note that you don't need this option if you just
|
|
|
|
want to run term (term is a program which gives you almost full
|
|
|
|
Internet connectivity if you have a regular dial up shell account on
|
|
|
|
some Internet connected Unix computer. Read
|
|
|
|
<http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
|
|
|
|
support will enlarge your kernel by about 4 KB. If unsure, say N.
|
|
|
|
|
2007-11-12 22:03:58 -07:00
|
|
|
To compile this driver as a module, choose M here. The module
|
|
|
|
will be called slip.
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
config SLIP_COMPRESSED
|
|
|
|
bool "CSLIP compressed headers"
|
|
|
|
depends on SLIP
|
2006-07-14 05:15:40 -06:00
|
|
|
select SLHC
|
2005-04-16 16:20:36 -06:00
|
|
|
---help---
|
|
|
|
This protocol is faster than SLIP because it uses compression on the
|
|
|
|
TCP/IP headers (not on the data itself), but it has to be supported
|
|
|
|
on both ends. Ask your access provider if you are not sure and
|
|
|
|
answer Y, just in case. You will still be able to use plain SLIP. If
|
|
|
|
you plan to use SLiRP, the SLIP emulator (available from
|
|
|
|
<ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
|
|
|
|
allows you to use SLIP over a regular dial up shell connection, you
|
|
|
|
definitely want to say Y here. The NET-3-HOWTO, available from
|
|
|
|
<http://www.tldp.org/docs.html#howto>, explains how to configure
|
|
|
|
CSLIP. This won't enlarge your kernel.
|
|
|
|
|
2006-07-14 05:15:40 -06:00
|
|
|
config SLHC
|
|
|
|
tristate
|
|
|
|
help
|
|
|
|
This option enables Van Jacobsen serial line header compression
|
|
|
|
routines.
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config SLIP_SMART
|
|
|
|
bool "Keepalive and linefill"
|
|
|
|
depends on SLIP
|
|
|
|
help
|
|
|
|
Adds additional capabilities to the SLIP driver to support the
|
|
|
|
RELCOM line fill and keepalive monitoring. Ideal on poor quality
|
|
|
|
analogue lines.
|
|
|
|
|
|
|
|
config SLIP_MODE_SLIP6
|
|
|
|
bool "Six bit SLIP encapsulation"
|
|
|
|
depends on SLIP
|
|
|
|
help
|
|
|
|
Just occasionally you may need to run IP over hostile serial
|
|
|
|
networks that don't pass all control characters or are only seven
|
|
|
|
bit. Saying Y here adds an extra mode you can use with SLIP:
|
|
|
|
"slip6". In this mode, SLIP will only send normal ASCII symbols over
|
|
|
|
the serial device. Naturally, this has to be supported at the other
|
|
|
|
end of the link as well. It's good enough, for example, to run IP
|
|
|
|
over the async ports of a Camtec JNT Pad. If unsure, say N.
|
|
|
|
|
|
|
|
config NET_FC
|
|
|
|
bool "Fibre Channel driver support"
|
2005-07-27 14:04:35 -06:00
|
|
|
depends on SCSI && PCI
|
2005-04-16 16:20:36 -06:00
|
|
|
help
|
|
|
|
Fibre Channel is a high speed serial protocol mainly used to connect
|
|
|
|
large storage devices to the computer; it is compatible with and
|
|
|
|
intended to replace SCSI.
|
|
|
|
|
|
|
|
If you intend to use Fibre Channel, you need to have a Fibre channel
|
|
|
|
adaptor card in your computer; say Y here and to the driver for your
|
|
|
|
adaptor below. You also should have said Y to "SCSI support" and
|
|
|
|
"SCSI generic support".
|
|
|
|
|
|
|
|
config NETCONSOLE
|
2010-03-21 17:59:23 -06:00
|
|
|
tristate "Network console logging support"
|
2005-04-16 16:20:36 -06:00
|
|
|
---help---
|
|
|
|
If you want to log kernel messages over the network, enable this.
|
|
|
|
See <file:Documentation/networking/netconsole.txt> for details.
|
|
|
|
|
[NET] netconsole: Support dynamic reconfiguration using configfs
Based upon initial work by Keiichi Kii <k-keiichi@bx.jp.nec.com>.
This patch introduces support for dynamic reconfiguration (adding, removing
and/or modifying parameters of netconsole targets at runtime) using a
userspace interface exported via configfs. Documentation is also updated
accordingly.
Issues and brief design overview:
(1) Kernel-initiated creation / destruction of kernel objects is not
possible with configfs -- the lifetimes of the "config items" is managed
exclusively from userspace. But netconsole must support boot/module
params too, and these are parsed in kernel and hence netpolls must be
setup from the kernel. Joel Becker suggested to separately manage the
lifetimes of the two kinds of netconsole_target objects -- those created
via configfs mkdir(2) from userspace and those specified from the
boot/module option string. This adds complexity and some redundancy here
and also means that boot/module param-created targets are not exposed
through the configfs namespace (and hence cannot be updated / destroyed
dynamically). However, this saves us from locking / refcounting
complexities that would need to be introduced in configfs to support
kernel-initiated item creation / destroy there.
(2) In configfs, item creation takes place in the call chain of the
mkdir(2) syscall in the driver subsystem. If we used an ioctl(2) to
create / destroy objects from userspace, the special userspace program is
able to fill out the structure to be passed into the ioctl and hence
specify attributes such as local interface that are required at the time
we set up the netpoll. For configfs, this information is not available at
the time of mkdir(2). So, we keep all newly-created targets (via
configfs) disabled by default. The user is expected to set various
attributes appropriately (including the local network interface if
required) and then write(2) "1" to the "enabled" attribute. Thus,
netpoll_setup() is then called on the set parameters in the context of
_this_ write(2) on the "enabled" attribute itself. This design enables
the user to reconfigure existing netconsole targets at runtime to be
attached to newly-come-up interfaces that may not have existed when
netconsole was loaded or when the targets were actually created. All this
effectively enables us to get rid of custom ioctls.
(3) Ultra-paranoid configfs attribute show() and store() operations, with
sanity and input range checking, using only safe string primitives, and
compliant with the recommendations in Documentation/filesystems/sysfs.txt.
(4) A new function netpoll_print_options() is created in the netpoll API,
that just prints out the configured parameters for a netpoll structure.
netpoll_parse_options() is modified to use that and it is also exported to
be used from netconsole.
Signed-off-by: Satyam Sharma <satyam@infradead.org>
Acked-by: Keiichi Kii <k-keiichi@bx.jp.nec.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-08-10 16:35:05 -06:00
|
|
|
config NETCONSOLE_DYNAMIC
|
2010-03-21 17:59:23 -06:00
|
|
|
bool "Dynamic reconfiguration of logging targets"
|
2011-06-21 02:01:20 -06:00
|
|
|
depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
|
|
|
|
!(NETCONSOLE=y && CONFIGFS_FS=m)
|
[NET] netconsole: Support dynamic reconfiguration using configfs
Based upon initial work by Keiichi Kii <k-keiichi@bx.jp.nec.com>.
This patch introduces support for dynamic reconfiguration (adding, removing
and/or modifying parameters of netconsole targets at runtime) using a
userspace interface exported via configfs. Documentation is also updated
accordingly.
Issues and brief design overview:
(1) Kernel-initiated creation / destruction of kernel objects is not
possible with configfs -- the lifetimes of the "config items" is managed
exclusively from userspace. But netconsole must support boot/module
params too, and these are parsed in kernel and hence netpolls must be
setup from the kernel. Joel Becker suggested to separately manage the
lifetimes of the two kinds of netconsole_target objects -- those created
via configfs mkdir(2) from userspace and those specified from the
boot/module option string. This adds complexity and some redundancy here
and also means that boot/module param-created targets are not exposed
through the configfs namespace (and hence cannot be updated / destroyed
dynamically). However, this saves us from locking / refcounting
complexities that would need to be introduced in configfs to support
kernel-initiated item creation / destroy there.
(2) In configfs, item creation takes place in the call chain of the
mkdir(2) syscall in the driver subsystem. If we used an ioctl(2) to
create / destroy objects from userspace, the special userspace program is
able to fill out the structure to be passed into the ioctl and hence
specify attributes such as local interface that are required at the time
we set up the netpoll. For configfs, this information is not available at
the time of mkdir(2). So, we keep all newly-created targets (via
configfs) disabled by default. The user is expected to set various
attributes appropriately (including the local network interface if
required) and then write(2) "1" to the "enabled" attribute. Thus,
netpoll_setup() is then called on the set parameters in the context of
_this_ write(2) on the "enabled" attribute itself. This design enables
the user to reconfigure existing netconsole targets at runtime to be
attached to newly-come-up interfaces that may not have existed when
netconsole was loaded or when the targets were actually created. All this
effectively enables us to get rid of custom ioctls.
(3) Ultra-paranoid configfs attribute show() and store() operations, with
sanity and input range checking, using only safe string primitives, and
compliant with the recommendations in Documentation/filesystems/sysfs.txt.
(4) A new function netpoll_print_options() is created in the netpoll API,
that just prints out the configured parameters for a netpoll structure.
netpoll_parse_options() is modified to use that and it is also exported to
be used from netconsole.
Signed-off-by: Satyam Sharma <satyam@infradead.org>
Acked-by: Keiichi Kii <k-keiichi@bx.jp.nec.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-08-10 16:35:05 -06:00
|
|
|
help
|
|
|
|
This option enables the ability to dynamically reconfigure target
|
|
|
|
parameters (interface, IP addresses, port numbers, MAC addresses)
|
|
|
|
at runtime through a userspace interface exported using configfs.
|
|
|
|
See <file:Documentation/networking/netconsole.txt> for details.
|
|
|
|
|
2005-07-18 14:45:12 -06:00
|
|
|
config NETPOLL
|
|
|
|
def_bool NETCONSOLE
|
|
|
|
|
|
|
|
config NETPOLL_TRAP
|
|
|
|
bool "Netpoll traffic trapping"
|
|
|
|
default n
|
|
|
|
depends on NETPOLL
|
|
|
|
|
|
|
|
config NET_POLL_CONTROLLER
|
|
|
|
def_bool NETPOLL
|
|
|
|
|
2007-10-21 19:03:37 -06:00
|
|
|
config VIRTIO_NET
|
|
|
|
tristate "Virtio network driver (EXPERIMENTAL)"
|
|
|
|
depends on EXPERIMENTAL && VIRTIO
|
|
|
|
---help---
|
2007-11-07 19:46:31 -07:00
|
|
|
This is the virtual network driver for virtio. It can be used with
|
2010-11-11 05:31:21 -07:00
|
|
|
lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
|
2007-10-21 19:03:37 -06:00
|
|
|
|
2009-10-13 01:15:51 -06:00
|
|
|
config VMXNET3
|
2010-11-11 05:31:21 -07:00
|
|
|
tristate "VMware VMXNET3 ethernet driver"
|
|
|
|
depends on PCI && INET
|
|
|
|
help
|
|
|
|
This driver supports VMware's vmxnet3 virtual ethernet NIC.
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
module will be called vmxnet3.
|
2009-10-13 01:15:51 -06:00
|
|
|
|
2007-06-13 13:48:53 -06:00
|
|
|
endif # NETDEVICES
|