Museum

Home

Lab Overview

Retrotechnology Articles

⇒ Online Manual

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

cird(7)

cied(7)

vme(7)

dsk(7)

rdsk(7)

vdm(7)

system(4)

intro(7)



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


NAME
       cimd - Ciprico VME SMD disk controller (88k only)

SYNOPSIS
       cimd(parent-bus[,controller-num[,unit-num]])  or
       cimd([controller-num[,unit-num]])

DESCRIPTION
       A cimd disk subsystem consists of a VME-based disk controller with up
       to 4 physical SMD (Storage Module Device) 8-inch 1066 megabyte units
       attached to it.  Two models are supported:  model 6541 (a single
       unit) and model 6542 (a package of two units).

       To configure such devices, you must add to the DG/UX system
       configuration file one or more device name entries of the forms
       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).  In the second form of the device name,
           this parameter is omitted, a parent bus of vme(0) is assumed, and
           all subsequent parameters move up one position.  Thus, cimd(3) is
           equivalent to cimd(vme(0),3).  Note that only the second device
           name form is accepted when specifying a boot command string to
           the AViiON SCM.

       ·   The controller-num parameter is a hexadecimal number in the range
           0 through 3 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 unit-num parameter is a hexadecimal number in the range 0
           through 3 which identifies the particular disk unit in question.
           The default value for unit-num is 0.  When specifying an SMD
           controller to be configured, this parameter is ignored, and all
           attached units on the controller are configured.

       Each cimd controller board contains two jumperable VME board address
       settings:  the interrupt vector number used by the board, and the A16
       address of the board's 16-bit control register space.  The following
       hexadecimal address values are used for the 4 standard controller-num
       instances supported by the device driver on each parent VME bus:

                   Controller  Interrupt   A16 Address
                   Number      Vector
                               Number

                   0           18          FFFFEE00
                   1           19          FFFFF100
                   2           1A          FFFFFB00
                   3           1B          FFFFFD00


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

           cimd@intr-vec-num(parent-bus,a16-addr[,unit-num])  or
           cimd@intr-vec-num(a16-addr[,unit-num])


       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 a16-addr parameter is the hexadecimal value of the VME A16
           address of the board's 16-bit control register space.  There is
           no default value for this parameter; it must always be specified
           explicitly.

       ·   The unit-num parameter has exactly the same meaning here as it
           does in the standard device name format.

FILES
       Each disk unit on a standard cimd controller creates a pair of device
       nodes when it is configured, with the pathnames:

           /dev/pdsk/cimd(parent-bus,controller-num,unit-num)
           /dev/rpdsk/cimd(parent-bus,controller-num,unit-num)


       The /dev/pdsk device node provides access as a block-special device
       as described in dsk(7).  The /dev/rpdsk device node provides access
       as a character-special device as described in dsk(7).  The cimd
       driver provides no bad block remapping for accesses to these device
       nodes.  See the vdm(7) man page for details on how to set up a bad-
       block remap area using the Virtual Disk Manager.

       The pathnames of the device nodes created for units on non-standard
       controller instances are:

           /dev/pdsk/cimd@intr-vec-num(parent-bus,a16-addr,unit-num)
           /dev/rpdsk/cimd@intr-vec-num(parent-bus,a16-addr,unit-num)


CAUTION
       The use of block 0 is reserved for the disk label.  Any attempt to
       use block 0 for any other purpose could render the disk useless until
       the label is reinstalled.

EXAMPLES
       The following entry in a DG/UX configuration file configures all disk
       units present on the third standard SMD controller on the first VME
       bus:

            cimd(vme(0),2)


       The following entry is a synonym for the example above:

            cimd(2)


       For more information about DG/UX device configuration, refer to
       "Writing a Device Driver" in Programming in the DG/UX Kernel
       Environment.

SEE ALSO
       cird(7), cied(7), vme(7), dsk(7), rdsk(7), vdm(7), system(4),
       intro(7).


Licensed material--property of copyright holder(s)

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