Porting drivers to DDI 8

Miscellaneous porting hints

Additional tips for people used to SCO OpenServer 5:

To enter single user mode, press <Enter> at the initial SCO logo screen during the boot process to get a boot prompt (boot#), the set the INITSTATE variable to 1:
```
   boot# INITSTATE=1
   boot# go
```
You will get a console login prompt in init state 1. Type ? or help at the boot prompt
kdb is the native SVR5 kernel debugger, but a version of the SCO OpenServer 5 scodb kernel debugger is also provided for SVR5. Both debuggers can be installed with the pkgadd command then configured into the system; kdb must be installed and configured before you can run scodb, but scodb is not required for kdb. If both debuggers are configured into the kernel, switch between them with the newdebug command.
For more information, see the following:
- ``Using crash and the kernel debuggers'' -- general information about using these tools.
- kdb for detailed information about using kdb.
- ``Using SCODB on SVR5'' -- detailed information about using scodb on SVR5
- ``SCO kdb and scodb quick reference'' -- quick reference listing for scodb on both platforms and for kdb.
Dynamically Loadable Kernel Modules (DLKMs) can be added to the kernel using the idinstall, idbuild, and modadmin commands. Most DLKMs can be installed with a command sequence such as the following, executed from the directory that contains the driver's DSP files:
```
   # cd <directory_containing_DSP>
   # /etc/conf/bin/idinstall -a -k -M <driver>
   # /etc/conf/bin/idbuild -M <driver>
   # modadmin -l <driver>
```
To unload the DLKM:
```
   # modadmin -U <driver>
```
To show all loaded DLKMs, run:
```
   # modadmin -S
```
All console messages that come from driver cmn_err(D3) calls are logged in the /usr/adm/log/osmlog file. When the system is rebooted, this file is saved as /usr/adm/log/osmlog.old file. See also syslogd.
Panic dumps can be saved to a file and analyzed with the crash command. See ``Using crash and the kernel debuggers'' for general information about using crash. ``SCO crash quick reference'' provides a quick reference listing of the crash commands that are supported on both platforms.
Note that you can write a module to extend the SVR5 crash command. For example, you could make it display structures that are defined just for your driver. See the crash manual page for more information.