NAME

intro − introduction to special files and hardware support

DESCRIPTION

Intro(4) describes the special files, related driver functions, and networking support available in the system. In this part of the manual, the “Synopsis” section of each configurable device gives a sample specification for use in constructing a system description for the config(8) program. The “Diagnostics” section lists messages that may appear on the console and in the system-error log as a result of errors in device operation.

This section contains devices that may be configured into the system -- “4” entries -- as well as network-related information (“4N”, “4P” and “4F” entries).  The networking support is introduced in intro(4N).

IBM RT PC and IBM 6152 Academic System DEVICE SUPPORT

This section describes the hardware supported on the IBM RT PC and on the IBM 6152 Academic System.  Software support for the devices comes in two forms.  A hardware device can be supported with a character or block device driver, or it can be used within the networking subsystem and have a network interface driver. Block and character devices are accessed through files in the file system of a special type; compare with mknod(8). Network interfaces are indirectly accessed through the interprocess communication facilities provided by the system (see socket(2)).

A hardware device is identified to the system at configuration time and the appropriate device or network interface driver is then compiled into the system.  When the resultant system is booted, the autoconfiguration facilities in the system probe for the device and, if found, enable the software support for it.  If a device does not respond at autoconfiguration time, it is not accessible at any time thereafter.  To enable a device that did not autoconfigure, reboot the system. 

The autoconfiguration system is described in autoconf(4). A list of the supported devices is given below.

DEVICES

The devices listed below are supported under PRPQ #5799-CGZ for the IBM RT PC; they are indicated by their functional interfaces. 

asyMulti-port asynchronous communications RS232C interface
busControl of access to the system I/O bus
fdFloppy disk drive interface
hdPC/AT, ESDI, and EESDI hard disk interface
ibm5081IBM 5081 Display interface (mpel)
ibm5151IBM 5151 Monochrome Display interface (mono)
ibm5154IBM 5154 Enhanced Graphics Display interface (ega)
ibm6153IBM 6153 Advanced Monochrome Graphics Display interface (apa8)
ibm6154IBM 6154 Advanced Color Graphics Display interface (apa8c)
ibm6155IBM 6155 Extended Monochrome Graphics Display interface (apa16)
ibmaedIBM Academic Information Systems experimental display interface (aed)
lanIBM RT PC Token-Ring Adapter
lpLine printer interface
mouseMouse interface
pspPlanar serial port RS232 interface
scIBM 9332 disk unit using the IBM Small Computer System Interface (SCSI) Adapter
speakerConsole speaker interface
stStreaming tape interface
unIBM RT PC Baseband Adapter for use with Ethernet

The devices listed below are supported for the IBM 6152 Academic System; they are indicated by their functional interfaces. 

asyAsynchronous communications RS232C interface
fdFloppy disk drive interface
hdPC/AT hard disk interface
ibm8514IBM 8514/A Display interface
lpLine printer interface
mouseMouse interface
lanIBM Token-Ring Network PC Adapter
unUngermann-Bass 10Mb/s Ethernet interface
vgaPS/2 Display interface

The following emulators provide a unified way for several different (but
related) functions to communicate with the operating system kernel. These
functions provide operator input, display output, and console buffering.

aedemulGraphics interfaces for IBM Academic Information Systems experimental display
(for the IBM RT PC only)
bufemulKernel buffering emulator
ibmemulIBM 3101 emulator
kbdemulDefault keyboard emulator
stdemulStandard output emulator (for the IBM RT PC only)
xemulX input emulator for queuing keyboard and mouse events

SEE ALSO

autoconf(4), intro(4N), config(8)

PRPQs 5799-WZQ/5799-PFF: IBM/4.3  —  Dec 1987