sdevice(F) 06 January 1993 sdevice(F) Name sdevice - local device configuration file Description Files in the directory /etc/conf/sdevice.d contain local system configu- ration information for each of the devices specified in the mdevice file. Each file contains one or more entries for a device specified in mde- vice(F). Every time a kernel is built using idbuild(ADM), these files are coalesced into the single file /etc/conf/cf.d/sdevice. 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'' indicat- ing 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 pseudo-device. In the case of serial devices, the value in this field selects an entry from the board configuration table (siosupbrds) in the file /etc/conf/pack.d/sio/space.c. Its value must be within the minimum and maximum values specified in fields 7 and 8 of the mdevice entry. 4. ``IPL'': the Interrupt Priority Level field specifies the System Priority Level (SPL) at which the driver's interrupt handler will run in the new system kernel. Legal values are 1 through 7. If the driver does not have an interrupt handling routine, put a 0 in this field. All of a driver's sdevice entries must specify the same IPL. 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 vector. 1 The device requires an interrupt vector. If the driver sup- ports more than one hardware controller, each controller requires a separate vector. 2 The device requires an interrupt vector. If the driver sup- ports more than one hardware controller, each controller will share the same vector. 3 The device requires an interrupt vector. If the driver sup- ports more than one hardware controller, each controller will share the same interrupt vector. Multiple device drivers hav- ing the same IPL can share this interrupt. 4 The device requires an interrupt vector. If the driver sup- ports more than one hardware controller, each of those control- lers may either share an interrupt vector with one of the other controllers or use a separate interrupt vector. Multiple de- vice drivers having the same IPL can share this interrupt. 5 The device requires an interrupt vector. If the device sup- ports more than one hardware controller, each controller will share the same interrupt. This interrupt type is only used by hard disk drivers to prevent other devices from sharing the same interrupt vector. 6. ``Vector'': this field contains the interrupt vector number used by the device. If the ``Type'' field contains a 0 (that is, no inter- rupt required), this field is ignored. Note that more than one de- vice can share an interrupt number provided that both devices are type 3, 4 or 5. 7. ``SIOA'': the Start I/O Address field contains the starting address on the I/O bus through which the device communicates. This field must be between 0x0 and 0xFFFF inclusive. (If this field is not used, it should be 0.) 8. ``EIOA'': the End I/O Address field contains the end address on the I/O bus through which the device communicates. This field must be within 0x0 and 0xFFFF inclusive. (If this field is not used, it should be 0.) The SIOA cannot be larger than the EIOA. 9. ``SCMA'': the Start Controller Memory Address field is used by con- trollers that have internal memory. It specifies the starting address of this memory. This field must be at least 0x10000. (If this field is not used, it should be 0.) 10. ``ECMA'': the End Controller Memory Address field specifies the end of the internal memory for the device. This field must be at least 0x1000. (If this field is not used, it should be 0.) The SCMA can- not be larger than the ECMA. See also idbuild(ADM), idinstall(ADM) and mdevice(F). Notes Some I/O Address ranges are reserved and cannot be used, including: _________________________________________________________________________ SIOA EIOA _________________________________________________________________________ 0x00 0x0F 0x20 0x21 0x40 0x43 0x63 0x63 0x70 0x7F 0x80 0x83 0xA0 0xA7