Technical data
Managing Peripheral Devices
8.5 Automatically Configuring Devices for OpenVMS Alpha Systems
The FLAGS keyword shows optional information about how to load the driver.
More than one flag may be specified, separated by a comma (,).
Example: FLAGS = NOVECTOR, CASE_BLIND, EXTENDED_ID, ISA_ON_
EISA
NOVECTOR Device has no interrupt vector.
CASE_BLIND Causes the ID to be treated as an ASCII string and converted to
uppercase. In addition, the ID from the hardware will also be
converted to uppercase before comparing. This flag is useful for
ISA device strings because the console ISACFG command will
not convert the HANDLE to uppercase. If this flag is specified,
the ID must be entered in the description as a string, and not
as a number, or an error will be displayed and the description
ignored.
EXTENDED_ID The flag is valid only for devices on the PCI bus. Normally, only
32-bit hardware IDs are used for PCI. If you have a PCI board
that supports the V2.1 PCI bus specification, set this flag. The
upper 32 bits of the hardware ID should contain the subsystem
ID and the subsystem vendor ID. For example, in the following
example, 1133 is the subsystem ID, and 10DF is the subsystem
vendor ID.
FLAGS = EXTENDED_ID
ID = 0x906D1OB5, 0 x 113310DF
If the EXTENDED_ID flag will be used to load a special driver,
but the same ID without the EXTENDED_ID bit will be defined
to load a generic driver, the description with the EXTENDED_
ID should be located before the generic description.
ISA_ON_EISA This flag is valid only when the value EISA is given to the
ADAPTER keyword, and the device is an ISA device. ISA
devices should set this flag to ensure that the value given
to the ID keyword is interpreted correctly. For ISA devices,
the system keeps the ID value as an ASCII string. When the
system believes that this is an EISA device, the ID value is
compressed into binary format.
• PRIVATE_DATA = string
This keyword is supported only when the value ISA is given to the ADAPTER
keyword. The statement may not span lines. If the string contains more than
one word, the string should be in quotes. The quotes are not passed as part
of the string. An ISA driver can retrieve this string by calling IOC$NODE_
DATA and passing the function code IOC$K_ISA_USER_PARAM.
• BEGIN_PRIVATE
This keyword is supported only when the value ISA is given to the ADAPTER
keyword. The BEGIN_PRIVATE and END_PRIVATE keywords can be used
instead of PRIVATE_DATA. They are not used as part of a PRIVATE_DATA
statement. When using BEGIN_PRIVATE and END_PRIVATE, all data
contained between the keywords is passed to the driver. The data may
contain special characters like quotation marks. The data may span multiple
lines. When multiple lines are used, the driver will find a line-feed character
to indicate a new line.
BEGIN_PRIVATE and END_PRIVATE must be used when trying to convert
some entries in ISA_CONFIG.DAT to file; for example, the statement in ISA_
CONFIG.DAT:
USER_PARAM = "some data"
Managing Peripheral Devices 8–15










