TR(4) BSD Programmer's Manual TR(4)NAMEtr - IBM TRA 16/4, 3COM 3C619B/C, 3C319 TokenLink III 16/4, and other
TROPIC based (or compatible) token ring adapters
SYNOPSIS
tr0 at isa? port 0xa20 iomem 0xd0000
tr0 at isa? port 0x280 iomem 0xd0000 iosiz 0x8000 flags 0x0001
DESCRIPTION
The tr interface provides access to a 4 Mb/s or 16 Mb/s token ring (IEEE
802.5) network.
Note that this device uses two distinct regions of shared memory. The
region displayed at boot time is called the shared RAM area; the other
region is referred to as the BOOT ROM, BIOS, or MMIO area in the manufac-
turer's documentation. The address of the BOOT ROM region is not config-
urable by the driver, it is either set via DIP switches or a vendor sup-
plied configuration program. The default location for the BOOT ROM area
for IBM and 3COM adapters is 0xCC000. Care must be taken to avoid con-
flicts with other devices that use this location (such as the BIOS on
some Adaptec SCSI host adapters).
Configurable parameters are:
o I/O base address, the value configured into the card must match
the port value in the kernel configuration file.
o Memory mapped I/O area address (size is always 8K bytes), also
sometimes referred to as the BOOT ROM area. This address is de-
termined by the adapter configuration.
o Shared memory area address and size. The size of the shared
memory area is part of the adapter configuration, the address
is always set by the kernel based on the iomem keyword. 32K is
recommended (16K is minimum, 64K is maximum). This area may not
overlap the memory mapped I/O area and must align on a boundary
commensurate with its size (ie: 32K boundary for 32K size).
o The IRQ number, determined from the adapter configuration.
o Media select (STP/UTP), determined by adapter configuration.
o Early token release disable option, determined by adapter con-
figuration (not available on some cards).
o Ring speed (4/16), determined by adapter configuration.
Paged shared memory (available on some adapters) is not supported by this
driver. Adapters that do not support the fast path transmit function are
not supported.
The IBM TRA 16/4 is configured by dip switches. The 3COM 3C619B and
3C619C are configured by running a DOS utility. Note that on the 3COM
cards currently you can use any of the enhanced 3COM mode interrupts or
port addresses (if you have an EISA machine you may have to disable EISA
configuration mode).
The driver also supports 3COM-style address selection. This mode is in-
voked by flags=1. The differences are:
o Much more flexability in I/O addresses: 0x200 - 0x3e0. (The
cards use a block of 16 I/O addresses)
o Higher flexability of IRQ's. Supported irq's are: 2(9), 3, 5,
6, 7, 10, 11, 15; a free IRQ will automatically be selected
during autoconfiguration if none is specified.
o I/O port, shared memory address and size are defined by the
driver, no DOS setup utility required.
o Ability to have more than two cards installed in the system.
The initialization routine will assign sequential unit numbers to 3COM
cards according to their station addresses. The 3COM configuration mode
uses a probe port (normally 0x100), this port can be changed (in steps of
0x10 addresses) by setting bit 4-7 of the flags field, i.e. a flag set-
ting of 0xex would result in a probe port of 0x1e0 being used. (This is
very similar to the way 3COM 3C509's are configured).
The adapter attempts to insert itself into the token ring when it is
ifconfig 'ed up. Ring insertion typically takes around 3 seconds. If in-
sertion fails or if a problem occurs while inserted the adapter may re-
move itself from the ring and initiate error recovery. A time delay
(which increases with each failure) is imposed before each retry. If the
network administrator sends a message to the adapter requesting it remove
itself it will not retry insertion.
MEDIA SELECTION
Media selection is performed by manually configuring the card. The if-
config(8) command is used to configure IP source route bridging and all
rings broadcast.
DIAGNOSTICS
Many diagnostics may be generated to give status or report on hardware or
configuration errors, more common ones are listed below:
tr%d: tr_reset: unsupported card revision
The adapter does not support the fast transmit feature, initialization
fails and the interface remains down.
tr%d: inserted in ring
The adapter has successfully inserted itself into the token ring.
tr%d: insertion retry in %d seconds
This messages indicates ring reinsertion will be retried after the speci-
fied time period, this is issued during error recovery. The adapter
failed to insert itself into the ring or was removed and a retry has been
scheduled.
A number of diagnostics regarding ring status may be generated if prob-
lems are detected with ring wiring or protocol. These errors fall into
the following categories:
o No signal detected or wiring fault: these usually mean there is
a break in the wiring or nothing is plugged into the port on
the card.
o No other sites detected: this generally happens when the lobe
cable isn't plugged into the MAU.
o Beacon frames being transmitted or received: this usually hap-
pens when there is a mismatch in ring speed or a wiring prob-
lem. After a few seconds in this mode the adapter will remove
itself from the ring.
SEE ALSOintro(4), inet(4), arp(4), ifconfig(8)BUGS
Token ring packet input and output errors are ignored, the error counters
on the interface are not updated.
There is no notion of a promiscuous mode provided by the hardware, this
makes tcpdump less useful than would be desired.
3COM configuration mode is experimental at this time.
HISTORY
The tr driver first appeared in BSD/OS 2.1.
BSDI BSD/OS May 7, 1996 2
