cs89x0.txt 23 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625
  1. NOTE
  2. ----
  3. This document was contributed by Cirrus Logic for kernel 2.2.5. This version
  4. has been updated for 2.3.48 by Andrew Morton.
  5. Cirrus make a copy of this driver available at their website, as
  6. described below. In general, you should use the driver version which
  7. comes with your Linux distribution.
  8. CIRRUS LOGIC LAN CS8900/CS8920 ETHERNET ADAPTERS
  9. Linux Network Interface Driver ver. 2.00 <kernel 2.3.48>
  10. ===============================================================================
  11. TABLE OF CONTENTS
  12. 1.0 CIRRUS LOGIC LAN CS8900/CS8920 ETHERNET ADAPTERS
  13. 1.1 Product Overview
  14. 1.2 Driver Description
  15. 1.2.1 Driver Name
  16. 1.2.2 File in the Driver Package
  17. 1.3 System Requirements
  18. 1.4 Licensing Information
  19. 2.0 ADAPTER INSTALLATION and CONFIGURATION
  20. 2.1 CS8900-based Adapter Configuration
  21. 2.2 CS8920-based Adapter Configuration
  22. 3.0 LOADING THE DRIVER AS A MODULE
  23. 4.0 COMPILING THE DRIVER
  24. 4.1 Compiling the Driver as a Loadable Module
  25. 4.2 Compiling the driver to support memory mode
  26. 4.3 Compiling the driver to support Rx DMA
  27. 5.0 TESTING AND TROUBLESHOOTING
  28. 5.1 Known Defects and Limitations
  29. 5.2 Testing the Adapter
  30. 5.2.1 Diagnostic Self-Test
  31. 5.2.2 Diagnostic Network Test
  32. 5.3 Using the Adapter's LEDs
  33. 5.4 Resolving I/O Conflicts
  34. 6.0 TECHNICAL SUPPORT
  35. 6.1 Contacting Cirrus Logic's Technical Support
  36. 6.2 Information Required Before Contacting Technical Support
  37. 6.3 Obtaining the Latest Driver Version
  38. 6.4 Current maintainer
  39. 6.5 Kernel boot parameters
  40. 1.0 CIRRUS LOGIC LAN CS8900/CS8920 ETHERNET ADAPTERS
  41. ===============================================================================
  42. 1.1 PRODUCT OVERVIEW
  43. The CS8900-based ISA Ethernet Adapters from Cirrus Logic follow
  44. IEEE 802.3 standards and support half or full-duplex operation in ISA bus
  45. computers on 10 Mbps Ethernet networks. The adapters are designed for operation
  46. in 16-bit ISA or EISA bus expansion slots and are available in
  47. 10BaseT-only or 3-media configurations (10BaseT, 10Base2, and AUI for 10Base-5
  48. or fiber networks).
  49. CS8920-based adapters are similar to the CS8900-based adapter with additional
  50. features for Plug and Play (PnP) support and Wakeup Frame recognition. As
  51. such, the configuration procedures differ somewhat between the two types of
  52. adapters. Refer to the "Adapter Configuration" section for details on
  53. configuring both types of adapters.
  54. 1.2 DRIVER DESCRIPTION
  55. The CS8900/CS8920 Ethernet Adapter driver for Linux supports the Linux
  56. v2.3.48 or greater kernel. It can be compiled directly into the kernel
  57. or loaded at run-time as a device driver module.
  58. 1.2.1 Driver Name: cs89x0
  59. 1.2.2 Files in the Driver Archive:
  60. The files in the driver at Cirrus' website include:
  61. readme.txt - this file
  62. build - batch file to compile cs89x0.c.
  63. cs89x0.c - driver C code
  64. cs89x0.h - driver header file
  65. cs89x0.o - pre-compiled module (for v2.2.5 kernel)
  66. config/Config.in - sample file to include cs89x0 driver in the kernel.
  67. config/Makefile - sample file to include cs89x0 driver in the kernel.
  68. config/Space.c - sample file to include cs89x0 driver in the kernel.
  69. 1.3 SYSTEM REQUIREMENTS
  70. The following hardware is required:
  71. * Cirrus Logic LAN (CS8900/20-based) Ethernet ISA Adapter
  72. * IBM or IBM-compatible PC with:
  73. * An 80386 or higher processor
  74. * 16 bytes of contiguous IO space available between 210h - 370h
  75. * One available IRQ (5,10,11,or 12 for the CS8900, 3-7,9-15 for CS8920).
  76. * Appropriate cable (and connector for AUI, 10BASE-2) for your network
  77. topology.
  78. The following software is required:
  79. * LINUX kernel version 2.3.48 or higher
  80. * CS8900/20 Setup Utility (DOS-based)
  81. * LINUX kernel sources for your kernel (if compiling into kernel)
  82. * GNU Toolkit (gcc and make) v2.6 or above (if compiling into kernel
  83. or a module)
  84. 1.4 LICENSING INFORMATION
  85. This program is free software; you can redistribute it and/or modify it under
  86. the terms of the GNU General Public License as published by the Free Software
  87. Foundation, version 1.
  88. This program is distributed in the hope that it will be useful, but WITHOUT
  89. ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
  90. FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
  91. more details.
  92. For a full copy of the GNU General Public License, write to the Free Software
  93. Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
  94. 2.0 ADAPTER INSTALLATION and CONFIGURATION
  95. ===============================================================================
  96. Both the CS8900 and CS8920-based adapters can be configured using parameters
  97. stored in an on-board EEPROM. You must use the DOS-based CS8900/20 Setup
  98. Utility if you want to change the adapter's configuration in EEPROM.
  99. When loading the driver as a module, you can specify many of the adapter's
  100. configuration parameters on the command-line to override the EEPROM's settings
  101. or for interface configuration when an EEPROM is not used. (CS8920-based
  102. adapters must use an EEPROM.) See Section 3.0 LOADING THE DRIVER AS A MODULE.
  103. Since the CS8900/20 Setup Utility is a DOS-based application, you must install
  104. and configure the adapter in a DOS-based system using the CS8900/20 Setup
  105. Utility before installation in the target LINUX system. (Not required if
  106. installing a CS8900-based adapter and the default configuration is acceptable.)
  107. 2.1 CS8900-BASED ADAPTER CONFIGURATION
  108. CS8900-based adapters shipped from Cirrus Logic have been configured
  109. with the following "default" settings:
  110. Operation Mode: Memory Mode
  111. IRQ: 10
  112. Base I/O Address: 300
  113. Memory Base Address: D0000
  114. Optimization: DOS Client
  115. Transmission Mode: Half-duplex
  116. BootProm: None
  117. Media Type: Autodetect (3-media cards) or
  118. 10BASE-T (10BASE-T only adapter)
  119. You should only change the default configuration settings if conflicts with
  120. another adapter exists. To change the adapter's configuration, run the
  121. CS8900/20 Setup Utility.
  122. 2.2 CS8920-BASED ADAPTER CONFIGURATION
  123. CS8920-based adapters are shipped from Cirrus Logic configured as Plug
  124. and Play (PnP) enabled. However, since the cs89x0 driver does NOT
  125. support PnP, you must install the CS8920 adapter in a DOS-based PC and
  126. run the CS8900/20 Setup Utility to disable PnP and configure the
  127. adapter before installation in the target Linux system. Failure to do
  128. this will leave the adapter inactive and the driver will be unable to
  129. communicate with the adapter.
  130. ****************************************************************
  131. * CS8920-BASED ADAPTERS: *
  132. * *
  133. * CS8920-BASED ADAPTERS ARE PLUG and PLAY ENABLED BY DEFAULT. *
  134. * THE CS89X0 DRIVER DOES NOT SUPPORT PnP. THEREFORE, YOU MUST *
  135. * RUN THE CS8900/20 SETUP UTILITY TO DISABLE PnP SUPPORT AND *
  136. * TO ACTIVATE THE ADAPTER. *
  137. ****************************************************************
  138. 3.0 LOADING THE DRIVER AS A MODULE
  139. ===============================================================================
  140. If the driver is compiled as a loadable module, you can load the driver module
  141. with the 'modprobe' command. Many of the adapter's configuration parameters can
  142. be specified as command-line arguments to the load command. This facility
  143. provides a means to override the EEPROM's settings or for interface
  144. configuration when an EEPROM is not used.
  145. Example:
  146. insmod cs89x0.o io=0x200 irq=0xA media=aui
  147. This example loads the module and configures the adapter to use an IO port base
  148. address of 200h, interrupt 10, and use the AUI media connection. The following
  149. configuration options are available on the command line:
  150. * io=### - specify IO address (200h-360h)
  151. * irq=## - specify interrupt level
  152. * use_dma=1 - Enable DMA
  153. * dma=# - specify dma channel (Driver is compiled to support
  154. Rx DMA only)
  155. * dmasize=# (16 or 64) - DMA size 16K or 64K. Default value is set to 16.
  156. * media=rj45 - specify media type
  157. or media=bnc
  158. or media=aui
  159. or media=auto
  160. * duplex=full - specify forced half/full/autonegotiate duplex
  161. or duplex=half
  162. or duplex=auto
  163. * debug=# - debug level (only available if the driver was compiled
  164. for debugging)
  165. NOTES:
  166. a) If an EEPROM is present, any specified command-line parameter
  167. will override the corresponding configuration value stored in
  168. EEPROM.
  169. b) The "io" parameter must be specified on the command-line.
  170. c) The driver's hardware probe routine is designed to avoid
  171. writing to I/O space until it knows that there is a cs89x0
  172. card at the written addresses. This could cause problems
  173. with device probing. To avoid this behaviour, add one
  174. to the `io=' module parameter. This doesn't actually change
  175. the I/O address, but it is a flag to tell the driver
  176. to partially initialise the hardware before trying to
  177. identify the card. This could be dangerous if you are
  178. not sure that there is a cs89x0 card at the provided address.
  179. For example, to scan for an adapter located at IO base 0x300,
  180. specify an IO address of 0x301.
  181. d) The "duplex=auto" parameter is only supported for the CS8920.
  182. e) The minimum command-line configuration required if an EEPROM is
  183. not present is:
  184. io
  185. irq
  186. media type (no autodetect)
  187. f) The following additional parameters are CS89XX defaults (values
  188. used with no EEPROM or command-line argument).
  189. * DMA Burst = enabled
  190. * IOCHRDY Enabled = enabled
  191. * UseSA = enabled
  192. * CS8900 defaults to half-duplex if not specified on command-line
  193. * CS8920 defaults to autoneg if not specified on command-line
  194. * Use reset defaults for other config parameters
  195. * dma_mode = 0
  196. g) You can use ifconfig to set the adapter's Ethernet address.
  197. h) Many Linux distributions use the 'modprobe' command to load
  198. modules. This program uses the '/etc/conf.modules' file to
  199. determine configuration information which is passed to a driver
  200. module when it is loaded. All the configuration options which are
  201. described above may be placed within /etc/conf.modules.
  202. For example:
  203. > cat /etc/conf.modules
  204. ...
  205. alias eth0 cs89x0
  206. options cs89x0 io=0x0200 dma=5 use_dma=1
  207. ...
  208. In this example we are telling the module system that the
  209. ethernet driver for this machine should use the cs89x0 driver. We
  210. are asking 'modprobe' to pass the 'io', 'dma' and 'use_dma'
  211. arguments to the driver when it is loaded.
  212. i) Cirrus recommend that the cs89x0 use the ISA DMA channels 5, 6 or
  213. 7. You will probably find that other DMA channels will not work.
  214. j) The cs89x0 supports DMA for receiving only. DMA mode is
  215. significantly more efficient. Flooding a 400 MHz Celeron machine
  216. with large ping packets consumes 82% of its CPU capacity in non-DMA
  217. mode. With DMA this is reduced to 45%.
  218. k) If your Linux kernel was compiled with inbuilt plug-and-play
  219. support you will be able to find information about the cs89x0 card
  220. with the command
  221. cat /proc/isapnp
  222. l) If during DMA operation you find erratic behavior or network data
  223. corruption you should use your PC's BIOS to slow the EISA bus clock.
  224. m) If the cs89x0 driver is compiled directly into the kernel
  225. (non-modular) then its I/O address is automatically determined by
  226. ISA bus probing. The IRQ number, media options, etc are determined
  227. from the card's EEPROM.
  228. n) If the cs89x0 driver is compiled directly into the kernel, DMA
  229. mode may be selected by providing the kernel with a boot option
  230. 'cs89x0_dma=N' where 'N' is the desired DMA channel number (5, 6 or 7).
  231. Kernel boot options may be provided on the LILO command line:
  232. LILO boot: linux cs89x0_dma=5
  233. or they may be placed in /etc/lilo.conf:
  234. image=/boot/bzImage-2.3.48
  235. append="cs89x0_dma=5"
  236. label=linux
  237. root=/dev/hda5
  238. read-only
  239. The DMA Rx buffer size is hardwired to 16 kbytes in this mode.
  240. (64k mode is not available).
  241. 4.0 COMPILING THE DRIVER
  242. ===============================================================================
  243. The cs89x0 driver can be compiled directly into the kernel or compiled into
  244. a loadable device driver module.
  245. 4.1 COMPILING THE DRIVER AS A LOADABLE MODULE
  246. To compile the driver into a loadable module, use the following command
  247. (single command line, without quotes):
  248. "gcc -D__KERNEL__ -I/usr/src/linux/include -I/usr/src/linux/net/inet -Wall
  249. -Wstrict-prototypes -O2 -fomit-frame-pointer -DMODULE -DCONFIG_MODVERSIONS
  250. -c cs89x0.c"
  251. 4.2 COMPILING THE DRIVER TO SUPPORT MEMORY MODE
  252. Support for memory mode was not carried over into the 2.3 series kernels.
  253. 4.3 COMPILING THE DRIVER TO SUPPORT Rx DMA
  254. The compile-time optionality for DMA was removed in the 2.3 kernel
  255. series. DMA support is now unconditionally part of the driver. It is
  256. enabled by the 'use_dma=1' module option.
  257. 5.0 TESTING AND TROUBLESHOOTING
  258. ===============================================================================
  259. 5.1 KNOWN DEFECTS and LIMITATIONS
  260. Refer to the RELEASE.TXT file distributed as part of this archive for a list of
  261. known defects, driver limitations, and work arounds.
  262. 5.2 TESTING THE ADAPTER
  263. Once the adapter has been installed and configured, the diagnostic option of
  264. the CS8900/20 Setup Utility can be used to test the functionality of the
  265. adapter and its network connection. Use the diagnostics 'Self Test' option to
  266. test the functionality of the adapter with the hardware configuration you have
  267. assigned. You can use the diagnostics 'Network Test' to test the ability of the
  268. adapter to communicate across the Ethernet with another PC equipped with a
  269. CS8900/20-based adapter card (it must also be running the CS8900/20 Setup
  270. Utility).
  271. NOTE: The Setup Utility's diagnostics are designed to run in a
  272. DOS-only operating system environment. DO NOT run the diagnostics
  273. from a DOS or command prompt session under Windows 95, Windows NT,
  274. OS/2, or other operating system.
  275. To run the diagnostics tests on the CS8900/20 adapter:
  276. 1.) Boot DOS on the PC and start the CS8900/20 Setup Utility.
  277. 2.) The adapter's current configuration is displayed. Hit the ENTER key to
  278. get to the main menu.
  279. 4.) Select 'Diagnostics' (ALT-G) from the main menu.
  280. * Select 'Self-Test' to test the adapter's basic functionality.
  281. * Select 'Network Test' to test the network connection and cabling.
  282. 5.2.1 DIAGNOSTIC SELF-TEST
  283. The diagnostic self-test checks the adapter's basic functionality as well as
  284. its ability to communicate across the ISA bus based on the system resources
  285. assigned during hardware configuration. The following tests are performed:
  286. * IO Register Read/Write Test
  287. The IO Register Read/Write test insures that the CS8900/20 can be
  288. accessed in IO mode, and that the IO base address is correct.
  289. * Shared Memory Test
  290. The Shared Memory test insures the CS8900/20 can be accessed in memory
  291. mode and that the range of memory addresses assigned does not conflict
  292. with other devices in the system.
  293. * Interrupt Test
  294. The Interrupt test insures there are no conflicts with the assigned IRQ
  295. signal.
  296. * EEPROM Test
  297. The EEPROM test insures the EEPROM can be read.
  298. * Chip RAM Test
  299. The Chip RAM test insures the 4K of memory internal to the CS8900/20 is
  300. working properly.
  301. * Internal Loop-back Test
  302. The Internal Loop Back test insures the adapter's transmitter and
  303. receiver are operating properly. If this test fails, make sure the
  304. adapter's cable is connected to the network (check for LED activity for
  305. example).
  306. * Boot PROM Test
  307. The Boot PROM test insures the Boot PROM is present, and can be read.
  308. Failure indicates the Boot PROM was not successfully read due to a
  309. hardware problem or due to a conflicts on the Boot PROM address
  310. assignment. (Test only applies if the adapter is configured to use the
  311. Boot PROM option.)
  312. Failure of a test item indicates a possible system resource conflict with
  313. another device on the ISA bus. In this case, you should use the Manual Setup
  314. option to reconfigure the adapter by selecting a different value for the system
  315. resource that failed.
  316. 5.2.2 DIAGNOSTIC NETWORK TEST
  317. The Diagnostic Network Test verifies a working network connection by
  318. transferring data between two CS8900/20 adapters installed in different PCs
  319. on the same network. (Note: the diagnostic network test should not be run
  320. between two nodes across a router.)
  321. This test requires that each of the two PCs have a CS8900/20-based adapter
  322. installed and have the CS8900/20 Setup Utility running. The first PC is
  323. configured as a Responder and the other PC is configured as an Initiator.
  324. Once the Initiator is started, it sends data frames to the Responder which
  325. returns the frames to the Initiator.
  326. The total number of frames received and transmitted are displayed on the
  327. Initiator's display, along with a count of the number of frames received and
  328. transmitted OK or in error. The test can be terminated anytime by the user at
  329. either PC.
  330. To setup the Diagnostic Network Test:
  331. 1.) Select a PC with a CS8900/20-based adapter and a known working network
  332. connection to act as the Responder. Run the CS8900/20 Setup Utility
  333. and select 'Diagnostics -> Network Test -> Responder' from the main
  334. menu. Hit ENTER to start the Responder.
  335. 2.) Return to the PC with the CS8900/20-based adapter you want to test and
  336. start the CS8900/20 Setup Utility.
  337. 3.) From the main menu, Select 'Diagnostic -> Network Test -> Initiator'.
  338. Hit ENTER to start the test.
  339. You may stop the test on the Initiator at any time while allowing the Responder
  340. to continue running. In this manner, you can move to additional PCs and test
  341. them by starting the Initiator on another PC without having to stop/start the
  342. Responder.
  343. 5.3 USING THE ADAPTER'S LEDs
  344. The 2 and 3-media adapters have two LEDs visible on the back end of the board
  345. located near the 10Base-T connector.
  346. Link Integrity LED: A "steady" ON of the green LED indicates a valid 10Base-T
  347. connection. (Only applies to 10Base-T. The green LED has no significance for
  348. a 10Base-2 or AUI connection.)
  349. TX/RX LED: The yellow LED lights briefly each time the adapter transmits or
  350. receives data. (The yellow LED will appear to "flicker" on a typical network.)
  351. 5.4 RESOLVING I/O CONFLICTS
  352. An IO conflict occurs when two or more adapter use the same ISA resource (IO
  353. address, memory address or IRQ). You can usually detect an IO conflict in one
  354. of four ways after installing and or configuring the CS8900/20-based adapter:
  355. 1.) The system does not boot properly (or at all).
  356. 2.) The driver cannot communicate with the adapter, reporting an "Adapter
  357. not found" error message.
  358. 3.) You cannot connect to the network or the driver will not load.
  359. 4.) If you have configured the adapter to run in memory mode but the driver
  360. reports it is using IO mode when loading, this is an indication of a
  361. memory address conflict.
  362. If an IO conflict occurs, run the CS8900/20 Setup Utility and perform a
  363. diagnostic self-test. Normally, the ISA resource in conflict will fail the
  364. self-test. If so, reconfigure the adapter selecting another choice for the
  365. resource in conflict. Run the diagnostics again to check for further IO
  366. conflicts.
  367. In some cases, such as when the PC will not boot, it may be necessary to remove
  368. the adapter and reconfigure it by installing it in another PC to run the
  369. CS8900/20 Setup Utility. Once reinstalled in the target system, run the
  370. diagnostics self-test to ensure the new configuration is free of conflicts
  371. before loading the driver again.
  372. When manually configuring the adapter, keep in mind the typical ISA system
  373. resource usage as indicated in the tables below.
  374. I/O Address Device IRQ Device
  375. ----------- -------- --- --------
  376. 200-20F Game I/O adapter 3 COM2, Bus Mouse
  377. 230-23F Bus Mouse 4 COM1
  378. 270-27F LPT3: third parallel port 5 LPT2
  379. 2F0-2FF COM2: second serial port 6 Floppy Disk controller
  380. 320-32F Fixed disk controller 7 LPT1
  381. 8 Real-time Clock
  382. 9 EGA/VGA display adapter
  383. 12 Mouse (PS/2)
  384. Memory Address Device 13 Math Coprocessor
  385. -------------- --------------------- 14 Hard Disk controller
  386. A000-BFFF EGA Graphics Adapter
  387. A000-C7FF VGA Graphics Adapter
  388. B000-BFFF Mono Graphics Adapter
  389. B800-BFFF Color Graphics Adapter
  390. E000-FFFF AT BIOS
  391. 6.0 TECHNICAL SUPPORT
  392. ===============================================================================
  393. 6.1 CONTACTING CIRRUS LOGIC'S TECHNICAL SUPPORT
  394. Cirrus Logic's CS89XX Technical Application Support can be reached at:
  395. Telephone :(800) 888-5016 (from inside U.S. and Canada)
  396. :(512) 442-7555 (from outside the U.S. and Canada)
  397. Fax :(512) 912-3871
  398. Email :ethernet@crystal.cirrus.com
  399. WWW :http://www.cirrus.com
  400. 6.2 INFORMATION REQUIRED BEFORE CONTACTING TECHNICAL SUPPORT
  401. Before contacting Cirrus Logic for technical support, be prepared to provide as
  402. Much of the following information as possible.
  403. 1.) Adapter type (CRD8900, CDB8900, CDB8920, etc.)
  404. 2.) Adapter configuration
  405. * IO Base, Memory Base, IO or memory mode enabled, IRQ, DMA channel
  406. * Plug and Play enabled/disabled (CS8920-based adapters only)
  407. * Configured for media auto-detect or specific media type (which type).
  408. 3.) PC System's Configuration
  409. * Plug and Play system (yes/no)
  410. * BIOS (make and version)
  411. * System make and model
  412. * CPU (type and speed)
  413. * System RAM
  414. * SCSI Adapter
  415. 4.) Software
  416. * CS89XX driver and version
  417. * Your network operating system and version
  418. * Your system's OS version
  419. * Version of all protocol support files
  420. 5.) Any Error Message displayed.
  421. 6.3 OBTAINING THE LATEST DRIVER VERSION
  422. You can obtain the latest CS89XX drivers and support software from Cirrus Logic's
  423. Web site. You can also contact Cirrus Logic's Technical Support (email:
  424. ethernet@crystal.cirrus.com) and request that you be registered for automatic
  425. software-update notification.
  426. Cirrus Logic maintains a web page at http://www.cirrus.com with the
  427. latest drivers and technical publications.
  428. 6.4 Current maintainer
  429. In February 2000 the maintenance of this driver was assumed by Andrew
  430. Morton.
  431. 6.5 Kernel module parameters
  432. For use in embedded environments with no cs89x0 EEPROM, the kernel boot
  433. parameter `cs89x0_media=' has been implemented. Usage is:
  434. cs89x0_media=rj45 or
  435. cs89x0_media=aui or
  436. cs89x0_media=bnc