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