Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ vitr(7) — DG/UX 5.4R3.00

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

vme(7)

system(4)

intro(7)



vitr(7)                        DG/UX 5.4R3.00                        vitr(7)


NAME
       vitr - Vilya Token Ring Controller interface

SYNOPSIS
       vitr([vmebus,][configuration number])
       vitr@devicecode([vmebus,]VMEaddress[,tokenringaddress][,productid])

DESCRIPTION
       The vitr interface provides access to a Token Ring network through
       Data General's VME Token Ring Controller (VTRC).  To set up this
       interface, you include one or more vitr entries in the DG/UX system
       configuration file.

       The vitr entry has two formats (shown above and illustrated below).
       The first format accepts all defaults for a specified controller
       board.  The second format specifies all values:

       vmebus        The device name of the parent VME bus to which the
                      vitr controller is attached, such as vme(0) or vme(1).
                      If this parameter is omitted, a parent bus of vme(0)
                      is assumed, and all subsequent parameters move up one
                      position.  Thus, vitr(3) is equivalent to
                      vitr(vme(0),3).

       configurationnumber
                      A number from 0 to 7, or null for 0, identifying the
                      controller board defaults to use.

       @devicecode   The network controller device code, preceded by the @
                      character.

       VMEaddress    The VME address of the controller.

       tokenringaddress
                      An alternate Token Ring address to use instead of the
                      default one assigned to the controller.

       productid     An alternate product ID to use instead of the default
                      product ID of 0.  Additional information on the
                      product ID may be found in the IBM Token-Ring Network
                      Architecture Reference.

       The vitr device is implemented as a clonable Streams driver.  This
       means that you can open a single node, such as /dev/vitr0, 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
       In the following two examples, default values for the initial vitr
       are assumed.



Licensed material--property of copyright holder(s)                         1




vitr(7)                        DG/UX 5.4R3.00                        vitr(7)


            vitr()
            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 Token Ring address and product ID are used.

            vitr@42(E4004000)


       The next example uses the same values as the previous values, but an
       alternate Token Ring address of 0x08001b123456 is supplied.

            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.  For more information about DG/UX device configuration, refer
       to "Writing a Device Driver" in Programming in the DG/UX Kernel
       Environment.

       For a full discussion of device naming conventions and a list of
       board defaults, see Customizing the DG/UX System.

SEE ALSO
       vme(7), system(4), intro(7).


















Licensed material--property of copyright holder(s)                         2


Typewritten Software • bear@typewritten.org • Edmonds, WA 98026