Filter
Top Products
Hardware Release Notes
6.21 Recompiling and Relinking OpenVMS Device Drivers
Note that for OpenVMS Version 7.1 all OpenVMS VAX SCSI device drivers
required recompiling and relinking. OpenVMS VAX device drivers that were
recompiled and relinked to run on OpenVMS Version 7.1 will run correctly on
OpenVMS Version 7.3 or higher.
6.21.2 OpenVMS Alpha Device Drivers
V7.1
Device drivers that were recompiled and relinked to run on OpenVMS Alpha
Version 7.0 do not require source-code changes and do not have to be recompiled
and relinked to run on OpenVMS Alpha Version 7.1 and higher. (Note that
Alpha SCSI drivers, however, must be recompiled and relinked as described in
Section 6.21.1.)
Device drivers from releases prior to OpenVMS Alpha Version 7.0 that were not
recompiled and relinked for OpenVMS Alpha Version 7.0 must be recompiled and
relinked to run on OpenVMS Alpha Version 7.1 and higher.
OpenVMS Alpha Version 7.0 included significant changes to OpenVMS Alpha
privileged interfaces and data structures. As a result of these changes, device
drivers from releases prior to OpenVMS Alpha Version 7.0 may also require
source-code changes to run correctly on OpenVMS Alpha Version 7.0 and higher.
For more details about OpenVMS Alpha Version 7.0 changes that may require
source changes to customer-written drivers, refer to the HP OpenVMS Guide to
Upgrading Privileged-Code Applications.
6.22 Device Driver MON Version Handling
V7.3
As of OpenVMS Version 7.3, when SYSTEM_CHECK is enabled, device driver
images with names of the form SYS$nnDRIVER_MON.EXE will be automatically
loaded by the system loader. If a corresponding _MON version does not exist, the
system will use the default image name: SYS$nnDRIVER.EXE.
6.23 Possible Per-Threads Security Impact on Alpha Device Drivers
V7.2
See Section 5.10.7 for information about how possible per-thread security impacts
OpenVMS Alpha device drivers.
6.24 Device IPL Setup for OpenVMS Alpha Drivers
V6.2
Alpha hardware platforms that support PCI, EISA, and ISA buses deliver I/O
device interrupts at different IPLs, either 20 or 21. The IPL at which device
interrupts are delivered can change if you move the device from one platform to
another. This is a problem if the driver declares its device IPL to be 20, and then
that driver is executed on a machine that delivers I/O device interrupts at IPL
21.
The simplest solution to this problem is for PCI, EISA, and ISA device drivers to
use IPL 21. This works correctly on platforms that deliver I/O device interrupts
at IPL 20 and on platforms that deliver I/O device interrupts at IPL 21.
Hardware Release Notes 6–21