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