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