Kconfig 105 KB

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