1
2 NOTE
3 ----
4
5 This document was contributed by Cirrus Logic for kernel 2.2.5. This version
6 has been updated for 2.3.48 by Andrew Morton <andrewm@uow.edu.au>
7
8 Cirrus make a copy of this driver available at their website, as
9 described below. In general, you should use the driver version which
10 comes with your Linux distribution.
11
12
13
14 CIRRUS LOGIC LAN CS8900/CS8920 ETHERNET ADAPTERS
15 Linux Network Interface Driver ver. 2.00 <kernel 2.3.48>
16 ===============================================================================
17
18
19 TABLE OF CONTENTS
20
21 1.0 CIRRUS LOGIC LAN CS8900/CS8920 ETHERNET ADAPTERS
22 1.1 Product Overview
23 1.2 Driver Description
24 1.2.1 Driver Name
25 1.2.2 File in the Driver Package
26 1.3 System Requirements
27 1.4 Licensing Information
28
29 2.0 ADAPTER INSTALLATION and CONFIGURATION
30 2.1 CS8900-based Adapter Configuration
31 2.2 CS8920-based Adapter Configuration
32
33 3.0 LOADING THE DRIVER AS A MODULE
34
35 4.0 COMPILING THE DRIVER
36 4.1 Compiling the Driver as a Loadable Module
37 4.2 Compiling the driver to support memory mode
38 4.3 Compiling the driver to support Rx DMA
39 4.4 Compiling the Driver into the Kernel
40
41 5.0 TESTING AND TROUBLESHOOTING
42 5.1 Known Defects and Limitations
43 5.2 Testing the Adapter
44 5.2.1 Diagnostic Self-Test
45 5.2.2 Diagnostic Network Test
46 5.3 Using the Adapter's LEDs
47 5.4 Resolving I/O Conflicts
48
49 6.0 TECHNICAL SUPPORT
50 6.1 Contacting Cirrus Logic's Technical Support
51 6.2 Information Required Before Contacting Technical Support
52 6.3 Obtaining the Latest Driver Version
53 6.4 Current maintainer
54
55
56
57 1.0 CIRRUS LOGIC LAN CS8900/CS8920 ETHERNET ADAPTERS
58 ===============================================================================
59
60
61 1.1 PRODUCT OVERVIEW
62
63 The CS8900-based ISA Ethernet Adapters from Cirrus Logic follow
64 IEEE 802.3 standards and support half or full-duplex operation in ISA bus
65 computers on 10 Mbps Ethernet networks. The adapters are designed for operation
66 in 16-bit ISA or EISA bus expansion slots and are available in
67 10BaseT-only or 3-media configurations (10BaseT, 10Base2, and AUI for 10Base-5
68 or fiber networks).
69
70 CS8920-based adapters are similar to the CS8900-based adapter with additional
71 features for Plug and Play (PnP) support and Wakeup Frame recognition. As
72 such, the configuration procedures differ somewhat between the two types of
73 adapters. Refer to the "Adapter Configuration" section for details on
74 configuring both types of adapters.
75
76
77 1.2 DRIVER DESCRIPTION
78
79 The CS8900/CS8920 Ethernet Adapter driver for Linux supports the Linux
80 v2.3.48 or greater kernel. It can be compiled directly into the kernel
81 or loaded at run-time as a device driver module.
82
83 1.2.1 Driver Name: cs89x0
84
85 1.2.2 Files in the Driver Archive:
86
87 The files in the driver at Cirrus' website include:
88
89 readme.txt - this file
90 build - batch file to compile cs89x0.c.
91 cs89x0.c - driver C code
92 cs89x0.h - driver header file
93 cs89x0.o - pre-compiled module (for v2.2.5 kernel)
94 config/Config.in - sample file to include cs89x0 driver in the kernel.
95 config/Makefile - sample file to include cs89x0 driver in the kernel.
96 config/Space.c - sample file to include cs89x0 driver in the kernel.
97
98
99
100 1.3 SYSTEM REQUIREMENTS
101
102 The following hardware is required:
103
104 * Cirrus Logic LAN (CS8900/20-based) Ethernet ISA Adapter
105
106 * IBM or IBM-compatible PC with:
107 * An 80386 or higher processor
108 * 16 bytes of contiguous IO space available between 210h - 370h
109 * One available IRQ (5,10,11,or 12 for the CS8900, 3-7,9-15 for CS8920).
110
111 * Appropriate cable (and connector for AUI, 10BASE-2) for your network
112 topology.
113
114 The following software is required:
115
116 * LINUX kernel version 2.3.48 or higher
117
118 * CS8900/20 Setup Utility (DOS-based)
119
120 * LINUX kernel sources for your kernel (if compiling into kernel)
121
122 * GNU Toolkit (gcc and make) v2.6 or above (if compiling into kernel
123 or a module)
124
125
126
127 1.4 LICENSING INFORMATION
128
129 This program is free software; you can redistribute it and/or modify it under
130 the terms of the GNU General Public License as published by the Free Software
131 Foundation, version 1.
132
133 This program is distributed in the hope that it will be useful, but WITHOUT
134 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
135 FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
136 more details.
137
138 For a full copy of the GNU General Public License, write to the Free Software
139 Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
140
141
142
143 2.0 ADAPTER INSTALLATION and CONFIGURATION
144 ===============================================================================
145
146 Both the CS8900 and CS8920-based adapters can be configured using parameters
147 stored in an on-board EEPROM. You must use the DOS-based CS8900/20 Setup
148 Utility if you want to change the adapter's configuration in EEPROM.
149
150 When loading the driver as a module, you can specify many of the adapter's
151 configuration parameters on the command-line to override the EEPROM's settings
152 or for interface configuration when an EEPROM is not used. (CS8920-based
153 adapters must use an EEPROM.) See Section 3.0 LOADING THE DRIVER AS A MODULE.
154
155 Since the CS8900/20 Setup Utility is a DOS-based application, you must install
156 and configure the adapter in a DOS-based system using the CS8900/20 Setup
157 Utility before installation in the target LINUX system. (Not required if
158 installing a CS8900-based adapter and the default configuration is acceptable.)
159
160
161 2.1 CS8900-BASED ADAPTER CONFIGURATION
162
163 CS8900-based adapters shipped from Cirrus Logic have been configured
164 with the following "default" settings:
165
166 Operation Mode: Memory Mode
167 IRQ: 10
168 Base I/O Address: 300
169 Memory Base Address: D0000
170 Optimization: DOS Client
171 Transmission Mode: Half-duplex
172 BootProm: None
173 Media Type: Autodetect (3-media cards) or
174 10BASE-T (10BASE-T only adapter)
175
176 You should only change the default configuration settings if conflicts with
177 another adapter exists. To change the adapter's configuration, run the
178 CS8900/20 Setup Utility.
179
180
181 2.2 CS8920-BASED ADAPTER CONFIGURATION
182
183 CS8920-based adapters are shipped from Cirrus Logic configured as Plug
184 and Play (PnP) enabled. However, since the cs89x0 driver does NOT
185 support PnP, you must install the CS8920 adapter in a DOS-based PC and
186 run the CS8900/20 Setup Utility to disable PnP and configure the
187 adapter before installation in the target Linux system. Failure to do
188 this will leave the adapter inactive and the driver will be unable to
189 communicate with the adapter.
190
191
192 ****************************************************************
193 * CS8920-BASED ADAPTERS: *
194 * *
195 * CS8920-BASED ADAPTERS ARE PLUG and PLAY ENABLED BY DEFAULT. *
196 * THE CS89X0 DRIVER DOES NOT SUPPORT PnP. THEREFORE, YOU MUST *
197 * RUN THE CS8900/20 SETUP UTILITY TO DISABLE PnP SUPPORT AND *
198 * TO ACTIVATE THE ADAPTER. *
199 ****************************************************************
200
201
202
203
204 3.0 LOADING THE DRIVER AS A MODULE
205 ===============================================================================
206
207 If the driver is compiled as a loadable module, you can load the driver module
208 with the 'modprobe' command. Many of the adapter's configuration parameters can
209 be specified as command-line arguments to the load command. This facility
210 provides a means to override the EEPROM's settings or for interface
211 configuration when an EEPROM is not used.
212
213 Example:
214
215 insmod cs89x0.o io=0x200 irq=0xA media=aui
216
217 This example loads the module and configures the adapter to use an IO port base
218 address of 200h, interrupt 10, and use the AUI media connection. The following
219 configuration options are available on the command line:
220
221 * io=### - specify IO address (200h-360h)
222 * irq=## - specify interrupt level
223 * use_dma=1 - Enable DMA
224 * dma=# - specify dma channel (Driver is compiled to support
225 Rx DMA only)
226 * dmasize=# (16 or 64) - DMA size 16K or 64K. Default value is set to 16.
227 * media=rj45 - specify media type
228 or media=bnc
229 or media=aui
230 or medai=auto
231 * duplex=full - specify forced half/full/autonegotiate duplex
232 or duplex=half
233 or duplex=auto
234 * debug=# - debug level (only available if the driver was compiled
235 for debugging)
236
237 NOTES:
238
239 a) If an EEPROM is present, any specified command-line parameter
240 will override the corresponding configuration value stored in
241 EEPROM.
242
243 b) The "io" parameter must be specified on the command-line.
244
245 c) In case you can not re-load the driver because Linux system
246 returns the "device or resource busy" message, try to re-load it by
247 increment the IO port address by one. The driver will write
248 commands to the IO base addresses to reset the data port pointer.
249 You can specify an I/O address with an address value one greater
250 than the configured address. Example, to scan for an adapter
251 located at IO base 0x300, specify an IO address of 0x301.
252
253 d) The "duplex=auto" parameter is only supported for the CS8920.
254
255 e) The minimum command-line configuration required if an EEPROM is
256 not present is:
257
258 io
259 irq
260 media type (no autodetect)
261
262 f) The following additional parameters are CS89XX defaults (values
263 used with no EEPROM or command-line argument).
264
265 * DMA Burst = enabled
266 * IOCHRDY Enabled = enabled
267 * UseSA = enabled
268 * CS8900 defaults to half-duplex if not specified on command-line
269 * CS8920 defaults to autoneg if not specified on command-line
270 * Use reset defaults for other config parameters
271 * dma_mode = 0
272
273 g) You can use ifconfig to set the adapter's Ethernet address.
274
275 h) Many Linux distributions use the 'modprobe' command to load
276 modules. This program uses the '/etc/conf.modules' file to
277 determine configuration information which is passed to a driver
278 module when it is loaded. All the configuration options which are
279 described above may be placed within /etc/conf.modules.
280
281 For example:
282
283 > cat /etc/conf.modules
284 ...
285 alias eth0 cs89x0
286 options cs89x0 io=0x0200 dma=5 use_dma=1
287 ...
288
289 In this example we are telling the module system that the
290 ethernet driver for this machine should use the cs89x0 driver. We
291 are asking 'modprobe' to pass the 'io', 'dma' and 'use_dma'
292 arguments to the driver when it is loaded.
293
294 i) Cirrus recommend that the cs89x0 use the ISA DMA channels 5, 6 or
295 7. You will probably find that other DMA channels will not work.
296
297 j) The cs89x0 supports DMA for receiving only. DMA mode is
298 significantly more efficient. Flooding a 400 MHz Celeron machine
299 with large ping packets consumes 82% of its CPU capacity in non-DMA
300 mode. With DMA this is reduced to 45%.
301
302 k) If your Linux kernel was compiled with inbuilt plug-and-play
303 support you will be able to find information about the cs89x0 card
304 with the command
305
306 cat /proc/isapnp
307
308 l) If during DMA operation you find erratic behavior or network data
309 corruption you should use your PC's BIOS to slow the EISA bus clock.
310
311 m) If the cs89x0 driver is compiled directly into the kernel
312 (non-modular) then its I/O address is automatically determined by
313 ISA bus probing. The IRQ number, media options, etc are determined
314 from the card's EEPROM.
315
316 n) If the cs89x0 driver is compiled directly into the kernel, DMA
317 mode may be selected by providing the kernel with a boot option
318 'cs89x0_dma=N' where 'N' is the desired DMA channel number (5, 6 or 7).
319
320 Kernel boot options may be provided on the LILO command line:
321
322 LILO boot: linux cs89x0_dma=5
323
324 or they may be placed in /etc/lilo.conf:
325
326 image=/boot/bzImage-2.3.48
327 append="cs89x0_dma=5"
328 label=linux
329 root=/dev/hda5
330 read-only
331
332 The DMA Rx buffer size is hardwired to 16 kbytes in this mode.
333 (64k mode is not available).
334
335
336 4.0 COMPILING THE DRIVER
337 ===============================================================================
338
339 The cs89x0 driver can be compiled directly into the kernel or compiled into
340 a loadable device driver module.
341
342
343 4.1 COMPILING THE DRIVER AS A LOADABLE MODULE
344
345 To compile the driver into a loadable module, use the following command
346 (single command line, without quotes):
347
348 "gcc -D__KERNEL__ -I/usr/src/linux/include -I/usr/src/linux/net/inet -Wall
349 -Wstrict-prototypes -O2 -fomit-frame-pointer -DMODULE -DCONFIG_MODVERSIONS
350 -c cs89x0.c"
351
352 4.2 COMPILING THE DRIVER TO SUPPORT MEMORY MODE
353
354 Support for memory mode was not carried over into the 2.3 series kernels.
355
356 4.3 COMPILING THE DRIVER TO SUPPORT Rx DMA
357
358 The compile-time optionality for DMA was removed in the 2.3 kernel
359 series. DMA support is now unconditionally part of the driver. It is
360 enabled by the 'use_dma=1' module option.
361
362 4.4 COMPILING THE DRIVER INTO THE KERNEL
363
364 If your Linux distribution already has support for the cs89x0 driver
365 then simply copy the source file to the /usr/src/linux/drivers/net
366 directory to replace the original ones and run the make utility to
367 rebuild the kernel. See Step 3 for rebuilding the kernel.
368
369 If your Linux does not include the cs89x0 driver, you need to edit three
370 configuration files, copy the source file to the /usr/src/linux/drivers/net
371 directory, and then run the make utility to rebuild the kernel.
372
373 1. Edit the following configuration files by adding the statements as
374 indicated. (When possible, try to locate the added text to the section of the
375 file containing similar statements).
376
377
378 a.) In /usr/src/linux/drivers/net/Config.in, add:
379
380 tristate 'CS89x0 support' CONFIG_CS89x0
381
382 Example:
383
384 if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then
385 tristate 'ICL EtherTeam 16i/32 support' CONFIG_ETH16I
386 fi
387
388 tristate 'CS89x0 support' CONFIG_CS89x0
389
390 tristate 'NE2000/NE1000 support' CONFIG_NE2000
391 if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then
392 tristate 'NI5210 support' CONFIG_NI52
393
394
395 b.) In /usr/src/linux/drivers/net/Makefile, add the following lines:
396
397 ifeq ($(CONFIG_CS89x0),y)
398 L_OBJS += cs89x0.o
399 else
400 ifeq ($(CONFIG_CS89x0),m)
401 M_OBJS += cs89x0.o
402 endif
403 endif
404
405
406 c.) In /linux/drivers/net/Space.c file, add the line:
407
408 extern int cs89x0_probe(struct device *dev);
409
410
411 Example:
412
413 extern int ultra_probe(struct device *dev);
414 extern int wd_probe(struct device *dev);
415 extern int el2_probe(struct device *dev);
416
417 extern int cs89x0_probe(struct device *dev);
418
419 extern int ne_probe(struct device *dev);
420 extern int hp_probe(struct device *dev);
421 extern int hp_plus_probe(struct device *dev);
422
423
424 Also add:
425
426 #ifdef CONFIG_CS89x0
427 { cs89x0_probe,0 },
428 #endif
429
430
431 2.) Copy the driver source files (cs89x0.c and cs89x0.h)
432 into the /usr/src/linux/drivers/net directory.
433
434
435 3.) Go to /usr/src/linux directory and run 'make config' followed by 'make dep'
436 and finally 'make' (or make bzImage) to rebuild the kernel.
437
438 4.) Use the DOS 'setup' utility to disable plug and play on the NIC.
439
440
441 5.0 TESTING AND TROUBLESHOOTING
442 ===============================================================================
443
444 5.1 KNOWN DEFECTS and LIMITATIONS
445
446 Refer to the RELEASE.TXT file distributed as part of this archive for a list of
447 known defects, driver limitations, and work arounds.
448
449
450 5.2 TESTING THE ADAPTER
451
452 Once the adapter has been installed and configured, the diagnostic option of
453 the CS8900/20 Setup Utility can be used to test the functionality of the
454 adapter and its network connection. Use the diagnostics 'Self Test' option to
455 test the functionality of the adapter with the hardware configuration you have
456 assigned. You can use the diagnostics 'Network Test' to test the ability of the
457 adapter to communicate across the Ethernet with another PC equipped with a
458 CS8900/20-based adapter card (it must also be running the CS8900/20 Setup
459 Utility).
460
461 NOTE: The Setup Utility's diagnostics are designed to run in a
462 DOS-only operating system environment. DO NOT run the diagnostics
463 from a DOS or command prompt session under Windows 95, Windows NT,
464 OS/2, or other operating system.
465
466 To run the diagnostics tests on the CS8900/20 adapter:
467
468 1.) Boot DOS on the PC and start the CS8900/20 Setup Utility.
469
470 2.) The adapter's current configuration is displayed. Hit the ENTER key to
471 get to the main menu.
472
473 4.) Select 'Diagnostics' (ALT-G) from the main menu.
474 * Select 'Self-Test' to test the adapter's basic functionality.
475 * Select 'Network Test' to test the network connection and cabling.
476
477
478 5.2.1 DIAGNOSTIC SELF-TEST
479
480 The diagnostic self-test checks the adapter's basic functionality as well as
481 its ability to communicate across the ISA bus based on the system resources
482 assigned during hardware configuration. The following tests are performed:
483
484 * IO Register Read/Write Test
485 The IO Register Read/Write test insures that the CS8900/20 can be
486 accessed in IO mode, and that the IO base address is correct.
487
488 * Shared Memory Test
489 The Shared Memory test insures the CS8900/20 can be accessed in memory
490 mode and that the range of memory addresses assigned does not conflict
491 with other devices in the system.
492
493 * Interrupt Test
494 The Interrupt test insures there are no conflicts with the assigned IRQ
495 signal.
496
497 * EEPROM Test
498 The EEPROM test insures the EEPROM can be read.
499
500 * Chip RAM Test
501 The Chip RAM test insures the 4K of memory internal to the CS8900/20 is
502 working properly.
503
504 * Internal Loop-back Test
505 The Internal Loop Back test insures the adapter's transmitter and
506 receiver are operating properly. If this test fails, make sure the
507 adapter's cable is connected to the network (check for LED activity for
508 example).
509
510 * Boot PROM Test
511 The Boot PROM test insures the Boot PROM is present, and can be read.
512 Failure indicates the Boot PROM was not successfully read due to a
513 hardware problem or due to a conflicts on the Boot PROM address
514 assignment. (Test only applies if the adapter is configured to use the
515 Boot PROM option.)
516
517 Failure of a test item indicates a possible system resource conflict with
518 another device on the ISA bus. In this case, you should use the Manual Setup
519 option to reconfigure the adapter by selecting a different value for the system
520 resource that failed.
521
522
523 5.2.2 DIAGNOSTIC NETWORK TEST
524
525 The Diagnostic Network Test verifies a working network connection by
526 transferring data between two CS8900/20 adapters installed in different PCs
527 on the same network. (Note: the diagnostic network test should not be run
528 between two nodes across a router.)
529
530 This test requires that each of the two PCs have a CS8900/20-based adapter
531 installed and have the CS8900/20 Setup Utility running. The first PC is
532 configured as a Responder and the other PC is configured as an Initiator.
533 Once the Initiator is started, it sends data frames to the Responder which
534 returns the frames to the Initiator.
535
536 The total number of frames received and transmitted are displayed on the
537 Initiator's display, along with a count of the number of frames received and
538 transmitted OK or in error. The test can be terminated anytime by the user at
539 either PC.
540
541 To setup the Diagnostic Network Test:
542
543 1.) Select a PC with a CS8900/20-based adapter and a known working network
544 connection to act as the Responder. Run the CS8900/20 Setup Utility
545 and select 'Diagnostics -> Network Test -> Responder' from the main
546 menu. Hit ENTER to start the Responder.
547
548 2.) Return to the PC with the CS8900/20-based adapter you want to test and
549 start the CS8900/20 Setup Utility.
550
551 3.) From the main menu, Select 'Diagnostic -> Network Test -> Initiator'.
552 Hit ENTER to start the test.
553
554 You may stop the test on the Initiator at any time while allowing the Responder
555 to continue running. In this manner, you can move to additional PCs and test
556 them by starting the Initiator on another PC without having to stop/start the
557 Responder.
558
559
560
561 5.3 USING THE ADAPTER'S LEDs
562
563 The 2 and 3-media adapters have two LEDs visible on the back end of the board
564 located near the 10Base-T connector.
565
566 Link Integrity LED: A "steady" ON of the green LED indicates a valid 10Base-T
567 connection. (Only applies to 10Base-T. The green LED has no significance for
568 a 10Base-2 or AUI connection.)
569
570 TX/RX LED: The yellow LED lights briefly each time the adapter transmits or
571 receives data. (The yellow LED will appear to "flicker" on a typical network.)
572
573
574 5.4 RESOLVING I/O CONFLICTS
575
576 An IO conflict occurs when two or more adapter use the same ISA resource (IO
577 address, memory address or IRQ). You can usually detect an IO conflict in one
578 of four ways after installing and or configuring the CS8900/20-based adapter:
579
580 1.) The system does not boot properly (or at all).
581
582 2.) The driver can not communicate with the adapter, reporting an "Adapter
583 not found" error message.
584
585 3.) You cannot connect to the network or the driver will not load.
586
587 4.) If you have configured the adapter to run in memory mode but the driver
588 reports it is using IO mode when loading, this is an indication of a
589 memory address conflict.
590
591 If an IO conflict occurs, run the CS8900/20 Setup Utility and perform a
592 diagnostic self-test. Normally, the ISA resource in conflict will fail the
593 self-test. If so, reconfigure the adapter selecting another choice for the
594 resource in conflict. Run the diagnostics again to check for further IO
595 conflicts.
596
597 In some cases, such as when the PC will not boot, it may be necessary to remove
598 the adapter and reconfigure it by installing it in another PC to run the
599 CS8900/20 Setup Utility. Once reinstalled in the target system, run the
600 diagnostics self-test to ensure the new configuration is free of conflicts
601 before loading the driver again.
602
603 When manually configuring the adapter, keep in mind the typical ISA system
604 resource usage as indicated in the tables below.
605
606 I/O Address Device IRQ Device
607 ----------- -------- --- --------
608 200-20F Game I/O adapter 3 COM2, Bus Mouse
609 230-23F Bus Mouse 4 COM1
610 270-27F LPT3: third parallel port 5 LPT2
611 2F0-2FF COM2: second serial port 6 Floppy Disk controller
612 320-32F Fixed disk controller 7 LPT1
613 8 Real-time Clock
614 9 EGA/VGA display adapter
615 12 Mouse (PS/2)
616 Memory Address Device 13 Math Coprocessor
617 -------------- --------------------- 14 Hard Disk controller
618 A000-BFFF EGA Graphics Adpater
619 A000-C7FF VGA Graphics Adpater
620 B000-BFFF Mono Graphics Adapter
621 B800-BFFF Color Graphics Adapter
622 E000-FFFF AT BIOS
623
624
625
626
627 6.0 TECHNICAL SUPPORT
628 ===============================================================================
629
630 6.1 CONTACTING CIRRUS LOGIC'S TECHNICAL SUPPORT
631
632 Cirrus Logic's CS89XX Technical Application Support can be reached at:
633
634 Telephone :(800) 888-5016 (from inside U.S. and Canada)
635 :(512) 442-7555 (from outside the U.S. and Canada)
636 Fax :(512) 912-3871
637 Email :ethernet@crystal.cirrus.com
638 WWW :http://www.cirrus.com
639
640
641 6.2 INFORMATION REQUIRED BEFORE CONTACTING TECHNICAL SUPPORT
642
643 Before contacting Cirrus Logic for technical support, be prepared to provide as
644 Much of the following information as possible.
645
646 1.) Adapter type (CRD8900, CDB8900, CDB8920, etc.)
647
648 2.) Adapter configuration
649
650 * IO Base, Memory Base, IO or memory mode enabled, IRQ, DMA channel
651 * Plug and Play enabled/disabled (CS8920-based adapters only)
652 * Configured for media auto-detect or specific media type (which type).
653
654 3.) PC System's Configuration
655
656 * Plug and Play system (yes/no)
657 * BIOS (make and version)
658 * System make and model
659 * CPU (type and speed)
660 * System RAM
661 * SCSI Adapter
662
663 4.) Software
664
665 * CS89XX driver and version
666 * Your network operating system and version
667 * Your system's OS version
668 * Version of all protocol support files
669
670 5.) Any Error Message displayed.
671
672
673
674 6.3 OBTAINING THE LATEST DRIVER VERSION
675
676 You can obtain the latest CS89XX drivers and support software from Cirrus Logic's
677 Web site. You can also contact Cirrus Logic's Technical Support (email:
678 ethernet@crystal.cirrus.com) and request that you be registered for automatic
679 software-update notification.
680
681 Cirrus Logic maintains a web page at http://www.cirrus.com with the
682 the latest drivers and technical publications.
683
684
685 6.4 Current maintainer
686
687 In February 2000 the maintenance of this driver was assumed by Andrew
688 Morton <andrewm@uow.edu.au>
This page was automatically generated by the
LXR engine.
Visit the LXR main site for more
information.