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