Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

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

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

cied(7)

cimd(7)

vme(7)

dsk(7)

rdsk(7)



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


NAME
       cird - Ciprico Rimfire disk controller

SYNOPSIS
       cird([vmebus,][[def],[unitnumber]]) or
       cird@devicecode([vmebus,]VMEA16addr,unitnumber)

DESCRIPTION
       The cird disk subsystem family consists of the set of VME-based disk
       controllers which support the following units:

       Model #    Size
       ESDI 6442  327 Mbyte full-height non-removable disk
       ESDI 6661  330 Mbyte half-height non-removable disk
       ESDI 6555  648 Mbyte full-height non-removable disk
       SMD  6541  1066 Mbyte non-removable disk
       SMD  6542  1066 Mbyte non-removable disks (package of two)

       The cird 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
                      cird 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, cird(3) is equivalent to
                      cird(vme(0),3).

       def            A number from 0 to 3, or null for 0, identifying the
                      controller board defaults to use

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

       VMEA16addr   The VME A16 (short I/O) address of the controller

       unitnumber    The disk unit number (0 through 3) on the controller.

       A physical disk unit may be accessed directly via the special file
       nodes in /dev/pdsk and /dev/rpdsk.  These nodes are named according
       to the second device name form listed above.

       The cird subsystem has 4 built-in defaults for the device code and
       control space starting address of the cird device specification.
       When using the defaults, a short form of the cird device
       specification can be used:

           cird(controller number)

       where controller number is the hexadecimal number of the controller
       in the system.  For example, the first cird controller is cird(0),
       the second is cird(1), etc.




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




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


           Controller #    Device Code/VME Address

           cird(0)         0x18/0xFFFFEE00
           cird(1)         0x19/0xFFFFF100
           cird(2)         0x1A/0xFFFFFB00
           cird(3)         0x1B/0xFFFFFD00

       The nodes in /dev/pdsk provide access as a block special device as
       described in dsk(7).  The nodes in /dev/rpdsk provide access as a
       character special device as described in rdsk(7).  When accessing a
       disk through a /dev/pdsk or /dev/rpdsk node, the operating system
       performs no bad block remapping.

FILES
       /dev/pdsk/*

       /dev/rpdsk/*

SEE ALSO
       cied(7), cimd(7), vme(7), dsk(7), rdsk(7).





































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


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