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 PHYLIB 242 select MDIO_BITBANG 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 || MN10300 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 || MN10300 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 SMSC911X_ARCH_HOOKS 1071 def_bool n 1072 depends on SMSC911X 1073 help 1074 If the arch enables this, it allows the arch to implement various 1075 hooks for more comprehensive interrupt control and also to override 1076 the source of the MAC address. 1077 1078config NET_VENDOR_RACAL 1079 bool "Racal-Interlan (Micom) NI cards" 1080 depends on ISA 1081 help 1082 If you have a network (Ethernet) card belonging to this class, such 1083 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO, 1084 available from <http://www.tldp.org/docs.html#howto>. 1085 1086 Note that the answer to this question doesn't directly affect the 1087 kernel: saying N will just cause the configurator to skip all 1088 the questions about NI cards. If you say Y, you will be asked for 1089 your specific card in the following questions. 1090 1091config NI5010 1092 tristate "NI5010 support (EXPERIMENTAL)" 1093 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP 1094 ---help--- 1095 If you have a network (Ethernet) card of this type, say Y and read 1096 the Ethernet-HOWTO, available from 1097 <http://www.tldp.org/docs.html#howto>. Note that this is still 1098 experimental code. 1099 1100 To compile this driver as a module, choose M here. The module 1101 will be called ni5010. 1102 1103config NI52 1104 tristate "NI5210 support" 1105 depends on NET_VENDOR_RACAL && ISA 1106 help 1107 If you have a network (Ethernet) card of this type, say Y and read 1108 the Ethernet-HOWTO, available from 1109 <http://www.tldp.org/docs.html#howto>. 1110 1111 To compile this driver as a module, choose M here. The module 1112 will be called ni52. 1113 1114config NI65 1115 tristate "NI6510 support" 1116 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API 1117 help 1118 If you have a network (Ethernet) card of this type, say Y and read 1119 the Ethernet-HOWTO, available from 1120 <http://www.tldp.org/docs.html#howto>. 1121 1122 To compile this driver as a module, choose M here. The module 1123 will be called ni65. 1124 1125config DNET 1126 tristate "Dave ethernet support (DNET)" 1127 depends on NET_ETHERNET && HAS_IOMEM 1128 select PHYLIB 1129 help 1130 The Dave ethernet interface (DNET) is found on Qong Board FPGA. 1131 Say Y to include support for the DNET chip. 1132 1133 To compile this driver as a module, choose M here: the module 1134 will be called dnet. 1135 1136source "drivers/net/tulip/Kconfig" 1137 1138config AT1700 1139 tristate "AT1700/1720 support (EXPERIMENTAL)" 1140 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL 1141 select CRC32 1142 ---help--- 1143 If you have a network (Ethernet) card of this type, say Y and read 1144 the Ethernet-HOWTO, available from 1145 <http://www.tldp.org/docs.html#howto>. 1146 1147 To compile this driver as a module, choose M here. The module 1148 will be called at1700. 1149 1150config DEPCA 1151 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support" 1152 depends on ISA || EISA || MCA 1153 select CRC32 1154 ---help--- 1155 If you have a network (Ethernet) card of this type, say Y and read 1156 the Ethernet-HOWTO, available from 1157 <http://www.tldp.org/docs.html#howto> as well as 1158 <file:drivers/net/depca.c>. 1159 1160 To compile this driver as a module, choose M here. The module 1161 will be called depca. 1162 1163config HP100 1164 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support" 1165 depends on ISA || EISA || PCI 1166 help 1167 If you have a network (Ethernet) card of this type, say Y and read 1168 the Ethernet-HOWTO, available from 1169 <http://www.tldp.org/docs.html#howto>. 1170 1171 To compile this driver as a module, choose M here. The module 1172 will be called hp100. 1173 1174config NET_ISA 1175 bool "Other ISA cards" 1176 depends on ISA 1177 ---help--- 1178 If your network (Ethernet) card hasn't been mentioned yet and its 1179 bus system (that's the way the cards talks to the other components 1180 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y. 1181 Make sure you know the name of your card. Read the Ethernet-HOWTO, 1182 available from <http://www.tldp.org/docs.html#howto>. 1183 1184 If unsure, say Y. 1185 1186 Note that the answer to this question doesn't directly affect the 1187 kernel: saying N will just cause the configurator to skip all 1188 the remaining ISA network card questions. If you say Y, you will be 1189 asked for your specific card in the following questions. 1190 1191config E2100 1192 tristate "Cabletron E21xx support" 1193 depends on NET_ISA 1194 select CRC32 1195 help 1196 If you have a network (Ethernet) card of this type, say Y and read 1197 the Ethernet-HOWTO, available from 1198 <http://www.tldp.org/docs.html#howto>. 1199 1200 To compile this driver as a module, choose M here. The module 1201 will be called e2100. 1202 1203config EWRK3 1204 tristate "EtherWORKS 3 (DE203, DE204, DE205) support" 1205 depends on NET_ISA 1206 select CRC32 1207 ---help--- 1208 This driver supports the DE203, DE204 and DE205 network (Ethernet) 1209 cards. If this is for you, say Y and read 1210 <file:Documentation/networking/ewrk3.txt> in the kernel source as 1211 well as the Ethernet-HOWTO, available from 1212 <http://www.tldp.org/docs.html#howto>. 1213 1214 To compile this driver as a module, choose M here. The module 1215 will be called ewrk3. 1216 1217config EEXPRESS 1218 tristate "EtherExpress 16 support" 1219 depends on NET_ISA 1220 ---help--- 1221 If you have an EtherExpress16 network (Ethernet) card, say Y and 1222 read the Ethernet-HOWTO, available from 1223 <http://www.tldp.org/docs.html#howto>. Note that the Intel 1224 EtherExpress16 card used to be regarded as a very poor choice 1225 because the driver was very unreliable. We now have a new driver 1226 that should do better. 1227 1228 To compile this driver as a module, choose M here. The module 1229 will be called eexpress. 1230 1231config EEXPRESS_PRO 1232 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support" 1233 depends on NET_ISA 1234 ---help--- 1235 If you have a network (Ethernet) card of this type, say Y. This 1236 driver supports Intel i82595{FX,TX} based boards. Note however 1237 that the EtherExpress PRO/100 Ethernet card has its own separate 1238 driver. Please read the Ethernet-HOWTO, available from 1239 <http://www.tldp.org/docs.html#howto>. 1240 1241 To compile this driver as a module, choose M here. The module 1242 will be called eepro. 1243 1244config HPLAN_PLUS 1245 tristate "HP PCLAN+ (27247B and 27252A) support" 1246 depends on NET_ISA 1247 select CRC32 1248 help 1249 If you have a network (Ethernet) card of this type, say Y and read 1250 the Ethernet-HOWTO, available from 1251 <http://www.tldp.org/docs.html#howto>. 1252 1253 To compile this driver as a module, choose M here. The module 1254 will be called hp-plus. 1255 1256config HPLAN 1257 tristate "HP PCLAN (27245 and other 27xxx series) support" 1258 depends on NET_ISA 1259 select CRC32 1260 help 1261 If you have a network (Ethernet) card of this type, say Y and read 1262 the Ethernet-HOWTO, available from 1263 <http://www.tldp.org/docs.html#howto>. 1264 1265 To compile this driver as a module, choose M here. The module 1266 will be called hp. 1267 1268config LP486E 1269 tristate "LP486E on board Ethernet" 1270 depends on NET_ISA 1271 help 1272 Say Y here to support the 82596-based on-board Ethernet controller 1273 for the Panther motherboard, which is one of the two shipped in the 1274 Intel Professional Workstation. 1275 1276config ETH16I 1277 tristate "ICL EtherTeam 16i/32 support" 1278 depends on NET_ISA 1279 help 1280 If you have a network (Ethernet) card of this type, say Y and read 1281 the Ethernet-HOWTO, available from 1282 <http://www.tldp.org/docs.html#howto>. 1283 1284 To compile this driver as a module, choose M here. The module 1285 will be called eth16i. 1286 1287config NE2000 1288 tristate "NE2000/NE1000 support" 1289 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX 1290 select CRC32 1291 ---help--- 1292 If you have a network (Ethernet) card of this type, say Y and read 1293 the Ethernet-HOWTO, available from 1294 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards 1295 without a specific driver are compatible with NE2000. 1296 1297 If you have a PCI NE2000 card however, say N here and Y to "PCI 1298 NE2000 and clone support" under "EISA, VLB, PCI and on board 1299 controllers" below. If you have a NE2000 card and are running on 1300 an MCA system (a bus system used on some IBM PS/2 computers and 1301 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support", 1302 below. 1303 1304 To compile this driver as a module, choose M here. The module 1305 will be called ne. 1306 1307config ZNET 1308 tristate "Zenith Z-Note support (EXPERIMENTAL)" 1309 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API 1310 help 1311 The Zenith Z-Note notebook computer has a built-in network 1312 (Ethernet) card, and this is the Linux driver for it. Note that the 1313 IBM Thinkpad 300 is compatible with the Z-Note and is also supported 1314 by this driver. Read the Ethernet-HOWTO, available from 1315 <http://www.tldp.org/docs.html#howto>. 1316 1317config SEEQ8005 1318 tristate "SEEQ8005 support (EXPERIMENTAL)" 1319 depends on NET_ISA && EXPERIMENTAL 1320 help 1321 This is a driver for the SEEQ 8005 network (Ethernet) card. If this 1322 is for you, read the Ethernet-HOWTO, available from 1323 <http://www.tldp.org/docs.html#howto>. 1324 1325 To compile this driver as a module, choose M here. The module 1326 will be called seeq8005. 1327 1328config NE2_MCA 1329 tristate "NE/2 (ne2000 MCA version) support" 1330 depends on MCA_LEGACY 1331 select CRC32 1332 help 1333 If you have a network (Ethernet) card of this type, say Y and read 1334 the Ethernet-HOWTO, available from 1335 <http://www.tldp.org/docs.html#howto>. 1336 1337 To compile this driver as a module, choose M here. The module 1338 will be called ne2. 1339 1340config IBMLANA 1341 tristate "IBM LAN Adapter/A support" 1342 depends on MCA 1343 ---help--- 1344 This is a Micro Channel Ethernet adapter. You need to set 1345 CONFIG_MCA to use this driver. It is both available as an in-kernel 1346 driver and as a module. 1347 1348 To compile this driver as a module, choose M here. The only 1349 currently supported card is the IBM LAN Adapter/A for Ethernet. It 1350 will both support 16K and 32K memory windows, however a 32K window 1351 gives a better security against packet losses. Usage of multiple 1352 boards with this driver should be possible, but has not been tested 1353 up to now due to lack of hardware. 1354 1355config IBMVETH 1356 tristate "IBM LAN Virtual Ethernet support" 1357 depends on PPC_PSERIES 1358 ---help--- 1359 This driver supports virtual ethernet adapters on newer IBM iSeries 1360 and pSeries systems. 1361 1362 To compile this driver as a module, choose M here. The module will 1363 be called ibmveth. 1364 1365source "drivers/net/ibm_newemac/Kconfig" 1366 1367config NET_PCI 1368 bool "EISA, VLB, PCI and on board controllers" 1369 depends on ISA || EISA || PCI 1370 help 1371 This is another class of network cards which attach directly to the 1372 bus. If you have one of those, say Y and read the Ethernet-HOWTO, 1373 available from <http://www.tldp.org/docs.html#howto>. 1374 1375 Note that the answer to this question doesn't directly affect the 1376 kernel: saying N will just cause the configurator to skip all 1377 the questions about this class of network cards. If you say Y, you 1378 will be asked for your specific card in the following questions. If 1379 you are unsure, say Y. 1380 1381config PCNET32 1382 tristate "AMD PCnet32 PCI support" 1383 depends on NET_PCI && PCI 1384 select CRC32 1385 select MII 1386 help 1387 If you have a PCnet32 or PCnetPCI based network (Ethernet) card, 1388 answer Y here and read the Ethernet-HOWTO, available from 1389 <http://www.tldp.org/docs.html#howto>. 1390 1391 To compile this driver as a module, choose M here. The module 1392 will be called pcnet32. 1393 1394config AMD8111_ETH 1395 tristate "AMD 8111 (new PCI lance) support" 1396 depends on NET_PCI && PCI 1397 select CRC32 1398 select MII 1399 help 1400 If you have an AMD 8111-based PCI lance ethernet card, 1401 answer Y here and read the Ethernet-HOWTO, available from 1402 <http://www.tldp.org/docs.html#howto>. 1403 1404 To compile this driver as a module, choose M here. The module 1405 will be called amd8111e. 1406 1407config ADAPTEC_STARFIRE 1408 tristate "Adaptec Starfire/DuraLAN support" 1409 depends on NET_PCI && PCI 1410 select CRC32 1411 select MII 1412 help 1413 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network 1414 adapter. The DuraLAN chip is used on the 64 bit PCI boards from 1415 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip 1416 driver. 1417 1418 To compile this driver as a module, choose M here: the module 1419 will be called starfire. This is recommended. 1420 1421config AC3200 1422 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)" 1423 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL 1424 select CRC32 1425 help 1426 If you have a network (Ethernet) card of this type, say Y and read 1427 the Ethernet-HOWTO, available from 1428 <http://www.tldp.org/docs.html#howto>. 1429 1430 To compile this driver as a module, choose M here. The module 1431 will be called ac3200. 1432 1433config KSZ884X_PCI 1434 tristate "Micrel KSZ8841/2 PCI" 1435 depends on NET_PCI && PCI 1436 select MII 1437 select CRC32 1438 help 1439 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip. 1440 1441 To compile this driver as a module, choose M here. The module 1442 will be called ksz884x. 1443 1444config APRICOT 1445 tristate "Apricot Xen-II on board Ethernet" 1446 depends on NET_PCI && ISA 1447 help 1448 If you have a network (Ethernet) controller of this type, say Y and 1449 read the Ethernet-HOWTO, available from 1450 <http://www.tldp.org/docs.html#howto>. 1451 1452 To compile this driver as a module, choose M here. The module 1453 will be called apricot. 1454 1455config B44 1456 tristate "Broadcom 440x/47xx ethernet support" 1457 depends on SSB_POSSIBLE && HAS_DMA 1458 select SSB 1459 select MII 1460 help 1461 If you have a network (Ethernet) controller of this type, say Y 1462 or M and read the Ethernet-HOWTO, available from 1463 <http://www.tldp.org/docs.html#howto>. 1464 1465 To compile this driver as a module, choose M here. The module 1466 will be called b44. 1467 1468# Auto-select SSB PCI-HOST support, if possible 1469config B44_PCI_AUTOSELECT 1470 bool 1471 depends on B44 && SSB_PCIHOST_POSSIBLE 1472 select SSB_PCIHOST 1473 default y 1474 1475# Auto-select SSB PCICORE driver, if possible 1476config B44_PCICORE_AUTOSELECT 1477 bool 1478 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE 1479 select SSB_DRIVER_PCICORE 1480 default y 1481 1482config B44_PCI 1483 bool 1484 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT 1485 default y 1486 1487config FORCEDETH 1488 tristate "nForce Ethernet support" 1489 depends on NET_PCI && PCI 1490 help 1491 If you have a network (Ethernet) controller of this type, say Y and 1492 read the Ethernet-HOWTO, available from 1493 <http://www.tldp.org/docs.html#howto>. 1494 1495 To compile this driver as a module, choose M here. The module 1496 will be called forcedeth. 1497 1498config CS89x0 1499 tristate "CS89x0 support" 1500 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \ 1501 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440) 1502 ---help--- 1503 Support for CS89x0 chipset based Ethernet cards. If you have a 1504 network (Ethernet) card of this type, say Y and read the 1505 Ethernet-HOWTO, available from 1506 <http://www.tldp.org/docs.html#howto> as well as 1507 <file:Documentation/networking/cs89x0.txt>. 1508 1509 To compile this driver as a module, choose M here. The module 1510 will be called cs89x0. 1511 1512config CS89x0_NONISA_IRQ 1513 def_bool y 1514 depends on CS89x0 != n 1515 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440 1516 1517config TC35815 1518 tristate "TOSHIBA TC35815 Ethernet support" 1519 depends on NET_PCI && PCI && MIPS 1520 select PHYLIB 1521 1522config E100 1523 tristate "Intel(R) PRO/100+ support" 1524 depends on NET_PCI && PCI 1525 select MII 1526 ---help--- 1527 This driver supports Intel(R) PRO/100 family of adapters. 1528 To verify that your adapter is supported, find the board ID number 1529 on the adapter. Look for a label that has a barcode and a number 1530 in the format 123456-001 (six digits hyphen three digits). 1531 1532 Use the above information and the Adapter & Driver ID Guide at: 1533 1534 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 1535 1536 to identify the adapter. 1537 1538 For the latest Intel PRO/100 network driver for Linux, see: 1539 1540 <http://www.intel.com/p/en_US/support/highlights/network/pro100plus> 1541 1542 More specific information on configuring the driver is in 1543 <file:Documentation/networking/e100.txt>. 1544 1545 To compile this driver as a module, choose M here. The module 1546 will be called e100. 1547 1548config LNE390 1549 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)" 1550 depends on NET_PCI && EISA && EXPERIMENTAL 1551 select CRC32 1552 help 1553 If you have a network (Ethernet) card of this type, say Y and read 1554 the Ethernet-HOWTO, available from 1555 <http://www.tldp.org/docs.html#howto>. 1556 1557 To compile this driver as a module, choose M here. The module 1558 will be called lne390. 1559 1560config FEALNX 1561 tristate "Myson MTD-8xx PCI Ethernet support" 1562 depends on NET_PCI && PCI 1563 select CRC32 1564 select MII 1565 help 1566 Say Y here to support the Myson MTD-800 family of PCI-based Ethernet 1567 cards. <http://www.myson.com.tw/> 1568 1569config NATSEMI 1570 tristate "National Semiconductor DP8381x series PCI Ethernet support" 1571 depends on NET_PCI && PCI 1572 select CRC32 1573 help 1574 This driver is for the National Semiconductor DP83810 series, 1575 which is used in cards from PureData, NetGear, Linksys 1576 and others, including the 83815 chip. 1577 More specific information and updates are available from 1578 <http://www.scyld.com/network/natsemi.html>. 1579 1580config NE2K_PCI 1581 tristate "PCI NE2000 and clones support (see help)" 1582 depends on NET_PCI && PCI 1583 select CRC32 1584 ---help--- 1585 This driver is for NE2000 compatible PCI cards. It will not work 1586 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000 1587 support" below). If you have a PCI NE2000 network (Ethernet) card, 1588 say Y and read the Ethernet-HOWTO, available from 1589 <http://www.tldp.org/docs.html#howto>. 1590 1591 This driver also works for the following NE2000 clone cards: 1592 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2 1593 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond 1594 Holtek HT80232 Holtek HT80229 1595 1596 To compile this driver as a module, choose M here. The module 1597 will be called ne2k-pci. 1598 1599config NE3210 1600 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)" 1601 depends on NET_PCI && EISA && EXPERIMENTAL 1602 select CRC32 1603 ---help--- 1604 If you have a network (Ethernet) card of this type, say Y and read 1605 the Ethernet-HOWTO, available from 1606 <http://www.tldp.org/docs.html#howto>. Note that this driver 1607 will NOT WORK for NE3200 cards as they are completely different. 1608 1609 To compile this driver as a module, choose M here. The module 1610 will be called ne3210. 1611 1612config ES3210 1613 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)" 1614 depends on NET_PCI && EISA && EXPERIMENTAL 1615 select CRC32 1616 help 1617 If you have a network (Ethernet) card of this type, say Y and read 1618 the Ethernet-HOWTO, available from 1619 <http://www.tldp.org/docs.html#howto>. 1620 1621 To compile this driver as a module, choose M here. The module 1622 will be called es3210. 1623 1624config 8139CP 1625 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)" 1626 depends on NET_PCI && PCI && EXPERIMENTAL 1627 select CRC32 1628 select MII 1629 help 1630 This is a driver for the Fast Ethernet PCI network cards based on 1631 the RTL8139C+ chips. If you have one of those, say Y and read 1632 the Ethernet-HOWTO, available from 1633 <http://www.tldp.org/docs.html#howto>. 1634 1635 To compile this driver as a module, choose M here: the module 1636 will be called 8139cp. This is recommended. 1637 1638config 8139TOO 1639 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support" 1640 depends on NET_PCI && PCI 1641 select CRC32 1642 select MII 1643 ---help--- 1644 This is a driver for the Fast Ethernet PCI network cards based on 1645 the RTL 8129/8130/8139 chips. If you have one of those, say Y and 1646 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>. 1647 1648 To compile this driver as a module, choose M here: the module 1649 will be called 8139too. This is recommended. 1650 1651config 8139TOO_PIO 1652 bool "Use PIO instead of MMIO" 1653 default y 1654 depends on 8139TOO 1655 help 1656 This instructs the driver to use programmed I/O ports (PIO) instead 1657 of PCI shared memory (MMIO). This can possibly solve some problems 1658 in case your mainboard has memory consistency issues. If unsure, 1659 say N. 1660 1661config 8139TOO_TUNE_TWISTER 1662 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)" 1663 depends on 8139TOO 1664 help 1665 This implements a function which might come in handy in case you 1666 are using low quality on long cabling. It is required for RealTek 1667 RTL-8139 revision K boards, and totally unused otherwise. It tries 1668 to match the transceiver to the cable characteristics. This is 1669 experimental since hardly documented by the manufacturer. 1670 If unsure, say Y. 1671 1672config 8139TOO_8129 1673 bool "Support for older RTL-8129/8130 boards" 1674 depends on 8139TOO 1675 help 1676 This enables support for the older and uncommon RTL-8129 and 1677 RTL-8130 chips, which support MII via an external transceiver, 1678 instead of an internal one. Disabling this option will save some 1679 memory by making the code size smaller. If unsure, say Y. 1680 1681config 8139_OLD_RX_RESET 1682 bool "Use older RX-reset method" 1683 depends on 8139TOO 1684 help 1685 The 8139too driver was recently updated to contain a more rapid 1686 reset sequence, in the face of severe receive errors. This "new" 1687 RX-reset method should be adequate for all boards. But if you 1688 experience problems, you can enable this option to restore the 1689 old RX-reset behavior. If unsure, say N. 1690 1691config R6040 1692 tristate "RDC R6040 Fast Ethernet Adapter support" 1693 depends on NET_PCI && PCI 1694 select CRC32 1695 select MII 1696 select PHYLIB 1697 help 1698 This is a driver for the R6040 Fast Ethernet MACs found in the 1699 the RDC R-321x System-on-chips. 1700 1701 To compile this driver as a module, choose M here: the module 1702 will be called r6040. This is recommended. 1703 1704config SIS900 1705 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support" 1706 depends on NET_PCI && PCI 1707 select CRC32 1708 select MII 1709 ---help--- 1710 This is a driver for the Fast Ethernet PCI network cards based on 1711 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in 1712 SiS 630 and SiS 540 chipsets. 1713 1714 This driver also supports AMD 79C901 HomePNA so that you can use 1715 your phone line as a network cable. 1716 1717 To compile this driver as a module, choose M here: the module 1718 will be called sis900. This is recommended. 1719 1720config EPIC100 1721 tristate "SMC EtherPower II" 1722 depends on NET_PCI && PCI 1723 select CRC32 1724 select MII 1725 help 1726 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC, 1727 which is based on the SMC83c17x (EPIC/100). 1728 More specific information and updates are available from 1729 <http://www.scyld.com/network/epic100.html>. 1730 1731config SMSC9420 1732 tristate "SMSC LAN9420 PCI ethernet adapter support" 1733 depends on NET_PCI && PCI 1734 select CRC32 1735 select PHYLIB 1736 select SMSC_PHY 1737 help 1738 This is a driver for SMSC's LAN9420 PCI ethernet adapter. 1739 Say Y if you want it compiled into the kernel, 1740 and read the Ethernet-HOWTO, available from 1741 <http://www.tldp.org/docs.html#howto>. 1742 1743 This driver is also available as a module. The module will be 1744 called smsc9420. If you want to compile it as a module, say M 1745 here and read <file:Documentation/kbuild/modules.txt> 1746 1747config SUNDANCE 1748 tristate "Sundance Alta support" 1749 depends on NET_PCI && PCI 1750 select CRC32 1751 select MII 1752 help 1753 This driver is for the Sundance "Alta" chip. 1754 More specific information and updates are available from 1755 <http://www.scyld.com/network/sundance.html>. 1756 1757config SUNDANCE_MMIO 1758 bool "Use MMIO instead of PIO" 1759 depends on SUNDANCE 1760 help 1761 Enable memory-mapped I/O for interaction with Sundance NIC registers. 1762 Do NOT enable this by default, PIO (enabled when MMIO is disabled) 1763 is known to solve bugs on certain chips. 1764 1765 If unsure, say N. 1766 1767config TLAN 1768 tristate "TI ThunderLAN support" 1769 depends on NET_PCI && (PCI || EISA) 1770 ---help--- 1771 If you have a PCI Ethernet network card based on the ThunderLAN chip 1772 which is supported by this driver, say Y and read the 1773 Ethernet-HOWTO, available from 1774 <http://www.tldp.org/docs.html#howto>. 1775 1776 Devices currently supported by this driver are Compaq Netelligent, 1777 Compaq NetFlex and Olicom cards. Please read the file 1778 <file:Documentation/networking/tlan.txt> for more details. 1779 1780 To compile this driver as a module, choose M here. The module 1781 will be called tlan. 1782 1783 Please email feedback to <torben.mathiasen@compaq.com>. 1784 1785config KS8842 1786 tristate "Micrel KSZ8841/42 with generic bus interface" 1787 depends on HAS_IOMEM && DMA_ENGINE 1788 help 1789 This platform driver is for KSZ8841(1-port) / KS8842(2-port) 1790 ethernet switch chip (managed, VLAN, QoS) from Micrel or 1791 Timberdale(FPGA). 1792 1793config KS8851 1794 tristate "Micrel KS8851 SPI" 1795 depends on SPI 1796 select MII 1797 select CRC32 1798 help 1799 SPI driver for Micrel KS8851 SPI attached network chip. 1800 1801config KS8851_MLL 1802 tristate "Micrel KS8851 MLL" 1803 depends on HAS_IOMEM 1804 select MII 1805 help 1806 This platform driver is for Micrel KS8851 Address/data bus 1807 multiplexed network chip. 1808 1809config VIA_RHINE 1810 tristate "VIA Rhine support" 1811 depends on NET_PCI && PCI 1812 select CRC32 1813 select MII 1814 help 1815 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A), 1816 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type 1817 Ethernet functions can also be found integrated on South Bridges 1818 (e.g. VT8235). 1819 1820 To compile this driver as a module, choose M here. The module 1821 will be called via-rhine. 1822 1823config VIA_RHINE_MMIO 1824 bool "Use MMIO instead of PIO" 1825 depends on VIA_RHINE 1826 help 1827 This instructs the driver to use PCI shared memory (MMIO) instead of 1828 programmed I/O ports (PIO). Enabling this gives an improvement in 1829 processing time in parts of the driver. 1830 1831 If unsure, say Y. 1832 1833config SC92031 1834 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)" 1835 depends on NET_PCI && PCI && EXPERIMENTAL 1836 select CRC32 1837 ---help--- 1838 This is a driver for the Fast Ethernet PCI network cards based on 1839 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you 1840 have one of these, say Y here. 1841 1842 To compile this driver as a module, choose M here: the module 1843 will be called sc92031. This is recommended. 1844 1845config CPMAC 1846 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)" 1847 depends on NET_ETHERNET && EXPERIMENTAL && AR7 1848 select PHYLIB 1849 help 1850 TI AR7 CPMAC Ethernet support 1851 1852config NET_POCKET 1853 bool "Pocket and portable adapters" 1854 depends on PARPORT 1855 ---help--- 1856 Cute little network (Ethernet) devices which attach to the parallel 1857 port ("pocket adapters"), commonly used with laptops. If you have 1858 one of those, say Y and read the Ethernet-HOWTO, available from 1859 <http://www.tldp.org/docs.html#howto>. 1860 1861 If you want to plug a network (or some other) card into the PCMCIA 1862 (or PC-card) slot of your laptop instead (PCMCIA is the standard for 1863 credit card size extension cards used by all modern laptops), you 1864 need the pcmcia-cs package (location contained in the file 1865 <file:Documentation/Changes>) and you can say N here. 1866 1867 Laptop users should read the Linux Laptop home page at 1868 <http://www.linux-on-laptops.com/> or 1869 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>. 1870 1871 Note that the answer to this question doesn't directly affect the 1872 kernel: saying N will just cause the configurator to skip all 1873 the questions about this class of network devices. If you say Y, you 1874 will be asked for your specific device in the following questions. 1875 1876config ATP 1877 tristate "AT-LAN-TEC/RealTek pocket adapter support" 1878 depends on NET_POCKET && PARPORT && X86 1879 select CRC32 1880 ---help--- 1881 This is a network (Ethernet) device which attaches to your parallel 1882 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO, 1883 available from <http://www.tldp.org/docs.html#howto>, if you 1884 want to use this. If you intend to use this driver, you should have 1885 said N to the "Parallel printer support", because the two drivers 1886 don't like each other. 1887 1888 To compile this driver as a module, choose M here: the module 1889 will be called atp. 1890 1891config DE600 1892 tristate "D-Link DE600 pocket adapter support" 1893 depends on NET_POCKET && PARPORT 1894 ---help--- 1895 This is a network (Ethernet) device which attaches to your parallel 1896 port. Read <file:Documentation/networking/DLINK.txt> as well as the 1897 Ethernet-HOWTO, available from 1898 <http://www.tldp.org/docs.html#howto>, if you want to use 1899 this. It is possible to have several devices share a single parallel 1900 port and it is safe to compile the corresponding drivers into the 1901 kernel. 1902 1903 To compile this driver as a module, choose M here: the module 1904 will be called de600. 1905 1906config DE620 1907 tristate "D-Link DE620 pocket adapter support" 1908 depends on NET_POCKET && PARPORT 1909 ---help--- 1910 This is a network (Ethernet) device which attaches to your parallel 1911 port. Read <file:Documentation/networking/DLINK.txt> as well as the 1912 Ethernet-HOWTO, available from 1913 <http://www.tldp.org/docs.html#howto>, if you want to use 1914 this. It is possible to have several devices share a single parallel 1915 port and it is safe to compile the corresponding drivers into the 1916 kernel. 1917 1918 To compile this driver as a module, choose M here: the module 1919 will be called de620. 1920 1921config SGISEEQ 1922 tristate "SGI Seeq ethernet controller support" 1923 depends on SGI_HAS_SEEQ 1924 help 1925 Say Y here if you have an Seeq based Ethernet network card. This is 1926 used in many Silicon Graphics machines. 1927 1928config DECLANCE 1929 tristate "DEC LANCE ethernet controller support" 1930 depends on MACH_DECSTATION 1931 select CRC32 1932 help 1933 This driver is for the series of Ethernet controllers produced by 1934 DEC (now Compaq) based on the AMD Lance chipset, including the 1935 DEPCA series. (This chipset is better known via the NE2100 cards.) 1936 1937config FEC 1938 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)" 1939 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \ 1940 IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC 1941 default IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC if ARM 1942 select PHYLIB 1943 help 1944 Say Y here if you want to use the built-in 10/100 Fast ethernet 1945 controller on some Motorola ColdFire and Freescale i.MX processors. 1946 1947config FEC_MPC52xx 1948 tristate "MPC52xx FEC driver" 1949 depends on PPC_MPC52xx && PPC_BESTCOMM 1950 select CRC32 1951 select PHYLIB 1952 select PPC_BESTCOMM_FEC 1953 ---help--- 1954 This option enables support for the MPC5200's on-chip 1955 Fast Ethernet Controller 1956 If compiled as module, it will be called fec_mpc52xx. 1957 1958config FEC_MPC52xx_MDIO 1959 bool "MPC52xx FEC MDIO bus driver" 1960 depends on FEC_MPC52xx 1961 default y 1962 ---help--- 1963 The MPC5200's FEC can connect to the Ethernet either with 1964 an external MII PHY chip or 10 Mbps 7-wire interface 1965 (Motorola? industry standard). 1966 If your board uses an external PHY connected to FEC, enable this. 1967 If not sure, enable. 1968 If compiled as module, it will be called fec_mpc52xx_phy. 1969 1970config NE_H8300 1971 tristate "NE2000 compatible support for H8/300" 1972 depends on H8300 1973 help 1974 Say Y here if you want to use the NE2000 compatible 1975 controller on the Renesas H8/300 processor. 1976 1977config ATL2 1978 tristate "Atheros L2 Fast Ethernet support" 1979 depends on PCI 1980 select CRC32 1981 select MII 1982 help 1983 This driver supports the Atheros L2 fast ethernet adapter. 1984 1985 To compile this driver as a module, choose M here. The module 1986 will be called atl2. 1987 1988config XILINX_EMACLITE 1989 tristate "Xilinx 10/100 Ethernet Lite support" 1990 depends on PPC32 || MICROBLAZE 1991 select PHYLIB 1992 help 1993 This driver supports the 10/100 Ethernet Lite from Xilinx. 1994 1995config BCM63XX_ENET 1996 tristate "Broadcom 63xx internal mac support" 1997 depends on BCM63XX 1998 select MII 1999 select PHYLIB 2000 help 2001 This driver supports the ethernet MACs in the Broadcom 63xx 2002 MIPS chipset family (BCM63XX). 2003 2004config FTMAC100 2005 tristate "Faraday FTMAC100 10/100 Ethernet support" 2006 depends on ARM 2007 select MII 2008 help 2009 This driver supports the FTMAC100 10/100 Ethernet controller 2010 from Faraday. It is used on Faraday A320, Andes AG101 and some 2011 other ARM/NDS32 SoC's. 2012 2013config LANTIQ_ETOP 2014 tristate "Lantiq SoC ETOP driver" 2015 depends on SOC_TYPE_XWAY 2016 help 2017 Support for the MII0 inside the Lantiq SoC 2018 2019 2020source "drivers/net/fs_enet/Kconfig" 2021 2022source "drivers/net/octeon/Kconfig" 2023 2024endif # NET_ETHERNET 2025 2026# 2027# Gigabit Ethernet 2028# 2029 2030menuconfig NETDEV_1000 2031 bool "Ethernet (1000 Mbit)" 2032 depends on !UML 2033 default y 2034 ---help--- 2035 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common 2036 type of Local Area Network (LAN) in universities and companies. 2037 2038 Say Y here to get to see options for Gigabit Ethernet drivers. 2039 This option alone does not add any kernel code. 2040 Note that drivers supporting both 100 and 1000 MBit may be listed 2041 under "Ethernet (10 or 100MBit)" instead. 2042 2043 If you say N, all options in this submenu will be skipped and disabled. 2044 2045if NETDEV_1000 2046 2047config ACENIC 2048 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support" 2049 depends on PCI 2050 ---help--- 2051 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear 2052 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet 2053 adapter. The driver allows for using the Jumbo Frame option (9000 2054 bytes/frame) however it requires that your switches can handle this 2055 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig 2056 line. 2057 2058 To compile this driver as a module, choose M here: the 2059 module will be called acenic. 2060 2061config ACENIC_OMIT_TIGON_I 2062 bool "Omit support for old Tigon I based AceNICs" 2063 depends on ACENIC 2064 help 2065 Say Y here if you only have Tigon II based AceNICs and want to leave 2066 out support for the older Tigon I based cards which are no longer 2067 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B 2068 version)). This will reduce the size of the driver object by 2069 app. 100KB. If you are not sure whether your card is a Tigon I or a 2070 Tigon II, say N here. 2071 2072 The safe and default value for this is N. 2073 2074config DL2K 2075 tristate "DL2000/TC902x-based Gigabit Ethernet support" 2076 depends on PCI 2077 select CRC32 2078 help 2079 This driver supports DL2000/TC902x-based Gigabit ethernet cards, 2080 which includes 2081 D-Link DGE-550T Gigabit Ethernet Adapter. 2082 D-Link DL2000-based Gigabit Ethernet Adapter. 2083 Sundance/Tamarack TC902x Gigabit Ethernet Adapter. 2084 2085 To compile this driver as a module, choose M here: the 2086 module will be called dl2k. 2087 2088config E1000 2089 tristate "Intel(R) PRO/1000 Gigabit Ethernet support" 2090 depends on PCI 2091 ---help--- 2092 This driver supports Intel(R) PRO/1000 gigabit ethernet family of 2093 adapters. For more information on how to identify your adapter, go 2094 to the Adapter & Driver ID Guide at: 2095 2096 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2097 2098 For general information and support, go to the Intel support 2099 website at: 2100 2101 <http://support.intel.com> 2102 2103 More specific information on configuring the driver is in 2104 <file:Documentation/networking/e1000.txt>. 2105 2106 To compile this driver as a module, choose M here. The module 2107 will be called e1000. 2108 2109config E1000E 2110 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support" 2111 depends on PCI && (!SPARC32 || BROKEN) 2112 select CRC32 2113 ---help--- 2114 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit 2115 ethernet family of adapters. For PCI or PCI-X e1000 adapters, 2116 use the regular e1000 driver For more information on how to 2117 identify your adapter, go to the Adapter & Driver ID Guide at: 2118 2119 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2120 2121 For general information and support, go to the Intel support 2122 website at: 2123 2124 <http://support.intel.com> 2125 2126 To compile this driver as a module, choose M here. The module 2127 will be called e1000e. 2128 2129config IP1000 2130 tristate "IP1000 Gigabit Ethernet support" 2131 depends on PCI && EXPERIMENTAL 2132 select MII 2133 ---help--- 2134 This driver supports IP1000 gigabit Ethernet cards. 2135 2136 To compile this driver as a module, choose M here: the module 2137 will be called ipg. This is recommended. 2138 2139config IGB 2140 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support" 2141 depends on PCI 2142 ---help--- 2143 This driver supports Intel(R) 82575/82576 gigabit ethernet family of 2144 adapters. For more information on how to identify your adapter, go 2145 to the Adapter & Driver ID Guide at: 2146 2147 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2148 2149 For general information and support, go to the Intel support 2150 website at: 2151 2152 <http://support.intel.com> 2153 2154 More specific information on configuring the driver is in 2155 <file:Documentation/networking/e1000.txt>. 2156 2157 To compile this driver as a module, choose M here. The module 2158 will be called igb. 2159 2160config IGB_DCA 2161 bool "Direct Cache Access (DCA) Support" 2162 default y 2163 depends on IGB && DCA && !(IGB=y && DCA=m) 2164 ---help--- 2165 Say Y here if you want to use Direct Cache Access (DCA) in the 2166 driver. DCA is a method for warming the CPU cache before data 2167 is used, with the intent of lessening the impact of cache misses. 2168 2169config IGBVF 2170 tristate "Intel(R) 82576 Virtual Function Ethernet support" 2171 depends on PCI 2172 ---help--- 2173 This driver supports Intel(R) 82576 virtual functions. For more 2174 information on how to identify your adapter, go to the Adapter & 2175 Driver ID Guide at: 2176 2177 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2178 2179 For general information and support, go to the Intel support 2180 website at: 2181 2182 <http://support.intel.com> 2183 2184 More specific information on configuring the driver is in 2185 <file:Documentation/networking/e1000.txt>. 2186 2187 To compile this driver as a module, choose M here. The module 2188 will be called igbvf. 2189 2190source "drivers/net/ixp2000/Kconfig" 2191 2192config NS83820 2193 tristate "National Semiconductor DP83820 support" 2194 depends on PCI 2195 help 2196 This is a driver for the National Semiconductor DP83820 series 2197 of gigabit ethernet MACs. Cards using this chipset include 2198 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX, 2199 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of 2200 zero copy. 2201 2202config HAMACHI 2203 tristate "Packet Engines Hamachi GNIC-II support" 2204 depends on PCI 2205 select MII 2206 help 2207 If you have a Gigabit Ethernet card of this type, say Y and read 2208 the Ethernet-HOWTO, available from 2209 <http://www.tldp.org/docs.html#howto>. 2210 2211 To compile this driver as a module, choose M here. The module will be 2212 called hamachi. 2213 2214config YELLOWFIN 2215 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)" 2216 depends on PCI && EXPERIMENTAL 2217 select CRC32 2218 ---help--- 2219 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet 2220 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is 2221 used by the Beowulf Linux cluster project. See 2222 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more 2223 information about this driver in particular and Beowulf in general. 2224 2225 To compile this driver as a module, choose M here: the module 2226 will be called yellowfin. This is recommended. 2227 2228config R8169 2229 tristate "Realtek 8169 gigabit ethernet support" 2230 depends on PCI 2231 select FW_LOADER 2232 select CRC32 2233 select MII 2234 ---help--- 2235 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter. 2236 2237 To compile this driver as a module, choose M here: the module 2238 will be called r8169. This is recommended. 2239 2240config SB1250_MAC 2241 tristate "SB1250 Gigabit Ethernet support" 2242 depends on SIBYTE_SB1xxx_SOC 2243 select PHYLIB 2244 ---help--- 2245 This driver supports Gigabit Ethernet interfaces based on the 2246 Broadcom SiByte family of System-On-a-Chip parts. They include 2247 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455 2248 and BCM1480 chips. 2249 2250 To compile this driver as a module, choose M here: the module 2251 will be called sb1250-mac. 2252 2253config SIS190 2254 tristate "SiS190/SiS191 gigabit ethernet support" 2255 depends on PCI 2256 select CRC32 2257 select MII 2258 ---help--- 2259 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or 2260 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to 2261 appear in lan on motherboard designs which are based on SiS 965 2262 and SiS 966 south bridge. 2263 2264 To compile this driver as a module, choose M here: the module 2265 will be called sis190. This is recommended. 2266 2267config SKGE 2268 tristate "Marvell Yukon Gigabit Ethernet support" 2269 depends on PCI 2270 select CRC32 2271 ---help--- 2272 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx 2273 and related Gigabit Ethernet adapters. It is a new smaller driver 2274 with better performance and more complete ethtool support. 2275 2276 It does not support the link failover and network management 2277 features that "portable" vendor supplied sk98lin driver does. 2278 2279 This driver supports adapters based on the original Yukon chipset: 2280 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T, 2281 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872. 2282 2283 It does not support the newer Yukon2 chipset: a separate driver, 2284 sky2, is provided for these adapters. 2285 2286 To compile this driver as a module, choose M here: the module 2287 will be called skge. This is recommended. 2288 2289config SKGE_DEBUG 2290 bool "Debugging interface" 2291 depends on SKGE && DEBUG_FS 2292 help 2293 This option adds the ability to dump driver state for debugging. 2294 The file /sys/kernel/debug/skge/ethX displays the state of the internal 2295 transmit and receive rings. 2296 2297 If unsure, say N. 2298 2299config SKGE_GENESIS 2300 bool "Support for older SysKonnect Genesis boards" 2301 depends on SKGE 2302 help 2303 This enables support for the older and uncommon SysKonnect Genesis 2304 chips, which support MII via an external transceiver, instead of 2305 an internal one. Disabling this option will save some memory 2306 by making code smaller. If unsure say Y. 2307 2308config SKY2 2309 tristate "Marvell Yukon 2 support" 2310 depends on PCI 2311 select CRC32 2312 ---help--- 2313 This driver supports Gigabit Ethernet adapters based on the 2314 Marvell Yukon 2 chipset: 2315 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/ 2316 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21 2317 2318 There is companion driver for the older Marvell Yukon and 2319 SysKonnect Genesis based adapters: skge. 2320 2321 To compile this driver as a module, choose M here: the module 2322 will be called sky2. This is recommended. 2323 2324config SKY2_DEBUG 2325 bool "Debugging interface" 2326 depends on SKY2 && DEBUG_FS 2327 help 2328 This option adds the ability to dump driver state for debugging. 2329 The file /sys/kernel/debug/sky2/ethX displays the state of the internal 2330 transmit and receive rings. 2331 2332 If unsure, say N. 2333 2334config VIA_VELOCITY 2335 tristate "VIA Velocity support" 2336 depends on PCI 2337 select CRC32 2338 select CRC_CCITT 2339 select MII 2340 help 2341 If you have a VIA "Velocity" based network card say Y here. 2342 2343 To compile this driver as a module, choose M here. The module 2344 will be called via-velocity. 2345 2346config TIGON3 2347 tristate "Broadcom Tigon3 support" 2348 depends on PCI 2349 select PHYLIB 2350 help 2351 This driver supports Broadcom Tigon3 based gigabit Ethernet cards. 2352 2353 To compile this driver as a module, choose M here: the module 2354 will be called tg3. This is recommended. 2355 2356config BNX2 2357 tristate "Broadcom NetXtremeII support" 2358 depends on PCI 2359 select CRC32 2360 select FW_LOADER 2361 help 2362 This driver supports Broadcom NetXtremeII gigabit Ethernet cards. 2363 2364 To compile this driver as a module, choose M here: the module 2365 will be called bnx2. This is recommended. 2366 2367config CNIC 2368 tristate "Broadcom CNIC support" 2369 depends on PCI 2370 select BNX2 2371 select UIO 2372 help 2373 This driver supports offload features of Broadcom NetXtremeII 2374 gigabit Ethernet cards. 2375 2376 To compile this driver as a module, choose M here: the module 2377 will be called cnic. This is recommended. 2378 2379config SPIDER_NET 2380 tristate "Spider Gigabit Ethernet driver" 2381 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB) 2382 select FW_LOADER 2383 help 2384 This driver supports the Gigabit Ethernet chips present on the 2385 Cell Processor-Based Blades from IBM. 2386 2387config TSI108_ETH 2388 tristate "Tundra TSI108 gigabit Ethernet support" 2389 depends on TSI108_BRIDGE 2390 help 2391 This driver supports Tundra TSI108 gigabit Ethernet ports. 2392 To compile this driver as a module, choose M here: the module 2393 will be called tsi108_eth. 2394 2395config GELIC_NET 2396 tristate "PS3 Gigabit Ethernet driver" 2397 depends on PPC_PS3 2398 select PS3_SYS_MANAGER 2399 help 2400 This driver supports the network device on the PS3 game 2401 console. This driver has built-in support for Ethernet. 2402 2403 To compile this driver as a module, choose M here: the 2404 module will be called ps3_gelic. 2405 2406config GELIC_WIRELESS 2407 bool "PS3 Wireless support" 2408 depends on WLAN 2409 depends on GELIC_NET 2410 select WIRELESS_EXT 2411 help 2412 This option adds the support for the wireless feature of PS3. 2413 If you have the wireless-less model of PS3 or have no plan to 2414 use wireless feature, disabling this option saves memory. As 2415 the driver automatically distinguishes the models, you can 2416 safely enable this option even if you have a wireless-less model. 2417 2418config FSL_PQ_MDIO 2419 tristate "Freescale PQ MDIO" 2420 depends on FSL_SOC 2421 select PHYLIB 2422 help 2423 This driver supports the MDIO bus used by the gianfar and UCC drivers. 2424 2425config GIANFAR 2426 tristate "Gianfar Ethernet" 2427 depends on FSL_SOC 2428 select FSL_PQ_MDIO 2429 select PHYLIB 2430 select CRC32 2431 help 2432 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx, 2433 and MPC86xx family of chips, and the FEC on the 8540. 2434 2435config UCC_GETH 2436 tristate "Freescale QE Gigabit Ethernet" 2437 depends on QUICC_ENGINE 2438 select FSL_PQ_MDIO 2439 select PHYLIB 2440 help 2441 This driver supports the Gigabit Ethernet mode of the QUICC Engine, 2442 which is available on some Freescale SOCs. 2443 2444config UGETH_TX_ON_DEMAND 2445 bool "Transmit on Demand support" 2446 depends on UCC_GETH 2447 2448config MV643XX_ETH 2449 tristate "Marvell Discovery (643XX) and Orion ethernet support" 2450 depends on (MV64X60 || PPC32 || PLAT_ORION) && INET 2451 select INET_LRO 2452 select PHYLIB 2453 help 2454 This driver supports the gigabit ethernet MACs in the 2455 Marvell Discovery PPC/MIPS chipset family (MV643XX) and 2456 in the Marvell Orion ARM SoC family. 2457 2458 Some boards that use the Discovery chipset are the Momenco 2459 Ocelot C and Jaguar ATX and Pegasos II. 2460 2461config XILINX_LL_TEMAC 2462 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver" 2463 depends on PPC || MICROBLAZE 2464 select PHYLIB 2465 help 2466 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC 2467 core used in Xilinx Spartan and Virtex FPGAs 2468 2469config QLA3XXX 2470 tristate "QLogic QLA3XXX Network Driver Support" 2471 depends on PCI 2472 help 2473 This driver supports QLogic ISP3XXX gigabit Ethernet cards. 2474 2475 To compile this driver as a module, choose M here: the module 2476 will be called qla3xxx. 2477 2478config ATL1 2479 tristate "Atheros/Attansic L1 Gigabit Ethernet support" 2480 depends on PCI 2481 select CRC32 2482 select MII 2483 help 2484 This driver supports the Atheros/Attansic L1 gigabit ethernet 2485 adapter. 2486 2487 To compile this driver as a module, choose M here. The module 2488 will be called atl1. 2489 2490config ATL1E 2491 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)" 2492 depends on PCI && EXPERIMENTAL 2493 select CRC32 2494 select MII 2495 help 2496 This driver supports the Atheros L1E gigabit ethernet adapter. 2497 2498 To compile this driver as a module, choose M here. The module 2499 will be called atl1e. 2500 2501config ATL1C 2502 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)" 2503 depends on PCI && EXPERIMENTAL 2504 select CRC32 2505 select MII 2506 help 2507 This driver supports the Atheros L1C gigabit ethernet adapter. 2508 2509 To compile this driver as a module, choose M here. The module 2510 will be called atl1c. 2511 2512config JME 2513 tristate "JMicron(R) PCI-Express Gigabit Ethernet support" 2514 depends on PCI 2515 select CRC32 2516 select MII 2517 ---help--- 2518 This driver supports the PCI-Express gigabit ethernet adapters 2519 based on JMicron JMC250 chipset. 2520 2521 To compile this driver as a module, choose M here. The module 2522 will be called jme. 2523 2524config S6GMAC 2525 tristate "S6105 GMAC ethernet support" 2526 depends on XTENSA_VARIANT_S6000 2527 select PHYLIB 2528 help 2529 This driver supports the on chip ethernet device on the 2530 S6105 xtensa processor. 2531 2532 To compile this driver as a module, choose M here. The module 2533 will be called s6gmac. 2534 2535source "drivers/net/stmmac/Kconfig" 2536 2537config PCH_GBE 2538 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GbE" 2539 depends on PCI 2540 select MII 2541 ---help--- 2542 This is a gigabit ethernet driver for EG20T PCH. 2543 EG20T PCH is the platform controller hub that is used in Intel's 2544 general embedded platform. 2545 EG20T PCH has Gigabit Ethernet interface. 2546 Using this interface, it is able to access system devices connected 2547 to Gigabit Ethernet. 2548 This driver enables Gigabit Ethernet function. 2549 2550 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/ 2551 Output Hub), ML7223. 2552 ML7223 IOH is for MP(Media Phone) use. 2553 ML7223 is companion chip for Intel Atom E6xx series. 2554 ML7223 is completely compatible for Intel EG20T PCH. 2555 2556config FTGMAC100 2557 tristate "Faraday FTGMAC100 Gigabit Ethernet support" 2558 depends on ARM 2559 select PHYLIB 2560 help 2561 This driver supports the FTGMAC100 Gigabit Ethernet controller 2562 from Faraday. It is used on Faraday A369, Andes AG102 and some 2563 other ARM/NDS32 SoC's. 2564 2565endif # NETDEV_1000 2566 2567# 2568# 10 Gigabit Ethernet 2569# 2570 2571menuconfig NETDEV_10000 2572 bool "Ethernet (10000 Mbit)" 2573 depends on !UML 2574 default y 2575 ---help--- 2576 Say Y here to get to see options for 10 Gigabit Ethernet drivers. 2577 This option alone does not add any kernel code. 2578 2579 If you say N, all options in this submenu will be skipped and disabled. 2580 2581if NETDEV_10000 2582 2583config MDIO 2584 tristate 2585 2586config CHELSIO_T1 2587 tristate "Chelsio 10Gb Ethernet support" 2588 depends on PCI 2589 select CRC32 2590 select MDIO 2591 help 2592 This driver supports Chelsio gigabit and 10-gigabit 2593 Ethernet cards. More information about adapter features and 2594 performance tuning is in <file:Documentation/networking/cxgb.txt>. 2595 2596 For general information about Chelsio and our products, visit 2597 our website at <http://www.chelsio.com>. 2598 2599 For customer support, please visit our customer support page at 2600 <http://www.chelsio.com/support.html>. 2601 2602 Please send feedback to <linux-bugs@chelsio.com>. 2603 2604 To compile this driver as a module, choose M here: the module 2605 will be called cxgb. 2606 2607config CHELSIO_T1_1G 2608 bool "Chelsio gigabit Ethernet support" 2609 depends on CHELSIO_T1 2610 help 2611 Enables support for Chelsio's gigabit Ethernet PCI cards. If you 2612 are using only 10G cards say 'N' here. 2613 2614config CHELSIO_T3 2615 tristate "Chelsio Communications T3 10Gb Ethernet support" 2616 depends on PCI && INET 2617 select FW_LOADER 2618 select MDIO 2619 help 2620 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet 2621 adapters. 2622 2623 For general information about Chelsio and our products, visit 2624 our website at <http://www.chelsio.com>. 2625 2626 For customer support, please visit our customer support page at 2627 <http://www.chelsio.com/support.html>. 2628 2629 Please send feedback to <linux-bugs@chelsio.com>. 2630 2631 To compile this driver as a module, choose M here: the module 2632 will be called cxgb3. 2633 2634config CHELSIO_T4 2635 tristate "Chelsio Communications T4 Ethernet support" 2636 depends on PCI 2637 select FW_LOADER 2638 select MDIO 2639 help 2640 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet 2641 adapters. 2642 2643 For general information about Chelsio and our products, visit 2644 our website at <http://www.chelsio.com>. 2645 2646 For customer support, please visit our customer support page at 2647 <http://www.chelsio.com/support.html>. 2648 2649 Please send feedback to <linux-bugs@chelsio.com>. 2650 2651 To compile this driver as a module choose M here; the module 2652 will be called cxgb4. 2653 2654config CHELSIO_T4VF 2655 tristate "Chelsio Communications T4 Virtual Function Ethernet support" 2656 depends on PCI 2657 help 2658 This driver supports Chelsio T4-based gigabit and 10Gb Ethernet 2659 adapters with PCI-E SR-IOV Virtual Functions. 2660 2661 For general information about Chelsio and our products, visit 2662 our website at <http://www.chelsio.com>. 2663 2664 For customer support, please visit our customer support page at 2665 <http://www.chelsio.com/support.html>. 2666 2667 Please send feedback to <linux-bugs@chelsio.com>. 2668 2669 To compile this driver as a module choose M here; the module 2670 will be called cxgb4vf. 2671 2672config EHEA 2673 tristate "eHEA Ethernet support" 2674 depends on IBMEBUS && INET && SPARSEMEM 2675 select INET_LRO 2676 ---help--- 2677 This driver supports the IBM pSeries eHEA ethernet adapter. 2678 2679 To compile the driver as a module, choose M here. The module 2680 will be called ehea. 2681 2682config ENIC 2683 tristate "Cisco VIC Ethernet NIC Support" 2684 depends on PCI && INET 2685 help 2686 This enables the support for the Cisco VIC Ethernet card. 2687 2688config IXGBE 2689 tristate "Intel(R) 10GbE PCI Express adapters support" 2690 depends on PCI && INET 2691 select MDIO 2692 ---help--- 2693 This driver supports Intel(R) 10GbE PCI Express family of 2694 adapters. For more information on how to identify your adapter, go 2695 to the Adapter & Driver ID Guide at: 2696 2697 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2698 2699 For general information and support, go to the Intel support 2700 website at: 2701 2702 <http://support.intel.com> 2703 2704 To compile this driver as a module, choose M here. The module 2705 will be called ixgbe. 2706 2707config IXGBE_DCA 2708 bool "Direct Cache Access (DCA) Support" 2709 default y 2710 depends on IXGBE && DCA && !(IXGBE=y && DCA=m) 2711 ---help--- 2712 Say Y here if you want to use Direct Cache Access (DCA) in the 2713 driver. DCA is a method for warming the CPU cache before data 2714 is used, with the intent of lessening the impact of cache misses. 2715 2716config IXGBE_DCB 2717 bool "Data Center Bridging (DCB) Support" 2718 default n 2719 depends on IXGBE && DCB 2720 ---help--- 2721 Say Y here if you want to use Data Center Bridging (DCB) in the 2722 driver. 2723 2724 If unsure, say N. 2725 2726config IXGBEVF 2727 tristate "Intel(R) 82599 Virtual Function Ethernet support" 2728 depends on PCI_MSI 2729 ---help--- 2730 This driver supports Intel(R) 82599 virtual functions. For more 2731 information on how to identify your adapter, go to the Adapter & 2732 Driver ID Guide at: 2733 2734 <http://support.intel.com/support/network/sb/CS-008441.htm> 2735 2736 For general information and support, go to the Intel support 2737 website at: 2738 2739 <http://support.intel.com> 2740 2741 More specific information on configuring the driver is in 2742 <file:Documentation/networking/ixgbevf.txt>. 2743 2744 To compile this driver as a module, choose M here. The module 2745 will be called ixgbevf. MSI-X interrupt support is required 2746 for this driver to work correctly. 2747 2748config IXGB 2749 tristate "Intel(R) PRO/10GbE support" 2750 depends on PCI 2751 ---help--- 2752 This driver supports Intel(R) PRO/10GbE family of adapters for 2753 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver 2754 instead. For more information on how to identify your adapter, go 2755 to the Adapter & Driver ID Guide at: 2756 2757 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2758 2759 For general information and support, go to the Intel support 2760 website at: 2761 2762 <http://support.intel.com> 2763 2764 More specific information on configuring the driver is in 2765 <file:Documentation/networking/ixgb.txt>. 2766 2767 To compile this driver as a module, choose M here. The module 2768 will be called ixgb. 2769 2770config S2IO 2771 tristate "Exar Xframe 10Gb Ethernet Adapter" 2772 depends on PCI 2773 ---help--- 2774 This driver supports Exar Corp's Xframe Series 10Gb Ethernet Adapters. 2775 2776 More specific information on configuring the driver is in 2777 <file:Documentation/networking/s2io.txt>. 2778 2779 To compile this driver as a module, choose M here. The module 2780 will be called s2io. 2781 2782config VXGE 2783 tristate "Exar X3100 Series 10GbE PCIe Server Adapter" 2784 depends on PCI && INET 2785 ---help--- 2786 This driver supports Exar Corp's X3100 Series 10 GbE PCIe 2787 I/O Virtualized Server Adapter. 2788 2789 More specific information on configuring the driver is in 2790 <file:Documentation/networking/vxge.txt>. 2791 2792 To compile this driver as a module, choose M here. The module 2793 will be called vxge. 2794 2795config VXGE_DEBUG_TRACE_ALL 2796 bool "Enabling All Debug trace statments in driver" 2797 default n 2798 depends on VXGE 2799 ---help--- 2800 Say Y here if you want to enabling all the debug trace statements in 2801 the vxge driver. By default only few debug trace statements are 2802 enabled. 2803 2804config MYRI10GE 2805 tristate "Myricom Myri-10G Ethernet support" 2806 depends on PCI && INET 2807 select FW_LOADER 2808 select CRC32 2809 select INET_LRO 2810 ---help--- 2811 This driver supports Myricom Myri-10G Dual Protocol interface in 2812 Ethernet mode. If the eeprom on your board is not recent enough, 2813 you will need a newer firmware image. 2814 You may get this image or more information, at: 2815 2816 <http://www.myri.com/scs/download-Myri10GE.html> 2817 2818 To compile this driver as a module, choose M here. The module 2819 will be called myri10ge. 2820 2821config MYRI10GE_DCA 2822 bool "Direct Cache Access (DCA) Support" 2823 default y 2824 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m) 2825 ---help--- 2826 Say Y here if you want to use Direct Cache Access (DCA) in the 2827 driver. DCA is a method for warming the CPU cache before data 2828 is used, with the intent of lessening the impact of cache misses. 2829 2830config NETXEN_NIC 2831 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC" 2832 depends on PCI 2833 select FW_LOADER 2834 help 2835 This enables the support for NetXen's Gigabit Ethernet card. 2836 2837config NIU 2838 tristate "Sun Neptune 10Gbit Ethernet support" 2839 depends on PCI 2840 select CRC32 2841 help 2842 This enables support for cards based upon Sun's 2843 Neptune chipset. 2844 2845config PASEMI_MAC 2846 tristate "PA Semi 1/10Gbit MAC" 2847 depends on PPC_PASEMI && PCI && INET 2848 select PHYLIB 2849 select INET_LRO 2850 help 2851 This driver supports the on-chip 1/10Gbit Ethernet controller on 2852 PA Semi's PWRficient line of chips. 2853 2854config MLX4_EN 2855 tristate "Mellanox Technologies 10Gbit Ethernet support" 2856 depends on PCI && INET 2857 select MLX4_CORE 2858 select INET_LRO 2859 help 2860 This driver supports Mellanox Technologies ConnectX Ethernet 2861 devices. 2862 2863config MLX4_CORE 2864 tristate 2865 depends on PCI 2866 default n 2867 2868config MLX4_DEBUG 2869 bool "Verbose debugging output" if (MLX4_CORE && EXPERT) 2870 depends on MLX4_CORE 2871 default y 2872 ---help--- 2873 This option causes debugging code to be compiled into the 2874 mlx4_core driver. The output can be turned on via the 2875 debug_level module parameter (which can also be set after 2876 the driver is loaded through sysfs). 2877 2878config TEHUTI 2879 tristate "Tehuti Networks 10G Ethernet" 2880 depends on PCI 2881 help 2882 Tehuti Networks 10G Ethernet NIC 2883 2884config BNX2X 2885 tristate "Broadcom NetXtremeII 10Gb support" 2886 depends on PCI 2887 select FW_LOADER 2888 select ZLIB_INFLATE 2889 select LIBCRC32C 2890 select MDIO 2891 help 2892 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards. 2893 To compile this driver as a module, choose M here: the module 2894 will be called bnx2x. This is recommended. 2895 2896config QLCNIC 2897 tristate "QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support" 2898 depends on PCI 2899 select FW_LOADER 2900 help 2901 This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet 2902 devices. 2903 2904config QLGE 2905 tristate "QLogic QLGE 10Gb Ethernet Driver Support" 2906 depends on PCI 2907 help 2908 This driver supports QLogic ISP8XXX 10Gb Ethernet cards. 2909 2910 To compile this driver as a module, choose M here: the module 2911 will be called qlge. 2912 2913config BNA 2914 tristate "Brocade 1010/1020 10Gb Ethernet Driver support" 2915 depends on PCI 2916 ---help--- 2917 This driver supports Brocade 1010/1020 10Gb CEE capable Ethernet 2918 cards. 2919 To compile this driver as a module, choose M here: the module 2920 will be called bna. 2921 2922 For general information and support, go to the Brocade support 2923 website at: 2924 2925 <http://support.brocade.com> 2926 2927source "drivers/net/sfc/Kconfig" 2928 2929source "drivers/net/benet/Kconfig" 2930 2931endif # NETDEV_10000 2932 2933source "drivers/net/tokenring/Kconfig" 2934 2935source "drivers/net/wireless/Kconfig" 2936 2937source "drivers/net/wimax/Kconfig" 2938 2939source "drivers/net/usb/Kconfig" 2940 2941source "drivers/net/pcmcia/Kconfig" 2942 2943source "drivers/net/wan/Kconfig" 2944 2945source "drivers/atm/Kconfig" 2946 2947source "drivers/ieee802154/Kconfig" 2948 2949source "drivers/s390/net/Kconfig" 2950 2951source "drivers/net/caif/Kconfig" 2952 2953config TILE_NET 2954 tristate "Tilera GBE/XGBE network driver support" 2955 depends on TILE 2956 default y 2957 select CRC32 2958 help 2959 This is a standard Linux network device driver for the 2960 on-chip Tilera Gigabit Ethernet and XAUI interfaces. 2961 2962 To compile this driver as a module, choose M here: the module 2963 will be called tile_net. 2964 2965config XEN_NETDEV_FRONTEND 2966 tristate "Xen network device frontend driver" 2967 depends on XEN 2968 select XEN_XENBUS_FRONTEND 2969 default y 2970 help 2971 This driver provides support for Xen paravirtual network 2972 devices exported by a Xen network driver domain (often 2973 domain 0). 2974 2975 The corresponding Linux backend driver is enabled by the 2976 CONFIG_XEN_NETDEV_BACKEND option. 2977 2978 If you are compiling a kernel for use as Xen guest, you 2979 should say Y here. To compile this driver as a module, chose 2980 M here: the module will be called xen-netfront. 2981 2982config XEN_NETDEV_BACKEND 2983 tristate "Xen backend network device" 2984 depends on XEN_BACKEND 2985 help 2986 This driver allows the kernel to act as a Xen network driver 2987 domain which exports paravirtual network devices to other 2988 Xen domains. These devices can be accessed by any operating 2989 system that implements a compatible front end. 2990 2991 The corresponding Linux frontend driver is enabled by the 2992 CONFIG_XEN_NETDEV_FRONTEND configuration option. 2993 2994 The backend driver presents a standard network device 2995 endpoint for each paravirtual network device to the driver 2996 domain network stack. These can then be bridged or routed 2997 etc in order to provide full network connectivity. 2998 2999 If you are compiling a kernel to run in a Xen network driver 3000 domain (often this is domain 0) you should say Y here. To 3001 compile this driver as a module, chose M here: the module 3002 will be called xen-netback. 3003 3004config ISERIES_VETH 3005 tristate "iSeries Virtual Ethernet driver support" 3006 depends on PPC_ISERIES 3007 3008config RIONET 3009 tristate "RapidIO Ethernet over messaging driver support" 3010 depends on RAPIDIO 3011 3012config RIONET_TX_SIZE 3013 int "Number of outbound queue entries" 3014 depends on RIONET 3015 default "128" 3016 3017config RIONET_RX_SIZE 3018 int "Number of inbound queue entries" 3019 depends on RIONET 3020 default "128" 3021 3022config FDDI 3023 tristate "FDDI driver support" 3024 depends on (PCI || EISA || TC) 3025 help 3026 Fiber Distributed Data Interface is a high speed local area network 3027 design; essentially a replacement for high speed Ethernet. FDDI can 3028 run over copper or fiber. If you are connected to such a network and 3029 want a driver for the FDDI card in your computer, say Y here (and 3030 then also Y to the driver for your FDDI card, below). Most people 3031 will say N. 3032 3033config DEFXX 3034 tristate "Digital DEFTA/DEFEA/DEFPA adapter support" 3035 depends on FDDI && (PCI || EISA || TC) 3036 ---help--- 3037 This is support for the DIGITAL series of TURBOchannel (DEFTA), 3038 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you 3039 to a local FDDI network. 3040 3041 To compile this driver as a module, choose M here: the module 3042 will be called defxx. If unsure, say N. 3043 3044config DEFXX_MMIO 3045 bool 3046 prompt "Use MMIO instead of PIO" if PCI || EISA 3047 depends on DEFXX 3048 default n if PCI || EISA 3049 default y 3050 ---help--- 3051 This instructs the driver to use EISA or PCI memory-mapped I/O 3052 (MMIO) as appropriate instead of programmed I/O ports (PIO). 3053 Enabling this gives an improvement in processing time in parts 3054 of the driver, but it may cause problems with EISA (DEFEA) 3055 adapters. TURBOchannel does not have the concept of I/O ports, 3056 so MMIO is always used for these (DEFTA) adapters. 3057 3058 If unsure, say N. 3059 3060config SKFP 3061 tristate "SysKonnect FDDI PCI support" 3062 depends on FDDI && PCI 3063 select BITREVERSE 3064 ---help--- 3065 Say Y here if you have a SysKonnect FDDI PCI adapter. 3066 The following adapters are supported by this driver: 3067 - SK-5521 (SK-NET FDDI-UP) 3068 - SK-5522 (SK-NET FDDI-UP DAS) 3069 - SK-5541 (SK-NET FDDI-FP) 3070 - SK-5543 (SK-NET FDDI-LP) 3071 - SK-5544 (SK-NET FDDI-LP DAS) 3072 - SK-5821 (SK-NET FDDI-UP64) 3073 - SK-5822 (SK-NET FDDI-UP64 DAS) 3074 - SK-5841 (SK-NET FDDI-FP64) 3075 - SK-5843 (SK-NET FDDI-LP64) 3076 - SK-5844 (SK-NET FDDI-LP64 DAS) 3077 - Netelligent 100 FDDI DAS Fibre SC 3078 - Netelligent 100 FDDI SAS Fibre SC 3079 - Netelligent 100 FDDI DAS UTP 3080 - Netelligent 100 FDDI SAS UTP 3081 - Netelligent 100 FDDI SAS Fibre MIC 3082 3083 Read <file:Documentation/networking/skfp.txt> for information about 3084 the driver. 3085 3086 Questions concerning this driver can be addressed to: 3087 <linux@syskonnect.de> 3088 3089 To compile this driver as a module, choose M here: the module 3090 will be called skfp. This is recommended. 3091 3092config HIPPI 3093 bool "HIPPI driver support (EXPERIMENTAL)" 3094 depends on EXPERIMENTAL && INET && PCI 3095 help 3096 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and 3097 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI 3098 can run over copper (25m) or fiber (300m on multi-mode or 10km on 3099 single-mode). HIPPI networks are commonly used for clusters and to 3100 connect to super computers. If you are connected to a HIPPI network 3101 and have a HIPPI network card in your computer that you want to use 3102 under Linux, say Y here (you must also remember to enable the driver 3103 for your HIPPI card below). Most people will say N here. 3104 3105config ROADRUNNER 3106 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)" 3107 depends on HIPPI && PCI 3108 help 3109 Say Y here if this is your PCI HIPPI network card. 3110 3111 To compile this driver as a module, choose M here: the module 3112 will be called rrunner. If unsure, say N. 3113 3114config ROADRUNNER_LARGE_RINGS 3115 bool "Use large TX/RX rings (EXPERIMENTAL)" 3116 depends on ROADRUNNER 3117 help 3118 If you say Y here, the RoadRunner driver will preallocate up to 2 MB 3119 of additional memory to allow for fastest operation, both for 3120 transmitting and receiving. This memory cannot be used by any other 3121 kernel code or by user space programs. Say Y here only if you have 3122 the memory. 3123 3124config PLIP 3125 tristate "PLIP (parallel port) support" 3126 depends on PARPORT 3127 ---help--- 3128 PLIP (Parallel Line Internet Protocol) is used to create a 3129 reasonably fast mini network consisting of two (or, rarely, more) 3130 local machines. A PLIP link from a Linux box is a popular means to 3131 install a Linux distribution on a machine which doesn't have a 3132 CD-ROM drive (a minimal system has to be transferred with floppies 3133 first). The kernels on both machines need to have this PLIP option 3134 enabled for this to work. 3135 3136 The PLIP driver has two modes, mode 0 and mode 1. The parallel 3137 ports (the connectors at the computers with 25 holes) are connected 3138 with "null printer" or "Turbo Laplink" cables which can transmit 4 3139 bits at a time (mode 0) or with special PLIP cables, to be used on 3140 bidirectional parallel ports only, which can transmit 8 bits at a 3141 time (mode 1); you can find the wiring of these cables in 3142 <file:Documentation/networking/PLIP.txt>. The cables can be up to 3143 15m long. Mode 0 works also if one of the machines runs DOS/Windows 3144 and has some PLIP software installed, e.g. the Crynwr PLIP packet 3145 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>) 3146 and winsock or NCSA's telnet. 3147 3148 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well 3149 as the NET-3-HOWTO, both available from 3150 <http://www.tldp.org/docs.html#howto>. Note that the PLIP 3151 protocol has been changed and this PLIP driver won't work together 3152 with the PLIP support in Linux versions 1.0.x. This option enlarges 3153 your kernel by about 8 KB. 3154 3155 To compile this driver as a module, choose M here. The module 3156 will be called plip. If unsure, say Y or M, in case you buy 3157 a laptop later. 3158 3159config PPP 3160 tristate "PPP (point-to-point protocol) support" 3161 select SLHC 3162 ---help--- 3163 PPP (Point to Point Protocol) is a newer and better SLIP. It serves 3164 the same purpose: sending Internet traffic over telephone (and other 3165 serial) lines. Ask your access provider if they support it, because 3166 otherwise you can't use it; most Internet access providers these 3167 days support PPP rather than SLIP. 3168 3169 To use PPP, you need an additional program called pppd as described 3170 in the PPP-HOWTO, available at 3171 <http://www.tldp.org/docs.html#howto>. Make sure that you have 3172 the version of pppd recommended in <file:Documentation/Changes>. 3173 The PPP option enlarges your kernel by about 16 KB. 3174 3175 There are actually two versions of PPP: the traditional PPP for 3176 asynchronous lines, such as regular analog phone lines, and 3177 synchronous PPP which can be used over digital ISDN lines for 3178 example. If you want to use PPP over phone lines or other 3179 asynchronous serial lines, you need to say Y (or M) here and also to 3180 the next option, "PPP support for async serial ports". For PPP over 3181 synchronous lines, you should say Y (or M) here and to "Support 3182 synchronous PPP", below. 3183 3184 If you said Y to "Version information on all symbols" above, then 3185 you cannot compile the PPP driver into the kernel; you can then only 3186 compile it as a module. To compile this driver as a module, choose M 3187 here. The module will be called ppp_generic. 3188 3189config PPP_MULTILINK 3190 bool "PPP multilink support (EXPERIMENTAL)" 3191 depends on PPP && EXPERIMENTAL 3192 help 3193 PPP multilink is a protocol (defined in RFC 1990) which allows you 3194 to combine several (logical or physical) lines into one logical PPP 3195 connection, so that you can utilize your full bandwidth. 3196 3197 This has to be supported at the other end as well and you need a 3198 version of the pppd daemon which understands the multilink protocol. 3199 3200 If unsure, say N. 3201 3202config PPP_FILTER 3203 bool "PPP filtering" 3204 depends on PPP 3205 help 3206 Say Y here if you want to be able to filter the packets passing over 3207 PPP interfaces. This allows you to control which packets count as 3208 activity (i.e. which packets will reset the idle timer or bring up 3209 a demand-dialed link) and which packets are to be dropped entirely. 3210 You need to say Y here if you wish to use the pass-filter and 3211 active-filter options to pppd. 3212 3213 If unsure, say N. 3214 3215config PPP_ASYNC 3216 tristate "PPP support for async serial ports" 3217 depends on PPP 3218 select CRC_CCITT 3219 ---help--- 3220 Say Y (or M) here if you want to be able to use PPP over standard 3221 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use 3222 a modem (not a synchronous or ISDN modem) to contact your ISP, you 3223 need this option. 3224 3225 To compile this driver as a module, choose M here. 3226 3227 If unsure, say Y. 3228 3229config PPP_SYNC_TTY 3230 tristate "PPP support for sync tty ports" 3231 depends on PPP 3232 help 3233 Say Y (or M) here if you want to be able to use PPP over synchronous 3234 (HDLC) tty devices, such as the SyncLink adapter. These devices 3235 are often used for high-speed leased lines like T1/E1. 3236 3237 To compile this driver as a module, choose M here. 3238 3239config PPP_DEFLATE 3240 tristate "PPP Deflate compression" 3241 depends on PPP 3242 select ZLIB_INFLATE 3243 select ZLIB_DEFLATE 3244 ---help--- 3245 Support for the Deflate compression method for PPP, which uses the 3246 Deflate algorithm (the same algorithm that gzip uses) to compress 3247 each PPP packet before it is sent over the wire. The machine at the 3248 other end of the PPP link (usually your ISP) has to support the 3249 Deflate compression method as well for this to be useful. Even if 3250 they don't support it, it is safe to say Y here. 3251 3252 To compile this driver as a module, choose M here. 3253 3254config PPP_BSDCOMP 3255 tristate "PPP BSD-Compress compression" 3256 depends on PPP 3257 ---help--- 3258 Support for the BSD-Compress compression method for PPP, which uses 3259 the LZW compression method to compress each PPP packet before it is 3260 sent over the wire. The machine at the other end of the PPP link 3261 (usually your ISP) has to support the BSD-Compress compression 3262 method as well for this to be useful. Even if they don't support it, 3263 it is safe to say Y here. 3264 3265 The PPP Deflate compression method ("PPP Deflate compression", 3266 above) is preferable to BSD-Compress, because it compresses better 3267 and is patent-free. 3268 3269 Note that the BSD compression code will always be compiled as a 3270 module; it is called bsd_comp and will show up in the directory 3271 modules once you have said "make modules". If unsure, say N. 3272 3273config PPP_MPPE 3274 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)" 3275 depends on PPP && EXPERIMENTAL 3276 select CRYPTO 3277 select CRYPTO_SHA1 3278 select CRYPTO_ARC4 3279 select CRYPTO_ECB 3280 ---help--- 3281 Support for the MPPE Encryption protocol, as employed by the 3282 Microsoft Point-to-Point Tunneling Protocol. 3283 3284 See http://pptpclient.sourceforge.net/ for information on 3285 configuring PPTP clients and servers to utilize this method. 3286 3287config PPPOE 3288 tristate "PPP over Ethernet (EXPERIMENTAL)" 3289 depends on EXPERIMENTAL && PPP 3290 help 3291 Support for PPP over Ethernet. 3292 3293 This driver requires the latest version of pppd from the CVS 3294 repository at cvs.samba.org. Alternatively, see the 3295 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>) 3296 which contains instruction on how to use this driver (under 3297 the heading "Kernel mode PPPoE"). 3298 3299config PPTP 3300 tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)" 3301 depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX 3302 help 3303 Support for PPP over IPv4.(Point-to-Point Tunneling Protocol) 3304 3305 This driver requires pppd plugin to work in client mode or 3306 modified pptpd (poptop) to work in server mode. 3307 See http://accel-pptp.sourceforge.net/ for information how to 3308 utilize this module. 3309 3310config PPPOATM 3311 tristate "PPP over ATM" 3312 depends on ATM && PPP 3313 help 3314 Support PPP (Point to Point Protocol) encapsulated in ATM frames. 3315 This implementation does not yet comply with section 8 of RFC2364, 3316 which can lead to bad results if the ATM peer loses state and 3317 changes its encapsulation unilaterally. 3318 3319config PPPOL2TP 3320 tristate "PPP over L2TP (EXPERIMENTAL)" 3321 depends on EXPERIMENTAL && L2TP && PPP 3322 help 3323 Support for PPP-over-L2TP socket family. L2TP is a protocol 3324 used by ISPs and enterprises to tunnel PPP traffic over UDP 3325 tunnels. L2TP is replacing PPTP for VPN uses. 3326 3327config SLIP 3328 tristate "SLIP (serial line) support" 3329 ---help--- 3330 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to 3331 connect to your Internet service provider or to connect to some 3332 other local Unix box or if you want to configure your Linux box as a 3333 Slip/CSlip server for other people to dial in. SLIP (Serial Line 3334 Internet Protocol) is a protocol used to send Internet traffic over 3335 serial connections such as telephone lines or null modem cables; 3336 nowadays, the protocol PPP is more commonly used for this same 3337 purpose. 3338 3339 Normally, your access provider has to support SLIP in order for you 3340 to be able to use it, but there is now a SLIP emulator called SLiRP 3341 around (available from 3342 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which 3343 allows you to use SLIP over a regular dial up shell connection. If 3344 you plan to use SLiRP, make sure to say Y to CSLIP, below. The 3345 NET-3-HOWTO, available from 3346 <http://www.tldp.org/docs.html#howto>, explains how to 3347 configure SLIP. Note that you don't need this option if you just 3348 want to run term (term is a program which gives you almost full 3349 Internet connectivity if you have a regular dial up shell account on 3350 some Internet connected Unix computer. Read 3351 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP 3352 support will enlarge your kernel by about 4 KB. If unsure, say N. 3353 3354 To compile this driver as a module, choose M here. The module 3355 will be called slip. 3356 3357config SLIP_COMPRESSED 3358 bool "CSLIP compressed headers" 3359 depends on SLIP 3360 select SLHC 3361 ---help--- 3362 This protocol is faster than SLIP because it uses compression on the 3363 TCP/IP headers (not on the data itself), but it has to be supported 3364 on both ends. Ask your access provider if you are not sure and 3365 answer Y, just in case. You will still be able to use plain SLIP. If 3366 you plan to use SLiRP, the SLIP emulator (available from 3367 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which 3368 allows you to use SLIP over a regular dial up shell connection, you 3369 definitely want to say Y here. The NET-3-HOWTO, available from 3370 <http://www.tldp.org/docs.html#howto>, explains how to configure 3371 CSLIP. This won't enlarge your kernel. 3372 3373config SLHC 3374 tristate 3375 help 3376 This option enables Van Jacobsen serial line header compression 3377 routines. 3378 3379config SLIP_SMART 3380 bool "Keepalive and linefill" 3381 depends on SLIP 3382 help 3383 Adds additional capabilities to the SLIP driver to support the 3384 RELCOM line fill and keepalive monitoring. Ideal on poor quality 3385 analogue lines. 3386 3387config SLIP_MODE_SLIP6 3388 bool "Six bit SLIP encapsulation" 3389 depends on SLIP 3390 help 3391 Just occasionally you may need to run IP over hostile serial 3392 networks that don't pass all control characters or are only seven 3393 bit. Saying Y here adds an extra mode you can use with SLIP: 3394 "slip6". In this mode, SLIP will only send normal ASCII symbols over 3395 the serial device. Naturally, this has to be supported at the other 3396 end of the link as well. It's good enough, for example, to run IP 3397 over the async ports of a Camtec JNT Pad. If unsure, say N. 3398 3399config NET_FC 3400 bool "Fibre Channel driver support" 3401 depends on SCSI && PCI 3402 help 3403 Fibre Channel is a high speed serial protocol mainly used to connect 3404 large storage devices to the computer; it is compatible with and 3405 intended to replace SCSI. 3406 3407 If you intend to use Fibre Channel, you need to have a Fibre channel 3408 adaptor card in your computer; say Y here and to the driver for your 3409 adaptor below. You also should have said Y to "SCSI support" and 3410 "SCSI generic support". 3411 3412config NETCONSOLE 3413 tristate "Network console logging support" 3414 ---help--- 3415 If you want to log kernel messages over the network, enable this. 3416 See <file:Documentation/networking/netconsole.txt> for details. 3417 3418config NETCONSOLE_DYNAMIC 3419 bool "Dynamic reconfiguration of logging targets" 3420 depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \ 3421 !(NETCONSOLE=y && CONFIGFS_FS=m) 3422 help 3423 This option enables the ability to dynamically reconfigure target 3424 parameters (interface, IP addresses, port numbers, MAC addresses) 3425 at runtime through a userspace interface exported using configfs. 3426 See <file:Documentation/networking/netconsole.txt> for details. 3427 3428config NETPOLL 3429 def_bool NETCONSOLE 3430 3431config NETPOLL_TRAP 3432 bool "Netpoll traffic trapping" 3433 default n 3434 depends on NETPOLL 3435 3436config NET_POLL_CONTROLLER 3437 def_bool NETPOLL 3438 3439config VIRTIO_NET 3440 tristate "Virtio network driver (EXPERIMENTAL)" 3441 depends on EXPERIMENTAL && VIRTIO 3442 ---help--- 3443 This is the virtual network driver for virtio. It can be used with 3444 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M. 3445 3446config VMXNET3 3447 tristate "VMware VMXNET3 ethernet driver" 3448 depends on PCI && INET 3449 help 3450 This driver supports VMware's vmxnet3 virtual ethernet NIC. 3451 To compile this driver as a module, choose M here: the 3452 module will be called vmxnet3. 3453 3454endif # NETDEVICES 3455