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