Porting drivers to DDI 8

Porting SCO OpenServer 5 DSP files to SVR5

DDI drivers require a Drvmap(DSP/4dsp) file. See the sample drivers for examples.
DDI drivers require a Node(DSP/4dsp) file. See the sample drivers for examples. Note that SVR5 drivers must use decimal integer values for the ``user'' and ``group'' fields rather than user names such as root and user that are used for SCO OpenServer 5. Check the man page and sample drivers carefully for information about the proper DDI 8 format for this file.
The SCO OpenServer 5 mdevice(F) file includes a single line with nine fields. This line becomes the last uncommented line in a DDI Master(DSP/4dsp) file with the following disposition of these fields:

xnamex
Leave as is; this becomes the module-name field for a DDI driver.

funcs
Remove for DDI 8 drivers; translate this information to $entry lines above this line that define the named entry point routines for DDI drivers written for versions prior to version 8.

chars
This field is used for all DDI drivers, but the set of flags used varies significantly between DDI drivers and SCO OpenServer 5 drivers. Note that DDI 8 drivers only use a small number of characteristics; check the manual page listing for details.

prefix
Replace with a dash (--) for DDI 8 drivers.

bmajor
Remove for DDI 8 drivers.

cmajor
Remove for DDI 8 drivers.

minu
Remove.

maxu
Remove.

dma
Remove.

A DDI 8 driver's Master file must include lines such as the following above the line that is translated from the SCO OpenServer 5 mdevice file line. The drivers in these example use the multiprocessor version of DDI 8, ddi 8mp.
```
   $version 2
   $modtype Network Adapter
   $maxchan 4
   $interface ddi 8mp
   $interface mdi 2
   $contact My Company, Inc, full address
   $contact phone number
```
Note that DDI 8 does not use named entry points so these routine names are not declared in the Master file. Instead, the "basic" entry point routines are declared in a drvinfo(D4) structure. See ``Entry-point routines''.
If your driver is not multithreaded, specify ddi 8 instead of ddi 8mp. SCO strongly discourages using functionality that is not part of a versioned interface, but if that is necessary, see ``DDI interface versioning'' for information about how to code the Master file for a non-conforming driver.
Specify L, S, and c in the characteristics field to indicate a loadable STREAMS driver. This applies to all MDI drivers as well as pure STREAMS drivers and modules.
Some other Master fields are different for SVR5 than they are for SCO OpenServer 5; check the manual page carefully for all fields being used in your driver's Master file. The Master files in the sample source code directories illustrate the standard requirements for each type of driver.
Some modifications are required for the System(DSP/4dsp) file. Note especially that the IPL values for each interface type are different; see ``IPLs (Interrupt Priority Levels)''. System files for PCI devices must specify ITYPE=4.