vitr(7) DG/UX 5.4.2 vitr(7)
NAME
vitr - Vilya TokenRing Controller interface
SYNOPSIS
vitr()
vitr(configuration number)
vitr@devicecode(VMEaddress[,tokenringaddress][,productid])
DESCRIPTION
The vitr interface provides access to a Token Ring network through a
Data General's VME TokenRing Controller (VTRC).
To support this board in the DG/UX system kernel, you must specify
the name of the controller in the system configuration file. The
three formats of the vitr system file entry are as follows:
Default: vitr()
short format: vitr(configuration number)
long format: vitr@device code(VME address,[tokenring address],
[product id])
You most often will use the default format. If you choose to use
different values for the VME address, you must use the long format.
With the long format, vitr requires the device code and VME address
to configure properly. Use the second and third parameters in the
long format to provide an alternate token ring address and an
alternate product id. If the alternate token ring address or the
alternate product id is not specified, the default token ring address
assigned to the controller and the default product id 0 is used.
Additional information on token ring address and product id may be
found in the IBM Token-Ring Network Architecture Reference. For more
information concerning device configuration, refer to Writing a
Device Driver for the DG/UX System.
The default and shorthand versions of the system file entry derive
the device code and VME address from the table listed below.
Configuration number 0 is the default system file entry.
Config # Device Code VME Address
-------- ----------- -----------
0 40 0x61000000
1 41 0x61002000
2 42 0xE4004000
3 43 0xE4006000
4 44 0xE4008000
5 45 0xE400A000
6 46 0xE400C000
7 47 0xE400E000
EXAMPLES
In the following two examples, default values for the initial vitr
are assumed.
vitr()
Licensed material--property of copyright holder(s) 1
vitr(7) DG/UX 5.4.2 vitr(7)
vitr(0)
In the next example, default values for the second vitr are assumed.
vitr(1)
In the next example, the device code is 0x42, the VME address is
0xE4004000. The default board assigned token ring address and product
id 0 is used.
vitr@42(E4004000)
The next example uses the same values as the previous values, but the
alternate token ring address is 0x08001b123456.
vitr@42(E4004000,08001b123456)
The VME address must match the jumpering on the VTRC controller. See
the Configuring the VME Token Ring Controller(VTRC) for AViiON Series
Systems for details about setting the base VME address using switches
on the board.
If the vitr device is configured in the kernel, the node /dev/vitr0
is created at boot time.
If you specify more than one device of the same type in the system
configuration file, additional nodes are created with increasing
identifiers. For example, if there are two entries in the config
file for vitr devices, then /dev/vitr0 and /dev/vitr1 are created at
boot time. /dev/vitr0 refers to the first entry and /dev/vitr1
refers to the second entry in the configuration file.
SEE ALSO
system(4), intro(7).
Licensed material--property of copyright holder(s) 2