sdevice(4) UNIX System V sdevice(4)
NAME
sdevice - file format.
SYNOPSIS
sdevice
DESCRIPTION
The sdevice file contains local system configuration information for each
of the devices specified in the mdevice file. It contains one or more
entries for each device specified in mdevice. sdevice is present in the
directory /etc/conf/cf.d, and is coalesced from component files in the
directory /etc/conf/sdevice.d. Files in /etc/conf/sdevice.d are the
System file components either delivered with the base system or installed
later via idinstall.
Each entry must contain the following whitespace-separated fields:
1. Device name: This field contains the internal name of the driver.
This must match one of the names in the first field of an mdevice
file entry.
2. Configure: This field must contain the character 'Y' indicating
that the device is to be installed in the Kernel. For testing
purposes, an 'N' may be entered indicating that the device will not
be installed.
3. Unit: This field can be encoded with a device dependent numeric
value. It is usually used to represent the number of subdevices on
a controller or psuedo-device. Its value must be within the minimum
and maximum values specified in fields 7 and 8 of the mdevice entry.
4. Ipl: The ipl field specifies the system ipl level at which the
driver's interrupt handler will run in the new system kernel. Legal
values are 0 through 8. If the driver doesn't have an interrupt
handling routine, put a 0 in this field.
5. Type: This field indicates the type of interrupt scheme required by
the device. The permissible values are:
0 - The device does not require an interrupt line.
1 - The device requires an interrupt line.
If the driver supports more than one hardware controller,
each controller requires a separate interrupt.
2 - The device requires an interrupt line.
If the driver supports more than one hardware controller,
each controller will share the same interrupt.
3 - The device requires an interrupt line.
If the driver supports more than one hardware controller,
each controller will share the same interrupt. Multiple
10/89 Page 1
sdevice(4) UNIX System V sdevice(4)
device drivers having the same ipl level can share this
interrupt.
6. Vector: This field contains the interrupt vector number used by the
device. If the Type field contains a 0 (i.e. no interrupt
required), this field should be encoded with a 0. Note that more
than one device can share an interrupt number.
7. SIOA: The SIOA field (Start I/O Address) contains the starting
address on the I/O bus through which the device communicates. This
field must be within 0x1 and 0xFFFE. (If this field is not used, it
should be encoded with the value zero.)
8. EIOA: The field (End I/O Address) contains the end address on the
I/O bus through which the device communicates. This field must be
greater than the value specified in the seventh field and no greater
than 0XFFFF. (If this field is not used, it should be encoded with
the value zero.)
9. SCMA: The SCMA field (Start Controller Memory Address) is used by
controllers that have internal memory. It specifies the starting
address of this memory. The start address is 0X10000. (If this
field is not used, it should be encoded with the value zero.)
10. ECMA: The ECMA (End Controller Memory Address) specifies the end of
the internal memory for the device. Its value must be greater than
the value of the eighth field. (If this field is not used, it
should be encoded with the value zero.)
SEE ALSO
mdevice(4).
idinstall(1m) in the System Administrator's Reference Manual.
Page 2 10/89