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