Kconfig 106 KB

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