vitr(7) DG/UX R4.11MU05 vitr(7)
NAME
vitr - Vilya VME Token Ring network controller (88K only)
SYNOPSIS
vitr(parent-bus[,controller-num[,alt-token-ring-addr[,product-id]]])
DESCRIPTION
The vitr device driver allows an AViiON system that includes a Vilya
VME Token Ring (VTRC) network controller to access a Token Ring
network. To configure such devices, you must add to the DG/UX system
configuration file one or more device name entries of the form
described in the synopsis above. The parameters in a device name
have the following meanings:
· The parent-bus parameter is itself a device name, representing
the VME bus device to which the controller is attached (vme(0) or
vme(1), for example). There is no default value for this
parameter; it must always be specified explicitly.
· The controller-num parameter is a hexadecimal number in the range
0 through 7 which distinguishes the various standard addressing
values to which the controller may be jumpered. Consult the
table below for details on these address settings. The default
value for controller-num is 0.
· The alt-token-ring-addr parameter can be used to override the
controller's default Token Ring address with a user-specified
value, which must be represented as a string of exactly 12
hexadecimal digits. If no alt-token-ring-addr parameter is
specified, the controller-resident default Token Ring address is
used.
· The product-id parameter can be used to specify a non-default
Product ID. Information on the product ID may be found in the
IBM Token-Ring Network Architecture Reference. The default value
for product-id is 0.
A special value (i.e. "F" or "f") in the product ID field of the vitr
device name in the system file can be used to disable Outbound Source
Routing. Systems which use the valid product IDs will not be able
able to disable Outbound Source Routing. The default is to leave
Outbound Source Routing "ENABLED". Valid product ids will result in
Outbound Source Routing "ENABLED". Informational message will be
written to console and STREAMS error log when Outbound Source Routing
is "DISABLED".
Each vitr controller board contains two jumperable VME board address
settings: the interrupt vector number used by the board and the A32
address of the board's 32-bit control register space. The following
hexadecimal address values are used for the 8 standard controller-num
instances supported by the device driver on each parent VME bus:
Controller Interrupt A32 Address
Number Vector
Number
0 40 E4000000 or 61000000
1 41 E4002000 or 61002000
2 42 E4004000
3 43 E4006000
4 44 E4008000
5 45 E400A000
6 46 E400C000
7 47 E400E000
A vitr device can still be used even if it is not jumpered to one of
the standard address settings. However, such a device is referred to
as a non-standard instance, and it requires a different device name
format:
vitr@intr-vec-num(parent-bus,a32-addr[,alt-token-ring-addr[,product-id]])
The parameters in a non-standard device name have the following
meanings:
· The intr-vec-num value is the hexadecimal VME interrupt vector
number used by the board. There is no default value for this
parameter; it must always be specified explicitly.
· The parent-bus parameter has exactly the same meaning here as it
does in the standard device name format.
· The a32-addr parameter is the hexadecimal value of the VME A32
address of the board's 32-bit control register space. There is
no default value for this parameter; it must always be specified
explicitly.
· The alt-token-ring-addr parameter has exactly the same meaning
here as it does in the standard device name format.
· The product-id parameter has exactly the same meaning here as it
does in the standard device name format.
FILES
Each standard vitr device creates single character-special device
node when it is configured, with the pathname:
/dev/net/vitr(parent-bus,controller-num)
The pathname of the device node created for non-standard device
instances is:
/dev/net/vitr@intr-vec-num(parent-bus,a32-addr)
The chk.devlink command is responsible for creating and maintaining
an additional link to each vitr device node, with a pathname of the
form /dev/net/vitr[0-9]*. See the chk.devlink(1M) and devlinktab(4M)
man pages for details.
The vitr device driver is a clonable Streams driver. This means that
you can open a single vitr device node to access any unused minor
device. Each subsequent access of the node via the open(2) system
call allocates a separate Stream (minor number) to the device driver.
DIAGNOSTICS
Use the -i option with netstat(1C).
EXAMPLES
The following entries in a DG/UX configuration file configure VTRC
controllers that use two of the standard sets of addressing values,
and which use their on-board default Token Ring addresses:
vitr(vme(1),0)
vitr(vme(0),4)
The following statement configures a VTRC controller using the
address settings for controller number 0, but specifies an alternate
Token Ring address:
vitr(vme(0),0,08001b123456)
The following statement configures a non-standard VTRC controller
which uses interrupt vector 0x42 and VME A32 address 0xE4004000, but
which accepts the default Token Ring address and Product ID:
vitr@42(vme(0),e4004000)
For details about setting the I/O and VME addresses on the board, see
Configuring the VME Token Ring Controller(VTRC) for AViiON Series
Systems.
For more information about DG/UX device configuration, refer to
"Writing a Device Driver" in Programming in the DG/UX Kernel
Environment.
SEE ALSO
ifconfig(1M), netinit(1M), system(4), arp(6P), inet(6F), vme(7),
chk.devlink(1M), devlinktab(4M), intro(7).
Licensed material--property of copyright holder(s)