Kconfig revision e06d41d09f314a1664ad60e46934b0ac131c6fa2
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 bool "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 SMC9194 891 tristate "SMC 9194 support" 892 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN) 893 select CRC32 894 ---help--- 895 This is support for the SMC9xxx based Ethernet cards. Choose this 896 option if you have a DELL laptop with the docking station, or 897 another SMC9192/9194 based chipset. Say Y if you want it compiled 898 into the kernel, and read the file 899 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO, 900 available from <http://www.tldp.org/docs.html#howto>. 901 902 To compile this driver as a module, choose M here. The module 903 will be called smc9194. 904 905config SMC91X 906 tristate "SMC 91C9x/91C1xxx support" 907 select CRC32 908 select MII 909 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \ 910 MIPS || BLACKFIN || MN10300 911 help 912 This is a driver for SMC's 91x series of Ethernet chipsets, 913 including the SMC91C94 and the SMC91C111. Say Y if you want it 914 compiled into the kernel, and read the file 915 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO, 916 available from <http://www.linuxdoc.org/docs.html#howto>. 917 918 This driver is also available as a module ( = code which can be 919 inserted in and removed from the running kernel whenever you want). 920 The module will be called smc91x. If you want to compile it as a 921 module, say M here and read <file:Documentation/kbuild/modules.txt>. 922 923config NET_NETX 924 tristate "NetX Ethernet support" 925 select MII 926 depends on ARCH_NETX 927 help 928 This is support for the Hilscher netX builtin Ethernet ports 929 930 To compile this driver as a module, choose M here. The module 931 will be called netx-eth. 932 933config TI_DAVINCI_EMAC 934 tristate "TI DaVinci EMAC Support" 935 depends on ARM && ARCH_DAVINCI 936 select PHYLIB 937 help 938 This driver supports TI's DaVinci Ethernet . 939 940 To compile this driver as a module, choose M here: the module 941 will be called davinci_emac_driver. This is recommended. 942 943config DM9000 944 tristate "DM9000 support" 945 depends on ARM || BLACKFIN || MIPS 946 select CRC32 947 select MII 948 ---help--- 949 Support for DM9000 chipset. 950 951 To compile this driver as a module, choose M here. The module 952 will be called dm9000. 953 954config DM9000_DEBUGLEVEL 955 int "DM9000 maximum debug level" 956 depends on DM9000 957 default 4 958 help 959 The maximum level of debugging code compiled into the DM9000 960 driver. 961 962config DM9000_FORCE_SIMPLE_PHY_POLL 963 bool "Force simple NSR based PHY polling" 964 depends on DM9000 965 ---help--- 966 This configuration forces the DM9000 to use the NSR's LinkStatus 967 bit to determine if the link is up or down instead of the more 968 costly MII PHY reads. Note, this will not work if the chip is 969 operating with an external PHY. 970 971config ENC28J60 972 tristate "ENC28J60 support" 973 depends on EXPERIMENTAL && SPI && NET_ETHERNET 974 select CRC32 975 ---help--- 976 Support for the Microchip EN28J60 ethernet chip. 977 978 To compile this driver as a module, choose M here. The module will be 979 called enc28j60. 980 981config ENC28J60_WRITEVERIFY 982 bool "Enable write verify" 983 depends on ENC28J60 984 ---help--- 985 Enable the verify after the buffer write useful for debugging purpose. 986 If unsure, say N. 987 988config ETHOC 989 tristate "OpenCores 10/100 Mbps Ethernet MAC support" 990 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA 991 select MII 992 select PHYLIB 993 select CRC32 994 select BITREVERSE 995 help 996 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC. 997 998config SMC911X 999 tristate "SMSC LAN911[5678] support" 1000 select CRC32 1001 select MII 1002 depends on ARM || SUPERH 1003 help 1004 This is a driver for SMSC's LAN911x series of Ethernet chipsets 1005 including the new LAN9115, LAN9116, LAN9117, and LAN9118. 1006 Say Y if you want it compiled into the kernel, 1007 and read the Ethernet-HOWTO, available from 1008 <http://www.linuxdoc.org/docs.html#howto>. 1009 1010 This driver is also available as a module. The module will be 1011 called smc911x. If you want to compile it as a module, say M 1012 here and read <file:Documentation/kbuild/modules.txt> 1013 1014config SMSC911X 1015 tristate "SMSC LAN911x/LAN921x families embedded ethernet support" 1016 depends on ARM || SUPERH || BLACKFIN || MIPS 1017 select CRC32 1018 select MII 1019 select PHYLIB 1020 ---help--- 1021 Say Y here if you want support for SMSC LAN911x and LAN921x families 1022 of ethernet controllers. 1023 1024 To compile this driver as a module, choose M here and read 1025 <file:Documentation/networking/net-modules.txt>. The module 1026 will be called smsc911x. 1027 1028config NET_VENDOR_RACAL 1029 bool "Racal-Interlan (Micom) NI cards" 1030 depends on ISA 1031 help 1032 If you have a network (Ethernet) card belonging to this class, such 1033 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO, 1034 available from <http://www.tldp.org/docs.html#howto>. 1035 1036 Note that the answer to this question doesn't directly affect the 1037 kernel: saying N will just cause the configurator to skip all 1038 the questions about NI cards. If you say Y, you will be asked for 1039 your specific card in the following questions. 1040 1041config NI5010 1042 tristate "NI5010 support (EXPERIMENTAL)" 1043 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP 1044 ---help--- 1045 If you have a network (Ethernet) card of this type, say Y and read 1046 the Ethernet-HOWTO, available from 1047 <http://www.tldp.org/docs.html#howto>. Note that this is still 1048 experimental code. 1049 1050 To compile this driver as a module, choose M here. The module 1051 will be called ni5010. 1052 1053config NI52 1054 tristate "NI5210 support" 1055 depends on NET_VENDOR_RACAL && ISA 1056 help 1057 If you have a network (Ethernet) card of this type, say Y and read 1058 the Ethernet-HOWTO, available from 1059 <http://www.tldp.org/docs.html#howto>. 1060 1061 To compile this driver as a module, choose M here. The module 1062 will be called ni52. 1063 1064config NI65 1065 tristate "NI6510 support" 1066 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API 1067 help 1068 If you have a network (Ethernet) card of this type, say Y and read 1069 the Ethernet-HOWTO, available from 1070 <http://www.tldp.org/docs.html#howto>. 1071 1072 To compile this driver as a module, choose M here. The module 1073 will be called ni65. 1074 1075config DNET 1076 tristate "Dave ethernet support (DNET)" 1077 depends on NET_ETHERNET && HAS_IOMEM 1078 select PHYLIB 1079 help 1080 The Dave ethernet interface (DNET) is found on Qong Board FPGA. 1081 Say Y to include support for the DNET chip. 1082 1083 To compile this driver as a module, choose M here: the module 1084 will be called dnet. 1085 1086source "drivers/net/tulip/Kconfig" 1087 1088config AT1700 1089 tristate "AT1700/1720 support (EXPERIMENTAL)" 1090 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL 1091 select CRC32 1092 ---help--- 1093 If you have a network (Ethernet) card of this type, say Y and read 1094 the Ethernet-HOWTO, available from 1095 <http://www.tldp.org/docs.html#howto>. 1096 1097 To compile this driver as a module, choose M here. The module 1098 will be called at1700. 1099 1100config DEPCA 1101 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support" 1102 depends on ISA || EISA || MCA 1103 select CRC32 1104 ---help--- 1105 If you have a network (Ethernet) card of this type, say Y and read 1106 the Ethernet-HOWTO, available from 1107 <http://www.tldp.org/docs.html#howto> as well as 1108 <file:drivers/net/depca.c>. 1109 1110 To compile this driver as a module, choose M here. The module 1111 will be called depca. 1112 1113config HP100 1114 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support" 1115 depends on ISA || EISA || PCI 1116 help 1117 If you have a network (Ethernet) card of this type, say Y and read 1118 the Ethernet-HOWTO, available from 1119 <http://www.tldp.org/docs.html#howto>. 1120 1121 To compile this driver as a module, choose M here. The module 1122 will be called hp100. 1123 1124config NET_ISA 1125 bool "Other ISA cards" 1126 depends on ISA 1127 ---help--- 1128 If your network (Ethernet) card hasn't been mentioned yet and its 1129 bus system (that's the way the cards talks to the other components 1130 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y. 1131 Make sure you know the name of your card. Read the Ethernet-HOWTO, 1132 available from <http://www.tldp.org/docs.html#howto>. 1133 1134 If unsure, say Y. 1135 1136 Note that the answer to this question doesn't directly affect the 1137 kernel: saying N will just cause the configurator to skip all 1138 the remaining ISA network card questions. If you say Y, you will be 1139 asked for your specific card in the following questions. 1140 1141config E2100 1142 tristate "Cabletron E21xx support" 1143 depends on NET_ISA 1144 select CRC32 1145 help 1146 If you have a network (Ethernet) card of this type, say Y and read 1147 the Ethernet-HOWTO, available from 1148 <http://www.tldp.org/docs.html#howto>. 1149 1150 To compile this driver as a module, choose M here. The module 1151 will be called e2100. 1152 1153config EWRK3 1154 tristate "EtherWORKS 3 (DE203, DE204, DE205) support" 1155 depends on NET_ISA 1156 select CRC32 1157 ---help--- 1158 This driver supports the DE203, DE204 and DE205 network (Ethernet) 1159 cards. If this is for you, say Y and read 1160 <file:Documentation/networking/ewrk3.txt> in the kernel source as 1161 well as the Ethernet-HOWTO, available from 1162 <http://www.tldp.org/docs.html#howto>. 1163 1164 To compile this driver as a module, choose M here. The module 1165 will be called ewrk3. 1166 1167config EEXPRESS 1168 tristate "EtherExpress 16 support" 1169 depends on NET_ISA 1170 ---help--- 1171 If you have an EtherExpress16 network (Ethernet) card, say Y and 1172 read the Ethernet-HOWTO, available from 1173 <http://www.tldp.org/docs.html#howto>. Note that the Intel 1174 EtherExpress16 card used to be regarded as a very poor choice 1175 because the driver was very unreliable. We now have a new driver 1176 that should do better. 1177 1178 To compile this driver as a module, choose M here. The module 1179 will be called eexpress. 1180 1181config EEXPRESS_PRO 1182 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support" 1183 depends on NET_ISA 1184 ---help--- 1185 If you have a network (Ethernet) card of this type, say Y. This 1186 driver supports Intel i82595{FX,TX} based boards. Note however 1187 that the EtherExpress PRO/100 Ethernet card has its own separate 1188 driver. Please read the Ethernet-HOWTO, available from 1189 <http://www.tldp.org/docs.html#howto>. 1190 1191 To compile this driver as a module, choose M here. The module 1192 will be called eepro. 1193 1194config HPLAN_PLUS 1195 tristate "HP PCLAN+ (27247B and 27252A) support" 1196 depends on NET_ISA 1197 select CRC32 1198 help 1199 If you have a network (Ethernet) card of this type, say Y and read 1200 the Ethernet-HOWTO, available from 1201 <http://www.tldp.org/docs.html#howto>. 1202 1203 To compile this driver as a module, choose M here. The module 1204 will be called hp-plus. 1205 1206config HPLAN 1207 tristate "HP PCLAN (27245 and other 27xxx series) support" 1208 depends on NET_ISA 1209 select CRC32 1210 help 1211 If you have a network (Ethernet) card of this type, say Y and read 1212 the Ethernet-HOWTO, available from 1213 <http://www.tldp.org/docs.html#howto>. 1214 1215 To compile this driver as a module, choose M here. The module 1216 will be called hp. 1217 1218config LP486E 1219 tristate "LP486E on board Ethernet" 1220 depends on NET_ISA 1221 help 1222 Say Y here to support the 82596-based on-board Ethernet controller 1223 for the Panther motherboard, which is one of the two shipped in the 1224 Intel Professional Workstation. 1225 1226config ETH16I 1227 tristate "ICL EtherTeam 16i/32 support" 1228 depends on NET_ISA 1229 help 1230 If you have a network (Ethernet) card of this type, say Y and read 1231 the Ethernet-HOWTO, available from 1232 <http://www.tldp.org/docs.html#howto>. 1233 1234 To compile this driver as a module, choose M here. The module 1235 will be called eth16i. 1236 1237config NE2000 1238 tristate "NE2000/NE1000 support" 1239 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX 1240 select CRC32 1241 ---help--- 1242 If you have a network (Ethernet) card of this type, say Y and read 1243 the Ethernet-HOWTO, available from 1244 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards 1245 without a specific driver are compatible with NE2000. 1246 1247 If you have a PCI NE2000 card however, say N here and Y to "PCI 1248 NE2000 and clone support" under "EISA, VLB, PCI and on board 1249 controllers" below. If you have a NE2000 card and are running on 1250 an MCA system (a bus system used on some IBM PS/2 computers and 1251 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support", 1252 below. 1253 1254 To compile this driver as a module, choose M here. The module 1255 will be called ne. 1256 1257config ZNET 1258 tristate "Zenith Z-Note support (EXPERIMENTAL)" 1259 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API 1260 help 1261 The Zenith Z-Note notebook computer has a built-in network 1262 (Ethernet) card, and this is the Linux driver for it. Note that the 1263 IBM Thinkpad 300 is compatible with the Z-Note and is also supported 1264 by this driver. Read the Ethernet-HOWTO, available from 1265 <http://www.tldp.org/docs.html#howto>. 1266 1267config SEEQ8005 1268 tristate "SEEQ8005 support (EXPERIMENTAL)" 1269 depends on NET_ISA && EXPERIMENTAL 1270 help 1271 This is a driver for the SEEQ 8005 network (Ethernet) card. If this 1272 is for you, read the Ethernet-HOWTO, available from 1273 <http://www.tldp.org/docs.html#howto>. 1274 1275 To compile this driver as a module, choose M here. The module 1276 will be called seeq8005. 1277 1278config NE2_MCA 1279 tristate "NE/2 (ne2000 MCA version) support" 1280 depends on MCA_LEGACY 1281 select CRC32 1282 help 1283 If you have a network (Ethernet) card of this type, say Y and read 1284 the Ethernet-HOWTO, available from 1285 <http://www.tldp.org/docs.html#howto>. 1286 1287 To compile this driver as a module, choose M here. The module 1288 will be called ne2. 1289 1290config IBMLANA 1291 tristate "IBM LAN Adapter/A support" 1292 depends on MCA 1293 ---help--- 1294 This is a Micro Channel Ethernet adapter. You need to set 1295 CONFIG_MCA to use this driver. It is both available as an in-kernel 1296 driver and as a module. 1297 1298 To compile this driver as a module, choose M here. The only 1299 currently supported card is the IBM LAN Adapter/A for Ethernet. It 1300 will both support 16K and 32K memory windows, however a 32K window 1301 gives a better security against packet losses. Usage of multiple 1302 boards with this driver should be possible, but has not been tested 1303 up to now due to lack of hardware. 1304 1305config IBMVETH 1306 tristate "IBM LAN Virtual Ethernet support" 1307 depends on PPC_PSERIES 1308 ---help--- 1309 This driver supports virtual ethernet adapters on newer IBM iSeries 1310 and pSeries systems. 1311 1312 To compile this driver as a module, choose M here. The module will 1313 be called ibmveth. 1314 1315source "drivers/net/ibm_newemac/Kconfig" 1316 1317config NET_PCI 1318 bool "EISA, VLB, PCI and on board controllers" 1319 depends on ISA || EISA || PCI 1320 help 1321 This is another class of network cards which attach directly to the 1322 bus. If you have one of those, say Y and read the Ethernet-HOWTO, 1323 available from <http://www.tldp.org/docs.html#howto>. 1324 1325 Note that the answer to this question doesn't directly affect the 1326 kernel: saying N will just cause the configurator to skip all 1327 the questions about this class of network cards. If you say Y, you 1328 will be asked for your specific card in the following questions. If 1329 you are unsure, say Y. 1330 1331config PCNET32 1332 tristate "AMD PCnet32 PCI support" 1333 depends on NET_PCI && PCI 1334 select CRC32 1335 select MII 1336 help 1337 If you have a PCnet32 or PCnetPCI based network (Ethernet) card, 1338 answer Y here and read the Ethernet-HOWTO, available from 1339 <http://www.tldp.org/docs.html#howto>. 1340 1341 To compile this driver as a module, choose M here. The module 1342 will be called pcnet32. 1343 1344config AMD8111_ETH 1345 tristate "AMD 8111 (new PCI lance) support" 1346 depends on NET_PCI && PCI 1347 select CRC32 1348 select MII 1349 help 1350 If you have an AMD 8111-based PCI lance ethernet card, 1351 answer Y here and read the Ethernet-HOWTO, available from 1352 <http://www.tldp.org/docs.html#howto>. 1353 1354 To compile this driver as a module, choose M here. The module 1355 will be called amd8111e. 1356 1357config ADAPTEC_STARFIRE 1358 tristate "Adaptec Starfire/DuraLAN support" 1359 depends on NET_PCI && PCI 1360 select CRC32 1361 select MII 1362 help 1363 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network 1364 adapter. The DuraLAN chip is used on the 64 bit PCI boards from 1365 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip 1366 driver. 1367 1368 To compile this driver as a module, choose M here: the module 1369 will be called starfire. This is recommended. 1370 1371config AC3200 1372 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)" 1373 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL 1374 select CRC32 1375 help 1376 If you have a network (Ethernet) card of this type, say Y and read 1377 the Ethernet-HOWTO, available from 1378 <http://www.tldp.org/docs.html#howto>. 1379 1380 To compile this driver as a module, choose M here. The module 1381 will be called ac3200. 1382 1383config KSZ884X_PCI 1384 tristate "Micrel KSZ8841/2 PCI" 1385 depends on NET_PCI && PCI 1386 select MII 1387 select CRC32 1388 help 1389 This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip. 1390 1391 To compile this driver as a module, choose M here. The module 1392 will be called ksz884x. 1393 1394config APRICOT 1395 tristate "Apricot Xen-II on board Ethernet" 1396 depends on NET_PCI && ISA 1397 help 1398 If you have a network (Ethernet) controller of this type, say Y and 1399 read the Ethernet-HOWTO, available from 1400 <http://www.tldp.org/docs.html#howto>. 1401 1402 To compile this driver as a module, choose M here. The module 1403 will be called apricot. 1404 1405config B44 1406 tristate "Broadcom 440x/47xx ethernet support" 1407 depends on SSB_POSSIBLE && HAS_DMA 1408 select SSB 1409 select MII 1410 help 1411 If you have a network (Ethernet) controller of this type, say Y 1412 or M and read the Ethernet-HOWTO, available from 1413 <http://www.tldp.org/docs.html#howto>. 1414 1415 To compile this driver as a module, choose M here. The module 1416 will be called b44. 1417 1418# Auto-select SSB PCI-HOST support, if possible 1419config B44_PCI_AUTOSELECT 1420 bool 1421 depends on B44 && SSB_PCIHOST_POSSIBLE 1422 select SSB_PCIHOST 1423 default y 1424 1425# Auto-select SSB PCICORE driver, if possible 1426config B44_PCICORE_AUTOSELECT 1427 bool 1428 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE 1429 select SSB_DRIVER_PCICORE 1430 default y 1431 1432config B44_PCI 1433 bool 1434 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT 1435 default y 1436 1437config FORCEDETH 1438 tristate "nForce Ethernet support" 1439 depends on NET_PCI && PCI 1440 help 1441 If you have a network (Ethernet) controller of this type, say Y and 1442 read the Ethernet-HOWTO, available from 1443 <http://www.tldp.org/docs.html#howto>. 1444 1445 To compile this driver as a module, choose M here. The module 1446 will be called forcedeth. 1447 1448config FORCEDETH_NAPI 1449 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)" 1450 depends on FORCEDETH && EXPERIMENTAL 1451 help 1452 NAPI is a new driver API designed to reduce CPU and interrupt load 1453 when the driver is receiving lots of packets from the card. It is 1454 still somewhat experimental and thus not yet enabled by default. 1455 1456 If your estimated Rx load is 10kpps or more, or if the card will be 1457 deployed on potentially unfriendly networks (e.g. in a firewall), 1458 then say Y here. 1459 1460 If in doubt, say N. 1461 1462config CS89x0 1463 tristate "CS89x0 support" 1464 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \ 1465 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS) 1466 ---help--- 1467 Support for CS89x0 chipset based Ethernet cards. If you have a 1468 network (Ethernet) card of this type, say Y and read the 1469 Ethernet-HOWTO, available from 1470 <http://www.tldp.org/docs.html#howto> as well as 1471 <file:Documentation/networking/cs89x0.txt>. 1472 1473 To compile this driver as a module, choose M here. The module 1474 will be called cs89x0. 1475 1476config CS89x0_NONISA_IRQ 1477 def_bool y 1478 depends on CS89x0 != n 1479 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS 1480 1481config TC35815 1482 tristate "TOSHIBA TC35815 Ethernet support" 1483 depends on NET_PCI && PCI && MIPS 1484 select PHYLIB 1485 1486config E100 1487 tristate "Intel(R) PRO/100+ support" 1488 depends on NET_PCI && PCI 1489 select MII 1490 ---help--- 1491 This driver supports Intel(R) PRO/100 family of adapters. 1492 To verify that your adapter is supported, find the board ID number 1493 on the adapter. Look for a label that has a barcode and a number 1494 in the format 123456-001 (six digits hyphen three digits). 1495 1496 Use the above information and the Adapter & Driver ID Guide at: 1497 1498 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 1499 1500 to identify the adapter. 1501 1502 For the latest Intel PRO/100 network driver for Linux, see: 1503 1504 <http://appsr.intel.com/scripts-df/support_intel.asp> 1505 1506 More specific information on configuring the driver is in 1507 <file:Documentation/networking/e100.txt>. 1508 1509 To compile this driver as a module, choose M here. The module 1510 will be called e100. 1511 1512config LNE390 1513 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)" 1514 depends on NET_PCI && EISA && EXPERIMENTAL 1515 select CRC32 1516 help 1517 If you have a network (Ethernet) card of this type, say Y and read 1518 the Ethernet-HOWTO, available from 1519 <http://www.tldp.org/docs.html#howto>. 1520 1521 To compile this driver as a module, choose M here. The module 1522 will be called lne390. 1523 1524config FEALNX 1525 tristate "Myson MTD-8xx PCI Ethernet support" 1526 depends on NET_PCI && PCI 1527 select CRC32 1528 select MII 1529 help 1530 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet 1531 cards. Specifications and data at 1532 <http://www.myson.com.hk/mtd/datasheet/>. 1533 1534config NATSEMI 1535 tristate "National Semiconductor DP8381x series PCI Ethernet support" 1536 depends on NET_PCI && PCI 1537 select CRC32 1538 help 1539 This driver is for the National Semiconductor DP83810 series, 1540 which is used in cards from PureData, NetGear, Linksys 1541 and others, including the 83815 chip. 1542 More specific information and updates are available from 1543 <http://www.scyld.com/network/natsemi.html>. 1544 1545config NE2K_PCI 1546 tristate "PCI NE2000 and clones support (see help)" 1547 depends on NET_PCI && PCI 1548 select CRC32 1549 ---help--- 1550 This driver is for NE2000 compatible PCI cards. It will not work 1551 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000 1552 support" below). If you have a PCI NE2000 network (Ethernet) card, 1553 say Y and read the Ethernet-HOWTO, available from 1554 <http://www.tldp.org/docs.html#howto>. 1555 1556 This driver also works for the following NE2000 clone cards: 1557 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2 1558 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond 1559 Holtek HT80232 Holtek HT80229 1560 1561 To compile this driver as a module, choose M here. The module 1562 will be called ne2k-pci. 1563 1564config NE3210 1565 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)" 1566 depends on NET_PCI && EISA && EXPERIMENTAL 1567 select CRC32 1568 ---help--- 1569 If you have a network (Ethernet) card of this type, say Y and read 1570 the Ethernet-HOWTO, available from 1571 <http://www.tldp.org/docs.html#howto>. Note that this driver 1572 will NOT WORK for NE3200 cards as they are completely different. 1573 1574 To compile this driver as a module, choose M here. The module 1575 will be called ne3210. 1576 1577config ES3210 1578 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)" 1579 depends on NET_PCI && EISA && EXPERIMENTAL 1580 select CRC32 1581 help 1582 If you have a network (Ethernet) card of this type, say Y and read 1583 the Ethernet-HOWTO, available from 1584 <http://www.tldp.org/docs.html#howto>. 1585 1586 To compile this driver as a module, choose M here. The module 1587 will be called es3210. 1588 1589config 8139CP 1590 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)" 1591 depends on NET_PCI && PCI && EXPERIMENTAL 1592 select CRC32 1593 select MII 1594 help 1595 This is a driver for the Fast Ethernet PCI network cards based on 1596 the RTL8139C+ chips. If you have one of those, say Y and read 1597 the Ethernet-HOWTO, available from 1598 <http://www.tldp.org/docs.html#howto>. 1599 1600 To compile this driver as a module, choose M here: the module 1601 will be called 8139cp. This is recommended. 1602 1603config 8139TOO 1604 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support" 1605 depends on NET_PCI && PCI 1606 select CRC32 1607 select MII 1608 ---help--- 1609 This is a driver for the Fast Ethernet PCI network cards based on 1610 the RTL 8129/8130/8139 chips. If you have one of those, say Y and 1611 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>. 1612 1613 To compile this driver as a module, choose M here: the module 1614 will be called 8139too. This is recommended. 1615 1616config 8139TOO_PIO 1617 bool "Use PIO instead of MMIO" 1618 default y 1619 depends on 8139TOO 1620 help 1621 This instructs the driver to use programmed I/O ports (PIO) instead 1622 of PCI shared memory (MMIO). This can possibly solve some problems 1623 in case your mainboard has memory consistency issues. If unsure, 1624 say N. 1625 1626config 8139TOO_TUNE_TWISTER 1627 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)" 1628 depends on 8139TOO 1629 help 1630 This implements a function which might come in handy in case you 1631 are using low quality on long cabling. It is required for RealTek 1632 RTL-8139 revision K boards, and totally unused otherwise. It tries 1633 to match the transceiver to the cable characteristics. This is 1634 experimental since hardly documented by the manufacturer. 1635 If unsure, say Y. 1636 1637config 8139TOO_8129 1638 bool "Support for older RTL-8129/8130 boards" 1639 depends on 8139TOO 1640 help 1641 This enables support for the older and uncommon RTL-8129 and 1642 RTL-8130 chips, which support MII via an external transceiver, 1643 instead of an internal one. Disabling this option will save some 1644 memory by making the code size smaller. If unsure, say Y. 1645 1646config 8139_OLD_RX_RESET 1647 bool "Use older RX-reset method" 1648 depends on 8139TOO 1649 help 1650 The 8139too driver was recently updated to contain a more rapid 1651 reset sequence, in the face of severe receive errors. This "new" 1652 RX-reset method should be adequate for all boards. But if you 1653 experience problems, you can enable this option to restore the 1654 old RX-reset behavior. If unsure, say N. 1655 1656config R6040 1657 tristate "RDC R6040 Fast Ethernet Adapter support" 1658 depends on NET_PCI && PCI 1659 select CRC32 1660 select MII 1661 help 1662 This is a driver for the R6040 Fast Ethernet MACs found in the 1663 the RDC R-321x System-on-chips. 1664 1665 To compile this driver as a module, choose M here: the module 1666 will be called r6040. This is recommended. 1667 1668config SIS900 1669 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support" 1670 depends on NET_PCI && PCI 1671 select CRC32 1672 select MII 1673 ---help--- 1674 This is a driver for the Fast Ethernet PCI network cards based on 1675 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in 1676 SiS 630 and SiS 540 chipsets. 1677 1678 This driver also supports AMD 79C901 HomePNA so that you can use 1679 your phone line as a network cable. 1680 1681 To compile this driver as a module, choose M here: the module 1682 will be called sis900. This is recommended. 1683 1684config EPIC100 1685 tristate "SMC EtherPower II" 1686 depends on NET_PCI && PCI 1687 select CRC32 1688 select MII 1689 help 1690 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC, 1691 which is based on the SMC83c17x (EPIC/100). 1692 More specific information and updates are available from 1693 <http://www.scyld.com/network/epic100.html>. 1694 1695config SMSC9420 1696 tristate "SMSC LAN9420 PCI ethernet adapter support" 1697 depends on NET_PCI && PCI 1698 select CRC32 1699 select PHYLIB 1700 select SMSC_PHY 1701 help 1702 This is a driver for SMSC's LAN9420 PCI ethernet adapter. 1703 Say Y if you want it compiled into the kernel, 1704 and read the Ethernet-HOWTO, available from 1705 <http://www.linuxdoc.org/docs.html#howto>. 1706 1707 This driver is also available as a module. The module will be 1708 called smsc9420. If you want to compile it as a module, say M 1709 here and read <file:Documentation/kbuild/modules.txt> 1710 1711config SUNDANCE 1712 tristate "Sundance Alta support" 1713 depends on NET_PCI && PCI 1714 select CRC32 1715 select MII 1716 help 1717 This driver is for the Sundance "Alta" chip. 1718 More specific information and updates are available from 1719 <http://www.scyld.com/network/sundance.html>. 1720 1721config SUNDANCE_MMIO 1722 bool "Use MMIO instead of PIO" 1723 depends on SUNDANCE 1724 help 1725 Enable memory-mapped I/O for interaction with Sundance NIC registers. 1726 Do NOT enable this by default, PIO (enabled when MMIO is disabled) 1727 is known to solve bugs on certain chips. 1728 1729 If unsure, say N. 1730 1731config TLAN 1732 tristate "TI ThunderLAN support" 1733 depends on NET_PCI && (PCI || EISA) 1734 ---help--- 1735 If you have a PCI Ethernet network card based on the ThunderLAN chip 1736 which is supported by this driver, say Y and read the 1737 Ethernet-HOWTO, available from 1738 <http://www.tldp.org/docs.html#howto>. 1739 1740 Devices currently supported by this driver are Compaq Netelligent, 1741 Compaq NetFlex and Olicom cards. Please read the file 1742 <file:Documentation/networking/tlan.txt> for more details. 1743 1744 To compile this driver as a module, choose M here. The module 1745 will be called tlan. 1746 1747 Please email feedback to <torben.mathiasen@compaq.com>. 1748 1749config KS8842 1750 tristate "Micrel KSZ8842" 1751 depends on HAS_IOMEM 1752 help 1753 This platform driver is for Micrel KSZ8842 / KS8842 1754 2-port ethernet switch chip (managed, VLAN, QoS). 1755 1756config KS8851 1757 tristate "Micrel KS8851 SPI" 1758 depends on SPI 1759 select MII 1760 select CRC32 1761 help 1762 SPI driver for Micrel KS8851 SPI attached network chip. 1763 1764config KS8851_MLL 1765 tristate "Micrel KS8851 MLL" 1766 depends on HAS_IOMEM 1767 select MII 1768 help 1769 This platform driver is for Micrel KS8851 Address/data bus 1770 multiplexed network chip. 1771 1772config VIA_RHINE 1773 tristate "VIA Rhine support" 1774 depends on NET_PCI && PCI 1775 select CRC32 1776 select MII 1777 help 1778 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A), 1779 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type 1780 Ethernet functions can also be found integrated on South Bridges 1781 (e.g. VT8235). 1782 1783 To compile this driver as a module, choose M here. The module 1784 will be called via-rhine. 1785 1786config VIA_RHINE_MMIO 1787 bool "Use MMIO instead of PIO" 1788 depends on VIA_RHINE 1789 help 1790 This instructs the driver to use PCI shared memory (MMIO) instead of 1791 programmed I/O ports (PIO). Enabling this gives an improvement in 1792 processing time in parts of the driver. 1793 1794 If unsure, say Y. 1795 1796config SC92031 1797 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)" 1798 depends on NET_PCI && PCI && EXPERIMENTAL 1799 select CRC32 1800 ---help--- 1801 This is a driver for the Fast Ethernet PCI network cards based on 1802 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you 1803 have one of these, say Y here. 1804 1805 To compile this driver as a module, choose M here: the module 1806 will be called sc92031. This is recommended. 1807 1808config CPMAC 1809 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)" 1810 depends on NET_ETHERNET && EXPERIMENTAL && AR7 1811 select PHYLIB 1812 help 1813 TI AR7 CPMAC Ethernet support 1814 1815config NET_POCKET 1816 bool "Pocket and portable adapters" 1817 depends on PARPORT 1818 ---help--- 1819 Cute little network (Ethernet) devices which attach to the parallel 1820 port ("pocket adapters"), commonly used with laptops. If you have 1821 one of those, say Y and read the Ethernet-HOWTO, available from 1822 <http://www.tldp.org/docs.html#howto>. 1823 1824 If you want to plug a network (or some other) card into the PCMCIA 1825 (or PC-card) slot of your laptop instead (PCMCIA is the standard for 1826 credit card size extension cards used by all modern laptops), you 1827 need the pcmcia-cs package (location contained in the file 1828 <file:Documentation/Changes>) and you can say N here. 1829 1830 Laptop users should read the Linux Laptop home page at 1831 <http://www.linux-on-laptops.com/> or 1832 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>. 1833 1834 Note that the answer to this question doesn't directly affect the 1835 kernel: saying N will just cause the configurator to skip all 1836 the questions about this class of network devices. If you say Y, you 1837 will be asked for your specific device in the following questions. 1838 1839config ATP 1840 tristate "AT-LAN-TEC/RealTek pocket adapter support" 1841 depends on NET_POCKET && PARPORT && X86 1842 select CRC32 1843 ---help--- 1844 This is a network (Ethernet) device which attaches to your parallel 1845 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO, 1846 available from <http://www.tldp.org/docs.html#howto>, if you 1847 want to use this. If you intend to use this driver, you should have 1848 said N to the "Parallel printer support", because the two drivers 1849 don't like each other. 1850 1851 To compile this driver as a module, choose M here: the module 1852 will be called atp. 1853 1854config DE600 1855 tristate "D-Link DE600 pocket adapter support" 1856 depends on NET_POCKET && PARPORT 1857 ---help--- 1858 This is a network (Ethernet) device which attaches to your parallel 1859 port. Read <file:Documentation/networking/DLINK.txt> as well as the 1860 Ethernet-HOWTO, available from 1861 <http://www.tldp.org/docs.html#howto>, if you want to use 1862 this. It is possible to have several devices share a single parallel 1863 port and it is safe to compile the corresponding drivers into the 1864 kernel. 1865 1866 To compile this driver as a module, choose M here: the module 1867 will be called de600. 1868 1869config DE620 1870 tristate "D-Link DE620 pocket adapter support" 1871 depends on NET_POCKET && PARPORT 1872 ---help--- 1873 This is a network (Ethernet) device which attaches to your parallel 1874 port. Read <file:Documentation/networking/DLINK.txt> as well as the 1875 Ethernet-HOWTO, available from 1876 <http://www.tldp.org/docs.html#howto>, if you want to use 1877 this. It is possible to have several devices share a single parallel 1878 port and it is safe to compile the corresponding drivers into the 1879 kernel. 1880 1881 To compile this driver as a module, choose M here: the module 1882 will be called de620. 1883 1884config SGISEEQ 1885 tristate "SGI Seeq ethernet controller support" 1886 depends on SGI_HAS_SEEQ 1887 help 1888 Say Y here if you have an Seeq based Ethernet network card. This is 1889 used in many Silicon Graphics machines. 1890 1891config DECLANCE 1892 tristate "DEC LANCE ethernet controller support" 1893 depends on MACH_DECSTATION 1894 select CRC32 1895 help 1896 This driver is for the series of Ethernet controllers produced by 1897 DEC (now Compaq) based on the AMD Lance chipset, including the 1898 DEPCA series. (This chipset is better known via the NE2100 cards.) 1899 1900config 68360_ENET 1901 bool "Motorola 68360 ethernet controller" 1902 depends on M68360 1903 help 1904 Say Y here if you want to use the built-in ethernet controller of 1905 the Motorola 68360 processor. 1906 1907config FEC 1908 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)" 1909 depends on M523x || M527x || M5272 || M528x || M520x || M532x || \ 1910 MACH_MX27 || ARCH_MX35 || ARCH_MX25 || ARCH_MX5 1911 help 1912 Say Y here if you want to use the built-in 10/100 Fast ethernet 1913 controller on some Motorola ColdFire and Freescale i.MX processors. 1914 1915config FEC2 1916 bool "Second FEC ethernet controller (on some ColdFire CPUs)" 1917 depends on FEC 1918 help 1919 Say Y here if you want to use the second built-in 10/100 Fast 1920 ethernet controller on some Motorola ColdFire processors. 1921 1922config FEC_MPC52xx 1923 tristate "MPC52xx FEC driver" 1924 depends on PPC_MPC52xx && PPC_BESTCOMM 1925 select CRC32 1926 select PHYLIB 1927 select PPC_BESTCOMM_FEC 1928 ---help--- 1929 This option enables support for the MPC5200's on-chip 1930 Fast Ethernet Controller 1931 If compiled as module, it will be called fec_mpc52xx. 1932 1933config FEC_MPC52xx_MDIO 1934 bool "MPC52xx FEC MDIO bus driver" 1935 depends on FEC_MPC52xx 1936 default y 1937 ---help--- 1938 The MPC5200's FEC can connect to the Ethernet either with 1939 an external MII PHY chip or 10 Mbps 7-wire interface 1940 (Motorola? industry standard). 1941 If your board uses an external PHY connected to FEC, enable this. 1942 If not sure, enable. 1943 If compiled as module, it will be called fec_mpc52xx_phy. 1944 1945config NE_H8300 1946 tristate "NE2000 compatible support for H8/300" 1947 depends on H8300 1948 help 1949 Say Y here if you want to use the NE2000 compatible 1950 controller on the Renesas H8/300 processor. 1951 1952config ATL2 1953 tristate "Atheros L2 Fast Ethernet support" 1954 depends on PCI 1955 select CRC32 1956 select MII 1957 help 1958 This driver supports the Atheros L2 fast ethernet adapter. 1959 1960 To compile this driver as a module, choose M here. The module 1961 will be called atl2. 1962 1963config XILINX_EMACLITE 1964 tristate "Xilinx 10/100 Ethernet Lite support" 1965 depends on PPC32 || MICROBLAZE 1966 select PHYLIB 1967 help 1968 This driver supports the 10/100 Ethernet Lite from Xilinx. 1969 1970config BCM63XX_ENET 1971 tristate "Broadcom 63xx internal mac support" 1972 depends on BCM63XX 1973 select MII 1974 select PHYLIB 1975 help 1976 This driver supports the ethernet MACs in the Broadcom 63xx 1977 MIPS chipset family (BCM63XX). 1978 1979source "drivers/net/fs_enet/Kconfig" 1980 1981source "drivers/net/octeon/Kconfig" 1982 1983endif # NET_ETHERNET 1984 1985# 1986# Gigabit Ethernet 1987# 1988 1989menuconfig NETDEV_1000 1990 bool "Ethernet (1000 Mbit)" 1991 depends on !UML 1992 default y 1993 ---help--- 1994 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common 1995 type of Local Area Network (LAN) in universities and companies. 1996 1997 Say Y here to get to see options for Gigabit Ethernet drivers. 1998 This option alone does not add any kernel code. 1999 Note that drivers supporting both 100 and 1000 MBit may be listed 2000 under "Ethernet (10 or 100MBit)" instead. 2001 2002 If you say N, all options in this submenu will be skipped and disabled. 2003 2004if NETDEV_1000 2005 2006config ACENIC 2007 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support" 2008 depends on PCI 2009 ---help--- 2010 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear 2011 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet 2012 adapter. The driver allows for using the Jumbo Frame option (9000 2013 bytes/frame) however it requires that your switches can handle this 2014 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig 2015 line. 2016 2017 To compile this driver as a module, choose M here: the 2018 module will be called acenic. 2019 2020config ACENIC_OMIT_TIGON_I 2021 bool "Omit support for old Tigon I based AceNICs" 2022 depends on ACENIC 2023 help 2024 Say Y here if you only have Tigon II based AceNICs and want to leave 2025 out support for the older Tigon I based cards which are no longer 2026 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B 2027 version)). This will reduce the size of the driver object by 2028 app. 100KB. If you are not sure whether your card is a Tigon I or a 2029 Tigon II, say N here. 2030 2031 The safe and default value for this is N. 2032 2033config DL2K 2034 tristate "DL2000/TC902x-based Gigabit Ethernet support" 2035 depends on PCI 2036 select CRC32 2037 help 2038 This driver supports DL2000/TC902x-based Gigabit ethernet cards, 2039 which includes 2040 D-Link DGE-550T Gigabit Ethernet Adapter. 2041 D-Link DL2000-based Gigabit Ethernet Adapter. 2042 Sundance/Tamarack TC902x Gigabit Ethernet Adapter. 2043 2044 To compile this driver as a module, choose M here: the 2045 module will be called dl2k. 2046 2047config E1000 2048 tristate "Intel(R) PRO/1000 Gigabit Ethernet support" 2049 depends on PCI 2050 ---help--- 2051 This driver supports Intel(R) PRO/1000 gigabit ethernet family of 2052 adapters. For more information on how to identify your adapter, go 2053 to the Adapter & Driver ID Guide at: 2054 2055 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2056 2057 For general information and support, go to the Intel support 2058 website at: 2059 2060 <http://support.intel.com> 2061 2062 More specific information on configuring the driver is in 2063 <file:Documentation/networking/e1000.txt>. 2064 2065 To compile this driver as a module, choose M here. The module 2066 will be called e1000. 2067 2068config E1000E 2069 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support" 2070 depends on PCI && (!SPARC32 || BROKEN) 2071 ---help--- 2072 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit 2073 ethernet family of adapters. For PCI or PCI-X e1000 adapters, 2074 use the regular e1000 driver For more information on how to 2075 identify your adapter, go to the Adapter & Driver ID Guide at: 2076 2077 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2078 2079 For general information and support, go to the Intel support 2080 website at: 2081 2082 <http://support.intel.com> 2083 2084 To compile this driver as a module, choose M here. The module 2085 will be called e1000e. 2086 2087config IP1000 2088 tristate "IP1000 Gigabit Ethernet support" 2089 depends on PCI && EXPERIMENTAL 2090 select MII 2091 ---help--- 2092 This driver supports IP1000 gigabit Ethernet cards. 2093 2094 To compile this driver as a module, choose M here: the module 2095 will be called ipg. This is recommended. 2096 2097config IGB 2098 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support" 2099 depends on PCI 2100 ---help--- 2101 This driver supports Intel(R) 82575/82576 gigabit ethernet family of 2102 adapters. For more information on how to identify your adapter, go 2103 to the Adapter & Driver ID Guide at: 2104 2105 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2106 2107 For general information and support, go to the Intel support 2108 website at: 2109 2110 <http://support.intel.com> 2111 2112 More specific information on configuring the driver is in 2113 <file:Documentation/networking/e1000.txt>. 2114 2115 To compile this driver as a module, choose M here. The module 2116 will be called igb. 2117 2118config IGB_DCA 2119 bool "Direct Cache Access (DCA) Support" 2120 default y 2121 depends on IGB && DCA && !(IGB=y && DCA=m) 2122 ---help--- 2123 Say Y here if you want to use Direct Cache Access (DCA) in the 2124 driver. DCA is a method for warming the CPU cache before data 2125 is used, with the intent of lessening the impact of cache misses. 2126 2127config IGBVF 2128 tristate "Intel(R) 82576 Virtual Function Ethernet support" 2129 depends on PCI 2130 ---help--- 2131 This driver supports Intel(R) 82576 virtual functions. For more 2132 information on how to identify your adapter, go to the Adapter & 2133 Driver ID Guide at: 2134 2135 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2136 2137 For general information and support, go to the Intel support 2138 website at: 2139 2140 <http://support.intel.com> 2141 2142 More specific information on configuring the driver is in 2143 <file:Documentation/networking/e1000.txt>. 2144 2145 To compile this driver as a module, choose M here. The module 2146 will be called igbvf. 2147 2148source "drivers/net/ixp2000/Kconfig" 2149 2150config MYRI_SBUS 2151 tristate "MyriCOM Gigabit Ethernet support" 2152 depends on SBUS 2153 help 2154 This driver supports MyriCOM Sbus gigabit Ethernet cards. 2155 2156 To compile this driver as a module, choose M here: the module 2157 will be called myri_sbus. This is recommended. 2158 2159config NS83820 2160 tristate "National Semiconductor DP83820 support" 2161 depends on PCI 2162 help 2163 This is a driver for the National Semiconductor DP83820 series 2164 of gigabit ethernet MACs. Cards using this chipset include 2165 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX, 2166 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of 2167 zero copy. 2168 2169config HAMACHI 2170 tristate "Packet Engines Hamachi GNIC-II support" 2171 depends on PCI 2172 select MII 2173 help 2174 If you have a Gigabit Ethernet card of this type, say Y and read 2175 the Ethernet-HOWTO, available from 2176 <http://www.tldp.org/docs.html#howto>. 2177 2178 To compile this driver as a module, choose M here. The module will be 2179 called hamachi. 2180 2181config YELLOWFIN 2182 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)" 2183 depends on PCI && EXPERIMENTAL 2184 select CRC32 2185 ---help--- 2186 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet 2187 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is 2188 used by the Beowulf Linux cluster project. See 2189 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more 2190 information about this driver in particular and Beowulf in general. 2191 2192 To compile this driver as a module, choose M here: the module 2193 will be called yellowfin. This is recommended. 2194 2195config R8169 2196 tristate "Realtek 8169 gigabit ethernet support" 2197 depends on PCI 2198 select CRC32 2199 select MII 2200 ---help--- 2201 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter. 2202 2203 To compile this driver as a module, choose M here: the module 2204 will be called r8169. This is recommended. 2205 2206config R8169_VLAN 2207 bool "VLAN support" 2208 depends on R8169 && VLAN_8021Q 2209 ---help--- 2210 Say Y here for the r8169 driver to support the functions required 2211 by the kernel 802.1Q code. 2212 2213 If in doubt, say Y. 2214 2215config SB1250_MAC 2216 tristate "SB1250 Gigabit Ethernet support" 2217 depends on SIBYTE_SB1xxx_SOC 2218 select PHYLIB 2219 ---help--- 2220 This driver supports Gigabit Ethernet interfaces based on the 2221 Broadcom SiByte family of System-On-a-Chip parts. They include 2222 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455 2223 and BCM1480 chips. 2224 2225 To compile this driver as a module, choose M here: the module 2226 will be called sb1250-mac. 2227 2228config SIS190 2229 tristate "SiS190/SiS191 gigabit ethernet support" 2230 depends on PCI 2231 select CRC32 2232 select MII 2233 ---help--- 2234 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or 2235 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to 2236 appear in lan on motherboard designs which are based on SiS 965 2237 and SiS 966 south bridge. 2238 2239 To compile this driver as a module, choose M here: the module 2240 will be called sis190. This is recommended. 2241 2242config SKGE 2243 tristate "New SysKonnect GigaEthernet support" 2244 depends on PCI 2245 select CRC32 2246 ---help--- 2247 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx 2248 and related Gigabit Ethernet adapters. It is a new smaller driver 2249 with better performance and more complete ethtool support. 2250 2251 It does not support the link failover and network management 2252 features that "portable" vendor supplied sk98lin driver does. 2253 2254 This driver supports adapters based on the original Yukon chipset: 2255 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T, 2256 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872. 2257 2258 It does not support the newer Yukon2 chipset: a separate driver, 2259 sky2, is provided for Yukon2-based adapters. 2260 2261 To compile this driver as a module, choose M here: the module 2262 will be called skge. This is recommended. 2263 2264config SKGE_DEBUG 2265 bool "Debugging interface" 2266 depends on SKGE && DEBUG_FS 2267 help 2268 This option adds the ability to dump driver state for debugging. 2269 The file /sys/kernel/debug/skge/ethX displays the state of the internal 2270 transmit and receive rings. 2271 2272 If unsure, say N. 2273 2274config SKY2 2275 tristate "SysKonnect Yukon2 support" 2276 depends on PCI 2277 select CRC32 2278 ---help--- 2279 This driver supports Gigabit Ethernet adapters based on the 2280 Marvell Yukon 2 chipset: 2281 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/ 2282 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21 2283 2284 There is companion driver for the older Marvell Yukon and 2285 Genesis based adapters: skge. 2286 2287 To compile this driver as a module, choose M here: the module 2288 will be called sky2. This is recommended. 2289 2290config SKY2_DEBUG 2291 bool "Debugging interface" 2292 depends on SKY2 && DEBUG_FS 2293 help 2294 This option adds the ability to dump driver state for debugging. 2295 The file /sys/kernel/debug/sky2/ethX displays the state of the internal 2296 transmit and receive rings. 2297 2298 If unsure, say N. 2299 2300config VIA_VELOCITY 2301 tristate "VIA Velocity support" 2302 depends on PCI 2303 select CRC32 2304 select CRC_CCITT 2305 select MII 2306 help 2307 If you have a VIA "Velocity" based network card say Y here. 2308 2309 To compile this driver as a module, choose M here. The module 2310 will be called via-velocity. 2311 2312config TIGON3 2313 tristate "Broadcom Tigon3 support" 2314 depends on PCI 2315 select PHYLIB 2316 help 2317 This driver supports Broadcom Tigon3 based gigabit Ethernet cards. 2318 2319 To compile this driver as a module, choose M here: the module 2320 will be called tg3. This is recommended. 2321 2322config BNX2 2323 tristate "Broadcom NetXtremeII support" 2324 depends on PCI 2325 select CRC32 2326 select FW_LOADER 2327 help 2328 This driver supports Broadcom NetXtremeII gigabit Ethernet cards. 2329 2330 To compile this driver as a module, choose M here: the module 2331 will be called bnx2. This is recommended. 2332 2333config CNIC 2334 tristate "Broadcom CNIC support" 2335 depends on PCI 2336 select BNX2 2337 select UIO 2338 help 2339 This driver supports offload features of Broadcom NetXtremeII 2340 gigabit Ethernet cards. 2341 2342 To compile this driver as a module, choose M here: the module 2343 will be called cnic. This is recommended. 2344 2345config SPIDER_NET 2346 tristate "Spider Gigabit Ethernet driver" 2347 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB) 2348 select FW_LOADER 2349 help 2350 This driver supports the Gigabit Ethernet chips present on the 2351 Cell Processor-Based Blades from IBM. 2352 2353config TSI108_ETH 2354 tristate "Tundra TSI108 gigabit Ethernet support" 2355 depends on TSI108_BRIDGE 2356 help 2357 This driver supports Tundra TSI108 gigabit Ethernet ports. 2358 To compile this driver as a module, choose M here: the module 2359 will be called tsi108_eth. 2360 2361config GELIC_NET 2362 tristate "PS3 Gigabit Ethernet driver" 2363 depends on PPC_PS3 2364 select PS3_SYS_MANAGER 2365 help 2366 This driver supports the network device on the PS3 game 2367 console. This driver has built-in support for Ethernet. 2368 2369 To compile this driver as a module, choose M here: the 2370 module will be called ps3_gelic. 2371 2372config GELIC_WIRELESS 2373 bool "PS3 Wireless support" 2374 depends on WLAN 2375 depends on GELIC_NET 2376 select WIRELESS_EXT 2377 help 2378 This option adds the support for the wireless feature of PS3. 2379 If you have the wireless-less model of PS3 or have no plan to 2380 use wireless feature, disabling this option saves memory. As 2381 the driver automatically distinguishes the models, you can 2382 safely enable this option even if you have a wireless-less model. 2383 2384config FSL_PQ_MDIO 2385 tristate "Freescale PQ MDIO" 2386 depends on FSL_SOC 2387 select PHYLIB 2388 help 2389 This driver supports the MDIO bus used by the gianfar and UCC drivers. 2390 2391config GIANFAR 2392 tristate "Gianfar Ethernet" 2393 depends on FSL_SOC 2394 select FSL_PQ_MDIO 2395 select PHYLIB 2396 select CRC32 2397 help 2398 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx, 2399 and MPC86xx family of chips, and the FEC on the 8540. 2400 2401config UCC_GETH 2402 tristate "Freescale QE Gigabit Ethernet" 2403 depends on QUICC_ENGINE 2404 select FSL_PQ_MDIO 2405 select PHYLIB 2406 help 2407 This driver supports the Gigabit Ethernet mode of the QUICC Engine, 2408 which is available on some Freescale SOCs. 2409 2410config UGETH_TX_ON_DEMAND 2411 bool "Transmit on Demand support" 2412 depends on UCC_GETH 2413 2414config MV643XX_ETH 2415 tristate "Marvell Discovery (643XX) and Orion ethernet support" 2416 depends on MV64X60 || PPC32 || PLAT_ORION 2417 select INET_LRO 2418 select PHYLIB 2419 help 2420 This driver supports the gigabit ethernet MACs in the 2421 Marvell Discovery PPC/MIPS chipset family (MV643XX) and 2422 in the Marvell Orion ARM SoC family. 2423 2424 Some boards that use the Discovery chipset are the Momenco 2425 Ocelot C and Jaguar ATX and Pegasos II. 2426 2427config XILINX_LL_TEMAC 2428 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver" 2429 select PHYLIB 2430 depends on PPC_DCR_NATIVE 2431 help 2432 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC 2433 core used in Xilinx Spartan and Virtex FPGAs 2434 2435config QLA3XXX 2436 tristate "QLogic QLA3XXX Network Driver Support" 2437 depends on PCI 2438 help 2439 This driver supports QLogic ISP3XXX gigabit Ethernet cards. 2440 2441 To compile this driver as a module, choose M here: the module 2442 will be called qla3xxx. 2443 2444config ATL1 2445 tristate "Atheros/Attansic L1 Gigabit Ethernet support" 2446 depends on PCI 2447 select CRC32 2448 select MII 2449 help 2450 This driver supports the Atheros/Attansic L1 gigabit ethernet 2451 adapter. 2452 2453 To compile this driver as a module, choose M here. The module 2454 will be called atl1. 2455 2456config ATL1E 2457 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)" 2458 depends on PCI && EXPERIMENTAL 2459 select CRC32 2460 select MII 2461 help 2462 This driver supports the Atheros L1E gigabit ethernet adapter. 2463 2464 To compile this driver as a module, choose M here. The module 2465 will be called atl1e. 2466 2467config ATL1C 2468 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)" 2469 depends on PCI && EXPERIMENTAL 2470 select CRC32 2471 select MII 2472 help 2473 This driver supports the Atheros L1C gigabit ethernet adapter. 2474 2475 To compile this driver as a module, choose M here. The module 2476 will be called atl1c. 2477 2478config JME 2479 tristate "JMicron(R) PCI-Express Gigabit Ethernet support" 2480 depends on PCI 2481 select CRC32 2482 select MII 2483 ---help--- 2484 This driver supports the PCI-Express gigabit ethernet adapters 2485 based on JMicron JMC250 chipset. 2486 2487 To compile this driver as a module, choose M here. The module 2488 will be called jme. 2489 2490config S6GMAC 2491 tristate "S6105 GMAC ethernet support" 2492 depends on XTENSA_VARIANT_S6000 2493 select PHYLIB 2494 help 2495 This driver supports the on chip ethernet device on the 2496 S6105 xtensa processor. 2497 2498 To compile this driver as a module, choose M here. The module 2499 will be called s6gmac. 2500 2501source "drivers/net/stmmac/Kconfig" 2502 2503endif # NETDEV_1000 2504 2505# 2506# 10 Gigabit Ethernet 2507# 2508 2509menuconfig NETDEV_10000 2510 bool "Ethernet (10000 Mbit)" 2511 depends on !UML 2512 default y 2513 ---help--- 2514 Say Y here to get to see options for 10 Gigabit Ethernet drivers. 2515 This option alone does not add any kernel code. 2516 2517 If you say N, all options in this submenu will be skipped and disabled. 2518 2519if NETDEV_10000 2520 2521config MDIO 2522 tristate 2523 2524config CHELSIO_T1 2525 tristate "Chelsio 10Gb Ethernet support" 2526 depends on PCI 2527 select CRC32 2528 select MDIO 2529 help 2530 This driver supports Chelsio gigabit and 10-gigabit 2531 Ethernet cards. More information about adapter features and 2532 performance tuning is in <file:Documentation/networking/cxgb.txt>. 2533 2534 For general information about Chelsio and our products, visit 2535 our website at <http://www.chelsio.com>. 2536 2537 For customer support, please visit our customer support page at 2538 <http://www.chelsio.com/support.htm>. 2539 2540 Please send feedback to <linux-bugs@chelsio.com>. 2541 2542 To compile this driver as a module, choose M here: the module 2543 will be called cxgb. 2544 2545config CHELSIO_T1_1G 2546 bool "Chelsio gigabit Ethernet support" 2547 depends on CHELSIO_T1 2548 help 2549 Enables support for Chelsio's gigabit Ethernet PCI cards. If you 2550 are using only 10G cards say 'N' here. 2551 2552config CHELSIO_T3_DEPENDS 2553 tristate 2554 depends on PCI && INET 2555 default y 2556 2557config CHELSIO_T3 2558 tristate "Chelsio Communications T3 10Gb Ethernet support" 2559 depends on CHELSIO_T3_DEPENDS 2560 select FW_LOADER 2561 select MDIO 2562 help 2563 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet 2564 adapters. 2565 2566 For general information about Chelsio and our products, visit 2567 our website at <http://www.chelsio.com>. 2568 2569 For customer support, please visit our customer support page at 2570 <http://www.chelsio.com/support.htm>. 2571 2572 Please send feedback to <linux-bugs@chelsio.com>. 2573 2574 To compile this driver as a module, choose M here: the module 2575 will be called cxgb3. 2576 2577config EHEA 2578 tristate "eHEA Ethernet support" 2579 depends on IBMEBUS && INET && SPARSEMEM 2580 select INET_LRO 2581 ---help--- 2582 This driver supports the IBM pSeries eHEA ethernet adapter. 2583 2584 To compile the driver as a module, choose M here. The module 2585 will be called ehea. 2586 2587config ENIC 2588 tristate "Cisco 10G Ethernet NIC support" 2589 depends on PCI && INET 2590 select INET_LRO 2591 help 2592 This enables the support for the Cisco 10G Ethernet card. 2593 2594config IXGBE 2595 tristate "Intel(R) 10GbE PCI Express adapters support" 2596 depends on PCI && INET 2597 select MDIO 2598 ---help--- 2599 This driver supports Intel(R) 10GbE PCI Express family of 2600 adapters. For more information on how to identify your adapter, go 2601 to the Adapter & Driver ID Guide at: 2602 2603 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2604 2605 For general information and support, go to the Intel support 2606 website at: 2607 2608 <http://support.intel.com> 2609 2610 To compile this driver as a module, choose M here. The module 2611 will be called ixgbe. 2612 2613config IXGBE_DCA 2614 bool "Direct Cache Access (DCA) Support" 2615 default y 2616 depends on IXGBE && DCA && !(IXGBE=y && DCA=m) 2617 ---help--- 2618 Say Y here if you want to use Direct Cache Access (DCA) in the 2619 driver. DCA is a method for warming the CPU cache before data 2620 is used, with the intent of lessening the impact of cache misses. 2621 2622config IXGBE_DCB 2623 bool "Data Center Bridging (DCB) Support" 2624 default n 2625 depends on IXGBE && DCB 2626 ---help--- 2627 Say Y here if you want to use Data Center Bridging (DCB) in the 2628 driver. 2629 2630 If unsure, say N. 2631 2632config IXGBEVF 2633 tristate "Intel(R) 82599 Virtual Function Ethernet support" 2634 depends on PCI_MSI 2635 ---help--- 2636 This driver supports Intel(R) 82599 virtual functions. For more 2637 information on how to identify your adapter, go to the Adapter & 2638 Driver ID Guide at: 2639 2640 <http://support.intel.com/support/network/sb/CS-008441.htm> 2641 2642 For general information and support, go to the Intel support 2643 website at: 2644 2645 <http://support.intel.com> 2646 2647 More specific information on configuring the driver is in 2648 <file:Documentation/networking/ixgbevf.txt>. 2649 2650 To compile this driver as a module, choose M here. The module 2651 will be called ixgbevf. MSI-X interrupt support is required 2652 for this driver to work correctly. 2653 2654config IXGB 2655 tristate "Intel(R) PRO/10GbE support" 2656 depends on PCI 2657 ---help--- 2658 This driver supports Intel(R) PRO/10GbE family of adapters for 2659 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver 2660 instead. For more information on how to identify your adapter, go 2661 to the Adapter & Driver ID Guide at: 2662 2663 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2664 2665 For general information and support, go to the Intel support 2666 website at: 2667 2668 <http://support.intel.com> 2669 2670 More specific information on configuring the driver is in 2671 <file:Documentation/networking/ixgb.txt>. 2672 2673 To compile this driver as a module, choose M here. The module 2674 will be called ixgb. 2675 2676config S2IO 2677 tristate "S2IO 10Gbe XFrame NIC" 2678 depends on PCI 2679 ---help--- 2680 This driver supports the 10Gbe XFrame NIC of S2IO. 2681 More specific information on configuring the driver is in 2682 <file:Documentation/networking/s2io.txt>. 2683 2684config VXGE 2685 tristate "Neterion X3100 Series 10GbE PCIe Server Adapter" 2686 depends on PCI && INET 2687 ---help--- 2688 This driver supports Neterion Inc's X3100 Series 10 GbE PCIe 2689 I/O Virtualized Server Adapter. 2690 More specific information on configuring the driver is in 2691 <file:Documentation/networking/vxge.txt>. 2692 2693config VXGE_DEBUG_TRACE_ALL 2694 bool "Enabling All Debug trace statments in driver" 2695 default n 2696 depends on VXGE 2697 ---help--- 2698 Say Y here if you want to enabling all the debug trace statements in 2699 driver. By default only few debug trace statements are enabled. 2700 2701config MYRI10GE 2702 tristate "Myricom Myri-10G Ethernet support" 2703 depends on PCI && INET 2704 select FW_LOADER 2705 select CRC32 2706 select INET_LRO 2707 ---help--- 2708 This driver supports Myricom Myri-10G Dual Protocol interface in 2709 Ethernet mode. If the eeprom on your board is not recent enough, 2710 you will need a newer firmware image. 2711 You may get this image or more information, at: 2712 2713 <http://www.myri.com/scs/download-Myri10GE.html> 2714 2715 To compile this driver as a module, choose M here. The module 2716 will be called myri10ge. 2717 2718config MYRI10GE_DCA 2719 bool "Direct Cache Access (DCA) Support" 2720 default y 2721 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m) 2722 ---help--- 2723 Say Y here if you want to use Direct Cache Access (DCA) in the 2724 driver. DCA is a method for warming the CPU cache before data 2725 is used, with the intent of lessening the impact of cache misses. 2726 2727config NETXEN_NIC 2728 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC" 2729 depends on PCI 2730 help 2731 This enables the support for NetXen's Gigabit Ethernet card. 2732 2733config NIU 2734 tristate "Sun Neptune 10Gbit Ethernet support" 2735 depends on PCI 2736 select CRC32 2737 help 2738 This enables support for cards based upon Sun's 2739 Neptune chipset. 2740 2741config PASEMI_MAC 2742 tristate "PA Semi 1/10Gbit MAC" 2743 depends on PPC_PASEMI && PCI 2744 select PHYLIB 2745 select INET_LRO 2746 help 2747 This driver supports the on-chip 1/10Gbit Ethernet controller on 2748 PA Semi's PWRficient line of chips. 2749 2750config MLX4_EN 2751 tristate "Mellanox Technologies 10Gbit Ethernet support" 2752 depends on PCI && INET 2753 select MLX4_CORE 2754 select INET_LRO 2755 help 2756 This driver supports Mellanox Technologies ConnectX Ethernet 2757 devices. 2758 2759config MLX4_CORE 2760 tristate 2761 depends on PCI 2762 default n 2763 2764config MLX4_DEBUG 2765 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED) 2766 depends on MLX4_CORE 2767 default y 2768 ---help--- 2769 This option causes debugging code to be compiled into the 2770 mlx4_core driver. The output can be turned on via the 2771 debug_level module parameter (which can also be set after 2772 the driver is loaded through sysfs). 2773 2774config TEHUTI 2775 tristate "Tehuti Networks 10G Ethernet" 2776 depends on PCI 2777 help 2778 Tehuti Networks 10G Ethernet NIC 2779 2780config BNX2X 2781 tristate "Broadcom NetXtremeII 10Gb support" 2782 depends on PCI 2783 select FW_LOADER 2784 select ZLIB_INFLATE 2785 select LIBCRC32C 2786 select MDIO 2787 help 2788 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards. 2789 To compile this driver as a module, choose M here: the module 2790 will be called bnx2x. This is recommended. 2791 2792config QLCNIC 2793 tristate "QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support" 2794 depends on PCI 2795 help 2796 This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet 2797 devices. 2798 2799config QLGE 2800 tristate "QLogic QLGE 10Gb Ethernet Driver Support" 2801 depends on PCI 2802 help 2803 This driver supports QLogic ISP8XXX 10Gb Ethernet cards. 2804 2805 To compile this driver as a module, choose M here: the module 2806 will be called qlge. 2807 2808source "drivers/net/sfc/Kconfig" 2809 2810source "drivers/net/benet/Kconfig" 2811 2812endif # NETDEV_10000 2813 2814source "drivers/net/tokenring/Kconfig" 2815 2816source "drivers/net/wireless/Kconfig" 2817 2818source "drivers/net/wimax/Kconfig" 2819 2820source "drivers/net/usb/Kconfig" 2821 2822source "drivers/net/pcmcia/Kconfig" 2823 2824source "drivers/net/wan/Kconfig" 2825 2826source "drivers/atm/Kconfig" 2827 2828source "drivers/ieee802154/Kconfig" 2829 2830source "drivers/s390/net/Kconfig" 2831 2832config XEN_NETDEV_FRONTEND 2833 tristate "Xen network device frontend driver" 2834 depends on XEN 2835 default y 2836 help 2837 The network device frontend driver allows the kernel to 2838 access network devices exported exported by a virtual 2839 machine containing a physical network device driver. The 2840 frontend driver is intended for unprivileged guest domains; 2841 if you are compiling a kernel for a Xen guest, you almost 2842 certainly want to enable this. 2843 2844config ISERIES_VETH 2845 tristate "iSeries Virtual Ethernet driver support" 2846 depends on PPC_ISERIES 2847 2848config RIONET 2849 tristate "RapidIO Ethernet over messaging driver support" 2850 depends on RAPIDIO 2851 2852config RIONET_TX_SIZE 2853 int "Number of outbound queue entries" 2854 depends on RIONET 2855 default "128" 2856 2857config RIONET_RX_SIZE 2858 int "Number of inbound queue entries" 2859 depends on RIONET 2860 default "128" 2861 2862config FDDI 2863 tristate "FDDI driver support" 2864 depends on (PCI || EISA || TC) 2865 help 2866 Fiber Distributed Data Interface is a high speed local area network 2867 design; essentially a replacement for high speed Ethernet. FDDI can 2868 run over copper or fiber. If you are connected to such a network and 2869 want a driver for the FDDI card in your computer, say Y here (and 2870 then also Y to the driver for your FDDI card, below). Most people 2871 will say N. 2872 2873config DEFXX 2874 tristate "Digital DEFTA/DEFEA/DEFPA adapter support" 2875 depends on FDDI && (PCI || EISA || TC) 2876 ---help--- 2877 This is support for the DIGITAL series of TURBOchannel (DEFTA), 2878 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you 2879 to a local FDDI network. 2880 2881 To compile this driver as a module, choose M here: the module 2882 will be called defxx. If unsure, say N. 2883 2884config DEFXX_MMIO 2885 bool 2886 prompt "Use MMIO instead of PIO" if PCI || EISA 2887 depends on DEFXX 2888 default n if PCI || EISA 2889 default y 2890 ---help--- 2891 This instructs the driver to use EISA or PCI memory-mapped I/O 2892 (MMIO) as appropriate instead of programmed I/O ports (PIO). 2893 Enabling this gives an improvement in processing time in parts 2894 of the driver, but it may cause problems with EISA (DEFEA) 2895 adapters. TURBOchannel does not have the concept of I/O ports, 2896 so MMIO is always used for these (DEFTA) adapters. 2897 2898 If unsure, say N. 2899 2900config SKFP 2901 tristate "SysKonnect FDDI PCI support" 2902 depends on FDDI && PCI 2903 select BITREVERSE 2904 ---help--- 2905 Say Y here if you have a SysKonnect FDDI PCI adapter. 2906 The following adapters are supported by this driver: 2907 - SK-5521 (SK-NET FDDI-UP) 2908 - SK-5522 (SK-NET FDDI-UP DAS) 2909 - SK-5541 (SK-NET FDDI-FP) 2910 - SK-5543 (SK-NET FDDI-LP) 2911 - SK-5544 (SK-NET FDDI-LP DAS) 2912 - SK-5821 (SK-NET FDDI-UP64) 2913 - SK-5822 (SK-NET FDDI-UP64 DAS) 2914 - SK-5841 (SK-NET FDDI-FP64) 2915 - SK-5843 (SK-NET FDDI-LP64) 2916 - SK-5844 (SK-NET FDDI-LP64 DAS) 2917 - Netelligent 100 FDDI DAS Fibre SC 2918 - Netelligent 100 FDDI SAS Fibre SC 2919 - Netelligent 100 FDDI DAS UTP 2920 - Netelligent 100 FDDI SAS UTP 2921 - Netelligent 100 FDDI SAS Fibre MIC 2922 2923 Read <file:Documentation/networking/skfp.txt> for information about 2924 the driver. 2925 2926 Questions concerning this driver can be addressed to: 2927 <linux@syskonnect.de> 2928 2929 To compile this driver as a module, choose M here: the module 2930 will be called skfp. This is recommended. 2931 2932config HIPPI 2933 bool "HIPPI driver support (EXPERIMENTAL)" 2934 depends on EXPERIMENTAL && INET && PCI 2935 help 2936 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and 2937 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI 2938 can run over copper (25m) or fiber (300m on multi-mode or 10km on 2939 single-mode). HIPPI networks are commonly used for clusters and to 2940 connect to super computers. If you are connected to a HIPPI network 2941 and have a HIPPI network card in your computer that you want to use 2942 under Linux, say Y here (you must also remember to enable the driver 2943 for your HIPPI card below). Most people will say N here. 2944 2945config ROADRUNNER 2946 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)" 2947 depends on HIPPI && PCI 2948 help 2949 Say Y here if this is your PCI HIPPI network card. 2950 2951 To compile this driver as a module, choose M here: the module 2952 will be called rrunner. If unsure, say N. 2953 2954config ROADRUNNER_LARGE_RINGS 2955 bool "Use large TX/RX rings (EXPERIMENTAL)" 2956 depends on ROADRUNNER 2957 help 2958 If you say Y here, the RoadRunner driver will preallocate up to 2 MB 2959 of additional memory to allow for fastest operation, both for 2960 transmitting and receiving. This memory cannot be used by any other 2961 kernel code or by user space programs. Say Y here only if you have 2962 the memory. 2963 2964config PLIP 2965 tristate "PLIP (parallel port) support" 2966 depends on PARPORT 2967 ---help--- 2968 PLIP (Parallel Line Internet Protocol) is used to create a 2969 reasonably fast mini network consisting of two (or, rarely, more) 2970 local machines. A PLIP link from a Linux box is a popular means to 2971 install a Linux distribution on a machine which doesn't have a 2972 CD-ROM drive (a minimal system has to be transferred with floppies 2973 first). The kernels on both machines need to have this PLIP option 2974 enabled for this to work. 2975 2976 The PLIP driver has two modes, mode 0 and mode 1. The parallel 2977 ports (the connectors at the computers with 25 holes) are connected 2978 with "null printer" or "Turbo Laplink" cables which can transmit 4 2979 bits at a time (mode 0) or with special PLIP cables, to be used on 2980 bidirectional parallel ports only, which can transmit 8 bits at a 2981 time (mode 1); you can find the wiring of these cables in 2982 <file:Documentation/networking/PLIP.txt>. The cables can be up to 2983 15m long. Mode 0 works also if one of the machines runs DOS/Windows 2984 and has some PLIP software installed, e.g. the Crynwr PLIP packet 2985 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>) 2986 and winsock or NCSA's telnet. 2987 2988 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well 2989 as the NET-3-HOWTO, both available from 2990 <http://www.tldp.org/docs.html#howto>. Note that the PLIP 2991 protocol has been changed and this PLIP driver won't work together 2992 with the PLIP support in Linux versions 1.0.x. This option enlarges 2993 your kernel by about 8 KB. 2994 2995 To compile this driver as a module, choose M here. The module 2996 will be called plip. If unsure, say Y or M, in case you buy 2997 a laptop later. 2998 2999config PPP 3000 tristate "PPP (point-to-point protocol) support" 3001 select SLHC 3002 ---help--- 3003 PPP (Point to Point Protocol) is a newer and better SLIP. It serves 3004 the same purpose: sending Internet traffic over telephone (and other 3005 serial) lines. Ask your access provider if they support it, because 3006 otherwise you can't use it; most Internet access providers these 3007 days support PPP rather than SLIP. 3008 3009 To use PPP, you need an additional program called pppd as described 3010 in the PPP-HOWTO, available at 3011 <http://www.tldp.org/docs.html#howto>. Make sure that you have 3012 the version of pppd recommended in <file:Documentation/Changes>. 3013 The PPP option enlarges your kernel by about 16 KB. 3014 3015 There are actually two versions of PPP: the traditional PPP for 3016 asynchronous lines, such as regular analog phone lines, and 3017 synchronous PPP which can be used over digital ISDN lines for 3018 example. If you want to use PPP over phone lines or other 3019 asynchronous serial lines, you need to say Y (or M) here and also to 3020 the next option, "PPP support for async serial ports". For PPP over 3021 synchronous lines, you should say Y (or M) here and to "Support 3022 synchronous PPP", below. 3023 3024 If you said Y to "Version information on all symbols" above, then 3025 you cannot compile the PPP driver into the kernel; you can then only 3026 compile it as a module. To compile this driver as a module, choose M 3027 here. The module will be called ppp_generic. 3028 3029config PPP_MULTILINK 3030 bool "PPP multilink support (EXPERIMENTAL)" 3031 depends on PPP && EXPERIMENTAL 3032 help 3033 PPP multilink is a protocol (defined in RFC 1990) which allows you 3034 to combine several (logical or physical) lines into one logical PPP 3035 connection, so that you can utilize your full bandwidth. 3036 3037 This has to be supported at the other end as well and you need a 3038 version of the pppd daemon which understands the multilink protocol. 3039 3040 If unsure, say N. 3041 3042config PPP_FILTER 3043 bool "PPP filtering" 3044 depends on PPP 3045 help 3046 Say Y here if you want to be able to filter the packets passing over 3047 PPP interfaces. This allows you to control which packets count as 3048 activity (i.e. which packets will reset the idle timer or bring up 3049 a demand-dialed link) and which packets are to be dropped entirely. 3050 You need to say Y here if you wish to use the pass-filter and 3051 active-filter options to pppd. 3052 3053 If unsure, say N. 3054 3055config PPP_ASYNC 3056 tristate "PPP support for async serial ports" 3057 depends on PPP 3058 select CRC_CCITT 3059 ---help--- 3060 Say Y (or M) here if you want to be able to use PPP over standard 3061 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use 3062 a modem (not a synchronous or ISDN modem) to contact your ISP, you 3063 need this option. 3064 3065 To compile this driver as a module, choose M here. 3066 3067 If unsure, say Y. 3068 3069config PPP_SYNC_TTY 3070 tristate "PPP support for sync tty ports" 3071 depends on PPP 3072 help 3073 Say Y (or M) here if you want to be able to use PPP over synchronous 3074 (HDLC) tty devices, such as the SyncLink adapter. These devices 3075 are often used for high-speed leased lines like T1/E1. 3076 3077 To compile this driver as a module, choose M here. 3078 3079config PPP_DEFLATE 3080 tristate "PPP Deflate compression" 3081 depends on PPP 3082 select ZLIB_INFLATE 3083 select ZLIB_DEFLATE 3084 ---help--- 3085 Support for the Deflate compression method for PPP, which uses the 3086 Deflate algorithm (the same algorithm that gzip uses) to compress 3087 each PPP packet before it is sent over the wire. The machine at the 3088 other end of the PPP link (usually your ISP) has to support the 3089 Deflate compression method as well for this to be useful. Even if 3090 they don't support it, it is safe to say Y here. 3091 3092 To compile this driver as a module, choose M here. 3093 3094config PPP_BSDCOMP 3095 tristate "PPP BSD-Compress compression" 3096 depends on PPP 3097 ---help--- 3098 Support for the BSD-Compress compression method for PPP, which uses 3099 the LZW compression method to compress each PPP packet before it is 3100 sent over the wire. The machine at the other end of the PPP link 3101 (usually your ISP) has to support the BSD-Compress compression 3102 method as well for this to be useful. Even if they don't support it, 3103 it is safe to say Y here. 3104 3105 The PPP Deflate compression method ("PPP Deflate compression", 3106 above) is preferable to BSD-Compress, because it compresses better 3107 and is patent-free. 3108 3109 Note that the BSD compression code will always be compiled as a 3110 module; it is called bsd_comp and will show up in the directory 3111 modules once you have said "make modules". If unsure, say N. 3112 3113config PPP_MPPE 3114 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)" 3115 depends on PPP && EXPERIMENTAL 3116 select CRYPTO 3117 select CRYPTO_SHA1 3118 select CRYPTO_ARC4 3119 select CRYPTO_ECB 3120 ---help--- 3121 Support for the MPPE Encryption protocol, as employed by the 3122 Microsoft Point-to-Point Tunneling Protocol. 3123 3124 See http://pptpclient.sourceforge.net/ for information on 3125 configuring PPTP clients and servers to utilize this method. 3126 3127config PPPOE 3128 tristate "PPP over Ethernet (EXPERIMENTAL)" 3129 depends on EXPERIMENTAL && PPP 3130 help 3131 Support for PPP over Ethernet. 3132 3133 This driver requires the latest version of pppd from the CVS 3134 repository at cvs.samba.org. Alternatively, see the 3135 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>) 3136 which contains instruction on how to use this driver (under 3137 the heading "Kernel mode PPPoE"). 3138 3139config PPPOATM 3140 tristate "PPP over ATM" 3141 depends on ATM && PPP 3142 help 3143 Support PPP (Point to Point Protocol) encapsulated in ATM frames. 3144 This implementation does not yet comply with section 8 of RFC2364, 3145 which can lead to bad results if the ATM peer loses state and 3146 changes its encapsulation unilaterally. 3147 3148config PPPOL2TP 3149 tristate "PPP over L2TP (EXPERIMENTAL)" 3150 depends on EXPERIMENTAL && PPP && INET 3151 help 3152 Support for PPP-over-L2TP socket family. L2TP is a protocol 3153 used by ISPs and enterprises to tunnel PPP traffic over UDP 3154 tunnels. L2TP is replacing PPTP for VPN uses. 3155 3156 This kernel component handles only L2TP data packets: a 3157 userland daemon handles L2TP the control protocol (tunnel 3158 and session setup). One such daemon is OpenL2TP 3159 (http://openl2tp.sourceforge.net/). 3160 3161config SLIP 3162 tristate "SLIP (serial line) support" 3163 ---help--- 3164 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to 3165 connect to your Internet service provider or to connect to some 3166 other local Unix box or if you want to configure your Linux box as a 3167 Slip/CSlip server for other people to dial in. SLIP (Serial Line 3168 Internet Protocol) is a protocol used to send Internet traffic over 3169 serial connections such as telephone lines or null modem cables; 3170 nowadays, the protocol PPP is more commonly used for this same 3171 purpose. 3172 3173 Normally, your access provider has to support SLIP in order for you 3174 to be able to use it, but there is now a SLIP emulator called SLiRP 3175 around (available from 3176 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which 3177 allows you to use SLIP over a regular dial up shell connection. If 3178 you plan to use SLiRP, make sure to say Y to CSLIP, below. The 3179 NET-3-HOWTO, available from 3180 <http://www.tldp.org/docs.html#howto>, explains how to 3181 configure SLIP. Note that you don't need this option if you just 3182 want to run term (term is a program which gives you almost full 3183 Internet connectivity if you have a regular dial up shell account on 3184 some Internet connected Unix computer. Read 3185 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP 3186 support will enlarge your kernel by about 4 KB. If unsure, say N. 3187 3188 To compile this driver as a module, choose M here. The module 3189 will be called slip. 3190 3191config SLIP_COMPRESSED 3192 bool "CSLIP compressed headers" 3193 depends on SLIP 3194 select SLHC 3195 ---help--- 3196 This protocol is faster than SLIP because it uses compression on the 3197 TCP/IP headers (not on the data itself), but it has to be supported 3198 on both ends. Ask your access provider if you are not sure and 3199 answer Y, just in case. You will still be able to use plain SLIP. If 3200 you plan to use SLiRP, the SLIP emulator (available from 3201 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which 3202 allows you to use SLIP over a regular dial up shell connection, you 3203 definitely want to say Y here. The NET-3-HOWTO, available from 3204 <http://www.tldp.org/docs.html#howto>, explains how to configure 3205 CSLIP. This won't enlarge your kernel. 3206 3207config SLHC 3208 tristate 3209 help 3210 This option enables Van Jacobsen serial line header compression 3211 routines. 3212 3213config SLIP_SMART 3214 bool "Keepalive and linefill" 3215 depends on SLIP 3216 help 3217 Adds additional capabilities to the SLIP driver to support the 3218 RELCOM line fill and keepalive monitoring. Ideal on poor quality 3219 analogue lines. 3220 3221config SLIP_MODE_SLIP6 3222 bool "Six bit SLIP encapsulation" 3223 depends on SLIP 3224 help 3225 Just occasionally you may need to run IP over hostile serial 3226 networks that don't pass all control characters or are only seven 3227 bit. Saying Y here adds an extra mode you can use with SLIP: 3228 "slip6". In this mode, SLIP will only send normal ASCII symbols over 3229 the serial device. Naturally, this has to be supported at the other 3230 end of the link as well. It's good enough, for example, to run IP 3231 over the async ports of a Camtec JNT Pad. If unsure, say N. 3232 3233config NET_FC 3234 bool "Fibre Channel driver support" 3235 depends on SCSI && PCI 3236 help 3237 Fibre Channel is a high speed serial protocol mainly used to connect 3238 large storage devices to the computer; it is compatible with and 3239 intended to replace SCSI. 3240 3241 If you intend to use Fibre Channel, you need to have a Fibre channel 3242 adaptor card in your computer; say Y here and to the driver for your 3243 adaptor below. You also should have said Y to "SCSI support" and 3244 "SCSI generic support". 3245 3246config NETCONSOLE 3247 tristate "Network console logging support (EXPERIMENTAL)" 3248 depends on EXPERIMENTAL 3249 ---help--- 3250 If you want to log kernel messages over the network, enable this. 3251 See <file:Documentation/networking/netconsole.txt> for details. 3252 3253config NETCONSOLE_DYNAMIC 3254 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)" 3255 depends on NETCONSOLE && SYSFS && EXPERIMENTAL 3256 select CONFIGFS_FS 3257 help 3258 This option enables the ability to dynamically reconfigure target 3259 parameters (interface, IP addresses, port numbers, MAC addresses) 3260 at runtime through a userspace interface exported using configfs. 3261 See <file:Documentation/networking/netconsole.txt> for details. 3262 3263config NETPOLL 3264 def_bool NETCONSOLE 3265 3266config NETPOLL_TRAP 3267 bool "Netpoll traffic trapping" 3268 default n 3269 depends on NETPOLL 3270 3271config NET_POLL_CONTROLLER 3272 def_bool NETPOLL 3273 3274config VIRTIO_NET 3275 tristate "Virtio network driver (EXPERIMENTAL)" 3276 depends on EXPERIMENTAL && VIRTIO 3277 ---help--- 3278 This is the virtual network driver for virtio. It can be used with 3279 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M. 3280 3281config VMXNET3 3282 tristate "VMware VMXNET3 ethernet driver" 3283 depends on PCI && INET 3284 help 3285 This driver supports VMware's vmxnet3 virtual ethernet NIC. 3286 To compile this driver as a module, choose M here: the 3287 module will be called vmxnet3. 3288 3289endif # NETDEVICES 3290