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