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