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