0001 .. SPDX-License-Identifier: GPL-2.0
0002
0003 ================================================
0004 Cirrus Logic LAN CS8900/CS8920 Ethernet Adapters
0005 ================================================
0006
0007 .. note::
0008
0009 This document was contributed by Cirrus Logic for kernel 2.2.5. This version
0010 has been updated for 2.3.48 by Andrew Morton.
0011
0012 Still, this is too outdated! A major cleanup is needed here.
0013
0014 Cirrus make a copy of this driver available at their website, as
0015 described below. In general, you should use the driver version which
0016 comes with your Linux distribution.
0017
0018
0019 Linux Network Interface Driver ver. 2.00 <kernel 2.3.48>
0020
0021
0022 .. TABLE OF CONTENTS
0023
0024 1.0 CIRRUS LOGIC LAN CS8900/CS8920 ETHERNET ADAPTERS
0025 1.1 Product Overview
0026 1.2 Driver Description
0027 1.2.1 Driver Name
0028 1.2.2 File in the Driver Package
0029 1.3 System Requirements
0030 1.4 Licensing Information
0031
0032 2.0 ADAPTER INSTALLATION and CONFIGURATION
0033 2.1 CS8900-based Adapter Configuration
0034 2.2 CS8920-based Adapter Configuration
0035
0036 3.0 LOADING THE DRIVER AS A MODULE
0037
0038 4.0 COMPILING THE DRIVER
0039 4.1 Compiling the Driver as a Loadable Module
0040 4.2 Compiling the driver to support memory mode
0041 4.3 Compiling the driver to support Rx DMA
0042
0043 5.0 TESTING AND TROUBLESHOOTING
0044 5.1 Known Defects and Limitations
0045 5.2 Testing the Adapter
0046 5.2.1 Diagnostic Self-Test
0047 5.2.2 Diagnostic Network Test
0048 5.3 Using the Adapter's LEDs
0049 5.4 Resolving I/O Conflicts
0050
0051 6.0 TECHNICAL SUPPORT
0052 6.1 Contacting Cirrus Logic's Technical Support
0053 6.2 Information Required Before Contacting Technical Support
0054 6.3 Obtaining the Latest Driver Version
0055 6.4 Current maintainer
0056 6.5 Kernel boot parameters
0057
0058
0059 1. Cirrus Logic LAN CS8900/CS8920 Ethernet Adapters
0060 ===================================================
0061
0062
0063 1.1. Product Overview
0064 =====================
0065
0066 The CS8900-based ISA Ethernet Adapters from Cirrus Logic follow
0067 IEEE 802.3 standards and support half or full-duplex operation in ISA bus
0068 computers on 10 Mbps Ethernet networks. The adapters are designed for operation
0069 in 16-bit ISA or EISA bus expansion slots and are available in
0070 10BaseT-only or 3-media configurations (10BaseT, 10Base2, and AUI for 10Base-5
0071 or fiber networks).
0072
0073 CS8920-based adapters are similar to the CS8900-based adapter with additional
0074 features for Plug and Play (PnP) support and Wakeup Frame recognition. As
0075 such, the configuration procedures differ somewhat between the two types of
0076 adapters. Refer to the "Adapter Configuration" section for details on
0077 configuring both types of adapters.
0078
0079
0080 1.2. Driver Description
0081 =======================
0082
0083 The CS8900/CS8920 Ethernet Adapter driver for Linux supports the Linux
0084 v2.3.48 or greater kernel. It can be compiled directly into the kernel
0085 or loaded at run-time as a device driver module.
0086
0087 1.2.1 Driver Name: cs89x0
0088
0089 1.2.2 Files in the Driver Archive:
0090
0091 The files in the driver at Cirrus' website include:
0092
0093 =================== ====================================================
0094 readme.txt this file
0095 build batch file to compile cs89x0.c.
0096 cs89x0.c driver C code
0097 cs89x0.h driver header file
0098 cs89x0.o pre-compiled module (for v2.2.5 kernel)
0099 config/Config.in sample file to include cs89x0 driver in the kernel.
0100 config/Makefile sample file to include cs89x0 driver in the kernel.
0101 config/Space.c sample file to include cs89x0 driver in the kernel.
0102 =================== ====================================================
0103
0104
0105
0106 1.3. System Requirements
0107 ------------------------
0108
0109 The following hardware is required:
0110
0111 * Cirrus Logic LAN (CS8900/20-based) Ethernet ISA Adapter
0112
0113 * IBM or IBM-compatible PC with:
0114 * An 80386 or higher processor
0115 * 16 bytes of contiguous IO space available between 210h - 370h
0116 * One available IRQ (5,10,11,or 12 for the CS8900, 3-7,9-15 for CS8920).
0117
0118 * Appropriate cable (and connector for AUI, 10BASE-2) for your network
0119 topology.
0120
0121 The following software is required:
0122
0123 * LINUX kernel version 2.3.48 or higher
0124
0125 * CS8900/20 Setup Utility (DOS-based)
0126
0127 * LINUX kernel sources for your kernel (if compiling into kernel)
0128
0129 * GNU Toolkit (gcc and make) v2.6 or above (if compiling into kernel
0130 or a module)
0131
0132
0133
0134 1.4. Licensing Information
0135 --------------------------
0136
0137 This program is free software; you can redistribute it and/or modify it under
0138 the terms of the GNU General Public License as published by the Free Software
0139 Foundation, version 1.
0140
0141 This program is distributed in the hope that it will be useful, but WITHOUT
0142 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
0143 FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
0144 more details.
0145
0146 For a full copy of the GNU General Public License, write to the Free Software
0147 Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
0148
0149
0150
0151 2. Adapter Installation and Configuration
0152 =========================================
0153
0154 Both the CS8900 and CS8920-based adapters can be configured using parameters
0155 stored in an on-board EEPROM. You must use the DOS-based CS8900/20 Setup
0156 Utility if you want to change the adapter's configuration in EEPROM.
0157
0158 When loading the driver as a module, you can specify many of the adapter's
0159 configuration parameters on the command-line to override the EEPROM's settings
0160 or for interface configuration when an EEPROM is not used. (CS8920-based
0161 adapters must use an EEPROM.) See Section 3.0 LOADING THE DRIVER AS A MODULE.
0162
0163 Since the CS8900/20 Setup Utility is a DOS-based application, you must install
0164 and configure the adapter in a DOS-based system using the CS8900/20 Setup
0165 Utility before installation in the target LINUX system. (Not required if
0166 installing a CS8900-based adapter and the default configuration is acceptable.)
0167
0168
0169 2.1. CS8900-based Adapter Configuration
0170 ---------------------------------------
0171
0172 CS8900-based adapters shipped from Cirrus Logic have been configured
0173 with the following "default" settings::
0174
0175 Operation Mode: Memory Mode
0176 IRQ: 10
0177 Base I/O Address: 300
0178 Memory Base Address: D0000
0179 Optimization: DOS Client
0180 Transmission Mode: Half-duplex
0181 BootProm: None
0182 Media Type: Autodetect (3-media cards) or
0183 10BASE-T (10BASE-T only adapter)
0184
0185 You should only change the default configuration settings if conflicts with
0186 another adapter exists. To change the adapter's configuration, run the
0187 CS8900/20 Setup Utility.
0188
0189
0190 2.2. CS8920-based Adapter Configuration
0191 ---------------------------------------
0192
0193 CS8920-based adapters are shipped from Cirrus Logic configured as Plug
0194 and Play (PnP) enabled. However, since the cs89x0 driver does NOT
0195 support PnP, you must install the CS8920 adapter in a DOS-based PC and
0196 run the CS8900/20 Setup Utility to disable PnP and configure the
0197 adapter before installation in the target Linux system. Failure to do
0198 this will leave the adapter inactive and the driver will be unable to
0199 communicate with the adapter.
0200
0201 ::
0202
0203 ****************************************************************
0204 * CS8920-BASED ADAPTERS: *
0205 * *
0206 * CS8920-BASED ADAPTERS ARE PLUG and PLAY ENABLED BY DEFAULT. *
0207 * THE CS89X0 DRIVER DOES NOT SUPPORT PnP. THEREFORE, YOU MUST *
0208 * RUN THE CS8900/20 SETUP UTILITY TO DISABLE PnP SUPPORT AND *
0209 * TO ACTIVATE THE ADAPTER. *
0210 ****************************************************************
0211
0212
0213
0214
0215 3. Loading the Driver as a Module
0216 =================================
0217
0218 If the driver is compiled as a loadable module, you can load the driver module
0219 with the 'modprobe' command. Many of the adapter's configuration parameters can
0220 be specified as command-line arguments to the load command. This facility
0221 provides a means to override the EEPROM's settings or for interface
0222 configuration when an EEPROM is not used.
0223
0224 Example::
0225
0226 insmod cs89x0.o io=0x200 irq=0xA media=aui
0227
0228 This example loads the module and configures the adapter to use an IO port base
0229 address of 200h, interrupt 10, and use the AUI media connection. The following
0230 configuration options are available on the command line::
0231
0232 io=### - specify IO address (200h-360h)
0233 irq=## - specify interrupt level
0234 use_dma=1 - Enable DMA
0235 dma=# - specify dma channel (Driver is compiled to support
0236 Rx DMA only)
0237 dmasize=# (16 or 64) - DMA size 16K or 64K. Default value is set to 16.
0238 media=rj45 - specify media type
0239 or media=bnc
0240 or media=aui
0241 or media=auto
0242 duplex=full - specify forced half/full/autonegotiate duplex
0243 or duplex=half
0244 or duplex=auto
0245 debug=# - debug level (only available if the driver was compiled
0246 for debugging)
0247
0248 **Notes:**
0249
0250 a) If an EEPROM is present, any specified command-line parameter
0251 will override the corresponding configuration value stored in
0252 EEPROM.
0253
0254 b) The "io" parameter must be specified on the command-line.
0255
0256 c) The driver's hardware probe routine is designed to avoid
0257 writing to I/O space until it knows that there is a cs89x0
0258 card at the written addresses. This could cause problems
0259 with device probing. To avoid this behaviour, add one
0260 to the ``io=`` module parameter. This doesn't actually change
0261 the I/O address, but it is a flag to tell the driver
0262 to partially initialise the hardware before trying to
0263 identify the card. This could be dangerous if you are
0264 not sure that there is a cs89x0 card at the provided address.
0265
0266 For example, to scan for an adapter located at IO base 0x300,
0267 specify an IO address of 0x301.
0268
0269 d) The "duplex=auto" parameter is only supported for the CS8920.
0270
0271 e) The minimum command-line configuration required if an EEPROM is
0272 not present is:
0273
0274 io
0275 irq
0276 media type (no autodetect)
0277
0278 f) The following additional parameters are CS89XX defaults (values
0279 used with no EEPROM or command-line argument).
0280
0281 * DMA Burst = enabled
0282 * IOCHRDY Enabled = enabled
0283 * UseSA = enabled
0284 * CS8900 defaults to half-duplex if not specified on command-line
0285 * CS8920 defaults to autoneg if not specified on command-line
0286 * Use reset defaults for other config parameters
0287 * dma_mode = 0
0288
0289 g) You can use ifconfig to set the adapter's Ethernet address.
0290
0291 h) Many Linux distributions use the 'modprobe' command to load
0292 modules. This program uses the '/etc/conf.modules' file to
0293 determine configuration information which is passed to a driver
0294 module when it is loaded. All the configuration options which are
0295 described above may be placed within /etc/conf.modules.
0296
0297 For example::
0298
0299 > cat /etc/conf.modules
0300 ...
0301 alias eth0 cs89x0
0302 options cs89x0 io=0x0200 dma=5 use_dma=1
0303 ...
0304
0305 In this example we are telling the module system that the
0306 ethernet driver for this machine should use the cs89x0 driver. We
0307 are asking 'modprobe' to pass the 'io', 'dma' and 'use_dma'
0308 arguments to the driver when it is loaded.
0309
0310 i) Cirrus recommend that the cs89x0 use the ISA DMA channels 5, 6 or
0311 7. You will probably find that other DMA channels will not work.
0312
0313 j) The cs89x0 supports DMA for receiving only. DMA mode is
0314 significantly more efficient. Flooding a 400 MHz Celeron machine
0315 with large ping packets consumes 82% of its CPU capacity in non-DMA
0316 mode. With DMA this is reduced to 45%.
0317
0318 k) If your Linux kernel was compiled with inbuilt plug-and-play
0319 support you will be able to find information about the cs89x0 card
0320 with the command::
0321
0322 cat /proc/isapnp
0323
0324 l) If during DMA operation you find erratic behavior or network data
0325 corruption you should use your PC's BIOS to slow the EISA bus clock.
0326
0327 m) If the cs89x0 driver is compiled directly into the kernel
0328 (non-modular) then its I/O address is automatically determined by
0329 ISA bus probing. The IRQ number, media options, etc are determined
0330 from the card's EEPROM.
0331
0332 n) If the cs89x0 driver is compiled directly into the kernel, DMA
0333 mode may be selected by providing the kernel with a boot option
0334 'cs89x0_dma=N' where 'N' is the desired DMA channel number (5, 6 or 7).
0335
0336 Kernel boot options may be provided on the LILO command line::
0337
0338 LILO boot: linux cs89x0_dma=5
0339
0340 or they may be placed in /etc/lilo.conf::
0341
0342 image=/boot/bzImage-2.3.48
0343 append="cs89x0_dma=5"
0344 label=linux
0345 root=/dev/hda5
0346 read-only
0347
0348 The DMA Rx buffer size is hardwired to 16 kbytes in this mode.
0349 (64k mode is not available).
0350
0351
0352 4. Compiling the Driver
0353 =======================
0354
0355 The cs89x0 driver can be compiled directly into the kernel or compiled into
0356 a loadable device driver module.
0357
0358 Just use the standard way to configure the driver and compile the Kernel.
0359
0360
0361 4.1. Compiling the Driver to Support Rx DMA
0362 -------------------------------------------
0363
0364 The compile-time optionality for DMA was removed in the 2.3 kernel
0365 series. DMA support is now unconditionally part of the driver. It is
0366 enabled by the 'use_dma=1' module option.
0367
0368
0369 5. Testing and Troubleshooting
0370 ==============================
0371
0372 5.1. Known Defects and Limitations
0373 ----------------------------------
0374
0375 Refer to the RELEASE.TXT file distributed as part of this archive for a list of
0376 known defects, driver limitations, and work arounds.
0377
0378
0379 5.2. Testing the Adapter
0380 ------------------------
0381
0382 Once the adapter has been installed and configured, the diagnostic option of
0383 the CS8900/20 Setup Utility can be used to test the functionality of the
0384 adapter and its network connection. Use the diagnostics 'Self Test' option to
0385 test the functionality of the adapter with the hardware configuration you have
0386 assigned. You can use the diagnostics 'Network Test' to test the ability of the
0387 adapter to communicate across the Ethernet with another PC equipped with a
0388 CS8900/20-based adapter card (it must also be running the CS8900/20 Setup
0389 Utility).
0390
0391 .. note::
0392
0393 The Setup Utility's diagnostics are designed to run in a
0394 DOS-only operating system environment. DO NOT run the diagnostics
0395 from a DOS or command prompt session under Windows 95, Windows NT,
0396 OS/2, or other operating system.
0397
0398 To run the diagnostics tests on the CS8900/20 adapter:
0399
0400 1. Boot DOS on the PC and start the CS8900/20 Setup Utility.
0401
0402 2. The adapter's current configuration is displayed. Hit the ENTER key to
0403 get to the main menu.
0404
0405 4. Select 'Diagnostics' (ALT-G) from the main menu.
0406 * Select 'Self-Test' to test the adapter's basic functionality.
0407 * Select 'Network Test' to test the network connection and cabling.
0408
0409
0410 5.2.1. Diagnostic Self-test
0411 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
0412
0413 The diagnostic self-test checks the adapter's basic functionality as well as
0414 its ability to communicate across the ISA bus based on the system resources
0415 assigned during hardware configuration. The following tests are performed:
0416
0417 * IO Register Read/Write Test
0418
0419 The IO Register Read/Write test insures that the CS8900/20 can be
0420 accessed in IO mode, and that the IO base address is correct.
0421
0422 * Shared Memory Test
0423
0424 The Shared Memory test insures the CS8900/20 can be accessed in memory
0425 mode and that the range of memory addresses assigned does not conflict
0426 with other devices in the system.
0427
0428 * Interrupt Test
0429
0430 The Interrupt test insures there are no conflicts with the assigned IRQ
0431 signal.
0432
0433 * EEPROM Test
0434
0435 The EEPROM test insures the EEPROM can be read.
0436
0437 * Chip RAM Test
0438
0439 The Chip RAM test insures the 4K of memory internal to the CS8900/20 is
0440 working properly.
0441
0442 * Internal Loop-back Test
0443
0444 The Internal Loop Back test insures the adapter's transmitter and
0445 receiver are operating properly. If this test fails, make sure the
0446 adapter's cable is connected to the network (check for LED activity for
0447 example).
0448
0449 * Boot PROM Test
0450
0451 The Boot PROM test insures the Boot PROM is present, and can be read.
0452 Failure indicates the Boot PROM was not successfully read due to a
0453 hardware problem or due to a conflicts on the Boot PROM address
0454 assignment. (Test only applies if the adapter is configured to use the
0455 Boot PROM option.)
0456
0457 Failure of a test item indicates a possible system resource conflict with
0458 another device on the ISA bus. In this case, you should use the Manual Setup
0459 option to reconfigure the adapter by selecting a different value for the system
0460 resource that failed.
0461
0462
0463 5.2.2. Diagnostic Network Test
0464 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
0465
0466 The Diagnostic Network Test verifies a working network connection by
0467 transferring data between two CS8900/20 adapters installed in different PCs
0468 on the same network. (Note: the diagnostic network test should not be run
0469 between two nodes across a router.)
0470
0471 This test requires that each of the two PCs have a CS8900/20-based adapter
0472 installed and have the CS8900/20 Setup Utility running. The first PC is
0473 configured as a Responder and the other PC is configured as an Initiator.
0474 Once the Initiator is started, it sends data frames to the Responder which
0475 returns the frames to the Initiator.
0476
0477 The total number of frames received and transmitted are displayed on the
0478 Initiator's display, along with a count of the number of frames received and
0479 transmitted OK or in error. The test can be terminated anytime by the user at
0480 either PC.
0481
0482 To setup the Diagnostic Network Test:
0483
0484 1. Select a PC with a CS8900/20-based adapter and a known working network
0485 connection to act as the Responder. Run the CS8900/20 Setup Utility
0486 and select 'Diagnostics -> Network Test -> Responder' from the main
0487 menu. Hit ENTER to start the Responder.
0488
0489 2. Return to the PC with the CS8900/20-based adapter you want to test and
0490 start the CS8900/20 Setup Utility.
0491
0492 3. From the main menu, Select 'Diagnostic -> Network Test -> Initiator'.
0493 Hit ENTER to start the test.
0494
0495 You may stop the test on the Initiator at any time while allowing the Responder
0496 to continue running. In this manner, you can move to additional PCs and test
0497 them by starting the Initiator on another PC without having to stop/start the
0498 Responder.
0499
0500
0501
0502 5.3. Using the Adapter's LEDs
0503 -----------------------------
0504
0505 The 2 and 3-media adapters have two LEDs visible on the back end of the board
0506 located near the 10Base-T connector.
0507
0508 Link Integrity LED: A "steady" ON of the green LED indicates a valid 10Base-T
0509 connection. (Only applies to 10Base-T. The green LED has no significance for
0510 a 10Base-2 or AUI connection.)
0511
0512 TX/RX LED: The yellow LED lights briefly each time the adapter transmits or
0513 receives data. (The yellow LED will appear to "flicker" on a typical network.)
0514
0515
0516 5.4. Resolving I/O Conflicts
0517 ----------------------------
0518
0519 An IO conflict occurs when two or more adapter use the same ISA resource (IO
0520 address, memory address or IRQ). You can usually detect an IO conflict in one
0521 of four ways after installing and or configuring the CS8900/20-based adapter:
0522
0523 1. The system does not boot properly (or at all).
0524
0525 2. The driver cannot communicate with the adapter, reporting an "Adapter
0526 not found" error message.
0527
0528 3. You cannot connect to the network or the driver will not load.
0529
0530 4. If you have configured the adapter to run in memory mode but the driver
0531 reports it is using IO mode when loading, this is an indication of a
0532 memory address conflict.
0533
0534 If an IO conflict occurs, run the CS8900/20 Setup Utility and perform a
0535 diagnostic self-test. Normally, the ISA resource in conflict will fail the
0536 self-test. If so, reconfigure the adapter selecting another choice for the
0537 resource in conflict. Run the diagnostics again to check for further IO
0538 conflicts.
0539
0540 In some cases, such as when the PC will not boot, it may be necessary to remove
0541 the adapter and reconfigure it by installing it in another PC to run the
0542 CS8900/20 Setup Utility. Once reinstalled in the target system, run the
0543 diagnostics self-test to ensure the new configuration is free of conflicts
0544 before loading the driver again.
0545
0546 When manually configuring the adapter, keep in mind the typical ISA system
0547 resource usage as indicated in the tables below.
0548
0549 ::
0550
0551 I/O Address Device IRQ Device
0552 ----------- -------- --- --------
0553 200-20F Game I/O adapter 3 COM2, Bus Mouse
0554 230-23F Bus Mouse 4 COM1
0555 270-27F LPT3: third parallel port 5 LPT2
0556 2F0-2FF COM2: second serial port 6 Floppy Disk controller
0557 320-32F Fixed disk controller 7 LPT1
0558 8 Real-time Clock
0559 9 EGA/VGA display adapter
0560 12 Mouse (PS/2)
0561 Memory Address Device 13 Math Coprocessor
0562 -------------- --------------------- 14 Hard Disk controller
0563 A000-BFFF EGA Graphics Adapter
0564 A000-C7FF VGA Graphics Adapter
0565 B000-BFFF Mono Graphics Adapter
0566 B800-BFFF Color Graphics Adapter
0567 E000-FFFF AT BIOS
0568
0569
0570
0571
0572 6. Technical Support
0573 ====================
0574
0575 6.1. Contacting Cirrus Logic's Technical Support
0576 ------------------------------------------------
0577
0578 Cirrus Logic's CS89XX Technical Application Support can be reached at::
0579
0580 Telephone :(800) 888-5016 (from inside U.S. and Canada)
0581 :(512) 442-7555 (from outside the U.S. and Canada)
0582 Fax :(512) 912-3871
0583 Email :ethernet@crystal.cirrus.com
0584 WWW :http://www.cirrus.com
0585
0586
0587 6.2. Information Required before Contacting Technical Support
0588 -------------------------------------------------------------
0589
0590 Before contacting Cirrus Logic for technical support, be prepared to provide as
0591 Much of the following information as possible.
0592
0593 1.) Adapter type (CRD8900, CDB8900, CDB8920, etc.)
0594
0595 2.) Adapter configuration
0596
0597 * IO Base, Memory Base, IO or memory mode enabled, IRQ, DMA channel
0598 * Plug and Play enabled/disabled (CS8920-based adapters only)
0599 * Configured for media auto-detect or specific media type (which type).
0600
0601 3.) PC System's Configuration
0602
0603 * Plug and Play system (yes/no)
0604 * BIOS (make and version)
0605 * System make and model
0606 * CPU (type and speed)
0607 * System RAM
0608 * SCSI Adapter
0609
0610 4.) Software
0611
0612 * CS89XX driver and version
0613 * Your network operating system and version
0614 * Your system's OS version
0615 * Version of all protocol support files
0616
0617 5.) Any Error Message displayed.
0618
0619
0620
0621 6.3 Obtaining the Latest Driver Version
0622 ---------------------------------------
0623
0624 You can obtain the latest CS89XX drivers and support software from Cirrus Logic's
0625 Web site. You can also contact Cirrus Logic's Technical Support (email:
0626 ethernet@crystal.cirrus.com) and request that you be registered for automatic
0627 software-update notification.
0628
0629 Cirrus Logic maintains a web page at http://www.cirrus.com with the
0630 latest drivers and technical publications.
0631
0632
0633 6.4. Current maintainer
0634 -----------------------
0635
0636 In February 2000 the maintenance of this driver was assumed by Andrew
0637 Morton.
0638
0639 6.5 Kernel module parameters
0640 ----------------------------
0641
0642 For use in embedded environments with no cs89x0 EEPROM, the kernel boot
0643 parameter ``cs89x0_media=`` has been implemented. Usage is::
0644
0645 cs89x0_media=rj45 or
0646 cs89x0_media=aui or
0647 cs89x0_media=bnc
