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