Museum

Home

Lab Overview

Retrotechnology Articles

⇒ Online Manual

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

ifconfig(1M)

netinit(1M)

system(4)

arp(6P)

inet(6F)

vme(7)

chk.devlink(1M)

devlinktab(4M)

intro(7)



cien(7)                        DG/UX R4.11MU05                       cien(7)


NAME
       cien - CMC-130 VME Ethernet network controller  (88K only)

SYNOPSIS
       cien(parent-bus[,controller-num[,,alt-ether-addr]])

DESCRIPTION
       The cien device driver allows an AViiON system that includes an
       intelligent VMEbus local area network (LAN) controller (VLCi) to
       access an Ethernet 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 third parameter position is unused, and is reserved for
           reasons of backward compatibility.

       ·   The alt-ether-addr parameter can be used to override the
           controller's default Ethernet address with a user-specified
           value, which must be represented as a string of exactly 12
           hexadecimal digits.  If no alt-ether-addr parameter is specified,
           the controller-resident default Ethernet address is used.

       The Internet address for each interface is specified at network
       configuration time with the SIOCSIFADDR ioctl; see ifconfig(1M) for
       details.

       Each cien 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           48          E1800000
                   1           49          E1900000
                   2           4A          E1A00000
                   3           4B          E1B00000
                   4           4C          E1C00000
                   5           4D          E1D00000
                   6           4E          E1E00000
                   7           4F          E1F00000


       A cien 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:

           cien@intr-vec-num(parent-bus,a32-addr[,,alt-ether-addr])


       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 third parameter position is unused, and is reserved for
           reasons of backward compatibility.

       ·   The alt-ether-addr parameter has exactly the same meaning here as
           it does in the standard device name format.

FILES
       Each standard cien device creates a single character-special device
       node when it is configured, with the pathname:

           /dev/net/cien(parent-bus,controller-num)


       The pathname of the device node created for non-standard device
       instances is:

           /dev/net/cien@intr-vec-num(parent-bus,a32-addr)


       The chk.devlink command is responsible for creating and maintaining
       an additional link to each cien device node, with a pathname of the
       form /dev/net/cien[0-9]*.  See the chk.devlink(1M) and devlinktab(4M)
       man pages for details.

       The cien device driver is a clonable Streams driver.  This means that
       you can open a single cien 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 VLCi
       controllers that use two of the standard sets of addressing values,
       and which use their on-board default Ethernet addresses:

            cien(vme(1),0)
            cien(vme(0),4)


       The following statement configures a VLCi controller using the
       address settings for controller number 0, but specifies an alternate
       Ethernet address:

            cien(vme(0),0,,08001b123456)


       The following statement configures a non-standard VLCi controller
       which uses interrupt vector number 0x4F and VME A32 address
       0xE1A00000, but which accepts the default Ethernet address:

            cien@4F(vme(0),E1A00000)


       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)

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